| Re: [cf-dev] Greetings from Paho! A question about your Maven Build. |
| Kind regards,
James Sutton Software Engineer - IoT Foundation - MQTT Open Source Projects Technical Trojan - Wimbledon Project |
| | ||
| Phone: 01962 815438 | Extension: x372454 E-mail: james.sutton@xxxxxxxxxx Personal Website: www.jsutton.co.uk Find me on: | Hursley Park Hursley, SO212JN United Kingdom | |
----- Original message -----
From: "Hudalla Kai (INST/ESY)" <Kai.Hudalla@xxxxxxxxxxxx>
Sent by: cf-dev-bounces@xxxxxxxxxxx
To: "Californium (Cf) developer discussions" <cf-dev@xxxxxxxxxxx>
Cc:
Subject: Re: [cf-dev] Greetings from Paho! A question about your Maven Build.
Date: Thu, Nov 12, 2015 8:59 AM
Hi James,
of course we'll help you get this thing going :-) Since I know how much effort it was to obtain the necessary knowledge to get it up and running, I am glad to share it with you.
From what I can see from the log, you are also using the Nexus Staging Maven Plugin, i.e. you have configured in in your top level pom.xml as a build plugin, right?
If this is true the first problem seems to be that you are deploying a SNAPSHOT version. The Nexus Staging plugin by default only deploys release (non-SNAPSHOT) versions to the OSSRH staging repo.
You should take a look at the plugin documentation on GitHub [1] in order to get a better understanding of the configuration options that influence that plugin's behavior.
In our Californium release build we first set the project version to the release version before we run mvn deploy because we only want our releases (non-SNAPSHOTs) to show up in Maven Central. We deploy our SNAPSHOTs to Eclipse repo only ...
I am not sure if the Nexus Staging Maven Plugin actually supports deployment of SNAPSHOTs to the OSSRH repo in one shot because operating mode "Staging" is only used for non-SNAPSHOT versions as described in [1].
However, my understanding is that you could use a two shot staging workflow [2] in which you first build the SNAPSHOT version and have it being staged locally only, i.e. all artifacts are put to the target/nexus-local folder, by invoking mvn deploy
and then, in a second step, use mvn nexus:deploy-staged to transfer these locally stage artifacts to the remote staging repo at OSSRH. However, I do not know whether the second step will always deploy to the remote OSSRH staging repo or will also do this only for non-SNAPSHOT versions... you will need to find this out by experiment.
Feel free to get back in touch if you need further help ...
[1] https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
[2] https://github.com/sonatype/nexus-maven-plugins/blob/master/staging/maven-plugin/WORKFLOWS.md
Regards,
Kai
________________________________________
Von: cf-dev-bounces@xxxxxxxxxxx [cf-dev-bounces@xxxxxxxxxxx]" im Auftrag von "James Sutton1 [james.sutton@xxxxxxxxxx]
Gesendet: Mittwoch, 11. November 2015 15:37
An: cf-dev@xxxxxxxxxxx
Betreff: [cf-dev] Greetings from Paho! A question about your Maven Build.
Hi Californium devs!
I'm a contributor on Paho and am currently trying to get our Java build to publish artifacts to the OSSRH as well as the Eclipse nexus. I've tried to follow what you have done on your own build but can't seem to get it to publish to OSSRH at all.
Mikael has set us up a "Deploy to repo.eclipse.org + OSSRH" settings in our HIPP instance and has created a signing key too. (https://bugs.eclipse.org/bugs/show_bug.cgi?id=479549)
I've also had a look through this: https://wiki.eclipse.org/Californium/Release_Process
and your Master POM: https://github.com/eclipse/californium/blob/master/pom.xml
Our build's pretty simple, we just run 'mvn clean deploy' with the following arguments: maven.test.failure.ignore=false snapshotDependencyAllowed=false enableEclipseJarSigner=true createGPGSignature=true
I've made sure that the selected 'Deploy to repo.eclipse.org + OSSRH' in the Global Settings drop down.
And this is the log output from the build: https://hudson.eclipse.org/paho/user/james.sutton@xxxxxxxxxx/my-views/view/My%20Builds/job/paho-java-maven-test/11/console
But the test build I've been working on (Which is a copy of our nightly build) only uploads to repo.eclipse.org and sends nothing to OSSRH :( I was wondering if someone who's involved in your build process might be able to help me debug our build please? I'm hoping we've just missed something obvious, but I've been playing with it for the last day with no success.
Kind regards,
James Sutton
Software Engineer - IoT Foundation - MQTT Open Source Projects
Technical Trojan - Wimbledon Project
________________________________
Phone: 01962 815438 | Extension: x372454
E-mail: james.sutton@xxxxxxxxxx<mailto:james.sutton@xxxxxxxxxx>
Personal Website: www.jsutton.co.uk<http://www.jsutton.co.uk>
Find me on: [http://www.ibm.com/webaccessories/emailsig/i/LinkedIn.jpg] <http://uk.linkedin.com/in/jpwsutton> [http://www.ibm.com/webaccessories/emailsig/i/WordPress.jpg] <http://www.jsutton.co.uk> [http://www.ibm.com/webaccessories/emailsig/i/Twitter.jpg] <https://twitter.com/jpwsutton>
[IBM]
Hursley Park
Hursley, SO212JN
United Kingdom
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev