Migration from kenai.com (in English)

» Back to forum topics
  2 posts   Feedicon  
Replies: 1 - Last Post: January 13, 2012 03:12
by: dnadezhin
« Older Topic » Newer Topic
showing 1 - 2 of 2
 
dnadezhin
Defaultpersonimage
Posted: January 13, 2012 02:49 by dnadezhin
» Permalink
The announcement on kenai.com home page says: "The transition from kenai.com to java.net has begun. Existing projects will continue to be maintained on kenai.com until late 2012." If we propose JInterval as a reference implementation of P1788 then it will not be desirable to change the URL of our project in a few months. We should jump to another site now.

Two sites come to mind
 
dnadezhin
Defaultpersonimage
Posted: January 13, 2012 03:12 by dnadezhin
» Permalink
The advantages of java.net
  • The same infrastructure as kenai.com , so we can copy the current content from kenai.com to java.net .
  • Maven support. java.net users can publish artifact in the Central Maven Repository

The advantages of github
  • Social git . External developers can make forks of the project's repository and make changes their. It is possible to visualize all forks using Web tool. Then external developers can send pull request to the main developer. And the main developer can either pukk or reject.


There are links where people tell how they maintain their maven repositories in github. However, this is a way to create own maven repository, this is not a way to publish in the Cental Maven Repository
Replies: 1 - Last Post: January 13, 2012 03:12
by: dnadezhin
« Older Topic » Newer Topic
  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2010, Oracle Corporation and/or its affiliates
(revision 20120518.3c65429)
 
 
Close
loading
Please Confirm
Close