|
Ok,
I think we will go for the second approach then :)
Thx again for the help provided,
Tony
Le 10/04/2014 11:15, Igor Fedorenko a écrit :
There
are two approaches that I know work.
One is to keep all versions the same and let tycho auto-generate
it
during each build, like we do in m2e, for example. It is also
possible
to manually version "release" builds, but personally I don't find
this
useful.
Another approach is to let tycho auto-generate version for each
plugin
individually based on scm commit timestamp, like this is done
during
Eclipse Platform build.
--
Regards,
Igor
On 2014-04-10, 10:53, Tony HEDOUX wrote:
Ok, I understand the main principle.
What is the general way to manage the plugin version number
then? Keep
the same version number for all of them in a product?
Thx for help,
Tony
Le 09/04/2014 17:11, Jeff MAURY a écrit :
I don't think so as this is a
recommanded practive in the Maven
community following the DRY principle.
Jeff
On Wed, Apr 9, 2014 at 4:12 PM, Tony HEDOUX
<tony.hedoux@xxxxxxxxxxx
<mailto:tony.hedoux@xxxxxxxxxxx>> wrote:
Hi,
I have an eclipse project with a basic structure :
parent
|--- child A
|--- child B
|--- child C
|--- child D
I would like to update the parent version with the Tycho
version
plugin :
/mvn
org.eclipse.tycho:tycho-versions-plugin:0.20.0:set-version
-DnewVersion=.....
/
But there is a side effect I want to avoid on children
poms : if
the version of pom is the same than the parent one, the
version is
removed.
This is a problem : In fact, at the next call to the Tycho
version
plugin, my children pom will be updated (with theirs
manifests),
even if I basically don't want to update their version
number.
There is a way to keep explicit the parent version number
in
children pom, even if they are identical?
Thx for help,
Tony
--
*Tony HEDOUX*
/Software Engineer/
Mail : toh@xxxxxxxxxxx <mailto:toh@xxxxxxxxxxx>
------------------------------------------------------------------------
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex -
FRANCE
www.all4tec.net <http://www.all4tec.net>
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
<mailto:tycho-user@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by
actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
*Tony HEDOUX*
/Software Engineer/
Mail : toh@xxxxxxxxxxx
------------------------------------------------------------------------
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net <http://www.all4tec.net>
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
|
