[
http://jira.jboss.com/jira/browse/JBSEAM-225?page=comments#action_12352290 ]
Petr Ferschmann commented on JBSEAM-225:
----------------------------------------
Hello,
I have created Seam Maven integration. I have created "profiles" - you just say
"I want to use Seam with PDF" and it will add all required dependencies.
I have also created few archetypes. And now I am improving the dependencies and creating
SeamGen for Maven.
See
http://software.softeu.cz/seam/ .
I think this can help usage of Seam with Maven.
Maven 2 support
---------------
Key: JBSEAM-225
URL:
http://jira.jboss.com/jira/browse/JBSEAM-225
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 1.0 beta 2
Environment: Maven 2.0.x
Reporter: Tuomas Kiviaho
Mavenizing of the project would be very helpful when using cvs shapshots instead of
prebuild releases.
It seems that all of the 3rd party projects previously available separately have been
merged together as thirdparty-all.jar. Some of the 3rd party jars are missing like
jsf-facelets.jar which should be some older version than the current release.
What is needed is a pom.xml currently producing both jboss-seam.jar and jboss-seam-ui.jar
and having all of the dependencies enlisted. Most of the dependent projects are already
available by default or then they exist in JBoss maven repository (refer to next gen
jboss build system). I see that (propably missing) installments like jBPM have similar
feature requests. pom.xml functions as a documentation where to place manually different
jars in order to get for instance jboss seam digester working.
An optional feature would be to replace all of the .classpath lib references with maven2
classpath container that comes with Maven2 Eclipse plugin. This will make pom.xml useful
for eclipse users even if current JBoss build engine is to be used, but requires maven2
plugin to be installed. The project wasn't not compiling for me directly when checked
out from CVS, so plugin requirement is less of a pain than sonting out "broken"
.classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira