openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey" <plins...@bea.com>
Subject RE: Improving the Maven story for GlassFish
Date Thu, 15 Jun 2006 06:22:02 GMT
I think that we should not maintain a separate set of jars.

-Patrick

-- 
Patrick Linskey
BEA Systems, Inc.  

> -----Original Message-----
> From: Craig.Russell@Sun.COM [mailto:Craig.Russell@Sun.COM] 
> Sent: Wednesday, June 14, 2006 9:00 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Improving the Maven story for GlassFish
> 
> Hi,
> 
> Please note, the official spec jars and reference 
> implementation of the Java Persistence are now available in 
> the glassfish maven repository.
> 
> We should talk about whether we want to have our own 
> competing implementation of the spec jars since they now 
> contain only the spec apis and not the TopLink implementation 
> of the spec.
> 
> To make it easier to discuss, here's the location of the 
> glassfish java persistence maven repository. It includes the 
> spec and implementation jars separately.
> 
> https://maven-repository.dev.java.net/nonav/repository/javax.p
ersistence/
> 
> 
> Craig
> 
> Begin forwarded message:
> 
> 
> 				We just pushed a few more 
> components to our maven repository (see
> 
> 				
> http://blogs.sun.com/roller/page/theaquarium?entry=java_persis
tence_and_ejb_jars)
> 
> 				and we will continue adding 
> components, and I expect that, as part of
> 
> 				GlassFish v2, we will normalize 
> and automate the creation of these
> 
> 				components.
> 
> 
> Craig Russell
> 
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 
> 408 276-5638 mailto:Craig.Russell@sun.com
> 
> P.S. A good JDO? O, Gasp!
> 
> 
> 
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

Mime
View raw message