yes, it's considered bad practice. That's the reason why I did like to get rid of our jboss repo references. Otoh, we still have them since some transitive dependencies of the JCDI TCK testing framework are only available there, and we used to have it for the main project too.
In the meantime Andrew pinged me that he and Chiba will go on uploading the artifact to sonatypes OSS nexus. So I have some hope again that it will hit maven.central in the next 2 weeks or so. LieGrue, strub ----- Original Message ---- > From: James Carman <[email protected]> > To: [email protected] > Sent: Wed, June 23, 2010 4:06:09 PM > Subject: Re: [DISCUSSION] javassist-3.12 > > Don't the maven folks frown upon having repository specs in any poms that go > in the central repo? I remember seeing something about that a while > back that they were trying to clean that stuff up for some reason. On > Wed, Jun 23, 2010 at 10:02 AM, Mark Struberg < > ymailto="mailto:[email protected]"; > href="mailto:[email protected]";>[email protected]> wrote: > > Hoi! > > Since javassist-3.11 has quite remarkable mem leaks, we > should use javassist-3.12 for our RC1 (or -alpha-1) release. > > The > problem is that javassist-3.12 is still not uploaded to maven.central. Pete > and > Andrew Dinn are working on that but it will most probably take a few further > weeks since Pete is not available atm (JBoss world, etc). > > The > release is available on the public jboss edge maven repo: > > > http://repository.jboss.org/maven2-brew > > Wdyt, should we use this > repo or should we continue delivering with javassist-3.11 for now and upgrade > to > 3.12 later? > > We can also write in our README that we know about > the mem leaks and that people should upgrade to 3.12 theirselfs if > needed. > > LieGrue, > > strub > > > >
