|Subject:||Re: Migrate to mercurial / git and mavenize project?|
|From:||Daniel Lopez (gree...@dev.java.net)|
|Date:||Nov 14, 2010 7:17:30 am|
I recently migrated one of my own projects to Mercurial and Maven, in order to be able to use SonaType offer of a public maven repository for OS projects, so I could help if necessary. One question though, as I "started from scratch" instead of migrating from CVS: which tool did you use to migrate the CVS repository to Mercurial? I have been able to migrate from SVN to Mercurial, but couldn't find a tool that worked for me from CVS to Mercurial. That was a long time ago though, so hopefully things have improved a bit. I'm planning to migrate all my projects to Mercurial as soon as this Kenai infrastructure move happens. I don't want to be tied again to a centralised repository where getting the real repository is so hard :(.
2010/10/16 Farrukh Najmi <farr...@wellfleetsoftware.com>
On 10/15/2010 03:30 PM, Yoko Harada wrote:
I am starting to use this good project and would like to contribute back to the work as a good citizen.
Specifically I offer to do the following:
Migrate project from CVS to hg (mercurial) or git whichever is preferred. CVS and svn are so old at this point. Migration will preserve all previous version history from CVS Mavenize the project so that all build and config management is done by maven instead of ant and all releases are properly versioned
Is there support for above? Please let me know. Note I have sent request to join dev team and already have a contributors agreement on file.
Good suggestion. I guess mercurial is among the choices since OpenJDK project uses it on java.net.
Anyway, how many script engines are still actively developed
onscripting.dev.java.net? I worked for JRuby engine before, but now it has been totally re-implemented and included in JRuby. The code base is not cut out but definitely outdated. I think Groovy engine is also included in Groovy now. Any other engines left this project?
There are many engines under the codebase. I am initially only interested in the xpath engine. I could just copy the 2-3 classes into my own project but thought it would be better to fix this project as proposed. I have already migrated it to an hg repo which I can copy to project's server once I get the green light from the dev team and authorization on the server. I have also started mavenizing the hg repo's clone locally. It seems it can all be done quickly and we can fine tune once its in place for all to see.
-- Regards, Farrukh