Pierre-Arnaud Marcelot schrieb: > I've managed to update all our "code" plugins: > > * aciitemeditor > * apacheds > * apacheds-configuration > * connection-core > * connectio-ui > * ldapbrowser-common > * ldapbrowser-core > * ldapbrowser-ui > * ldif-parser > * ldifeditor > * rcp > * schemaeditor > * valueeditors > > Everything is working fine. > > I'm now going on to the help plugins but I can't get the > "bundle:manifest" goal to be run by the Studio plugin. > Do you have any idea, Felix ?
It's only run if the studio-plugin is configured in the specific pom and <skip> is set to false. Maybe we need to to have a another property in the studio-plugin (like skip) for the execution of the bundle:manifest. It looks like none of the *help poms has a studio-plugin configured. I think adding a new property to execute the bundle:manifest will solve the problem. So we'll have skip=true and the genmanifest=true if only the bundle:manifest part shall be done. Shall I have a look on this? HTH Felix > > Thanks, > Pierre-Arnaud > > On Tue, Sep 23, 2008 at 4:54 PM, Pierre-Arnaud Marcelot <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hi all, > > [WARNING] > I'm in the process of removing the MANIFEST.MF files from SVN and > replace them by generated ones. > This, and the modifications we've been doing with Felix on the Maven > Studio plugin, may have a huge impact on the build until everything > has been migrated. > > Don't be surprised if you get a build error from time to time, or if > the generated RCP application does not work... > [/WARNING] > > Just wanted to warn everybody. ;) > > Regards, > Pierre-Arnaud > > On Tue, Sep 23, 2008 at 2:15 PM, Pierre-Arnaud Marcelot > <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > > On Tue, Sep 23, 2008 at 2:07 PM, Felix Knecht <[EMAIL PROTECTED] > <mailto:[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 > > >
