Though I think this is technically possible, the conventions in general from maven artifactIds is more to try and use an always lower case naming. This might lead to a whole lot of surprises (being able to have both TestFairy-1.0 and testfairy-1.0 releases e.g., but would then clash on Windows machines if you try to install both, and so on).
And as Daniel said, changing an artifactId afterwards is gonna disconnect you from your existing users, since they won't see the updates and will have to install a NEW plugin (and make sure to uninstall the other one... I guess). Anyway, in your case, to see if the artifactId change can be the source of your authentication pb, you could revert temporarily the code to the previous artifactId, and then release some special version like 2.5.1-testversion-donotinstall-beta (having beta somewhere in the name will have the advantage to not show up in the "production" update center). My 2 cents Cheers 2015-02-10 14:04 GMT+01:00 Giltsl <[email protected]>: > I am trying to release a new version (2.5.1) with the correct artifact id > which is "TestFairy" > > And I got the attached output. > > My setting.xml file includes user name and password, so I can't > understand why I am getting "401, ReasonPhrase: Unauthorized." > > > [INFO] 1174/1174 KB >> >> [INFO] >> >> [INFO] Uploading: >> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/TestFairy/2.5.1/TestFairy-2.5.1.pom >> >> [INFO] 2/3 KB >> >> [INFO] 3/3 KB >> >> [INFO] >> >> [INFO] [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] [INFO] BUILD FAILURE >> >> [INFO] [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] [INFO] Total time: 46.873 s >> >> [INFO] [INFO] Finished at: 2015-02-10T14:56:46+02:00 >> >> [INFO] [INFO] Final Memory: 40M/85M >> >> [INFO] [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins: >> maven-deploy-plugin:2.6:deploy (default-deploy) on project TestFairy: >> Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci. >> plugins:TestFairy:hpi:2.5.1 from/to maven.jenkins-ci.org ( >> http://maven.jenkins-ci.org:8081/content/repositories/releases): Failed >> to transfer file: >> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/TestFairy/2.5.1/TestFairy-2.5.1.hpi. >> Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] >> >> [INFO] [ERROR] >> >> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven >> with the -e switch. >> >> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug >> logging. >> >> [INFO] [ERROR] >> >> [INFO] [ERROR] For more information about the errors and possible >> solutions, please read the following articles: >> >> [INFO] [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] BUILD FAILURE >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [INFO] Total time: 01:51 min >> >> [INFO] Finished at: 2015-02-10T14:56:46+02:00 >> >> [INFO] Final Memory: 11M/81M >> >> [INFO] >> ------------------------------------------------------------------------ >> >> [ERROR] Failed to execute goal org.apache.maven.plugins: >> maven-release-plugin:2.5:perform (default-cli) on project TestFairy: >> Maven execution failed, exit code: '1' -> [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 >> > > > On Monday, February 9, 2015 at 7:44:24 PM UTC+2, Daniel Beck wrote: >> >> You're not supposed to change artifact ID after a release. Artifact ID >> is how Jenkins identifies plugins e.g. to offer upgrades from a >> previously installed version. The plugins where this happened appear >> twice (or more) on the update center, once for each ID. If users install >> both, who knows what'll happen... >> >> In this case, it could be a bug related to case sensitivity in the update >> center. >> >> On 09.02.2015, at 13:48, Giltsl <[email protected]> wrote: >> >> > It is not a version problem. I am using the latest Jenkins version. >> > >> > Maybe it's related to some "artifactId" mismatch I did. >> > When I released the version, I used "testfairy" instead of TestFairy" >> as an artifactId in my pom.xml. >> > http://mirrors.jenkins-ci.org/plugins/testfairy/2.2/testfairy.hpi >> will return 404 >> > http://mirrors.jenkins-ci.org/plugins/TestFairy/2.2/TestFairy.hpi work >> > >> > >> > Thanks for your help. >> > >> > >> > On Monday, February 9, 2015 at 12:34:30 PM UTC+2, Baptiste Mathus >> wrote: >> > Last plugin version seems to require 1.596 which is very recent. Maybe >> your Jenkins version is just < 1.596? >> > >> > Le 9 févr. 2015 11:31, "Baptiste Mathus" <[email protected]> a écrit : >> > What is your Jenkins version? >> > >> > Le 9 févr. 2015 09:12, "Giltsl" <[email protected]> a écrit : >> > Hi, >> > >> > We had been published a new version (2.2) for the TestFairy plugin, >> it's already listed on update-center.json >> > But I still can install only the previous version 1.0 (the new version >> is not visible) >> > >> > In addition, the link to the new hpi file (2.2) is broken on >> http://updates.jenkins-ci.org/download/plugins/TestFairy/ >> > >> > Please advise how it should be fixed >> > Thanks >> > Gil >> > >> > -- >> > 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/3e24ce15-efb3-4947-92c2-f677291902d7% >> 40googlegroups.com. >> > 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/cc8b2706-a809-426b-9a94-12957839104b% >> 40googlegroups.com. >> > 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/e6730f40-dbca-4a19-bd1d-d02416f5e3ed%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/e6730f40-dbca-4a19-bd1d-d02416f5e3ed%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! > nbsp;! > -- 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/CANWgJS5-HnB3RkoMLJ3dBhCcMkd4AdwfFcO4j97MtWjtXqv-vA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
