Re: Plugin release to wrong maven repo?
You also hit the maven snapshot bug, seems that the wiki note https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins needs to be more prominent… See https://groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk Am 28.05.2014 um 10:51 schrieb Cees Bos cbos...@gmail.com: Hi all, I followed the steps on https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to release the send-stacktrace-to-eclipse-plugin. As mentioned on the wiki page I did check http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ to see if the plugin is there, but it is not. This is what was published by the release process: [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/send-stacktrace-to-eclipse-plugin-1.5-20140528.083705-1-javadoc.jar (37 KB at 22.1 KB/sec) [INFO] Uploading: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml [INFO] 2/2 KB [INFO] [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml (2 KB at 1.4 KB/sec) Maven build was successful. It looks like it did publish the content to a different maven repository. The POM of my plugin can be found here. Regards, Cees -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Plugin release to wrong maven repo?
Hi Ulli, Thanks for you quick response! Based on the referred mail thread it is not clear to me what to change to publish it is in the right way. I am not that familiar with maven. Is there something I need to change in my pom.xml of settings.xml? I am using maven 3.0.5. Regards, Cees On Wed, May 28, 2014 at 11:30 AM, Ulli Hafner ullrich.haf...@gmail.comwrote: You also hit the maven snapshot bug, seems that the wiki note https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins needs to be more prominent… See https://groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk Am 28.05.2014 um 10:51 schrieb Cees Bos cbos...@gmail.com: Hi all, I followed the steps on https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to release the send-stacktrace-to-eclipse-plugin. As mentioned on the wiki page I did check http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ to see if the plugin is there, but it is not. This is what was published by the release process: [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/send-stacktrace-to-eclipse-plugin-1.5-20140528.083705-1-javadoc.jar(37 KB at 22.1 KB/sec) [INFO] Uploading: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml [INFO] 2/2 KB [INFO] [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml(2 KB at 1.4 KB/sec) Maven build was successful. It looks like it did publish the content to a different maven repository. The POM of my plugin can be found here. Regards, Cees -- 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 jenkinsci-dev+unsubscr...@googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Plugin release to wrong maven repo?
First, Working around common issues, last note *No prepare commits in git.* Feel free to extend this note with more comments. On Wednesday, May 28, 2014 12:49:11 PM UTC+3, Cees Bos wrote: Hi Ulli, Thanks for you quick response! Based on the referred mail thread it is not clear to me what to change to publish it is in the right way. I am not that familiar with maven. Is there something I need to change in my pom.xml of settings.xml? I am using maven 3.0.5. Regards, Cees On Wed, May 28, 2014 at 11:30 AM, Ulli Hafner ullrich...@gmail.comjavascript: wrote: You also hit the maven snapshot bug, seems that the wiki note https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins needs to be more prominent… See https://groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk Am 28.05.2014 um 10:51 schrieb Cees Bos cbo...@gmail.com javascript:: Hi all, I followed the steps on https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to release the send-stacktrace-to-eclipse-plugin. As mentioned on the wiki page I did check http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ to see if the plugin is there, but it is not. This is what was published by the release process: [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/send-stacktrace-to-eclipse-plugin-1.5-20140528.083705-1-javadoc.jar(37 KB at 22.1 KB/sec) [INFO] Uploading: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml [INFO] 2/2 KB [INFO] [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml(2 KB at 1.4 KB/sec) Maven build was successful. It looks like it did publish the content to a different maven repository. The POM of my plugin can be found here. Regards, Cees -- 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 jenkinsci-de...@googlegroups.com javascript:. 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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Plugin release to wrong maven repo?
Add this to the build section of your log: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.5/version dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId version1.9/version /dependency /dependencies /plugin PS: Please update the wiki if that works:-) Am 28.05.2014 um 11:49 schrieb Cees Bos cbos...@gmail.com: Hi Ulli, Thanks for you quick response! Based on the referred mail thread it is not clear to me what to change to publish it is in the right way. I am not that familiar with maven. Is there something I need to change in my pom.xml of settings.xml? I am using maven 3.0.5. Regards, Cees On Wed, May 28, 2014 at 11:30 AM, Ulli Hafner ullrich.haf...@gmail.com wrote: You also hit the maven snapshot bug, seems that the wiki note https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins needs to be more prominent… See https://groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk Am 28.05.2014 um 10:51 schrieb Cees Bos cbos...@gmail.com: Hi all, I followed the steps on https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to release the send-stacktrace-to-eclipse-plugin. As mentioned on the wiki page I did check http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ to see if the plugin is there, but it is not. This is what was published by the release process: [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/send-stacktrace-to-eclipse-plugin-1.5-20140528.083705-1-javadoc.jar (37 KB at 22.1 KB/sec) [INFO] Uploading: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml [INFO] 2/2 KB [INFO] [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml (2 KB at 1.4 KB/sec) Maven build was successful. It looks like it did publish the content to a different maven repository. The POM of my plugin can be found here. Regards, Cees -- 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 jenkinsci-dev+unsubscr...@googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Plugin release to wrong maven repo?
Hi all, I had similar problem when releasing biouno plug-ins. Even though it uses a custom update center and maven repository, the problem was similar; my releases were going to the snapshot repository [1]. I think the solution so far has been changing the release-plugin version. In my case I changed a configuration in my git repository as in [2]. Apparently git changed the status message, what caused the release plugin to interpret my release as a snapshot - in my case. What I did in my git repositories for Java projects was: `git config --add status.displayCommentPrefix true` Not sure if it is the same issue that is happening for some plugins, but worth a shot in case you don't want to change your maven settings. HTH, Bruno [1] http://jira.codehaus.org/browse/SCM-740 [2] http://ilikeorangutans.github.io/2014/04/29/maven-release-plugin-and-git-19 From: Ulli Hafner ullrich.haf...@gmail.com To: jenkinsci-dev@googlegroups.com Sent: Wednesday, May 28, 2014 12:44 PM Subject: Re: Plugin release to wrong maven repo? Add this to the build section of your log: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.5/version dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId version1.9/version /dependency /dependencies /plugin PS: Please update the wiki if that works:-) Am 28.05.2014 um 11:49 schrieb Cees Bos cbos...@gmail.com: Hi Ulli, Thanks for you quick response! Based on the referred mail thread it is not clear to me what to change to publish it is in the right way. I am not that familiar with maven. Is there something I need to change in my pom.xml of settings.xml? I am using maven 3.0.5. Regards, Cees On Wed, May 28, 2014 at 11:30 AM, Ulli Hafner ullrich.haf...@gmail.com wrote: You also hit the maven snapshot bug, seems that the wiki note https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins needs to be more prominent… See https://groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk Am 28.05.2014 um 10:51 schrieb Cees Bos cbos...@gmail.com: Hi all, I followed the steps on https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to release the send-stacktrace-to-eclipse-plugin. As mentioned on the wiki page I did check http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/ to see if the plugin is there, but it is not. This is what was published by the release process: [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/send-stacktrace-to-eclipse-plugin-1.5-20140528.083705-1-javadoc.jar (37 KB at 22.1 KB/sec) [INFO] Uploading: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml [INFO] 2/2 KB [INFO] [INFO] Uploaded: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/send-stacktrace-to-eclipse-plugin/1.5-SNAPSHOT/maven-metadata.xml (2 KB at 1.4 KB/sec) Maven build was successful. It looks like it did publish the content to a different maven repository. The POM of my plugin can be found here. Regards, Cees -- 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 jenkinsci-dev+unsubscr...@googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
