Currently, tycho expands versions in manifest.mf/feature.xml/site.xml
during every build. Expanded version is calculated by build-qualifier
mojo. By default build-qualifier mojo will use current date to calculate
the qualifier, but this can be overridden either on command line or in
pom.xml.
Even though I have not thought much about release process, I think it
should be possible to achieve what you need using maven profiles and
build-qualifier configuration using something like this
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.codehaus.tycho</groupId>
<artifactId>maven-osgi-packaging-plugin</artifactId>
<configuration>
<forceContextQualifier>xxxx</forceContextQualifier>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
or you can use -DforceContextQualifier=xxxx on command line.
If I am not mistaken, in maven version 1.0.0 is considered newer than
1.0.0-SNAPSHOT while in eclipse 1.0.0 is actually older than
1.0.0.qualifier. This means that you will most likely need to set
version to something like 1.0.0.20081031 both in pom.xml and force it to
manifest.mf/feature.xml/site.xml using build-qualifier mojo configuration.
This is not very well thought through (just made this all up, to be
honest), so I will be more than happy to discuss/implement alternative
solutions.
--
Regards,
Igor
PascalLeclercq wrote:
Hi,
we aim to use Tycho in manifest-first mode.
My question is about version synchronisation between pom.xml and
manifest.MF.
Is the version in the manifest file being modified when we "release" the
artifact ?
If not what can we do to synchronize it and do you plan to do deliver this
functionnality.
This is quite an issue for us.
Thank in advance.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
