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 <davidkarl...@gmail.com> wrote: > 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 Mathus <bmat...@batmat.net>: > >> 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). >> >> So the question is, where do you thin the MOJO project go? And how to do >> we handle the migration? >> >> To sum up quickly, we use: >> * SCM : SVN (which would make github a hard choice for migration) >> * JIRA? Ask atlassian for a JIRA SaaS? >> https://www.atlassian.com/opensource/overview >> * CI? Ask CloudBees? >> https://www.cloudbees.com/resources/foss/program-details >> >> WDYT? >> >> -- >> Baptiste >> > > > > -- > -- > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen >
