Maven Dependency Profiles

[wesleyhales]

Great news about the move toward maven!... I'm trying to setup a project using the dependency profiles. If I understand correctly from the readme.txt file in profiles, all one would have to do is:

 <dependency>
 <groupId>org.jboss.seam.profile.functional</groupId>
 <artifactId>seam-ui-facelets</artifactId>
 </dependency>

 <dependency>
 <groupId>org.jboss.seam.profile.functional</groupId>
 <artifactId>seam-security-all</artifactId>
 </dependency>

in the pom and all jars/dependencies should be added into the project. Also, I made the root.pom.xml my parent and snapshots.jboss.org/maven2 is my repo. The dependencies can't be found and nothing gets downloaded, am I missing anything?

One other thought for the overall design of the profiles - for Tomcat+EJB vs. JBoss, you will have drools and jbpm in the war for Tomcat and in the root of the ear for Jboss. JSF RI won't be included for JBoss (normally) and will be for Tomcat. With all the mixing and matching for the 2 containers it seems that it may be better to have a division in the profiles or actually use the profile section of the pom for organizing of what you have already created. Just an idea...

[pmuir]

Oops, that stuff should have been deleted.

http://in.relation.to/Bloggers/SeamPublishedToMaven (now copied into the docs) is your best guide.

Michael also blogged about this: http://www.michaelyuan.com/blog/2007/10/02/jboss-seam-project-setup-with-maven/

We need feedback and ideas about how to best use the Maven support.

Profile support definitely needs to split down library/deployment lines as you suggest. Unfortunately I think Maven 2.0 doesn't offer great support for this (it's just fine if you use the seam root pom as your parent pom, but many people don't like this idea and I understand why).

You can expect to see profiles appearing in the root pom pretty soon (to support the examples).

I understand its dependency profiles are better in Maven 2.1 - I plan to look at this soon.