| Re: [tm-dev] tycho-versions-plugin |
|
Dear TM Committers, After some more investigations, we found that adding the tycho-versions-plugin to our build would not give us any significant benefit. The build fails today when the MANIFEST.MF and pom.xml differ: Just fails with the error like "Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.eclipse.tm:org.eclipse.rse.files.ui:jar:3.2.101-SNAPSHOT",
here is an example: https://hudson.eclipse.org/hudson/job/tm-master-nightly/889/console Having the tycho-versions-plugin, it would just fail for other reasons. The point is, that people need to take care of the build error notifications.
If you submit your changes via Gerrit, you’ll get that build verification for free – since Gerrit will veto your change when it doesn’t build. Submitting through Gerrit is actually no harder than committing directly, and some projects actually REQUIRE all changes to go through Gerrit.
Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 From: tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx]
On Behalf Of Anna Dushistova Hi Martin, Would you happen to know any project that has it as a part of their build? It will sure help to look at the working example. Thanks! Anna.
On Tue, May 7, 2013 at 8:13 PM, Oberhuber, Martin <Martin.Oberhuber@xxxxxxxxxxxxx> wrote:
Hi Committers,
As just discussed on the committer call, related to keeping versions of MANIFEST.MF and POM.XML in sync:
This is the bug which discusses automating this – and the comment references the tycho-versions-plugin which can at least _check_ for inconsistencies during the build. It should be added to the TM build if it’s not in there already:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=387802#c1
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct
+43.662.457915.85 fax
+43.662.457915.6
|