[scxml-eclipse] m2 build in addition to layout

[Rahul Akolkar <ra...@gmail.com>]

Long,

Thanks for getting started with your project in SVN. I will make a few
comments that will require some moving around in SVN at some point
(not urgent). However, please note that any reorganization in SVN must
use 'svn move' rather than deleting and re-adding files or directories
-- this way we retain history in SVN and avoid remove/add SVN noise.

First comment is that while the directory structure in your project
trunk is close to the m2 (Maven 2) standard, we don't have a m2 build
yet. The projects have been checked in as Eclipse projects. This is
perfectly fine to start with, but at some point we should think about
moving to a multi-module m2 build:

  http://maven.apache.org/guides/getting-started/index.html#How_do_I_build_more_than_one_project_at_once

Here is one example of a Commons component that does multiple modules
(note the parent pom.xml in trunk and the various modules):

  http://svn.apache.org/repos/asf/commons/proper/jci/trunk/

It'd be great to start thinking about adding an m2 build and what that
would entail.

-Rahul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [scxml-eclipse] m2 build in addition to layout

[Xun Long Gui <us...@gmail.com>]

Hi Rahul,

Thank you for your review, I will use SVN move command rather than
delete/add command and also i will think about this m2 build things :-)

2010/5/18 Rahul Akolkar <ra...@gmail.com>

> Long,
>
> Thanks for getting started with your project in SVN. I will make a few
> comments that will require some moving around in SVN at some point
> (not urgent). However, please note that any reorganization in SVN must
> use 'svn move' rather than deleting and re-adding files or directories
> -- this way we retain history in SVN and avoid remove/add SVN noise.
>
> First comment is that while the directory structure in your project
> trunk is close to the m2 (Maven 2) standard, we don't have a m2 build
> yet. The projects have been checked in as Eclipse projects. This is
> perfectly fine to start with, but at some point we should think about
> moving to a multi-module m2 build:
>
>
> http://maven.apache.org/guides/getting-started/index.html#How_do_I_build_more_than_one_project_at_once
>
> Here is one example of a Commons component that does multiple modules
> (note the parent pom.xml in trunk and the various modules):
>
>  http://svn.apache.org/repos/asf/commons/proper/jci/trunk/
>
> It'd be great to start thinking about adding an m2 build and what that
> would entail.
>
> -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
Best Regards

Gui Xun Long (桂训龙)