Yes this is a very good idea. The modern way to go is to create an
archetype.
Is that also a goal for M2 or for a later stage?
/Ludwig
-----Ursprungligt meddelande-----
From: Jeffery Painter
Sent: Thursday, June 23, 2011 10:02 PM
To: Turbine Developers List
Subject: Re: [DISCUSS] What happens after M1?
My biggest complaint would be documentation. It is difficult for new users
to get on board with the complexities of Turbine without a basic sample
application they can download and explore which takes advantage of most of
the major components that Turbine has to offer.
I want to help out in this area, but I've been swamped. I'm hoping that as
I get back into development, I can contribute some along the way.
The various versions of Turbine, getting build environments configured
correctly, etc. lead to confusion to those who are un-initiated.
The old TDK made things very simple. I think the maven plugin is still the
way to go, but getting a version which works with a modern release of
Maven seems to me an area that should see some attention.
Just my 0.02.
--
Jeffery Painter
M2 of course...
But seriously:
- What do we want to achieve until M2?
- When shall we schedule the M2 release?
My thoughts
- Replace the security service with the Fulcrum components
... and remove the old one. As the security components of Fulcrum are
not released yet: Anyone having a better idea?
- Think about the OSGi integration again.
A service provider is ready to be committed.
- Some annotation support for modules, tools and services
This would remove the need for the fixed package layout. But maybe this
is Turbines biggest advantage? WDYT?
- Dependency injection for modules
Just like the pull tools with different lifestyles. Services may be
simpler to use.
- More sophisticated caching for modules
Currently, modules need to be threadsafe for caching to work. This puts
a burden on developers, especially because caching is normally off
during development and you see the issues only in production.
- Maven staging
Like here: http://www.apache.org/dev/publishing-maven-artifacts.html
Anyone having experience?
- A common parent POM for Turbine Core and Fulcrum
Any other ideas, comments, criticism etc. are most welcome.
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]
