springframework-developer

[Springframework-developer] Scheduler update #3

[Ivan R. <iv...@we...>]

I've managed to spend some more time working the scheduler,
and now I'm mostly satisfied with it. Since the last time
I added the JUnit tests (with 83% coverage measured with
Clover), made changes as was suggested (most importantly
added the name field), and packaged the library as a proper
project (using the Hibernate documentation generation
method).

You can download it from here:

  http://www.webkreator.com/download/chronos-1.0m1.zip

I don't want to label it full 1.0 before I (or someone else)
actually use it in a project. Ignore the licence, I always
use GPL by default.

Trevor, do you think you could look at it and see if the
interfaces are clean enough to be used with Quartz?

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]

RE: [Springframework-developer] Scheduler update #3

[Mark I. <mar...@po...>]

Ivan Ristic <> scribbled on Monday, December 22, 2003 9:03 AM:

> I don't want to label it full 1.0 before I (or someone else) actually
> use it in a project. Ignore the licence, I always use GPL by default. 

I don't believe the ASL, which Spring is licensed under, can include GPLed
code without violating the GPL.  The LGPL would probably be ok, since it
explicitly allows linking.  

I could be wrong, but that's my understanding of the situation.  Someone
please correct me if I'm missing something.

-Mark

Re: [Springframework-developer] Scheduler update #3

[Ivan R. <iv...@we...>]

Mark Imbriaco wrote:

> Ivan Ristic <> scribbled on Monday, December 22, 2003 9:03 AM:
> 
>>I don't want to label it full 1.0 before I (or someone else) actually
>>use it in a project. Ignore the licence, I always use GPL by default. 
> 
> I don't believe the ASL, which Spring is licensed under, can include GPLed
> code without violating the GPL.  The LGPL would probably be ok, since it
> explicitly allows linking.  
> 
> I could be wrong, but that's my understanding of the situation.  Someone
> please correct me if I'm missing something.

   I don't think that ASL is compatible with GPL (or LGPL) either. But
   I had to put some kind of licence on the code and I normally use
   GPL.

   If the scheduler makes it into Spring the licence will be ASL.

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]

Re: [Springframework-developer] Scheduler update #3

[Mike Cannon-B. <mi...@at...>]

Yah, you can't really use GPL or LGPL code with Java - it would need to be
under a BSD compatible license to be usable with Spring in any distributed
applications.

Cheers,
Mike

On 23/12/03 3:58 AM, "Ivan Ristic" (iv...@we...) penned the words:

> Mark Imbriaco wrote:
> 
>> Ivan Ristic <> scribbled on Monday, December 22, 2003 9:03 AM:
>> 
>>> I don't want to label it full 1.0 before I (or someone else) actually
>>> use it in a project. Ignore the licence, I always use GPL by default.
>> 
>> I don't believe the ASL, which Spring is licensed under, can include GPLed
>> code without violating the GPL.  The LGPL would probably be ok, since it
>> explicitly allows linking.
>> 
>> I could be wrong, but that's my understanding of the situation.  Someone
>> please correct me if I'm missing something.
> 
>  I don't think that ASL is compatible with GPL (or LGPL) either. But
>  I had to put some kind of licence on the code and I normally use
>  GPL.
> 
>  If the scheduler makes it into Spring the licence will be ASL.