As Sun makes changes to an active development line for Java EE they
have changed the license. So it might not be an issue to use Geronimo
jars for the older ones. I'm still checking on JTA since that has
just had some active development.
Craig
On Jul 11, 2006, at 4:47 PM, Craig L Russell w
I got half an answer. The jars that are there are those whose sources
are published under Sun's CDDL, not the older Sun Community Source
License (SCSL). More info as I get it.
Craig
On Jul 11, 2006, at 4:30 PM, Marc Prud'hommeaux wrote:
Craig-
It'd be great if we could get the authoritati
Craig-
It'd be great if we could get the authoritative jars published there.
I know it would ease headaches for a lot of maven projects that
depend on those libraries (that currently require that the user
perform the cumbersome download-and-install-the-sun-libraries step in
order to build
For the record, https://maven-repository.dev.java.net/nonav/
repository/ is the repository that Glassfish development teams
publish to. I've asked the responsible engineer at Sun about the
plans for adding JTA, JCA, and JMS to this repository. I'll let
everyone know when I get an answer.
C
Personally, I'd prefer to go this route than to use the Geronimo
versions, especially for the JPA jars, which have non-trivial
behavior in them.
We actually are using the same JPA jars that Glassfish is using (from
a third repository I hadn't mentioned, at https://maven-
repository.dev.j
> > These must be the Geronimo versions then. I think Glassfish
> will have
> > the latest versions. As you know, javax.transaction was
> just updated
> > for Java EE 5.
>
> I hadn't noticed the Geronimo versions! They seem to contain
> everything we need. Once I get SVN write access, I'll fi
Ah, gotcha. I think we're just grabbing the jars from ibiblio
currently.
Well, we're actually getting them from a second, unofficial
repository right now. The problem is that many of the official Sun
jars (JTA, JPA, JMS, and JCA, to use a lot of J-TLAs) seems to have
an ambiguous enough
> The openjpa-lib project was not installing since it had the
> test failures.
> Thus, the dependency on openjpa-lib from the openjpa-kernel
> project was not being fulfilled. I worked around this by
> moving the "test" folder out of the way and re-running "mvn
> install" to get openjpa-lib in
On Jul 11, 2006, at 9:56 AM, Patrick Linskey wrote:
On 7/11/06, Patrick Linskey <[EMAIL PROTECTED]> wrote:
1) Have we decided how to resolve the Java EE 5 dependency?
I didn't see where we had set up a maven dependency for these
interfaces. For now, I can just use my own copy, but we should
Okay, making some progress...
The openjpa-lib project was not installing since it had the test failures.
Thus, the dependency on openjpa-lib from the openjpa-kernel project was not
being fulfilled. I worked around this by moving the "test" folder out of
the way and re-running "mvn install" to ge
> On 7/11/06, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> >
> > > 1) Have we decided how to resolve the Java EE 5 dependency?
> > > I didn't see where we had set up a maven dependency for these
> > > interfaces. For now, I can just use my own copy, but we should
> > > decide the formal solutio
On 7/11/06, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> 1) Have we decided how to resolve the Java EE 5 dependency?
> I didn't see where we had set up a maven dependency for these
> interfaces. For now, I can just use my own copy, but we
> should decide the formal solution.
I don't follow --
On 7/11/06, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> 1) Have we decided how to resolve the Java EE 5 dependency?
> I didn't see where we had set up a maven dependency for these
> interfaces. For now, I can just use my own copy, but we
> should decide the formal solution.
I don't follow --
> 1) Have we decided how to resolve the Java EE 5 dependency?
> I didn't see where we had set up a maven dependency for these
> interfaces. For now, I can just use my own copy, but we
> should decide the formal solution.
I don't follow -- what's the problem? To my knowledge, we don't have an
14 matches
Mail list logo