[mojo-dev] Nexus@Codehaus shutdown plan

2015-05-01 Thread Baptiste Mathus
Hi Ben, As per that mail from Brian Fox [1] we've come to understand that Nexus@Codehaus should stay available longer than the rest of the Codehaus infra. But viewing the codehaus tweet this morning, I've started being in doubt. Could you please confirm (or not) that information? Because if that

Re: [mojo-dev] [Result] [VOTE] Release flatten-maven-plugin version 1.0.0-beta-4

2015-05-01 Thread Jörg Hohwiller
Hi, This vote has passed with lazy consensus, I will proceed to promote the artifact to Maven Central Right next I will start the next release to pull out the NPE fix we did on trunk. Regards Jörg Am 26.04.2015 um 11:29 schrieb Jörg Hohwiller: > Hi, > > I'd like to release version 1.0.0-beta

[mojo-dev] staging repository gone?

2015-05-01 Thread Jörg Hohwiller
Hi there, I wanted to release the flatten-maven-plugin but the staging repository is gone in oss.sonatype.org or at least I can not see it anymore. Can someone shed a light into this? I can still see the content here: https://nexus.codehaus.org/content/groups/staging/org/codehaus/mojo/flatten-mave

Re: [mojo-dev] staging repository gone?

2015-05-01 Thread Dan Tran
ATM, Codehaus MOJO does not have a staging repo at Sonatype yet. Your staging after promoted will go directly to Maven central -D On Fri, May 1, 2015 at 12:41 AM, Jörg Hohwiller wrote: > Hi there, > > I wanted to release the flatten-maven-plugin but the staging repository > is gone in oss.sona

[mojo-dev] [jira] (MVERSIONS-286) NullPointerException in versions:set

2015-05-01 Thread Sergei Ivanov (JIRA)
Title: Message Title Sergei Ivanov commented on an issue

[mojo-dev] [jira] (MVERSIONS-287) versions:set NPE Regression failure

2015-05-01 Thread Sergei Ivanov (JIRA)
Title: Message Title Sergei Ivanov commented on an issue

[mojo-dev] Re: Nexus@Codehaus shutdown plan

2015-05-01 Thread Baptiste Mathus
FYI 2015-05-01 11:46 GMT+02:00 Ben Walding : > Yes that's fine. > > Regards, > > Ben > > On 1 May 2015, at 19:34, Baptiste Mathus wrote: > > Good news :). Do you mind if I forward your answer to the mojo dev list? > > Cheers > Le 1 mai 2015 9:37 AM, "Codehaus Support" a écrit : > >> Just a poor

[mojo-dev] [jira] (MVERSIONS-285) Goal set:version fails if groupId is defined in parent pom

2015-05-01 Thread Tomer Cohen (JIRA)
Title: Message Title Tomer Cohen updated an issue

[mojo-dev] Re: [DISCUSS] Codehaus EOL and MOJO migration

2015-05-01 Thread keeganwitt
I'm sure you probably already know about this, but in case you don't: GitHub has an importer that doesn't require a dump: https://help.github.com/articles/importing-from-subversion/#importing-a-subversion-project-using-githubs-importer. I've used it for a smallish repo without any issue, but I'm

Re: [mojo-dev] staging repository gone?

2015-05-01 Thread Jörg Hohwiller
Maybe I used the wrong wording but in the menu there is an entry called "Staging Repositories". There I usually see the content that I uploaded and there I found it and "closed" it. After the vote I usually find it again and the choose "Release" but this time it is gone. Still hoping for help. J

Re: [mojo-dev] staging repository gone?

2015-05-01 Thread Jörg Hohwiller
Stupid me. Too many different OSS projects in parallel. For mojo I need to log in at nexus.sonartype.org and not oss.sonartype.org. Release is promoted. Sorry for confusing... Regards Jörg Am 01.05.2015 um 15:46 schrieb Jörg Hohwiller: > Maybe I used the wrong wording but in the menu there is a

Re: [mojo-dev] staging repository gone?

2015-05-01 Thread Baptiste Mathus
I suppose you mean nexus.codehaus.org. Cheers Le 1 mai 2015 3:52 PM, "Jörg Hohwiller" a écrit : > Stupid me. Too many different OSS projects in parallel. For mojo I need > to log in at nexus.sonartype.org and not oss.sonartype.org. Release is > promoted. > Sorry for confusing... > > Regards >

[mojo-dev] can not perform release - site fails

2015-05-01 Thread Jörg Hohwiller
Hi there, mvn release:perform failed. Is codehaus already down for some services? [INFO] --- maven-site-plugin:3.3:deploy (default-deploy) @ flatten-maven-plugin --- [INFO] Parent project loaded from repository: org.codehaus.mojo:mojo-parent:pom:33 [INFO] Parent project loaded from re

[mojo-dev] [jira] (MOJO-2080) NPE in FlattenMojo.isCentralRepositoryFromSuperPom(FlattenMojo.java:641)

2015-05-01 Thread JIRA
Title: Message Title Jörg Hohwiller commented on an issue

[mojo-dev] [jira] (MVERSIONS-286) NullPointerException in versions:set

2015-05-01 Thread Trevor Robinson (JIRA)
Title: Message Title Trevor Robinson closed an issue as Duplicate

Re: [mojo-dev] Sources migration to GitHub (was: [DISCUSS] Codehaus EOL and MOJO migration)

2015-05-01 Thread Baptiste Mathus
Hi guys, Quick reminder, the file https://github.com/MojoHaus/convert-to-git/blob/master/mojo-committers.list will be used for the conversion. For anyone inside that file *without the correct format*, git svn will stop and refuse to continue. So, for any line in the above file, the used format wi

Re: [mojo-dev] Re: Nexus@Codehaus shutdown plan

2015-05-01 Thread Lennart Jörelid
Great news :) 2015-05-01 13:28 GMT+02:00 Baptiste Mathus : > FYI > > 2015-05-01 11:46 GMT+02:00 Ben Walding : > >> Yes that's fine. >> >> Regards, >> >> Ben >> >> On 1 May 2015, at 19:34, Baptiste Mathus wrote: >> >> Good news :). Do you mind if I forward your answer to the mojo dev list? >> >>

Re: [mojo-dev] Sources migration to GitHub (was: [DISCUSS] Codehaus EOL and MOJO migration)

2015-05-01 Thread Baptiste Mathus
Hi, I finally wrote a rough script yesterday that seems to work. *Please review.* https://github.com/mojohaus/convert-to-git/blob/master/convert.sh I currently declare the repo I want to migrate in a dedicated file (still needs to be enriched to support sandbox and weird cases, currently only sup