gvSIG bugs #318

Add dummy pom files for some dependencies in the gvSIG repository

Added by Cesar Ordiñana over 12 years ago. Updated almost 12 years ago.

Status:Closed% Done:

100%

Priority:NormalSpent time:-
Assignee:Cesar Ordiñana
Category:-
Target version:2.0.0-alpha5
Severity: Add-on version:
gvSIG version:2.0.0 Add-on build:
gvSIG build:2045 Add-on resolve version:
Operative System: Add-on resolve build:
Keywords: Proyecto:
Has patch:No Hito:
Add-on name:Unknown

Description

There are some dependencies in the gvSIG repository that don't have a pom.xml file, only the jar file.

Those are dependencies not available in the maven central repository, that were uploaded to our repository, but only de jar file.

This way, in every compilation, maven tries to download their pom.xml file. As it doesn't exist, it keeps trying to download them each time, making a slower build process and putting more burden in the used maven repositories.

The list of dependencies to create a pom.xml for is:

org.jzkit:jzkit2-core:pom:2.0.0
org.jzkit:jzkit2-z3950:pom:2.0.0
org.jzkit:jzkit2-origin:pom:2.0.0
org.jzkit:a2j-runtime:pom:2.0.9
org.jzkit:a2j:pom:2.0.9
net.swing:amic-util:pom:unknown

History

#1 Updated by Cesar Ordiñana over 12 years ago

  • Status changed from New to In progress
  • Assignee set to Cesar Ordiñana

I'm going to try to solve this bug as otherwise the eclipse m2eclipse plugin complains in some cases and shows annoying errors. Also any maven operation tries each time to download those poms, so the compilation process becomes slower.

#2 Updated by Cesar Ordiñana over 12 years ago

  • Status changed from In progress to Fixed
  • Target version set to 2.0.0-alpha5
  • % Done changed from 0 to 100
  • gvSIG build changed from 2044 to 2045

I have re-deployed the jar files through maven, so the default pom file has been created for them.

#3 Updated by Joaquín del Cerro Murciano almost 12 years ago

  • Status changed from Fixed to Closed

Also available in: Atom PDF