This is something we can consider after the release of 1.5.4. I didn't feel
the need to add a Maven build in the first place, and I surely don't like
the idea of having to move stuff all around to accommodate it so there will
be resistance.
-Ben
On Sun, Oct 31, 2010 at 11:17 AM, VANKEISBELCK Remi <r...@rvkb.com> wrote:
> Hi Nathan,
>
> In order to keep the current tooling (ant, ide settings, scripts, etc)
> working, and to get the first maven build working smoothly without being
> intrusive, it has been agreed that nothing had to be changed.
>
> Now that it works, I already talked about some refactoring of the folders
> to allow less config in poms, and more importantly, to allow tests to be in
> the same module than the core code.
>
> For the moment, due to the folder layout that was imposed, I had to create
> a specific module for the unit tests. This means that the core module is
> built (and deployed if you do mvn deploy) even when tests fail. It only has
> to compile to get installed/deployed into maven repos. That sucks (not that
> word again...) a lot, and IMHO is the main reason to so some small
> refactorings.
>
> Ben ? Have you thought about it a little ? Would you mind if I do some
> small surgery in 1.5.x and trunk so that we have the tests in the core
> module ?
>
> Cheers
>
> Remi
>
>
> 2010/10/31 Nathan Maves <nathan.ma...@gmail.com>
>
>> Just curious if anyone has thought to migrate the current layout of the
>> stripes code to use more Maven conventions?
>>
>> Nathan
>>
>
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
