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> >>> <artifactId>maven-release-plugin</artifactId> >>> <version>${maven-release-plugin.version}</version> >>> <dependencies> >>> <dependency> >>> <groupId>org.apache.maven.scm</groupId> >>> <artifactId>maven-scm-provider-gitexe</artifactId> >>> <version>1.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
