• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Maven Optimism
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Maven Optimism


  • Subject: Re: Maven Optimism
  • From: Henrique Prange <email@hidden>
  • Date: Thu, 10 Jul 2008 00:36:10 -0300

Hi all,

Am I late for the party? :)

Anjo Krank wrote:


macbook:Wonder ak$ wc `find . -name pom.xml`|tail -1
    2152    2438   66007 total

It's still more than zero (if someone would consider this a measure at all).

"It's not the size, it's the magic it does". :p

I think the measure is good to show that you don't have to write tons of XML code. But show that you have to write some XML code. Fair enough.


Thirdly from what I've seen, someone needs to change all these files whenever we bump a version. All of Ulrichs commits so far where these xml fixes. All *I* need to do is set one property.

Wonder don't use Maven for the release process. So, we have to update the POMs manually to reflect the version change. When Maven is used, the release plug-in take care of the changes. You don't have to worry about any property.


I'm reviewing the POMs of Wonder and removing some redundant data present on child POMs (thanks Pierce for updating all the POMs). I hope we can reduce the amount of change. Anyway, I'm not bothered of doing a find and replace on Eclipse from '<version>4.0.0-SNAPSHOT</version>' to '<version>5.0.0-SNAPSHOT</version>' on every POM file.


The other issues I have with it is that I actually *need* the flexibility in deployment structure. In some projects I *don't* want all-embedded builds as that stuff goes out of hand with 7 apps*all the frameworks. The resulting release tops 250M. So I want some of them embed only some jars. Show me how this works with maven *without* writing any "goals" or "mojos".

<scope>provided</scope> as described by Lachlan. You can also use <skipAppleProvidedFrameworks>true</skipAppleProvidedFrameworks> on maven-wolifecycle-plugin to skip all Apple libraries in one shot.



So in summary, maven may or may not be nice. But I've been building Wonder with the build files for 7 years now and they haven't really changed a lot in this time. They do the roughly the same as some 20MB tool chain where you *still* have to write java plugins for.



I hope you don't stop doing good stuff with Ant builds. If we can also build Wonder with Maven, it is a plus.


Cheers,

Henrique
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Maven Optimism (From: Pierce T.Wetter III <email@hidden>)
 >Re: Maven Optimism (From: Anjo Krank <email@hidden>)

  • Prev by Date: AjaxUpdateLink and Query Parameters
  • Next by Date: Re: Maven Optimism
  • Previous by thread: Re: Maven Optimism
  • Next by thread: Re: Maven Optimism
  • Index(es):
    • Date
    • Thread