2011/5/9 Thomas Heute <theute@redhat.com>
On 05/09/2011 11:08 AM, Arnaud Héritier wrote:
I remember this old bug but I didn't remember it was existing again in 2.2.1
Are you using a mirror in your maven settings ??

Nope.


Even if it is optional you should do it like it was described by Paul in this doc : http://community.jboss.org/wiki/MavenGettingStarted-Developers
This may avoid you to discover too lately that some dependencies are missing in Jboss repositories.
And it should greatly increase your maven performances by using only this repository

 

I remember that it was a workaround when we were waiting for the fix.

Ok, for now I imported the gatein-dep versions manually

ok
 

It is almost sure that if the bug always exists in 2.2.1 it won't never
be solved in this branch

Yep, that's what I fear :)

Yes :(
 

Thanks for the info,
Thomas




Arnaud Héritier
eXo - Software Factory Manager
aheritier@exoplatform.com <mailto:aheritier@exoplatform.com>




On Mon, May 9, 2011 at 11:02 AM, Thomas Heute <theute@redhat.com
<mailto:theute@redhat.com>> wrote:



   I can't build trunk with Maven 2.2.1 (which was the version of Maven we
   'standardized' on).

   There is a bug in that version of Maven and the way it manages
   dependencies on scope:import the consequence is that it cannot find
   gatein-dep 1.1.0 Beta02 which is a dependency currently used by at least
   one of the components. (See http://jira.codehaus.org/browse/MNG-3553)

   I'm ok to 'standardize' on Maven 3 if that helps (It will help for that
   issue)

   Thomas.

   _______________________________________________
   gatein-dev mailing list
   gatein-dev@lists.jboss.org <mailto:gatein-dev@lists.jboss.org>

   https://lists.jboss.org/mailman/listinfo/gatein-dev




--
Thomas Heute
Technical Development Manager | JBoss Enterprise Platform & GateIn
+41 32 720 9266 | Switzerland
Twitter: http://twitter.com/theute
EPP Blog: http://jboss-epp.professional-blog.com