[Biojava-dev] more updates...

[Richard Holland]

What bit of the code is it actually used for? Do we still need to do  
that?

Either way, the easiest solution is to make bytecode.jar into its own  
separate maven/svn project. It's not really bio-specific and so could  
live quite happily as its own project.

On 5 Sep 2009, at 04:40, Michael Heuer wrote:

> Andy Law (RI) wrote:
>
>> Andreas,
>>
>> On 4 Sep 2009, at 07:53, Andreas Prlic wrote:
>>
>>> Hi,
>>>
>>> quick update: new modules:
>>> biojava-biosql and
>>> biojava-gui
>>> biojava-das compiles, still talking off list with Jonathan about
>>> details.
>>>
>>> mvn install works fine for me on the current svn.
>>
>>
>> We can't get a clean check-out to build on our systems at Roslin.
>>
>> I have Trevor Paterson (my local maven maven) working on detailing  
>> why
>> not - he'll be joining us later on the list to give us a rundown.
>>
>> First issue is the bytecode jar. I recognise that you have stuck it
>> into a folder with a README file, but that is not a good solution.  
>> The
>> folder that you have put it in is not displayed in the Project view  
>> of
>> the Netbeans IDE because it is not a standard maven location.
>> Obviously the best solution would be to include the bytecode source  
>> as
>> a subproject and have it build or alternatively to publish the
>> bytecode jar into a publicly accessible (central) maven repository.
>
> Perhaps the biojava code that depends on bytecode.jar should be  
> refactored
> to use BCEL or some other third party bytecode generation library.
>
>   michael
>
> _______________________________________________
> biojava-dev mailing list
> biojava-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/biojava-dev

--
Richard Holland, BSc MBCS
Operations and Delivery Director, Eagle Genomics Ltd
T: +44 (0)1223 654481 ext 3 | E: holland at eaglegenomics.com
http://www.eaglegenomics.com/