We are in a bit of a fix. We can't release any Seam 3 example that uses JSF 2.0 until Mojarra is in Maven Central (because of the policy of not using external repositories). Since we really only need it to compile (or run in a servlet), I think we should link against the Apache implementation instead of Mojarra (since Apache always publishes to central). http://repo2.maven.org/maven2/org/apache/myfaces/core/myfaces-api/ Btw, I have been working with the Mojarra team to get published to central. They are all setup in Nexus OSS, they just need to do it :) -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 https://lists.jboss.org/mailman/listinfo/seam-dev

Yes, I was talking about the API, though for servlet examples we would need to depend on the impl. I'm not sure how far the policy goes that you can't depend on external repositories, but either way, there is no API or impl in Maven Central for Mojarra 2. But, hold that thought! I was able to prompt Jason Lee of the Mojarra team into rekindling the effort to publish Mojarra to Maven Central. He is working on it right now and has promised to keep me updated. They already have a Nexus OSS repository setup and I've shared with him the instructions I wrote last night for publishing a Seam 3 module. So, we may have nothing to worry about. Stay tuned. -Dan On Wed, Apr 7, 2010 at 9:00 AM, Pete Muir <pmuir(a)redhat.com&gt; wrote: You are talking about the JSF API? Not the impl. On 7 Apr 2010, at 03:01, Dan Allen wrote: > We are in a bit of a fix. We can't release any Seam 3 example that uses JSF 2.0 until Mojarra is in Maven Central (because of the policy of not using external repositories). Since we really only need it to compile (or run in a servlet), I think we should link against the Apache implementation instead of Mojarra (since Apache always publishes to central). > > http://repo2.maven.org/maven2/org/apache/myfaces/core/myfaces-api/ > > Btw, I have been working with the Mojarra team to get published to central. They are all setup in Nexus OSS, they just need to do it :) > > -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 > https://lists.jboss.org/mailman/listinfo/seam-dev -- 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

On Wed, Apr 7, 2010 at 12:53 PM, Pete Muir <pmuir(a)redhat.com&gt; wrote: > Ok. > > Bear in mind Juven @ Sonatype is actively working on getting the java.netrepo sync'd to Maven central now. I'm not sure of the ETA on it (every email > I get on the subject says "coming soon" ;-), so if we can wait a few weeks, > everything will be there. > > I would much prefer to stick with using the javax.faces:jsf-api dependency > if possible. We can alternatively introduce a JBoss Java EE namespaced > jsf-api. > Sounds good. As long as we have motion, which it seems like we have on two fronts, that's good. I'll see Jason tonight at dinner, so I'll see if he is willing to share some more info regarding this migration :) He told me about it at DevNexus in March, but at the time it sounded like they were dealing with some roadblocks. -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