Ok I see, something like the eclipse:eclipse task (which creates the .project and .classpath)...
But, the fact is we use Eclipse editors [1][2] to edit this MANIFEST.MF file as well as the plugin.xml file. So I don't know if it's really an advantage to have it generated by Maven... Is there any advantage we could have from using a Maven generated MANIFEST.MF file ? Regards, P-A [1] http://www.ibm.com/developerworks/cn/aix/library/au-fiteclipse2/AddPluginDependency.jpg- The "Required Plugins" are represented in the MANIFEST.MF file by the 'Require-Bundle' property. [2] http://cs.unibg.it/gargantini/didattica/eclipse/libs_runtime.png - The "Classpath" is represented in the the MANIFEST.MF file as by the 'Bundle-ClassPath' property. On 10/26/07, Felix Knecht <[EMAIL PROTECTED] > wrote: > > From my POV it would be nice, if this can be done as well for the > MANIFEST.MF . > I'd like to get rid of adapting versions of dependencies in the > Bundle-Classpath. I could imagine having a task in a maven-studio-plugin > writing the MANIFEST.MF in the same manor as done for the lib directory. > The configuration for the MANIFEST.MF will stay in pom.xml where we can > also reference to dependencies. > > WDYT? > > Felix > > > Pierre-Arnaud Marcelot schrieb: > > 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* <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> 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 > > > > > >
