You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by offbyone <ry...@iridiumsuite.com> on 2011/05/03 22:05:07 UTC
multiple project builds
I am developing an extremely large project that has a separate build
procedure for the client and the server. Currently, the project is one
large project. I am currently using Ant, but would like to embrace maven.
I understand that the "maven way" is to have a separate project per build,
but I am finding this very difficult to do since the code is fairly
intertwined. It will be very difficult if even possible for me to
completely separate the client code from the server code. This intertwined
dependency was a design decision which has resulted in code reuse. So I
don't see this as a bad design.
I would really like to use maven, so what are my options?
Is there no way to specify 2 builds in a single project?
--
View this message in context: http://maven.40175.n5.nabble.com/multiple-project-builds-tp4368244p4368244.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multiple project builds
Posted by Alex Lopez <al...@flordeutopia.pt>.
You could check out the books freely available in sonatype website
(books section), maven reference and maven by example, these really
helped me a lot to understand whan a multi-module/reactor project is and
how to arrange a good structure for it (ie separate inheritance from
modularity etc)
Em 03-05-2011 23:02, Tommy Chheng escreveu:
> Check out
> https://github.com/apache/mahout
>
> by etc, i meant any other sub-project.
>
>
> On Tue, May 3, 2011 at 2:53 PM, offbyone<ry...@iridiumsuite.com> wrote:
>
>> I am curious about the use of "etc" in your example. What is that all
>> about?
>>
>> Do you perchance know the location of any examples like this that I could
>> look at?
>>
>> --
>> View this message in context:
>> http://maven.40175.n5.nabble.com/multiple-project-builds-tp4368244p4368529.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multiple project builds
Posted by Tommy Chheng <to...@gmail.com>.
Check out
https://github.com/apache/mahout
by etc, i meant any other sub-project.
On Tue, May 3, 2011 at 2:53 PM, offbyone <ry...@iridiumsuite.com> wrote:
> I am curious about the use of "etc" in your example. What is that all
> about?
>
> Do you perchance know the location of any examples like this that I could
> look at?
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/multiple-project-builds-tp4368244p4368529.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
@tommychheng
http://tommy.chheng.com
Re: multiple project builds
Posted by offbyone <ry...@iridiumsuite.com>.
I am curious about the use of "etc" in your example. What is that all
about?
Do you perchance know the location of any examples like this that I could
look at?
--
View this message in context: http://maven.40175.n5.nabble.com/multiple-project-builds-tp4368244p4368529.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multiple project builds
Posted by Tommy Chheng <to...@gmail.com>.
Yes, you can still have a flat structure.
In app-server/etc, you can specify base-utillites/app-common as a dependency
xml block.
On Tue, May 3, 2011 at 2:21 PM, offbyone <ry...@iridiumsuite.com> wrote:
> Thanks for the reply.
>
> I am looking at something like this:
> base-utilities
> app-common
> app-client
> app-server
>
> With these modules the dependencies look something like this:
> base-utilities -> app-common -> app-client, app-server
>
> Based on this representation could I still have a flat directory structure
> like this:
> app
> ...base-utilities
> ...app-common
> ...app-client
> ...app-server
>
> or do I need this?
> app
> ...base-utilities
> ......app-common
> .........app-client
> .........app-server
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/multiple-project-builds-tp4368244p4368451.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
@tommychheng
http://tommy.chheng.com
Re: multiple project builds
Posted by offbyone <ry...@iridiumsuite.com>.
Thanks for the reply.
I am looking at something like this:
base-utilities
app-common
app-client
app-server
With these modules the dependencies look something like this:
base-utilities -> app-common -> app-client, app-server
Based on this representation could I still have a flat directory structure
like this:
app
...base-utilities
...app-common
...app-client
...app-server
or do I need this?
app
...base-utilities
......app-common
.........app-client
.........app-server
--
View this message in context: http://maven.40175.n5.nabble.com/multiple-project-builds-tp4368244p4368451.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multiple project builds
Posted by Tommy Chheng <to...@gmail.com>.
I assume your client and server projects build separate JAR files?
If there are intertwined code, you can have:
project-core
project-server
project-client
Both project-server/project-client can have a dependency on project-core
You can use parent POM or module poms to build
http://stackoverflow.com/questions/1992213/maven-parent-pom-vs-modules-pom
On Tue, May 3, 2011 at 1:05 PM, offbyone <ry...@iridiumsuite.com> wrote:
> I am developing an extremely large project that has a separate build
> procedure for the client and the server. Currently, the project is one
> large project. I am currently using Ant, but would like to embrace maven.
>
> I understand that the "maven way" is to have a separate project per build,
> but I am finding this very difficult to do since the code is fairly
> intertwined. It will be very difficult if even possible for me to
> completely separate the client code from the server code. This intertwined
> dependency was a design decision which has resulted in code reuse. So I
> don't see this as a bad design.
>
> I would really like to use maven, so what are my options?
>
> Is there no way to specify 2 builds in a single project?
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/multiple-project-builds-tp4368244p4368244.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
@tommychheng
http://tommy.chheng.com