ya, I'm working on cleaning up
java.net repository (including
java.net m2,
java.net m1, and Glassfish), I want to remove/fix as much garbage as I can,
it's mostly done.
you can simply remove
java.net repo definition in your POM and release your
project, then our staging rules won't complain.
thanks
On Thu, Apr 8, 2010 at 1:02 AM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
On Wed, Apr 7, 2010 at 12:53 PM, Pete Muir <pmuir(a)redhat.com>
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
--
- juven