Re: [seam-dev] Seam JIRA for Seam 3

I agree with the latter as well. I'd like to see a JIRA project-per-module. I think it makes the most sense, and will prevent future headache, make it easier to track issues related to specific projects. +1 On Wed, Mar 10, 2010 at 12:11 PM, Dan Allen <dan.j.allen(a)gmail.com <mailto:dan.j.allen@gmail.com>> wrote: Q : How will this work with Maven? Won't it be annoying for developers to have to explicitly specify which module to depend on (and update this every time a Seam bundle comes out)? We'll provide a so called "stack POM" [1], which users can import into their project. They then just bump the Seam version number: <dependency> <groupId>org.jboss.seam</groupId> <artifactId>seam-bom</artifactId> <version>3.0.2.CR1</version> <type>pom</type> <scope>import</scope> </dependency> +1 This is where we get a lot of milage out of Maven (and dependency management in general). -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://mojavelinux.com http://mojavelinux.com/seaminaction http://www.google.com/profiles/dan.j.allen _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org <mailto:seam-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/seam-dev -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev