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

Hi there, I guess this will not be the codebase for the final migration as there was not announcement for a "code freeze". Just in case you need several runs: For taking a dump of an SVN repo you do not even need server-side access. Just use svnsync to clone the entire repo to a full local copy an

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

Hi there, (mail was stuck in outbox - sorry for delay) sounds great. I am a big fan of the github platform. In that case we should also discuss if we create one repo for each MOJO instead of having one for all as we currently have in SVN (what actually sucks). Then only the core maintainers of eac

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

Copied here to not hit Codehaus bandwidth too heavily: https://dl.dropboxusercontent.com/u/6790263/mojo-20150407.bz2 Cheers -- Forwarded message -- From: Codehaus Support Date: 2015-04-07 13:11 GMT+02:00 Subject: Re: [mojo-dev] [DISCUSS] Codehaus EOL and MOJO migration To

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

Hi Ben, Do you think you'll be able to provide the dump some day? Btw, we're also gonna need some equivalent for JIRA... Thanks and have a good WE. 2015-03-24 10:00 GMT+01:00 Codehaus Support : > I'm away on a cancer research fundraising cycle ride at the moment. Will > be back on Monday. > >

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

As long as I get access to the dump I'll see what I can do; I'd appreciate anyone else chipping in too :) 2015-03-24 6:40 GMT+01:00 Baptiste Mathus : > No we're still waiting to hear from Ben after my last mail. > > I'll be able to work on it as soon as we have it. But any help is welcome, > and I

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

Only just saw this massive chain of emails now and would like to extend a personal thanks to all of those who put hours and blood/sweat/tears into codehaus over the years. Sad to see it go, but it looks like the content migration is well under control with you lot! :-) On Tue, Mar 24, 2015 at 6:40

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

No we're still waiting to hear from Ben after my last mail. I'll be able to work on it as soon as we have it. But any help is welcome, and I think Kristian's experience of doing the same on the Apache side would be valuable. Le 24 mars 2015 05:54, "Kristian Rosenvold" a écrit : > Did we get an s

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

Did we get an svn dump ? K 23. mars 2015 21:54 skrev "Arnaud Héritier" : Is there someone who can take the lead to and manage a little bit the migration ? Myself I afraid to have few free time before may. I hope it will change after that. On Sun, Mar 22, 2015 at 11:10 PM, Werner Guttmann wrote:

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

Is there someone who can take the lead to and manage a little bit the migration ? Myself I afraid to have few free time before may. I hope it will change after that. On Sun, Mar 22, 2015 at 11:10 PM, Werner Guttmann wrote: > Please add me (wguttmn) as well; I'd love to help with the move of the

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

Please add me (wguttmn) as well; I'd love to help with the move of the castor-maven-plugin (given that I have just moved the Castor code from Codehaus to github). Regards Werner On 22.03.2015 21:09, Mirko Friedenhagen wrote: Please add me (mfriedenhagen) as well. I think our group is small en

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

Please add me (mfriedenhagen) as well. I think our group is small enough to allow everyone full access for now. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Fri, Mar 20, 201

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

I created a "developers" team with everyone in it. For now there is no repo This group has only pull/push rights I don't know what you have in mind in term of permissions Do we keep a despots/admin group ? Do we give all rights to everyone ?? cheers On Fri, Mar 20, 2015 at 7:53 PM, Alexandre COLLI

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

What about me then? acollign :D. Have a nice weekend everyone, -- Alexandre COLLIGNON https://keybase.io/acollign https://plus.google.com/+AlexandreCOLLIGNON/ On 3/20/15 1:55 PM, Anders Hammar wrote: > And me please: andham > > /Anders > > On Fri, Mar 20, 2015 at 1:52 PM, Dennis Lundberg

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

Please add dantran -D On Friday, March 20, 2015, Anders Hammar wrote: > And me please: andham > > /Anders > > On Fri, Mar 20, 2015 at 1:52 PM, Dennis Lundberg > wrote: > >> Please add me as well: >> >> dennisl >> >> >> On Fri, Mar 20, 2015 at 9:06 AM, Stefan Birkner > > wrote: >> > Please add

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

And me please: andham /Anders On Fri, Mar 20, 2015 at 1:52 PM, Dennis Lundberg wrote: > Please add me as well: > > dennisl > > > On Fri, Mar 20, 2015 at 9:06 AM, Stefan Birkner > wrote: > > Please add me too: stefanbirkner > > > > 2015-03-20 9:02 GMT+01:00 Kristian Rosenvold : > >> krosenvold

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

Please add me as well: dennisl On Fri, Mar 20, 2015 at 9:06 AM, Stefan Birkner wrote: > Please add me too: stefanbirkner > > 2015-03-20 9:02 GMT+01:00 Kristian Rosenvold : >> krosenvold too :) >> >> >> 2015-03-20 7:47 GMT+01:00 Rickard von Essen : >>> please add me too Id: rickard-von-essen >>>

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

Please add me too: stefanbirkner 2015-03-20 9:02 GMT+01:00 Kristian Rosenvold : > krosenvold too :) > > > 2015-03-20 7:47 GMT+01:00 Rickard von Essen : >> please add me too Id: rickard-von-essen >> /Rickard >> >> On Mar 20, 2015 7:43 AM, "Milos Kleint" wrote: >>> >>> mkleint at github >>> >>> Tha

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

krosenvold too :) 2015-03-20 7:47 GMT+01:00 Rickard von Essen : > please add me too Id: rickard-von-essen > /Rickard > > On Mar 20, 2015 7:43 AM, "Milos Kleint" wrote: >> >> mkleint at github >> >> Thanks. >> >> Milos Kleint >> >> On Sun, Mar 15, 2015 at 12:30 AM, Tony Chemit >> wrote: >>> >>>

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

please add me too Id: rickard-von-essen /Rickard On Mar 20, 2015 7:43 AM, "Milos Kleint" wrote: > mkleint at github > > Thanks. > > Milos Kleint > > On Sun, Mar 15, 2015 at 12:30 AM, Tony Chemit > wrote: > >> On Sat, 14 Mar 2015 14:11:47 +0100 >> Karl Heinz Marbaise wrote: >> >> > BTW: Could yo

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

mkleint at github Thanks. Milos Kleint On Sun, Mar 15, 2015 at 12:30 AM, Tony Chemit wrote: > On Sat, 14 Mar 2015 14:11:47 +0100 > Karl Heinz Marbaise wrote: > > > BTW: Could you please add me to the organization... > > Hy herve, Can you also add me in organization. (tchemit on github) > > th

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

And me. github id: davidkarlsen codehaus id: david 14. mars 2015 14:11 skrev "Karl Heinz Marbaise" : > Hi Hervé, > > On 3/14/15 1:43 PM, Hervé BOUTEMY wrote: > >> ok, we have a clear winner: MojoHaus >> (and we'll have a statement like "formerly known as Codehaus Mojo >> project" on >> our websi

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

Hi Ben, thanks for answering. Yes, I guess we may need an SVN dump if you can provide us with it when possible. That's likely to be useful to prevent us from using codehaus bandwidth and increase your costs if we want to experiment different kind of svn->Git conversions (as we have a big svn tree

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

Hello Hervé, All right; move to the next MojoHaus incarnation. Would you please add me as well (https://github.com/lennartj) 2015-03-14 13:43 GMT+01:00 Hervé BOUTEMY : > ok, we have a clear winner: MojoHaus > (and we'll have a statement like "formerly known as Codehaus Mojo project" > on > our w

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

... This time actually supp...@codehaus.org in CC. 2015-03-14 14:52 GMT+01:00 Baptiste Mathus : > +1 please (http://github.com/batmat). > And just in case: I bought http://mojohaus.org > > Adding Codehaus support in CC: > > @CodeHaus Support: > As for migration, how do we proceed? We've got a pre

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

+1 please (http://github.com/batmat). And just in case: I bought http://mojohaus.org Adding Codehaus support in CC: @CodeHaus Support: As for migration, how do we proceed? We've got a pretty big svn tree to split in a myriad of small ones. How should we do that? I mean, I know what to do technica

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

That name must have been my largest contribution to the cause so far :) -- Sergei > >Saturday, 14 March 2015 12:43 + from Hervé BOUTEMY >: >ok, we have a clear winner: MojoHaus >(and we'll have a statement like "formerly known as Codehaus Mojo project" on >our website once migrated) >I creat

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

On Sat, 14 Mar 2015 14:11:47 +0100 Karl Heinz Marbaise wrote: > BTW: Could you please add me to the organization... Hy herve, Can you also add me in organization. (tchemit on github) thanks, tony. -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email:

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

Hi Hervé, On 3/14/15 1:43 PM, Hervé BOUTEMY wrote: ok, we have a clear winner: MojoHaus (and we'll have a statement like "formerly known as Codehaus Mojo project" on our website once migrated) I created the github organization: https://github.com/MojoHaus what are the next steps? Migrati

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

ok, we have a clear winner: MojoHaus (and we'll have a statement like "formerly known as Codehaus Mojo project" on our website once migrated) I created the github organization: https://github.com/MojoHaus what are the next steps? Regards, Hervé Le mercredi 11 mars 2015 08:54:09 Hervé BOUTEMY

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

On 3/4/15 2:16 PM, Baptiste Mathus wrote: > *Mailing list* > Google groups seems reasonable. What about freelists [0]? It seems to have everything we need and doesn't require a Google account ;-). One might argue that it is possible to subscribe to google groups with any email address but my exper

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

On 3/12/15 11:05 AM, Rickard von Essen wrote: > +1 for MojoHaus if Codehaus is not applicable. +1 for MojoHaus. We might want to have a statement like "formerly known as Mojo Codehaus" on our website. /Alex > > On Thu, Mar 12, 2015 at 10:54 AM, Arnaud Héritier > mailto:aherit...@codehaus.org>>

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

+1 for MojoHaus if Codehaus is not applicable. On Thu, Mar 12, 2015 at 10:54 AM, Arnaud Héritier wrote: > +1 for MojoHaus > > On Thu, Mar 12, 2015 at 7:41 AM, Tony Chemit wrote: > >> On Wed, 11 Mar 2015 08:54:09 +0100 >> Hervé BOUTEMY wrote: >> >> +1 MojoHaus >> >> > then we have a few proposa

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

+1 for MojoHaus On Thu, Mar 12, 2015 at 7:41 AM, Tony Chemit wrote: > On Wed, 11 Mar 2015 08:54:09 +0100 > Hervé BOUTEMY wrote: > > +1 MojoHaus > > > then we have a few proposals: > > - Mojo Extras > > - MojoHaus > > - The Mojo Project > > > > > > I really like MojoHaus > > > > Regards, > > > >

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

On Wed, 11 Mar 2015 08:54:09 +0100 Hervé BOUTEMY wrote: +1 MojoHaus > then we have a few proposals: > - Mojo Extras > - MojoHaus > - The Mojo Project > > > I really like MojoHaus > > Regards, > > Hervé > > Le mardi 10 mars 2015 09:28:59 vous avez écrit : > > I think it's a bad idea to not i

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

+1 for MojoHaus Olivier On 11 March 2015 at 18:54, Hervé BOUTEMY wrote: > then we have a few proposals: > - Mojo Extras > - MojoHaus > - The Mojo Project > > > I really like MojoHaus > > Regards, > > Hervé > > Le mardi 10 mars 2015 09:28:59 vous avez écrit : > > I think it's a bad idea to not i

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

+1 for MojoHaus On Wed, Mar 11, 2015 at 8:54 AM, Hervé BOUTEMY wrote: > then we have a few proposals: > - Mojo Extras > - MojoHaus > - The Mojo Project > > > I really like MojoHaus > > Regards, > > Hervé > > Le mardi 10 mars 2015 09:28:59 vous avez écrit : >> I think it's a bad idea to not includ

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

+1 I really like the name - MojoHaus -D On Wed, Mar 11, 2015 at 1:49 PM, Robert Scholte wrote: > +1 for MojoHaus > > Op Wed, 11 Mar 2015 12:06:34 +0100 schreef Brett Okken < > brett.okken...@gmail.com>: > > > +1 for MojoHaus >> On Mar 11, 2015 4:35 AM, "Stephen Connolly" > com> >> wrote: >> >>

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

+1 for MojoHaus Op Wed, 11 Mar 2015 12:06:34 +0100 schreef Brett Okken : +1 for MojoHaus On Mar 11, 2015 4:35 AM, "Stephen Connolly" wrote: On 11 March 2015 at 07:54, Hervé BOUTEMY wrote: then we have a few proposals: - Mojo Extras - MojoHaus - The Mojo Project I really like MojoH

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

+1 for MojoHaus On Mar 11, 2015 4:35 AM, "Stephen Connolly" wrote: > On 11 March 2015 at 07:54, Hervé BOUTEMY wrote: > >> then we have a few proposals: >> - Mojo Extras >> - MojoHaus >> - The Mojo Project >> >> >> I really like MojoHaus >> > > I am tempted to don my despot hat and decree MojoHau

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

On 11 March 2015 at 07:54, Hervé BOUTEMY wrote: > then we have a few proposals: > - Mojo Extras > - MojoHaus > - The Mojo Project > > > I really like MojoHaus > I am tempted to don my despot hat and decree MojoHaus the winner ;-) > > Regards, > > Hervé > > Le mardi 10 mars 2015 09:28:59 vous a

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

+1 I also like the CodeMaison idea :-) 2015-03-11 8:54 GMT+01:00 Hervé BOUTEMY : > then we have a few proposals: > - Mojo Extras > - MojoHaus > - The Mojo Project > > > I really like MojoHaus > > Regards, > > Hervé > > Le mardi 10 mars 2015 09:28:59 vous avez écrit : > > I think it's a bad ide

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

then we have a few proposals: - Mojo Extras - MojoHaus - The Mojo Project I really like MojoHaus Regards, Hervé Le mardi 10 mars 2015 09:28:59 vous avez écrit : > I think it's a bad idea to not include the "Mojo" name in some form. The > project has been around for over 10 years now and it wid

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

I think it's a bad idea to not include the "Mojo" name in some form. The project has been around for over 10 years now and it widely known and used in the Maven community. I think Mojo Extras is a good name, I would like to propose "The Mojo Project". -- Trygve On Tue, Mar 10, 2015 at 08:14:3

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

Another idea for a GitHub org that I recently had was a MojoHaus mash-up. That would have at least some heritage of CodeHaus Mojo brand preserved. A quick google search reveals that the name is only used on the music scene, so should be clear to use in software world. -- Sergei > >Tuesday, 10 M

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

ok, another idea: Mojo Extras (I just reserved the github org) = Mojo (ie plugins for Maven) that can't be hosted at ASF for license issues, or generally less strict rules about anything (which comes at a price: this is not a foundation, no dev protection, or anything the rules are done for) I

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

Hello Hervé, I would suggest that "mojo" is quite unknown for most developers (who are non-maven-plugin developers) out there. Few would even contemplate calling the plugins by their full - or even abbreviated - name. Whenever I hear people talking about a plugin, they simply say "the aspectj plug

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

I think the community needs a unique and recognisable name. If CodeHaus is subject to copyright or any other rights outside of public domain, then we need a replacement. To please the French people on this list, I was about to suggest CodeMaison as a replacement for CodeHaus brand, but it looks

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

2015-03-05 9:24 GMT+01:00 Hervé BOUTEMY : > Le mercredi 4 mars 2015 14:16:08 vous avez écrit : > > *Project name* > > May not be a concern, but that needs to be cleared out sooner than later. > > I think that one of the most pressing subject may indeed not be technical > > but about the name of ou

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

Le mercredi 4 mars 2015 14:16:08 vous avez écrit : > *Project name* > May not be a concern, but that needs to be cleared out sooner than later. > I think that one of the most pressing subject may indeed not be technical > but about the name of our project: what name should/could we use for the > pr

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

OK. Trying to sum up+some points that popped to mind since: *Project name* May not be a concern, but that needs to be cleared out sooner than later. I think that one of the most pressing subject may indeed not be technical but about the name of our project: what name should/could we use for the pr

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

IMHO the Apache Maven team should focus on Maven Core, (java)-build lifecycle plugins, plugin-development tools, transport (SCM, Wagon) and project-health tools. There are probably a couple of Codehaus-Mojo plugins which might be interesting to move Apache Maven (assuming legal issues will

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

2015-03-02 11:40 GMT+01:00 Sergei Ivanov : > I believe the answers to 1. and 2. are yes and yes. Maven sites can be > published to gh-pages, which is separate to the wikis. As for 3. I think it > requires investigation. There is a need for a mailing list like this, and I > am not sure if such case

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

I believe the answers to 1. and 2. are yes and yes. Maven sites can be published to gh-pages, which is separate to the wikis. As for 3. I think it requires investigation. There is a need for a mailing list like this, and I am not sure if such case is covered by the GitHub offering. -- Sergei >

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

Fair point. I would aim at getting the best of both worlds. If I absolutely *have* to move to Apache, I would. But GitHub is currently the better infrastructure and process, I feel. So ... what do we need which is missing from GitHub presently? 1. Is the GitHub issue tracker sufficient for o

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

Mailing lists _are_ important. I was not trying to imply that mailing lists should be dropped, merely stating the fact that the functionality could be procured elsewhere and plugged into GitHub. If GitHub does not provide enough flexibility in that respect, then we need to talk to GitHub produ

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

Even if I agree ML shouldn't be an issue. It's not so unimportant for us as a developer community. We need a wee bit more than just pushing and reviewing code. 2015-03-02 9:46 GMT+01:00 Sergei Ivanov : > Mailing lists are a completely orthogonal feature to the development > stack. I am struggling

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

Mailing lists are a completely orthogonal feature to the development stack. I am struggling to understand why can they not be hosted somewhere else and why the lack of mailing lists is an impediment to migration to git and GitHub. -- Sergei > >Monday, 2 March 2015 08:38 + from Trygve Laugstø

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

One of the reasons not moving to ASF is to keep the "process" much simpler/lightweighter. At least that's how I've seen it so far. The threshold to start a new plugin here at Mojos has been very small. But I guess that could be changed. Maybe we could introduce something like the sandbox over att

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

On Sun, Mar 01, 2015 at 12:14:19AM -0800, Dan Tran wrote: > Apache process may send some new potential committers away :) > > +1 for Github, but stay together under on umbrella of org.code.mojo > groupId. +1 The concern with moving to Github is their lack of mailing lists, but I guess a Google

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

is MIT license compatible with ASF license? Mojo has a few MIT ones -D On Mon, Mar 2, 2015 at 12:26 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > My vote is move to github. > > Mojo exists to hold those plugins that have licenses that are not > compatible with being hosted in

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

My vote is move to github. Mojo exists to hold those plugins that have licenses that are not compatible with being hosted in Apache. I would say we should move all compatible plugins/components to ASF and leave the license entangled plugins at mojo. Github issues is fine from my perspective. Not

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

Apache process may send some new potential committers away :) +1 for Github, but stay together under on umbrella of org.code.mojo groupId. -D btw, i found this https://github.com/codehaus-plexus so we may something similar like that? On Sat, Feb 28, 2015 at 11:26 PM, Tony Chemit wrote: > O

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

On Fri, 27 Feb 2015 12:51:18 +0100 Lennart Jörelid wrote: > I second the opinions for moving to GitHub (or Bitbucket) instead of > remaining in SVN. > If doing so, I suggest we reuse as much as possible of the GitHub > infrastructure - Wiki, Issue Tracker, Mailing lists etc. > If we are already b

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

Should we change snapshot to sonatype repo?? On Friday, February 27, 2015, Sergei Ivanov wrote: > Hi, > > I should say, if Codehaus is no more, GitHub would be my obvious first > choice of an alternative platform. > > 1. Version control. > SVN is a dinosaur and a major impediment for contributin

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

Hi, I should say, if Codehaus is no more, GitHub would be my obvious first choice of an alternative platform. 1. Version control. SVN is a dinosaur and a major impediment for contributing and integrating patches. Git provides a much more streamlined workflow from both committer's and contribu

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

2015-02-27 11:37 GMT+01:00 Arnaud Héritier : > We can ask to Ben (and sonatype/central) but I'm almost sure he'll have > nothing to let us use org.codehaus.* for existing projects. > The question may be for future new plugins. Maybe we should reserve a new > groupId and update maven to look at thi

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

I second the opinions for moving to GitHub (or Bitbucket) instead of remaining in SVN. If doing so, I suggest we reuse as much as possible of the GitHub infrastructure - Wiki, Issue Tracker, Mailing lists etc. If we are already bound for some major migrations, let's make the best of them - and a Di

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

We can ask to Ben (and sonatype/central) but I'm almost sure he'll have nothing to let us use org.codehaus.* for existing projects. The question may be for future new plugins. Maybe we should reserve a new groupId and update maven to look at this groupId in addition of org.apache.maven.plugins and

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

Good point Anders, that's indeed something we want to double-check with Codehaus people (btw, who else than Ben, is there anyone else?) 2015-02-27 10:50 GMT+01:00 Anders Hammar : > Hmmm. Is it only me that sees a problem with the org.codehaus.mojo > groupId? Can we continue to use that in the fut

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

Hi, GitHub is a very good platform. I've moved my projects from self-hosted Confluence/JIRA to GitHub completely. Extremely happy with the move. * SCM - move to GIT, why stay with SVN? You can move old SVNs to GIT with GitHub mover quite nicely. * JIRA - I currently even prefer GitHub's issue tra

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

Hmmm. Is it only me that sees a problem with the org.codehaus.mojo groupId? Can we continue to use that in the future when syncing to central? Other than that I guess this is a good time to migrate to git instead of svn. /Anders On Fri, Feb 27, 2015 at 10:38 AM, David Karlsen wrote: > Codehaus

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

Codehaus.org does not respond - already EOL? ;) The choises seem sane - except for sticking with svn. git svn and pointing to the correct places for tags and branches should make it possible to convert each module into a git repo (and use github for hosting). 2015-02-27 10:24 GMT+01:00 Baptiste M

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

Hi all, Might be old news to you, but I guess some may not be aware of that news yet: Codehaus is coming to EOL... https://codehaus.org/ And it doesn't seem like it's considered to be taken over by other staff members if I read correctly the article (IIUC, this means you cannot even apply to help