Hmm... I think this can be fixed by providing those artifacts in a
snapshot repository so maven can download them.
Emmanuel Lecharny wrote:
Hi all,
it's actually impossible to build Apache Directory Server project just
after a svn co, with a clean maven repo (like a new user will do), for
some (unknown) reason, maven is looking for a missing plugin, which
will always miss, because this plugin is generated later :) (kind of
chicken/egg pb, isn't it ;)
This is sad, because to be able to build the project, a new user must
go through a tough path (like building MINA, then shared, then
apacheds/sar-plugin, then apacheds ...)
Is somebody can figure out why maven tries to download this missing
plugin *before* doing anything else, even if modules are described in
an order which has been selected to avoid such a burden ?
Any help wecome !!!
Emmanuel
PS : for those who want to experiment such a problem, it's easy : just
svn co
http://svn.apache.org/repos/asf/directory/branches/apacheds/1.0-trunks/
and type mvn install after having removed ~/.m2/repository
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
