I'd like to release version 2.7 of the Cobertura Maven Plugin
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11226&version=19561
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11226&status=1
Stag
Title: Message Title
Stefan Svensson updated an issue
Title: Message Title
Stefan Svensson created an issue
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
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
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
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
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
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
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
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
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
Title: Message Title
Stefan Birkner assigned an issue to Stefan Birkner
Title: Message Title
Stefan Birkner updated an issue
14 matches
Mail list logo
