directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot">
Subject Re: svn commit: r617101 - in /directory/studio/branches/studio-maven: apacheds-configuration-feature/META-INF/ apacheds-configuration/META-INF/ connection-core/META-INF/ connection-ui/META-INF/ jars/META-INF/ ldapbrowser-common/META-INF/ ldapbrowser-
Date Thu, 31 Jan 2008 12:24:44 GMT
You're totally right...

I was getting strange behavior with the studio:eclipse command. Version
numbers were not referring the version I put in the root pom.xm file. So I
put them by hand in the Manifest.MF files.

I finally found that this was because of version number of the pom parent
which was still using the one from you sandbox.

This is fixed now.


On Jan 31, 2008 12:04 PM, Felix Knecht <> wrote:

> IMO Bundle-Version should be updated when running mvn eclipse:eclipse
> studio:eclipse with the version number from the pom (or the one set as
> property in the root pom). Also the Bundle-Classpath should be updated
> when running this command.
> Regards
> Felix
> > URL:
> > Log:
> > Fixed Features recognition. Updated Manifests with correct version
> numbers..
> >
> >

View raw message