Ok, that probably explains the difference between version 1.1 and 1.0.1B
Thanks,
Johan.

2009/11/4 Anders Hammar <and...@hammar.net>

> The issue with those "old" Sun libraries is that they require some kind of
> click-through licensing agreement. That cannot be accomplished with Maven,
> so that's why you have to download it manually.
> In more recent version/implementations this limitation has been removed, my
> guess is that that is because they are now truly open source.
>
> As Mathus points out, the solution is to have your own (corporate) repo
> manager. This is best-practise in the Maven world.
>
> /Anders
>
> On Wed, Nov 4, 2009 at 17:10, Baptiste MATHUS <m...@batmat.net> wrote:
>
> > Well, no. The generic solution is to put a maven repository manager
> inside
> > your own repository. This way, you'll be able to handle configuration
> very
> > simply without depending on public repositories only. It just doesn't
> > scale.
> > Sometimes, you want things that'll never exist publicly. As Anders
> > explained, jta is to be retrieved manually (read the pom).
> > For instance, that's what we did inside our MRM. I guess this
> "limitation"
> > kind of comes from the license.
> >
> > And putting a mrm between is the almost only solution to handle it
> > properly.
> > Even apart from the fact that without a mrm between your developers and
> the
> > net, your company will hit central repository (and others) thousands of
> > times instead of just once...
> > The corresponding link:
> >
> >
> http://www.sonatype.com/people/2008/08/be-a-good-maven-citizen-dont-scrape-the-whole-damn-central-repository/
> >
> > Cheers.
> >
> > 2009/11/4 Johan Vogelzang <johan.vogelz...@gmail.com>
> >
> > > I do not see why this is correct in central.
> > > The more recent version 1.1 seems to be correctly deployed to central
> > see:
> > > http://repo2.maven.org/maven2/javax/transaction/jta/1.1
> > > You can see the jar file there.
> > >
> > > We do not manage this dependency ourselfs. Jta is a transitive
> > dependency,
> > > that comes with hibernate 3.2.5.ga. And depending on the java.netMaven
> > > repo
> > > is not a generic solution, becouse every developer or everry project
> need
> > > to
> > > take manualy steps to configure this repo.
> > >
> > > Regards,
> > > Johan.
> > >
> > >
> > >
> > >
> > >
> > > 2009/11/4 Anders Hammar <and...@hammar.net>
> > >
> > > > It's correct in central. You can get it from there, as it states in
> the
> > > > pom.
> > > > You need to download it manually. But you've found in at java.net,
> so
> > > use
> > > > that. Or some other implementation that is available at central (I
> > guess
> > > > there is a geronimo one).
> > > >
> > > > /A
> > > >
> > > > On Wed, Nov 4, 2009 at 15:56, Johan Vogelzang <
> > johan.vogelz...@gmail.com
> > > > >wrote:
> > > >
> > > > > Anyway it seems that this artifact in not correctly deployed (or
> > > > > synchronized).
> > > > >
> > > > > Johan.
> > > > >
> > > > > 2009/11/4 Anders Hammar <and...@hammar.net>
> > > > >
> > > > > > I don't think it has ever been there. Are you sure that it has
> been
> > > > > > removed?
> > > > > >
> > > > > > /A
> > > > > >
> > > > > > On Wed, Nov 4, 2009 at 14:10, Johan Vogelzang <
> > > > johan.vogelz...@gmail.com
> > > > > > >wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Today I discovered that jta-1.0.1B.jar is removed from the
> > central
> > > > > Maven
> > > > > > > repository.
> > > > > > > See:
> http://repo1.maven.org/maven2/javax/transaction/jta/1.0.1B
> > > > > > > Causing our builds to fail.
> > > > > > >
> > > > > > > It still exists in
> > > > > > > http://download.java.net/maven/2/javax/transaction/jta/1.0.1B
> > > > > > > What steps can I take to tackle this issue?
> > > > > > >
> > > > > > > Regards,
> > > > > > > Johan
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Johan Vogelzang
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Johan Vogelzang
> > >
> >
> >
> >
> > --
> > Baptiste <Batmat> MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
> >
>



-- 
Johan Vogelzang

Reply via email to