Here's the other post from DAllen regarding this topic:
Dan Allen - 23/Oct/08 11:57 AM
I welcome the idea of Maven's archetype plugin becoming more flexible. The biggest issue right now is that like many Maven features in the past, it ain't ready yet. Therefore, it's not useful yet.
I want to briefly mention (since this is not a forum and we shouldn't be threading opinions) why I don't think Maven is best for our users. First, 'ant explode' is extremely fast and that is not something Maven can do because it has to go through its whole life cycle. Plus, Maven does not have built-in support for dual source directories, so doing hot deployment of Java classes is a huge hack. Times will change I am sure, but seam-gen has to stick with what works today and evolve as time goes on.
Ok, so out for Seam 2 and Maven 2 I guess?
Other problems reported here: http://seamframework.org/Community/MavenSeamArchetype
So what about Seam 3 and/or Maven 2/3?
There was another thread I started on here about the build number and one guy recommended Maven as the best solution. Can I do that mojo plugin with Ivy instead of Maven? Sorry, I have no experience with Maven or Ivy...
Francisco Peredo wrote on May 27, 2009 01:02:
Yes, I also answered to that post, proposing you to use Ivy build number management task, and I see no advantage in the Maven solution over the Ivy solution that I proposed.
Can you explain me exactly what feature of mojo did you find particularly advantageous?
The problem is I didn't look at the Ivy alternative. I just did. It looks very similar but makes no explicit reference to svn. This is a possible alternative then as I've heard it's not too difficult to incorporate Ivy with Ant (as compared to using Maven only and changing your project structure, etc.)
thx for the tip!
Arbi Sookazian wrote on May 27, 2009 17:23:
The problem is I didn't look at the Ivy alternative. I just did. It looks very similar but makes no explicit reference to svn.
Well, I integrated it with svn using the ivysvn project.
This is a possible alternative then as I've heard it's not too difficult to incorporate Ivy with Ant (as compared to using Maven only and changing your project structure, etc.)
thx for the tip!
In my experience, integrating Ant with Ivy is lot easier than learning to use Maven. I also do not like Maven because with Maven is the Maven way or the highway. You can not bend Maven to you will.
There are WAY too many frameworks that are required in Java EE nowadays. IMHO it's better to be a .NET developer or LAMP, etc.
I'm really getting tired of reading all these specs and books and don't have the luxury of time anymore.
JEE = flexibility and choice
.NET = easier life and productivity
Which do you really prefer at the end of the day?
You want to build your app and go home and spend time with your hobbies and family, etc.
JEE just gets worse and worse year after year in this regard...