Re: [Repast-developer] Maven, Repast Development and Ibibilio

[Mark R. D. <mdi...@la...>]

Jason Woodard wrote:

>Mark,
>
>Tom and I started going down this path last fall; James Macgill also
>offered us an introduction to the Ibiblio folks, since he has a
>repository there for GeoTools.
>
>  
>
Ibiblio really has nothing to do with it. Its all Apache/Maven 
developers who establish these mandates to cover their ^$$. The process 
to get most jars onto the repository is rather simple.

>They seemed quite strict about ensuring that all jars are properly
>licensed for redistribution.  I was in the middle of verifying this
>when I got distracted by my dissertation.  (The issue was complicated
>by the fact that some of the jars distributed with RePast originate
>with Sun and either don't contain licenses or contain licenses without
>explicit redistribution clauses.)
>
>  
>
Yes, its important that the jars are distributed from their "origin". If 
repast is modifying something and repackagin it, repast should be able 
to distribute it, If its just a tool, we go to the canonical developers 
and approach them to ok its distribution. Yes, the real stinker is Sun, 
they are very restrictive about redistribution ( it really hurts the 
community overall in a big way ). Those jars will have to stay outside 
of Ibiblio and be distributed with the application. In such situations, 
RePast Developers can either start with a RePast distribution including 
it or go get it from Sun themselves.

>I'd be happy to pick this up again if there's interest.  Be warned,
>though, that getting into compliance might require moving to later
>versions of jars or refactoring to eliminate dependencies.
>
>(This would also reopen the question of whether it makes sense to move
>to a Mavenized build process.  As you remember, it was still pretty
>bloody when we experimented with it in the fall, but possibily the
>benefits would outweigh the costs.)
>
>  
>
I suspect theres going to be some growing pains here because there have 
been changes to the original tree that are not in the Mavenized 
"branch". I suspect we would need to go through and "catch up" with 
those modifications.

-Mark