| Re: [kura-dev] Troubles re-building Kura 3.1 |
Hi,
We noticed that too but unfortunately too late.
The reason we added the exist-maven-plugin was to protect the Kura build from itself ;-)
It has to do with the way we used to version the Kura plugins which might lead to attempt redeploying the same version of the artifact to Nexus.
Before adding the plugin we had to manually check all the versions against those deployed to Nexus. A tedious and error prone process.
This in turn has to do with the Kura incremental upgrades where we could ship an upgrade containing only the differences since the last release.
It turns out that these ideas are very difficult to manage and complicate the build process.
Reviewing the build is a topic for the next Kura release.
To rebuild Kura from the KURA_3.1.0_RELEASE tag it’s enough to comment out the plugin from the poms.
We will document it or we will make a fix and create a new tag.
Regards,
Cristiano
From: <kura-dev-bounces@xxxxxxxxxxx> on behalf of Jens Reimann <jreimann@xxxxxxxxxx>
Reply-To: Kura Developers mailing list <kura-dev@xxxxxxxxxxx>
Date: Monday, October 16, 2017 at 17:31
To: Kura Developers mailing list <kura-dev@xxxxxxxxxxx>
Subject: [kura-dev] Troubles re-building Kura 3.1
Hi,
I just tried to rebuild the Kura 3.1 release and found out that this isn't possible anymore.
----
[INFO] ------------------------------------------------------------ ------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------ ------------
[INFO] Total time: 25.772 s
[INFO] Finished at: 2017-10-16T15:15:45+00:00
[INFO] Final Memory: 24M/397M
[INFO] ------------------------------------------------------------ ------------
[ERROR] Failed to execute goal org.honton.chas:exists-maven-plugin:0.0.3:remote (default) on project target-platform: Artifact already exists in repository: org.eclipse.kura:target- platform:3.1.0/target- platform-3.1.0.pom -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ MojoExecutionException
----Looking at the configuration it seems that Kura actively checks if "out there" exists Kura 3.1 and then simply fails the build:
----
<groupId>org.honton.chas</groupId>
<artifactId>exists-maven-plugin</artifactId>
----Which effectively makes it impossible to simply re-build Kura from scratch. Or did I get this wrong maybe?
So unless I got it wrong, I would like to understand why an open source project takes those measures and how to work around them?
Thanks for your help
Jens
--Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
____________________________________________________________ _________________
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill
_______________________________________________
kura-dev mailing list
kura-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kura-dev