directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot">
Subject Re: Buildsystem studio
Date Mon, 22 Oct 2007 08:39:48 GMT
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

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... :'( ) ?


PS: As you're starting to have something working, maybe it could be
interesting that we create in a sandbox a branch for Maven build of Studio.
It could help us work together on this.
What do you think guys ?
If I create a branch in my sandox (/directory/sandbox/pamarcelot/trunks),
will Felix be allowed to commit in it ?

On 10/22/07, Felix Knecht <> wrote:
> Pierre-Arnaud Marcelot schrieb:
> > Hi Felix,
> >
> > On 10/22/07, *Felix Knecht* <
> > <>> wrote:
> >
> >     For the moment I'm stating 2 problems I haven't found a solution
> >     for and
> >     where I think it make sense to write an own plugin:
> >
> >     - Adapting the <Bundle-Classpath> in Manifest files
> >     <configuration>
> >       <classpath>., ...</classpath>
> >       <artifactItems>
> >         <artifact>
> >           <groupId></groupId>
> >           <artifactId></artifactId>
> >         </artifact>
> >         ....
> >       </artifactItems>
> >     </configuration>
> >
> >
> > Does this mean you want to get rid of the META-INF folder and the
> > MANIFEST.MF file in SVN and replace it by one generated by Maven when
> > creating the jar of the plugin ?
> > In this case, it could be a problem, as when we develop the plugins,
> > we usually launch our plugins within eclipse (the green arrow "Run"
> > button) for testing and debugging.
> > To be able to do that, Eclipse bundles the plugins (only the opened
> > projects) in it workspace and launches a new instance of itself with
> > the plugin under development loaded.
> > A part of this mechanism is based on this MANIFEST.MF file which
> > stores the name and id of the plugins and their classpathes.
> > Are you sure that automating the generation of such file(s) will not
> > corrupt this functionality, which we really use every day and is
> > really a must-have.
> No, I'm absolutely not sure, thanks for the hint.
> It'll probably not work when MANIFEST.MF is create automatically,
> because it would exist only after a maven build within the generated
> jar. Therefore Eclipse wouldn't know about the MANIFEST.MF.
> I don't think that it makes sense to automate MANIFEST creation automated.
> Felix

View raw message