Hi folks,
The main advantage of integrating the extensions to the main build is to
centralize everything : you build the framework, you build the extensions.
We benefit of our C.I. infrastructure etc. I can't see what the problem is.
Look at other frameworks, that's how they do it (Spring,
Hi Samuel,
2. Validate what belongs to core and what doesn't, I do believe
that:
3. Stripes Security should be moved from plugin to core
(Security and JAAS integration is a fundamental feature in any
Java web framework).
I disagree with that. By your logic of not
Hi Freddy,
On Tue, Apr 19, 2011 at 1:40 PM, Freddy Daoud xf2...@fastmail.fm wrote:
Hi Samuel,
2. Validate what belongs to core and what doesn't, I do believe
that:
3. Stripes Security should be moved from plugin to core
(Security and JAAS integration is a fundamental feature
Moren,
Clearly we all agree that Ant alone isn't going to cut it and as such we
should focus on removing it.
The debate as to whether to go to Maven or Ivy or something else also is
really not a big debate IMHO as we have partial Maven build capabilities
build into the project today!
Hi there,
+1 for Maven. It simplifies development and build process - especially
for different IDE's and developer machines. Plus it enables me to
checkout and build the trunk within 5 minutes. Hudson/Jenkins
configuration will also be simplified. This would also enable us to
make use of plugins
I'm not going to copy the entire thread, and I'm not responding to any one in
particular.
Not being a maven fan, even I can agree with the conversion to Maven. The
primary reason is that Maven has become a de facto portable project meta data
that all of the IDEs support well, and makes IDE
