[ http://jira.jboss.com/jira/browse/JBSEAM-983?page=comments#action_12357490 ] Manfred Moser commented on JBSEAM-983: -------------------------------------- Oh and it might be much easier to publish to the JBoss Maven 2 repo and tell users to reference it in their pom.xml or settings.xml. -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-983?page=comments#action_12362541 ] Manfred Moser commented on JBSEAM-983: -------------------------------------- Alain, We are not building seam in maven2 and have not created a pom file that contains the dependencies. We have only created our own repo into which we push all the jars (seam, jbpm and so on) and build our seam app in maven2. The pom without dependencies gets created when you use the mvn install plugin to push a jar into the local repo. There are some poms for seam out there but we are not using them. manfred -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-983?page=all ] Pete Muir reassigned JBSEAM-983: -------------------------------- Assignee: Pete Muir -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-983?page=comments#action_12366260 ] Dan Allen commented on JBSEAM-983: ---------------------------------- Please don't assume that you have to build with maven2 to deploy to a maven2 repository. The Maven 2 repository is just as much about centralizing libraries as it is about the build tool. Half the time I create my pom.xml files by hand anyway, because using Maven 2 can be a PITA for simple tasks. The important part is to name the library consistently (consistent with the maven2 requirements) and to identify the dependencies so that others can get started quickly. I will attach the pom files that I use for a couple of the seam modules. I happen to think that they work quite well. My suggestion for naming the seam files is as such: groupId=org.jboss.seam artifactId=[jboss-seam-core, jboss-seam-ui, jboss-seam-remoting, jboss-seam-debug, jboss-seam-ioc] and so on -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-983?page=all ] Dan Allen updated JBSEAM-983: ----------------------------- Attachment: jboss-seam-debug-1.2.1.ga.pom jboss-seam-ioc-1.2.1.ga.pom -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-983?page=comments#action_12366262 ] Dan Allen commented on JBSEAM-983: ---------------------------------- Oops, there is a bug in my poms. I changed jboss-seam to jboss-seam-core, but then didn't update the references. You get the idea. -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-983?page=comments#action_12377469 ] Dan Allen commented on JBSEAM-983: ---------------------------------- I hate to make this an Us vs Them issue, but Spring just got their act together with three separate repositories. Again, the point here is not to outdo Spring. I think that would be a stupid pursuit. What we want is to make Seam more easily accessible. Right now, the extremely large download size and cryptic *-all.jar libraries is unsatisfactory to a lot of potential users. http://blog.interface21.com/main/2007/09/18/maven-artifacts-2/ -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-983?page=comments#action_12377476 ] Robert Stevens commented on JBSEAM-983: --------------------------------------- It would also increase the exposure of Seam. Google Trends, Monster, RentACoder.com -- there aren't yet many Seam jobs or qualified Seam coders. -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-983?page=all ] Pete Muir resolved JBSEAM-983. ------------------------------ Fix Version/s: 2.0.0.CR2 Resolution: Done http://in.relation.to/Bloggers/SeamPublishedToMaven -- 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