Re: mvn release does not work, only publishes SNAPSHOT releases
After upgrading my pom.xml with: parent groupIdorg.jenkins-ci.plugins/groupId artifactIdplugin/artifactId version1.576/version /parent I can again use mvn release:prepare release:perform without any hacks :) Regards Piotr On Thursday, July 31, 2014 7:52:51 PM UTC+2, davidkarlsen wrote: For reference, this is the maven release plugin issue: https://jira.codehaus.org/browse/MRELEASE-812 AFAIK. 2014-07-31 15:12 GMT+02:00 Marco Miller miller...@me.com javascript:: Indeed; and that is basically the info I added to the wiki(*) some weeks ago, when I experienced such troubles myself: (*) https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues = wiki should have all the needed info by now. /Marco Le mercredi 30 juillet 2014 10:15:00 UTC-4, Stephen Connolly a écrit : there is a much simpler way to get a release: instead of doing $ mvn release:prepare release:perform (with the -B if you are feeling YOLO) you do $ mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare org.apache.maven.plugins:maven-release-plugin:2.5:perform Simples On 30 July 2014 14:59, Markus Pfeiffer m.pfe...@mwaysolutions.com wrote: I've run into the same issue using git 1.9.1 + maven 3.2.2 on Ubuntu and git 1.8.5.2 + maven 3.1.1 on Mac. The release version is never committed and never appears in the store. I also seem to be in the same boat as Ulrich Hafner, our Jenkins plugin is in a subfolder of the git repository and none of the workarounds seem to work. I've used nigelm's tip and simply did a manual deploy using a combination of mvn version:set and mvn deploy. To simplify the process in the future I've written a simple bash script that others may find useful: #!/bin/bash # NAME=tag-name echo Preparing $NAME for release # Query user for info read -p Enter version number to use for the release: VERSION_RELEASE read -p Enter name for the release tag [$NAME-$VERSION_RELEASE]: TAG_RELEASE read -p Enter version number for next development iteration: VERSION_SNAPSHOT if [[ -z $TAG_RELEASE ]]; then TAG_RELEASE=$NAME-$VERSION_RELEASE fi if [[ $VERSION_SNAPSHOT != *-SNAPSHOT ]]; then VERSION_SNAPSHOT=$VERSION_SNAPSHOT-SNAPSHOT fi # Show info for review echo echo Release version : $VERSION_RELEASE echo Tag release with : $TAG_RELEASE echo Next iteration : $VERSION_SNAPSHOT read -p Continue (y/N)? -s -n1 KEY echo if [[ $KEY != y ]]; then echo Aborted exit fi # Set the new version, commit, create a tag mvn versions:set -DnewVersion=$VERSION_RELEASE git add pom.xml git commit -m prepare release $TAG_RELEASE git tag $TAG_RELEASE # Deploy the new version mvn deploy # Set the new snapshot version, commit mvn versions:set -DnewVersion=$VERSION_SNAPSHOT git add pom.xml git commit -m prepare for next development iteration # Push changes and tags # git push # git push --tags # Clean up backup files # rm pom.xml.versionsBackup echo echo done. The push is commented out just to be on the save side. -- 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. 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-de...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen -- 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: mvn release does not work, only publishes SNAPSHOT releases
For reference, this is the maven release plugin issue: https://jira.codehaus.org/browse/MRELEASE-812 AFAIK. 2014-07-31 15:12 GMT+02:00 Marco Miller miller.ma...@me.com: Indeed; and that is basically the info I added to the wiki(*) some weeks ago, when I experienced such troubles myself: (*) https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues = wiki should have all the needed info by now. /Marco Le mercredi 30 juillet 2014 10:15:00 UTC-4, Stephen Connolly a écrit : there is a much simpler way to get a release: instead of doing $ mvn release:prepare release:perform (with the -B if you are feeling YOLO) you do $ mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare org.apache.maven.plugins:maven-release-plugin:2.5:perform Simples On 30 July 2014 14:59, Markus Pfeiffer m.pfe...@mwaysolutions.com wrote: I've run into the same issue using git 1.9.1 + maven 3.2.2 on Ubuntu and git 1.8.5.2 + maven 3.1.1 on Mac. The release version is never committed and never appears in the store. I also seem to be in the same boat as Ulrich Hafner, our Jenkins plugin is in a subfolder of the git repository and none of the workarounds seem to work. I've used nigelm's tip and simply did a manual deploy using a combination of mvn version:set and mvn deploy. To simplify the process in the future I've written a simple bash script that others may find useful: #!/bin/bash # NAME=tag-name echo Preparing $NAME for release # Query user for info read -p Enter version number to use for the release: VERSION_RELEASE read -p Enter name for the release tag [$NAME-$VERSION_RELEASE]: TAG_RELEASE read -p Enter version number for next development iteration: VERSION_SNAPSHOT if [[ -z $TAG_RELEASE ]]; then TAG_RELEASE=$NAME-$VERSION_RELEASE fi if [[ $VERSION_SNAPSHOT != *-SNAPSHOT ]]; then VERSION_SNAPSHOT=$VERSION_SNAPSHOT-SNAPSHOT fi # Show info for review echo echo Release version : $VERSION_RELEASE echo Tag release with : $TAG_RELEASE echo Next iteration : $VERSION_SNAPSHOT read -p Continue (y/N)? -s -n1 KEY echo if [[ $KEY != y ]]; then echo Aborted exit fi # Set the new version, commit, create a tag mvn versions:set -DnewVersion=$VERSION_RELEASE git add pom.xml git commit -m prepare release $TAG_RELEASE git tag $TAG_RELEASE # Deploy the new version mvn deploy # Set the new snapshot version, commit mvn versions:set -DnewVersion=$VERSION_SNAPSHOT git add pom.xml git commit -m prepare for next development iteration # Push changes and tags # git push # git push --tags # Clean up backup files # rm pom.xml.versionsBackup echo echo done. The push is commented out just to be on the save side. -- 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. 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. -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen -- 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: mvn release does not work, only publishes SNAPSHOT releases
I've run into the same issue using git 1.9.1 + maven 3.2.2 on Ubuntu and git 1.8.5.2 + maven 3.1.1 on Mac. The release version is never committed and never appears in the store. I also seem to be in the same boat as Ulrich Hafner, our Jenkins plugin is in a subfolder of the git repository and none of the workarounds seem to work. I've used nigelm's tip and simply did a manual deploy using a combination of mvn version:set and mvn deploy. To simplify the process in the future I've written a simple bash script that others may find useful: #!/bin/bash # NAME=tag-name echo Preparing $NAME for release # Query user for info read -p Enter version number to use for the release: VERSION_RELEASE read -p Enter name for the release tag [$NAME-$VERSION_RELEASE]: TAG_RELEASE read -p Enter version number for next development iteration: VERSION_SNAPSHOT if [[ -z $TAG_RELEASE ]]; then TAG_RELEASE=$NAME-$VERSION_RELEASE fi if [[ $VERSION_SNAPSHOT != *-SNAPSHOT ]]; then VERSION_SNAPSHOT=$VERSION_SNAPSHOT-SNAPSHOT fi # Show info for review echo echo Release version : $VERSION_RELEASE echo Tag release with : $TAG_RELEASE echo Next iteration : $VERSION_SNAPSHOT read -p Continue (y/N)? -s -n1 KEY echo if [[ $KEY != y ]]; then echo Aborted exit fi # Set the new version, commit, create a tag mvn versions:set -DnewVersion=$VERSION_RELEASE git add pom.xml git commit -m prepare release $TAG_RELEASE git tag $TAG_RELEASE # Deploy the new version mvn deploy # Set the new snapshot version, commit mvn versions:set -DnewVersion=$VERSION_SNAPSHOT git add pom.xml git commit -m prepare for next development iteration # Push changes and tags # git push # git push --tags # Clean up backup files # rm pom.xml.versionsBackup echo echo done. The push is commented out just to be on the save side. -- 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: mvn release does not work, only publishes SNAPSHOT releases
there is a much simpler way to get a release: instead of doing $ mvn release:prepare release:perform (with the -B if you are feeling YOLO) you do $ mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare org.apache.maven.plugins:maven-release-plugin:2.5:perform Simples On 30 July 2014 14:59, Markus Pfeiffer m.pfeif...@mwaysolutions.com wrote: I've run into the same issue using git 1.9.1 + maven 3.2.2 on Ubuntu and git 1.8.5.2 + maven 3.1.1 on Mac. The release version is never committed and never appears in the store. I also seem to be in the same boat as Ulrich Hafner, our Jenkins plugin is in a subfolder of the git repository and none of the workarounds seem to work. I've used nigelm's tip and simply did a manual deploy using a combination of mvn version:set and mvn deploy. To simplify the process in the future I've written a simple bash script that others may find useful: #!/bin/bash # NAME=tag-name echo Preparing $NAME for release # Query user for info read -p Enter version number to use for the release: VERSION_RELEASE read -p Enter name for the release tag [$NAME-$VERSION_RELEASE]: TAG_RELEASE read -p Enter version number for next development iteration: VERSION_SNAPSHOT if [[ -z $TAG_RELEASE ]]; then TAG_RELEASE=$NAME-$VERSION_RELEASE fi if [[ $VERSION_SNAPSHOT != *-SNAPSHOT ]]; then VERSION_SNAPSHOT=$VERSION_SNAPSHOT-SNAPSHOT fi # Show info for review echo echo Release version : $VERSION_RELEASE echo Tag release with : $TAG_RELEASE echo Next iteration : $VERSION_SNAPSHOT read -p Continue (y/N)? -s -n1 KEY echo if [[ $KEY != y ]]; then echo Aborted exit fi # Set the new version, commit, create a tag mvn versions:set -DnewVersion=$VERSION_RELEASE git add pom.xml git commit -m prepare release $TAG_RELEASE git tag $TAG_RELEASE # Deploy the new version mvn deploy # Set the new snapshot version, commit mvn versions:set -DnewVersion=$VERSION_SNAPSHOT git add pom.xml git commit -m prepare for next development iteration # Push changes and tags # git push # git push --tags # Clean up backup files # rm pom.xml.versionsBackup echo echo done. The push is commented out just to be on the save side. -- 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: mvn release does not work, only publishes SNAPSHOT releases
Hehehe. So there is no hope for fixing this ever? At least, could you be so kind as to describe those neccessary changes that should fix the project layout? Like removing the extra depends/versions? Or separating the Jenkins pom from plugin pom? -- 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: mvn release does not work, only publishes SNAPSHOT releases
Have u got any patches / pull requests one can look at?
On Wednesday, May 14, 2014 1:26:24 PM UTC+4, Stephen Connolly wrote:
Well I have long maintained that Jenkins's pom structure does it all
wrong but any time I have wanted to try and fix it *and* had a time window
to try, KK puts too much of a barrier with regard to people getting
confused.
I guess it doesn't help that to fix it, I need to redo the hpi plugin so
that it actually works the Maven way... but then if the people who wrote
the original hpi plugin understood the Maven way they would never have
written the Maven project type in Jenkins the way they did and it would not
be evil!
On 13 May 2014 23:46, Ivan Kalinin pups...@gmail.com javascript:wrote:
Has similar problem recently and your fix did help. But latest parent (
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/jenkins/1.33/)
still uses 2.2.2 -- is there any plan to fix that?
On Saturday, March 8, 2014 11:05:15 PM UTC+4, Stephen Connolly wrote:
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
And if that tags correctly then same with perform. Should fix the
-SNAPSHOT issue... The other issue could be a different story
On Saturday, 8 March 2014, Ulli Hafner ullrich...@gmail.com wrote:
git version is 1.8.5.3
The dependency hack does only work if the plugin is top-level. I’m
releasing in a sub-folder.
Am 08.03.2014 um 12:36 schrieb Stephen Connolly
stephen.alan.conno...@gmail.com:
What version of git are you using?
Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com
wrote:
Has someone a workaround for that problem if the plugin/libray to
release is not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of
https://github.com/jenkinsci/pomincoporating the changes to the release
plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise any
time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com
wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-pr
oviders-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
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.
--
Sent from my phone
--
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: mvn release does not work, only publishes SNAPSHOT releases
Ha! When I do get around to fixing this it will look a lot like NIH
syndrome, because quite frankly most of the current parent pom is overbaked
and too heavyweight and includes too many workarounds for the incorrect
design within the hpi plugin.
Pull requests would not be compatible with the scope of change required to
do this right
On 15 May 2014 09:45, Ivan Kalinin pupss...@gmail.com wrote:
Have u got any patches / pull requests one can look at?
On Wednesday, May 14, 2014 1:26:24 PM UTC+4, Stephen Connolly wrote:
Well I have long maintained that Jenkins's pom structure does it all
wrong but any time I have wanted to try and fix it *and* had a time window
to try, KK puts too much of a barrier with regard to people getting
confused.
I guess it doesn't help that to fix it, I need to redo the hpi plugin so
that it actually works the Maven way... but then if the people who wrote
the original hpi plugin understood the Maven way they would never have
written the Maven project type in Jenkins the way they did and it would not
be evil!
On 13 May 2014 23:46, Ivan Kalinin pups...@gmail.com wrote:
Has similar problem recently and your fix did help. But latest parent (
http://maven.jenkins-ci.org:8081/content/repositories/
releases/org/jenkins-ci/jenkins/1.33/) still uses 2.2.2 -- is there any
plan to fix that?
On Saturday, March 8, 2014 11:05:15 PM UTC+4, Stephen Connolly wrote:
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
And if that tags correctly then same with perform. Should fix the
-SNAPSHOT issue... The other issue could be a different story
On Saturday, 8 March 2014, Ulli Hafner ullrich...@gmail.com wrote:
git version is 1.8.5.3
The dependency hack does only work if the plugin is top-level. I’m
releasing in a sub-folder.
Am 08.03.2014 um 12:36 schrieb Stephen Connolly
stephen.alan.conno...@gmail.com:
What version of git are you using?
Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com
wrote:
Has someone a workaround for that problem if the plugin/libray to
release is not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of
https://github.com/jenkinsci/pomincoporating the changes to the release
plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise
any time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com
wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-pr
oviders-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
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.
--
Sent from my phone
--
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.
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: mvn release does not work, only publishes SNAPSHOT releases
Well I have long maintained that Jenkins's pom structure does it all
wrong but any time I have wanted to try and fix it *and* had a time window
to try, KK puts too much of a barrier with regard to people getting
confused.
I guess it doesn't help that to fix it, I need to redo the hpi plugin so
that it actually works the Maven way... but then if the people who wrote
the original hpi plugin understood the Maven way they would never have
written the Maven project type in Jenkins the way they did and it would not
be evil!
On 13 May 2014 23:46, Ivan Kalinin pupss...@gmail.com wrote:
Has similar problem recently and your fix did help. But latest parent (
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/jenkins/1.33/)
still uses 2.2.2 -- is there any plan to fix that?
On Saturday, March 8, 2014 11:05:15 PM UTC+4, Stephen Connolly wrote:
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
And if that tags correctly then same with perform. Should fix the
-SNAPSHOT issue... The other issue could be a different story
On Saturday, 8 March 2014, Ulli Hafner ullrich...@gmail.com wrote:
git version is 1.8.5.3
The dependency hack does only work if the plugin is top-level. I’m
releasing in a sub-folder.
Am 08.03.2014 um 12:36 schrieb Stephen Connolly
stephen.alan.conno...@gmail.com:
What version of git are you using?
Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com wrote:
Has someone a workaround for that problem if the plugin/libray to
release is not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of
https://github.com/jenkinsci/pomincoporating the changes to the release
plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise any
time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com
wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-pr
oviders-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
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.
--
Sent from my phone
--
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: mvn release does not work, only publishes SNAPSHOT releases
Has similar problem recently and your fix did help. But latest parent
(http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/jenkins/1.33/)
still uses 2.2.2 -- is there any plan to fix that?
On Saturday, March 8, 2014 11:05:15 PM UTC+4, Stephen Connolly wrote:
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
And if that tags correctly then same with perform. Should fix the
-SNAPSHOT issue... The other issue could be a different story
On Saturday, 8 March 2014, Ulli Hafner ullrich...@gmail.com javascript:
wrote:
git version is 1.8.5.3
The dependency hack does only work if the plugin is top-level. I’m
releasing in a sub-folder.
Am 08.03.2014 um 12:36 schrieb Stephen Connolly
stephen.alan.conno...@gmail.com:
What version of git are you using?
Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com wrote:
Has someone a workaround for that problem if the plugin/libray to release
is not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of https://github.com/jenkinsci/pomincoporating
the changes to the release plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise any
time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com
wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-
providers-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
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.
--
Sent from my phone
--
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: mvn release does not work, only publishes SNAPSHOT releases
Has someone a workaround for that problem if the plugin/libray to release is
not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of https://github.com/jenkinsci/pom
incoporating the changes to the release plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise any time
- sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the release
plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
I have seen this problem today using:
maven 3.1.1
maven-releas-plugin 2.2.2
git 1.8.5
Worked around downgrading git to 1.8.4.
http://jira.codehaus.org/browse/MRELEASE-812
--
oliver
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
--
Sent from my phone
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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/groups/opt_out.
signature.asc
Description: Message signed with OpenPGP using GPGMail
Re: mvn release does not work, only publishes SNAPSHOT releases
What version of git are you using?
Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com wrote:
Has someone a workaround for that problem if the plugin/libray to release
is not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner
ullrich.haf...@gmail.comjavascript:_e(%7B%7D,'cvml','ullrich.haf...@gmail.com');
:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of https://github.com/jenkinsci/pomincoporating
the changes to the release plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I'll try to take a look at the m-r-p, but I currently can't promise any
time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don't have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-
providers-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
I have seen this problem today using:
maven 3.1.1
maven-releas-plugin 2.2.2
git 1.8.5
Worked around downgrading git to 1.8.4.
http://jira.codehaus.org/browse/MRELEASE-812
--
oliver
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiv
--
Sent from my phone
--
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: mvn release does not work, only publishes SNAPSHOT releases
git version is 1.8.5.3
The dependency hack does only work if the plugin is top-level. I’m releasing in
a sub-folder.
Am 08.03.2014 um 12:36 schrieb Stephen Connolly
stephen.alan.conno...@gmail.com:
What version of git are you using?
Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com wrote:
Has someone a workaround for that problem if the plugin/libray to release is
not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of https://github.com/jenkinsci/pom
incoporating the changes to the release plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise any
time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
I have seen this problem today using:
maven 3.1.1
maven-releas-plugin 2.2.2
git 1.8.5
Worked around downgrading git to 1.8.4.
http://jira.codehaus.org/browse/MRELEASE-812
--
oliver
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiv
--
Sent from my phone
--
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: mvn release does not work, only publishes SNAPSHOT releases
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
And if that tags correctly then same with perform. Should fix the -SNAPSHOT
issue... The other issue could be a different story
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com wrote:
git version is 1.8.5.3
The dependency hack does only work if the plugin is top-level. I'm
releasing in a sub-folder.
Am 08.03.2014 um 12:36 schrieb Stephen Connolly
stephen.alan.conno...@gmail.comjavascript:_e(%7B%7D,'cvml','stephen.alan.conno...@gmail.com');
:
What version of git are you using?
Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com wrote:
Has someone a workaround for that problem if the plugin/libray to release
is not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of https://github.com/jenkinsci/pomincoporating
the changes to the release plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I'll try to take a look at the m-r-p, but I currently can't promise any
time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don't have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-
providers-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
To unsubscribe from this group and stop receiving emails from it, send an
email to
jenkinsci-dev+unsubscr...@googlegroups.comjavascript:_e(%7B%7D,'cvml','jenkinsci-dev%2bunsubscr...@googlegroups.com');
.
For more options, visit https://groups.google.com/d/optout.
--
Sent from my phone
--
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: mvn release does not work, only publishes SNAPSHOT releases
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of https://github.com/jenkinsci/pom incoporating
the changes to the release plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise any time
- sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the release
plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
I have seen this problem today using:
maven 3.1.1
maven-releas-plugin 2.2.2
git 1.8.5
Worked around downgrading git to 1.8.4.
http://jira.codehaus.org/browse/MRELEASE-812
--
oliver
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
--
Sent from my phone
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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/groups/opt_out.
signature.asc
Description: Message signed with OpenPGP using GPGMail
Re: mvn release does not work, only publishes SNAPSHOT releases
Should we pull a new release of https://github.com/jenkinsci/pom
incoporating the changes to the release plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch javascript:
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise any
time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly
stephen.al...@gmail.comjavascript:
wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
I have seen this problem today using:
maven 3.1.1
maven-releas-plugin 2.2.2
git 1.8.5
Worked around downgrading git to 1.8.4.
http://jira.codehaus.org/browse/MRELEASE-812
--
oliver
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
--
Sent from my phone
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: mvn release does not work, only publishes SNAPSHOT releases
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi d...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise any
time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
I have seen this problem today using:
maven 3.1.1
maven-releas-plugin 2.2.2
git 1.8.5
Worked around downgrading git to 1.8.4.
http://jira.codehaus.org/browse/MRELEASE-812
--
oliver
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
--
Sent from my phone
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: mvn release does not work, only publishes SNAPSHOT releases
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay
nigel.mag...@gmail.comjavascript:_e({}, 'cvml', 'nigel.mag...@gmail.com');
wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.comjavascript:_e({},
'cvml', 'ogon...@gmail.com');
wrote:
I have seen this problem today using:
maven 3.1.1
maven-releas-plugin 2.2.2
git 1.8.5
Worked around downgrading git to 1.8.4.
http://jira.codehaus.org/browse/MRELEASE-812
--
oliver
--
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 javascript:_e({},
'cvml', 'jenkinsci-dev%2bunsubscr...@googlegroups.com');.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 javascript:_e({},
'cvml', 'jenkinsci-dev+unsubscr...@googlegroups.com');.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 javascript:_e({},
'cvml', 'jenkinsci-dev%2bunsubscr...@googlegroups.com');.
For more options, visit https://groups.google.com/groups/opt_out.
--
Sent from my phone
--
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/groups/opt_out.
Re: mvn release does not work, only publishes SNAPSHOT releases
;-) I’ll try to take a look at the m-r-p, but I currently can’t promise any time - sorry :( /Domi On 13.01.2014, at 09:21, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On Sunday, 12 January 2014, Dominik Bartholdi wrote: The maven team Nice dodge of self promotion there ;-) Btw do you want to take a run at m-r-p? has just release a git provider based on jgit, if you configure the release plugin to use this one, then you don’t have to downgrade git. http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html /Domi On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote: I've just had this problem too, with two separate plugins. maven-release-plugin is just total crapola. Just do a manual mvn versions:set and deploy. On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote: I have seen this problem today using: maven 3.1.1 maven-releas-plugin 2.2.2 git 1.8.5 Worked around downgrading git to 1.8.4. http://jira.codehaus.org/browse/MRELEASE-812 -- oliver -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- Sent from my phone -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: mvn release does not work, only publishes SNAPSHOT releases
I've just had this problem too, with two separate plugins. maven-release-plugin is just total crapola. Just do a manual mvn versions:set and deploy. On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote: I have seen this problem today using: maven 3.1.1 maven-releas-plugin 2.2.2 git 1.8.5 Worked around downgrading git to 1.8.4. http://jira.codehaus.org/browse/MRELEASE-812 -- oliver -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: mvn release does not work, only publishes SNAPSHOT releases
The maven team has just release a git provider based on jgit, if you configure the release plugin to use this one, then you don’t have to downgrade git. http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html /Domi On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote: I've just had this problem too, with two separate plugins. maven-release-plugin is just total crapola. Just do a manual mvn versions:set and deploy. On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote: I have seen this problem today using: maven 3.1.1 maven-releas-plugin 2.2.2 git 1.8.5 Worked around downgrading git to 1.8.4. http://jira.codehaus.org/browse/MRELEASE-812 -- oliver -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: mvn release does not work, only publishes SNAPSHOT releases
I have seen this problem today using: maven 3.1.1 maven-releas-plugin 2.2.2 git 1.8.5 Worked around downgrading git to 1.8.4. http://jira.codehaus.org/browse/MRELEASE-812 -- oliver -- 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/groups/opt_out.
Re: mvn release does not work, only publishes SNAPSHOT releases
I'm having the same problem using maven directly for releasing to the git repository (mvn release:prepare release:perform). Using maven-release-plugin 2.4 it builds the snapshot version as release - using version 2.3.2 it works as intended :) Is there already a bugreport somewhere? Regards, Bernhard Friedreich On Sunday, March 3, 2013 3:02:27 PM UTC+1, Georg Gruetter wrote: Hi Baptiste, * upgrade to mvn 3.0.4 or 3.0.5, 3.0.3 have had some issues that even led jenkins core to forbid building with it I already upgraded to 3.0.5 but the problem persists. * which mvn-release-p version are you using? 2.4 has some issues with git. Prefer sticking to 2.3.2 before it's fixed. I'm using 2.2.2 as prescribed by the jenkins parent pom version 1.498. I'll try manually setting 2.3.2 when I do the next release. Thanks for the tip. Cheers, Georg Le 1 mars 2013 01:36, Georg Gruetter grue...@gmail.com a écrit : Hi all, this is a followup of a thread I started earlierhttps://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/BdERU5oBRMk. I'm trying to publish my first release of the stashnotifier pluginhttps://github.com/jenkinsci/stashnotifier-pluginbut continue to fail. Here's what happens 1. I am ready to perform a maven release (SNAPSHOT version, all changes committed and pushed to GitHub). I'm on the develop branch (I usually use the git-flow branching model and tried the same on a release branch - same problem. I haven't tried this on the master branch though). 2. I perform mvn release:prepare release:perform 3. When prompted for the release version, I enter 1.0.2 (current + next SNAPSHOT version is 1.1-SNAPSHOT) 4. the release runs through successfully without any error but only publishes the SNAPSHOT version I think the problem occurs in the release:prepare. After release:prepare, I'd expect so see a commit in my local repository where the artifact version in my pom.xml is set to the release version (1.0.2). However - no commit. As a result, the artifact version is still 1.1-SNAPSHOT and I guess that's why maven decides to deploy it to the SNAPSHOTS repository. Tagging works and the tag is also pushed to the remote. From what I can tell, maven sort of omits the commit command and no changes are pushed as a result: [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git add -- pom.xml [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git status [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Tagging release with the label stashNotifier-1.0.2... [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git tag -F /var/folders/dr/xxbtyycs1z9dl2_snlj87zrhgn/T/maven-scm-678409272.commit stashNotifier-1.0.2 [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git push g...@github.com:jenkinsci/stashnotifier-plugin.git stashNotifier-1.0.2 [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git ls-files [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Transforming 'Stash Notifier'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git add -- pom.xml [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git status [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Release preparation complete. I have appended the complete mvn output of the release run for your reference. I'm running Maven 3.0.3, by the way. Can anyone please tell me what I'm doing wrong? I'm banging my head against the wall on this for a couple of days now. Thanks for your help and cheers, Georg -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: mvn release does not work, only publishes SNAPSHOT releases
Hi Baptiste, * upgrade to mvn 3.0.4 or 3.0.5, 3.0.3 have had some issues that even led jenkins core to forbid building with it I already upgraded to 3.0.5 but the problem persists. * which mvn-release-p version are you using? 2.4 has some issues with git. Prefer sticking to 2.3.2 before it's fixed. I'm using 2.2.2 as prescribed by the jenkins parent pom version 1.498. I'll try manually setting 2.3.2 when I do the next release. Thanks for the tip. Cheers, Georg Le 1 mars 2013 01:36, Georg Gruetter grue...@gmail.com javascript: a écrit : Hi all, this is a followup of a thread I started earlierhttps://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/BdERU5oBRMk. I'm trying to publish my first release of the stashnotifier pluginhttps://github.com/jenkinsci/stashnotifier-pluginbut continue to fail. Here's what happens 1. I am ready to perform a maven release (SNAPSHOT version, all changes committed and pushed to GitHub). I'm on the develop branch (I usually use the git-flow branching model and tried the same on a release branch - same problem. I haven't tried this on the master branch though). 2. I perform mvn release:prepare release:perform 3. When prompted for the release version, I enter 1.0.2 (current + next SNAPSHOT version is 1.1-SNAPSHOT) 4. the release runs through successfully without any error but only publishes the SNAPSHOT version I think the problem occurs in the release:prepare. After release:prepare, I'd expect so see a commit in my local repository where the artifact version in my pom.xml is set to the release version (1.0.2). However - no commit. As a result, the artifact version is still 1.1-SNAPSHOT and I guess that's why maven decides to deploy it to the SNAPSHOTS repository. Tagging works and the tag is also pushed to the remote. From what I can tell, maven sort of omits the commit command and no changes are pushed as a result: [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git add -- pom.xml [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git status [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Tagging release with the label stashNotifier-1.0.2... [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git tag -F /var/folders/dr/xxbtyycs1z9dl2_snlj87zrhgn/T/maven-scm-678409272.commit stashNotifier-1.0.2 [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git push g...@github.com:jenkinsci/stashnotifier-plugin.git stashNotifier-1.0.2 [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git ls-files [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Transforming 'Stash Notifier'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git add -- pom.xml [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier git status [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier [INFO] Release preparation complete. I have appended the complete mvn output of the release run for your reference. I'm running Maven 3.0.3, by the way. Can anyone please tell me what I'm doing wrong? I'm banging my head against the wall on this for a couple of days now. Thanks for your help and cheers, Georg -- 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/groups/opt_out. -- 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/groups/opt_out.
