Maven Article

[Charles Chan <ch...@yahoo.com>]

Hi, I wrote an article on my experience with Maven and
it's now published in IBM developerWorks:

http://www-106.ibm.com/developerworks/java/library/j-maven/

Enjoy and let's convert more developers to Maven :)

Charles


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com

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

Re: Maven Article

[Rafal Krzewski <Ra...@caltha.pl>]

Aslak Hellesoy wrote:

> What I have been thinking about is to move the EAR project down along as a
> sibling with the three other sub projects, and have the EAR built via
> reactor just like the EJB, WAR and common jar sub projects. What do you
> think about this approach?

I think this is your best bet at setting up the dependencies in a sane
way. The top-level project would contain a master-POM that all contained
POMs extend, maven.xml that defines shared tags and goals plus the
machinery needed to run the reactor builds. EAR project as a sibling of
WAR etc. that depends on them seems to me a really good idea.

R.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: Maven Article

[Aslak Hellesoy <as...@netcom.no>]

Hi Charles,

Very good propaganda!

I'm currently setting up a J2EE project and I had planned to organise it
exactly like you suggest in your article. But then I came to think about a
catch 22:

Let's assume the master (EAR) Maven project works the way you suggest. It
invokes maven:reactor to build the three sub projects. So far so good. -But
if you want this same project to be able to package an EAR file with the
ear:ear goal, you also have to declare dependencies to the three sub
projects in the POM.

See the problem? Maven will never fire up properly, because it won't be able
to resolve the dependencies to the three sub components. They haven't been
built yet!

What's your secret? How do you deal with this?

What I have been thinking about is to move the EAR project down along as a
sibling with the three other sub projects, and have the EAR built via
reactor just like the EJB, WAR and common jar sub projects. What do you
think about this approach?

Cheers,
Aslak

> -----Original Message-----
> From: Charles Chan [mailto:charles_cynthia@yahoo.com]
> Sent: 8. april 2003 19:41
> To: maven-user; maven-dev
> Subject: Maven Article
>
>
> Hi, I wrote an article on my experience with Maven and
> it's now published in IBM developerWorks:
>
> http://www-106.ibm.com/developerworks/java/library/j-maven/
>
> Enjoy and let's convert more developers to Maven :)
>
> Charles
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - File online, calculators, forms, and more
> http://tax.yahoo.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