[jboss-dev-forums] [Design of JBoss Build System] - Re: Can't do a release because of bogus dependency issue

[pgier]

"adrian at jboss.org" wrote : "pgier" wrote : I deployed a patched maven jar plugin here:
  |   | http://repository.jboss.com/maven2/org/apache/maven/plugins/maven-jar-plugin/2.1-jboss-1/
  |   | And I updated the jboss kernel pom to use this version.  That should resolve the dependency issue.
  |   | 
  | 
  | This hasn't fixed the problem.
  | 
  | The maven-metadata is saying to use the 2.1 release, even
  | though there is also a 2.2 release in our repository as well?
  | http://repository.jboss.com/maven2/org/apache/maven/plugins/maven-jar-plugin/maven-metadata.xml

Looks like the metadata there is incorrect.  Whoever added 2.2 must not have updated it.  You should be able to use the 2.2 version now since it includes the fix that was in 2.1-jboss-1.  Can you set it to 2.2 in your pom?

The next version of the jboss-parent is going to have set versions for all the plugins (which you can still override).  So hopefully we won't have to rely on the metadata.



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138329#4138329

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138329