In this case, we'll continue to use our maven archetypes for project creation and
forge (or ROO) for code generation.
We've not exactly set between Forge and ROO, we need to create a dumb plugin to
compare those technologies - it will wait, we're evaluating Seam 3 before.
On paper, I would prefer Forge - it seems quite simpler.
Moreover I don't like ROO's ITDs all over the place.
Once more thanks for your clear answers !
De : "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com>
À : Adrian Gonzalez <adr_gonzalez(a)yahoo.fr>; forge-users List
Envoyé le : Mardi 25 Octobre 2011 18h55
Objet : Re: [forge-users] Maven archetypes
You can use Forge on any Maven project (even projects generated using Archetypes.) We
would like to be able to run archetypes from within forge as well, but currently don't
have that feature yet. For now you can generate an archetype using Maven, then use Forge
on the result - that will work fine :)
If you are interested in getting the archetype generation working in Forge, we have a
feature request you could pick up!
I hope this makes sense,
On Tue, Oct 25, 2011 at 9:28 AM, Adrian Gonzalez <adr_gonzalez(a)yahoo.fr> wrote:
Is it coherent to use maven archetypes for project creation AND Seam Forge for code
generation only ?
Or is it a rather complicated or *no future* solution ?
The point is :
* there are a lot of maven archetypes all around internet.
* we also have some archetypes in our company and there's no value migrating those
ones to forge.
* m2e for eclipse is becoming widespread, people are (becoming?) used to use New Project
> Maven Projet > Use Archetype...
My sentiment is that this approach can be viable if forge code generation plugin
(scaffold, richfaces, etc...) are 'universal' plugins (by universal I mean : can
be applied to any project - generared by Forge or no) - but I'm really a forge
forge-users mailing list
Lincoln Baxter, III
"Keep it Simple"