+1 for profile jar Idea. -1 for removing combined jar.

I agree with John and besides, there’re situations that is pretty useful, e.g.  when using shrinkwap mavenresolver it’s easier having one combined jar (less code to write and keep)

//war is a shrinkwrap web archive.

war.addAsLibraries(DependencyResolvers.use(MavenDependencyResolver.class)

.artifact(“org.jboss.seam.faces:seam-faces:3.1.0-SNAPSHOT”)

                        .resolveAs(GenericArchive.class));

Atenciosamente,

José Rodolfo Carrijo de Freitas
Analista de Sistemas
Pesquisa e desenvolvimento

Softplan/Poligraph

+ 55 48 3027-8000

www.softplan.com.br

De: seam-dev-bounces@lists.jboss.org [mailto:seam-dev-bounces@lists.jboss.org] Em nome de Dan Allen
Enviada em: quinta-feira, 9 de junho de 2011 21:04
Para: Jordan Ganoff
Cc: seam-dev@lists.jboss.org
Assunto: Re: [seam-dev] Removing the combined jar

On Thu, Jun 9, 2011 at 20:00, Jordan Ganoff <jganoff@gmail.com> wrote:

+1 for "profile" jars and removal of the combiner jar.

I'd like to see a friendly user interface for choosing modules which would generate the required Maven/Gradle/Ivy dependency list you can copy/paste... that is of course if you're not using Forge. This would be hosted at the Seam University for example.

That might be best for our new project site, which is in the ice box while we fight off some oppression. "Help! I'm being oppressed!"

We could do this with a little jQuery magic :)

-Dan

--

Dan Allen

Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction