[Biojava-dev] next steps

[Andy Yates]

Maven's big plus points are easy integration into just about any IDE &
its transitive dependency management capability. On a project like
BioJava (need people to get setup & running quickly over a wide range of
development environments) these two points really make it one of the
only viable choices I can would use. This isn't to say the other build
systems are not as good/better (rake, raven, gant, gradle, ant) just
they do not fit the bill as well.

Andy

juber patel wrote:
> just a small observation:
> 
> Maven may not be easy to use and switch to maven should be done after
> some consideration. I have personally not used it, but have seen
> people on the Mahout list struggling with maven. Its utility may not
> justify its complexity.
> 
> juber
> 
> 
> On Thu, May 28, 2009 at 10:01 AM, Andreas Prlic <andreas at sdsc.edu> wrote:
>> Hi Scooter,
>>
>> quick update: There is also an eclipse plugin for JDepend, that
>> provides a user interface to browse thought the dependencies.
>>
>> As I already mentioned earlier, I had some quick progress with the
>> maven plugin to convert the project to maven and create a first pom.
>> At the moment I am testing how  best to create  sub-projects that
>> should contain the modules.  The plugin does not seem to make it easy
>> to create new modules, so I agree with your earlier suggestion that it
>> is best to modularize first and the mavenize 2nd... Should we create a
>> branch in svn and play around with refactoring there and once we are
>> happy with it we can switch that branch to become the trunk?
>>
>> Andreas
>>
>>
>>
>>
>> On Mon, May 25, 2009 at 3:59 PM, Scooter Willis <HWillis at scripps.edu> wrote:
>>> I attached the JDepend output for BioJava. This will help on the circular
>>> dependencies where core classes should not have dependencies on other
>>> packages and if they do it should be refactored into the core class.
>>>
>>> Scooter
>>> ________________________________
>>> From: mike.smoot at gmail.com on behalf of Mike Smoot
>>> Sent: Mon 5/25/2009 1:07 PM
>>> To: Scooter Willis
>>> Cc: Andreas Prlic; biojava-dev at lists.open-bio.org
>>> Subject: Re: [Biojava-dev] next steps
>>>
>>>
>>>
>>> On Mon, May 25, 2009 at 7:48 AM, Scooter Willis <HWillis at scripps.edu> wrote:
>>>> I was looking at the biojava code yesterday to see how easy it would be to
>>>> divide up into functionally grouped jars based on package hierarchy. I tried
>>>> to find some refactoring tools that would give a network graph view of class
>>>> relationships. It is simple enough to parse source for import statements and
>>>> build some sort of graph relationship tool. It is also easy enough to start
>>>> dragging packages around to different projects in netbeans and resolve
>>>> compiler errors.
>>> JDepend is a nice tool for evaluating package dependencies.
>>>
>>> http://www.clarkware.com/software/JDepend.html
>>>
>>>
>>> Mike
>>>
>>> --
>>> ____________________________________________________________
>>> Michael Smoot, Ph.D.               Bioengineering Department
>>> tel: 858-822-4756         University of California San Diego
>>>
>> _______________________________________________
>> biojava-dev mailing list
>> biojava-dev at lists.open-bio.org
>> http://lists.open-bio.org/mailman/listinfo/biojava-dev
>>
> 
> 
>