Thanks Manfred! It looks like I should be good to go. Given the dated versions I use would you advise I submit a subsequent release using the new versions?
This is really intended to be our initial release of this plugin. <parent> <groupId>org.jenkins-ci.plugins</groupId> <artifactId>plugin</artifactId> <version>2.3</version> <relativePath /> </parent> <artifactId>fortify-on-demand-uploader</artifactId> <version>1.02-SNAPSHOT</version> <packaging>hpi</packaging> <name>Fortify on Demand Uploader Plugin</name> <description>Gathers build artifacts and uploads them to Fortify on Demand service with user-specified options.</description> <url>https://wiki.jenkins-ci.org/display/JENKINS/Fortify+On+Demand+Uploader+Plugin</url> <properties> <jenkins.version>1.580.1</jenkins.version> </properties> On Wednesday, February 24, 2016 at 2:21:09 PM UTC-6, Manfred Moser wrote: > > also use the parent pom version 2.3 ... > > On Wed, Feb 24, 2016 at 11:53 AM, Ryan Black <[email protected] > <javascript:>> wrote: > >> Try the specific Maven release plugin, I should say. >> >> >> >> >> >> On Wednesday, February 24, 2016 at 1:52:17 PM UTC-6, Ryan Black wrote: >>> >>> I can try the specific version. My plugin version is 1.580.1 >>> >>> <groupId>org.jenkins-ci.plugins</groupId> >>> <artifactId>plugin</artifactId> >>> <!-- Baseline Jenkins version you use to build and test the plugin. >>> Users must have this version or newer to run. --> >>> <version>1.580.1</version> >>> >>> To be certain, the <jenkins.version>1.580.1</jenkins.version> key is >>> appended where in the POM? >>> >>> >>> Aside these two changes I have removed the release file and POM backup >>> as to reset the prepare step. If this looks like all I should check I'll >>> give it another go with an incremented version number once more. >>> >>> >>> >>> On Wednesday, February 24, 2016 at 1:04:04 PM UTC-6, Jesse Glick wrote: >>>> >>>> On Wed, Feb 24, 2016 at 1:44 PM, Ryan Black <[email protected]> wrote: >>>> > Before I continue to iterate releases, perhaps in error, to have my >>>> > release version not include -SNAPSHOT, would you have any advice on >>>> this >>>> > scenario? >>>> >>>> Possibly you are accidentally using an old, and buggy, version of the >>>> release plugin. Try >>>> >>>> mvn org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare >>>> org.apache.maven.plugins:maven-release-plugin:2.5.1:perform >>>> >>>> I also recommend switching to a 2.x version of the (Jenkins) plugin >>>> parent POM, which defines newer (Maven) plugin versions, among other >>>> improvements. You need merely define your Jenkins dependency version >>>> like this: >>>> >>>> <jenkins.version>1.580.1</jenkins.version> >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/25c5d118-5bb4-4b2f-abfd-be0ebbd413e7%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/25c5d118-5bb4-4b2f-abfd-be0ebbd413e7%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4796d77d-a50f-4a54-af78-043a8b2bf79c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
