Hi all, the archetype seems to be now pretty ready and I would prepare a release.
What do you think? Should we wait for the intake release? But Turbine 4 RC is waiting too .. ;-) I would recommend to release this archetype soon, because then the archetype trunk could be updated soon and this might be quite useful - having the archetype ready at hand as a test environment for Turbine 4. Have we not found this way some bugs now? Best regards, Georg Von: "Georg Kallidis" <[email protected]> An: "Turbine Developers List" <[email protected]> Datum: 07.11.2016 15:53 Betreff: Re: Re: Errors found trying to use the new Turbine4-M2 Archetype Hi Thomas, @JNDI That´s a good idea, to appear like a well-behaved practicioner ;-) I´ll check what´s needed to get it to work .. update is coming soon.. Best regards, Georg Von: Thomas Vandahl <[email protected]> An: Turbine Developers List <[email protected]> Datum: 05.11.2016 12:35 Betreff: Re: Errors found trying to use the new Turbine4-M2 Archetype Hi Georg, On 02.11.16 16:30, Georg Kallidis wrote: > If you think it´s ok, we have really to prepare release. Then I would > suggest to first release Fulcrum Intake and Security, test it in Turbine > 4.0, and only after this release the latter. As I discussed with Jeffery earlier, I would like to insist on the JNDI configuration as a recommendation of best-practice to the user. I believe it is simply wrong to have credentials for database access in the application. Following the path of best-practice recommendations, I modified some of the modules to take advantage of the new Turbine annotations. However I have yet to test this before commit. Moreover, in the new archetype plugin you can execute maven goals at the end of the generation process. So we could prepare the Turbine application to be ready to run according to Jefferys how-to. WDYT? Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
