directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot" ...@marcelot.net>
Subject Re: Buildsystem studio
Date Mon, 22 Oct 2007 08:59:50 GMT
Ok, then it's not an issue... :)

We need to run "$ ant resolve" to get  the dependencies right now, so it's
not really a problem. As long as it is in the documentation on how to build
the trunk, then I think it's ok.

Thanks,
P-A

On 10/22/07, Felix Knecht <felixk@apache.org> wrote:
>
> Pierre-Arnaud Marcelot schrieb:
> > Ok, thanks Felix.
> >
> > I'm also realizing there could be another problem with the jar
> > dependencies.
> > I know that usualy (that's what is done in ApacheDS projects) jar
> > dependencies declared in Maven are linked in Eclipse using the M2_REPO
> > location (basically '~/.m2/repository') in the classpath properties of
> > a project.
> >
> > Here (in Studio), we really need the dependencies to be copied in the
> > a 'lib' folder because:
> > - they need to be bundled in the jar of the plugin to work
> > - Eclipse needs them when bundling the plugin to launch it for testing
> > and debugging (same situation as the MANIFEST.MF file).
> >
> > Do you think this is possible to have such a behavior for dependencies
> > in Maven (I'm really not a Maven expert... :'( ) ?
>
> Yes, this can be done - but you would need to run once maven to have
> them there. This could be done havind a specific profile. After a new
> svn checkout of a project you'll need to run e.g.
> $ mvn install -Pprepare-for-eclipse to have all the needed jar files
> copied to ${module}/lib.
>
> Felix
>

Mime
View raw message