Hi guys, I'm still trying to get the release plugin working.
We've made great improvements with the generation of the MANIFEST.MF files. However I'm still having a problem when using the release plugin. Our test-integration-* projects use Apache DS 1.5.5-SNAPSHOT dependencies which becomes 1.5.5 dependencies when using the release plugin which makes the build fail because Apache DS 1.5.5 is not there yet. This is plain normal. I was wondering if it is possible for us to use the released Apache DS 1.5.4 dependencies instead of the 1.5.5-SNAPSHOT ones? Stefan, any thoughts ? I think this is the last issue we'll be having to make the release plugin work. The generated jars look fine. Thanks, Pierre-Arnaud On Tue, Sep 23, 2008 at 2:15 PM, Pierre-Arnaud Marcelot <[EMAIL PROTECTED]>wrote: > On Tue, Sep 23, 2008 at 2:07 PM, Felix Knecht <[EMAIL PROTECTED]> wrote: > >> If we manage to get the eclipse:eclipse forked this shouldn't be a >> problem anymore. > > > Yeah, as we're running a command line, instead of just running 'mvn > eclipse:eclipse', we could be running 'mvn eclipe:eclipse bundle:manifest'. > > We then also should think about adding the manifest >> goal to the release plugin definition (meaning clone the one from the >> TLP pom and add the manifest goal) to make sure that the latest uptodate >> manifest is in the release. > > > I don't think it's necessary, because it will still be defined in the > pom.xml file of the project and the file won't be in SVN anymore... So the > generated manifest will contain up-to-date informations about the version, > dependencies versions etc. > > >> ATM I try to get the eclipse:eclipse forked stuff running. > > > Thanks! > > Regards, > Pierre-Arnaud > >
