From my experience Maveninzing an existing build system is never a good
idea. What is probably of more use to people is if a POM was generated &
the biojava files uploaded to a maven repository (or host it on our
website). That way it would keep people happy who are using the
dependency management systems (I think buildr, raven & the alike can use
the same systems as Maven2) & means we don't have to go through the
heartache of reconfiguring Maven/our codebase to friendly to one of the
other.
Andy
Richard Holland wrote:
Hello. BioJava 3 will make use of Maven. It's currently undergoing
some use-case development to work out what to work on first, but we
have a shell of a maven project already in our subversion hierarchy
(under the biojava3 branch of the biojava-live project) and will set
it up in the main maven repository when it's ready for release.
Thanks for the offer though. If you're keen, you could go ahead and
maven-ize the existing BioJava JAR files (version 1.6)? But, you would
need to preserve the existing Ant config as well so that existing
users are not affected.
cheers,
Richard
2008/7/5 James Carman <[EMAIL PROTECTED]>:
Would the biojava project be interested in being "mavenized"? I'd be
willing to help get you guys set up if you'd like. Also, it'd be nice
to have biojava in the main maven repository.
_______________________________________________
Biojava-l mailing list - [email protected]
http://lists.open-bio.org/mailman/listinfo/biojava-l
_______________________________________________
Biojava-l mailing list - [email protected]
http://lists.open-bio.org/mailman/listinfo/biojava-l
_______________________________________________
Biojava-l mailing list - [email protected]
http://lists.open-bio.org/mailman/listinfo/biojava-l
