Hi Thomas,

I think it is ok to remove or deprecate TorqueSchedulerService and remove 
SQL script generation. If you have a lot of jobs may be it´s useful, but 
more appropriate in Fulcrum Quartz or better Fulcrum Security, because of 
the dependencies and it´s a kind of security question having scheduled 
jobs configuration in a database, isn´t it? ;-). 

BTW: In Fulcrum Security the Opensymphony and Turbine Adapters seem to be 
deprecated or otherwise removable.

@4.0FinalRelease
I think it would be not a bad idea to set an release date target, e.g. in 
December or January for 4.0 final, if it´s only about internal stuff. Then 
we could focus, what is really needed, (doing some more cleanup?) ...

@ApacheCon:  I should definitely decide it this week (coming to Apache 
Core). You could make it? Siegfried as well?

Best regards, Georg





Von:    Thomas Vandahl <t...@apache.org>
An:     Turbine Developers List <dev@turbine.apache.org>
Datum:  27.07.2015 19:43
Betreff:        Re: Antwort: Re: Turbine 4.0 M2 Archetype Trunk Release



Hi Georg,

On 27.07.15 17:19, Georg Kallidis wrote:
> wow, it seems you updated the scheduler already! Tests are running 
> successfully here (Windows, Java 1.7). 

Good to know. I guess some docs are still missing.
Do we want to deprecate the TorqueSchedulerService now? If so, I could
remove the whole SQL script generation stuff from the POM and make
Torque an optional dependency. WDYT?

> Do you think Turbine M2 release is ready for take-off (in September or 
> earlier)? ;-) We could release the archetype build then soon after this. 


Yes, if it's a milestone release. I would like to clean up the module
stuff and RunData/PipelineData mess before going 4.0 final.

> P.S: More upcoming releases are Fulcrum Testcontainer and Yaafi 
hopefully. 
> Wasn´t a new Fulcrum Script in discussion, of course without backporting 

> to Java 8 Nashorn (as far as I know ;-) ..

Anybody going to ApacheCon Budapest this year? Perhaps we could do a
little hacking together?

Bye, Thomas.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@turbine.apache.org
For additional commands, e-mail: dev-h...@turbine.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@turbine.apache.org
For additional commands, e-mail: dev-h...@turbine.apache.org

Reply via email to