openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey" <plins...@bea.com>
Subject RE: svn commit: r471080 - /incubator/openjpa/trunk/openjpa-lib/pom.xml
Date Tue, 07 Nov 2006 00:26:47 GMT
I just reverted back to serp 1.11. Once 1.12 is in ibiblio, we can
decide whether or not we need the new version.

-Patrick

-- 
Patrick Linskey
BEA Systems, Inc. 

_______________________________________________________________________
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. 

> -----Original Message-----
> From: David Jencks [mailto:david_jencks@yahoo.com] 
> Sent: Monday, November 06, 2006 2:59 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: svn commit: r471080 - 
> /incubator/openjpa/trunk/openjpa-lib/pom.xml
> 
> 
> On Nov 6, 2006, at 12:21 PM, Kevin Sutter wrote:
> 
> > Abe,
> > I've got a couple of questions about this change...
> >
> > 1.  What was changed in serp that required this change?  Without  
> > the update
> > to serp v1.12, the only build problem I am having is with OpenJPA  
> > testcases,
> > not the shipped source code.  So, what was the "required" update.
> >
> > 2.  Shouldn't we have some group consensus about moving up 
> versions  
> > of the
> > prereqs?  Maybe this serp update is a requirement for needed OpenJPA
> > function.  But, changing a prereq level can be a pain for some
> > organizations.  I guess I would like to have some advance notice and
> > planning for prereq updates.
> 
> I suggest at a minimum you track these with  jira entries.  It makes  
> it much easier to follow what has changed.
> 
> Geronimo seems to be running into this problem also.... when is this  
> serp binary going to be published properly?  Making sure that an  
> artifact is publically avaiable before using it is a pretty good  
> idea :-)
> 
> thanks
> david jencks
> 
> >
> > 3.  Normal maven processing doesn't seem to find the new serp
> > 1.12binaries.  I had to add another maven repository to the 
> main level
> > pom.xml in order to find it.  Either that, or I would have to  
> > install it
> > manually into my local maven repository (which is what I probably  
> > did the
> > first time).  I can check in these changes, if you wish.
> >
> > Thanks,
> > Kevin
> >
> > On 11/3/06, awhite@apache.org <awhite@apache.org> wrote:
> >>
> >> Author: awhite
> >> Date: Fri Nov  3 16:38:22 2006
> >> New Revision: 471080
> >>
> >> URL: http://svn.apache.org/viewvc?view=rev&rev=471080
> >> Log:
> >> Update serp version.
> >>
> >>
> >> Modified:
> >>     incubator/openjpa/trunk/openjpa-lib/pom.xml
> >>
> >> Modified: incubator/openjpa/trunk/openjpa-lib/pom.xml
> >> URL:
> >> http://svn.apache.org/viewvc/incubator/openjpa/trunk/openjpa-lib/ 
> >> pom.xml?view=diff&rev=471080&r1=471079&r2=471080
> >>
> >> 
> ===================================================================== 
> >> =========
> >> --- incubator/openjpa/trunk/openjpa-lib/pom.xml (original)
> >> +++ incubator/openjpa/trunk/openjpa-lib/pom.xml Fri Nov  3  
> >> 16:38:22 2006
> >> @@ -53,7 +53,7 @@
> >>          <dependency>
> >>              <groupId>net.sourceforge.serp</groupId>
> >>              <artifactId>serp</artifactId>
> >> -            <version>1.11.0</version>
> >> +            <version>1.12.0</version>
> >>              <scope>compile</scope>
> >>          </dependency>
> >>      </dependencies>
> >>
> >>
> >>
> 
> 

Mime
View raw message