Pierre-Arnaud Marcelot schrieb: > 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 ?
The only one I could see is getting the Bundle-ClassPath updated by maven instead of doing it manually when a version of a referenced jar in the Bundle-ClassPath is changed in the root pom.xml. But I haven't known about the this feature of eclipse. So there is no need to do it. Thanks for spotting. Felix > > 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] > <mailto:[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 >
