Re:[RESCINDED] [VOTE] publish openjpa 0.9.7-incubating release
I'm rescinding this vote due to issues with the license header included in the source files. Thanks Craig for finding the problem. I've removed the artifacts from my home directory on people.apache.org - I'll publish a new release candidate early this week. On 4/13/07, Craig L Russell <[EMAIL PROTECTED]> wrote: Hi Mike, I now understand that your message only mentioned a subset of the artifacts that we're planning on publishing for the release of 0.9.7. On Apr 13, 2007, at 1:54 PM, Michael Dick wrote: > Marc beat me to it, but in case this helps here's the xml that can > be used > to access the staging repository : > > > >staging-repository >mikedd's staging repository > > > http://people.apache.org/~mikedd/staging-repository people.apache.org/%7Emikedd/staging-repository> > > >. . . > > > > All the OpenJPA artifacts can be accessed this way (at least I was > able to > download them). If there are other artifacts that we need to > publish then > I'll go ahead and put them on people.apache.org/~mikedd too. Maybe > we just > need to include these instructions in the email that we send out > for the > vote? Yes, I think this would make it clear that we're not releasing just the binary and source zip files but the binary maven jar and pom artifacts as well. It was the message not the staging of the artifacts that threw me off. Thanks! Craig > > Thanks, > > > On 4/13/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: >> >> Craig- >> >> > I'm really asking that the 0.9.7 release that we plan to put into >> > the incubating repository needs to be put to a vote at the same >> > time as we release the other artifacts. The pom.xml and the >> openjpa- >> > all.0.9.7-incubating.jar should be part of the vote and available >> > in the staging repository. >> >> I'm not sure I completely understand your issue, but I am guessing >> you are either asking whether other maven-friendly jar artifacts were >> created for the release, or else whether those jar artifacts need to >> be listed and voted on. >> >> In the previous release, we just voted on the final binary (http:// >> people.apache.org/~mikedd/staging-repository/org/apache/openjpa/ >> openjpa-project/0.9.7-incubating/openjpa-project-0.9.7-incubating- >> binary.zip). The deploy process does also deploy the other module >> jars (e.g., see http://people.apache.org/~mikedd/staging-repository/ >> org/apache/openjpa/openjpa-all/0.9.7-incubating/), so you should be >> able access them in a pom.xml just like any repository. >> >> AFAIK, this is how all the other projects that use Maven have done it >> (e.g., ActiveMQ). Since the other deployed artifacts are either >> identical to, or derivative from, the binary assembly, it seems to me >> that listing every uploaded artifact might be needlessly cumbersome. >> >> >> Please let me know if I have mis-understood your issue. >> >> >> >> >> >> On Apr 13, 2007, at 12:40 PM, Craig L Russell wrote: >> >> > Hi Marc, >> > >> > Artifacts need to be approved (voted on by the PMC) before they are >> > put into repositories. The 0.9.6 release was put into the >> > incubating repository only after it was approved by the IPMC. >> > >> > I'm really asking that the 0.9.7 release that we plan to put into >> > the incubating repository needs to be put to a vote at the same >> > time as we release the other artifacts. The pom.xml and the >> openjpa- >> > all.0.9.7-incubating.jar should be part of the vote and available >> > in the staging repository. >> > >> > Craig >> > >> > On Apr 13, 2007, at 12:09 PM, Marc Prud'hommeaux wrote: >> > >> >> Craig- >> >> >> >>> I thought we were going to also release a maven download for the >> >>> jar file containing all the openjpa stuff and a pom that contains >> >>> the dependencies. This would enable folks using maven to simply >> >>> put the five lines of code naming the dependency into their pom >> >>> and put the incubating repository into their maven repositories >> >>> list and they would be done. >> >> >> >> Note that they can do that already with the existing artifacts, >> >> since Maven downloads transitive dependencies. For example, this >> >> pom.xml works fine for me in that it downloads and uses all of the >> >> OpenJPA libraries and dependencies: >> >> >> >> >> >> >> >> 4.0.0 >> >> some-project >> >> some-artifact >> >> jar >> >> My Project >> >> 1.0.0 >> >> >> >> >> >> apache-snapshots >> >> http://people.apache.org/repo/m2-incubating- >> >> repository >> >> >> >> >> >> >> >> >> >> org.apache.openjpa >> >> openjpa-all >> >> 0.9.6-incubating >> >> >> >> >> >> >> >> >> >> >> >> There might be some other good reasons to make a separate >> >> distribution that bundles all of the jars into a single uber-jar, >> >> but, as I mentioned before, I personally don't think i
Re: [RESCINDED] [VOTE] publish openjpa 0.9.7-incubating release
Mike-- Thanks; is there any chance that the old artifacts are still around somewhere? I was going to give them a review this weekend which could save us a release round trip if any issues crop up. If they're around somewhere, send along a link. Thanks. Eddie On 4/14/07, Michael Dick <[EMAIL PROTECTED]> wrote: I'm rescinding this vote due to issues with the license header included in the source files. Thanks Craig for finding the problem. I've removed the artifacts from my home directory on people.apache.org - I'll publish a new release candidate early this week. On 4/13/07, Craig L Russell <[EMAIL PROTECTED]> wrote: > > Hi Mike, > > I now understand that your message only mentioned a subset of the > artifacts that we're planning on publishing for the release of 0.9.7. > > On Apr 13, 2007, at 1:54 PM, Michael Dick wrote: > > > Marc beat me to it, but in case this helps here's the xml that can > > be used > > to access the staging repository : > > > > > > > >staging-repository > >mikedd's staging repository > > > > > > http://people.apache.org/~mikedd/staging-repository > people.apache.org/%7Emikedd/staging-repository> > > > > > >. . . > > > > > > > > All the OpenJPA artifacts can be accessed this way (at least I was > > able to > > download them). If there are other artifacts that we need to > > publish then > > I'll go ahead and put them on people.apache.org/~mikedd too. Maybe > > we just > > need to include these instructions in the email that we send out > > for the > > vote? > > Yes, I think this would make it clear that we're not releasing just > the binary and source zip files but the binary maven jar and pom > artifacts as well. It was the message not the staging of the > artifacts that threw me off. > > Thanks! > > Craig > > > > Thanks, > > > > > > On 4/13/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: > >> > >> Craig- > >> > >> > I'm really asking that the 0.9.7 release that we plan to put into > >> > the incubating repository needs to be put to a vote at the same > >> > time as we release the other artifacts. The pom.xml and the > >> openjpa- > >> > all.0.9.7-incubating.jar should be part of the vote and available > >> > in the staging repository. > >> > >> I'm not sure I completely understand your issue, but I am guessing > >> you are either asking whether other maven-friendly jar artifacts were > >> created for the release, or else whether those jar artifacts need to > >> be listed and voted on. > >> > >> In the previous release, we just voted on the final binary (http:// > >> people.apache.org/~mikedd/staging-repository/org/apache/openjpa/ > >> openjpa-project/0.9.7-incubating/openjpa-project-0.9.7-incubating- > >> binary.zip). The deploy process does also deploy the other module > >> jars (e.g., see http://people.apache.org/~mikedd/staging-repository/ > >> org/apache/openjpa/openjpa-all/0.9.7-incubating/), so you should be > >> able access them in a pom.xml just like any repository. > >> > >> AFAIK, this is how all the other projects that use Maven have done it > >> (e.g., ActiveMQ). Since the other deployed artifacts are either > >> identical to, or derivative from, the binary assembly, it seems to me > >> that listing every uploaded artifact might be needlessly cumbersome. > >> > >> > >> Please let me know if I have mis-understood your issue. > >> > >> > >> > >> > >> > >> On Apr 13, 2007, at 12:40 PM, Craig L Russell wrote: > >> > >> > Hi Marc, > >> > > >> > Artifacts need to be approved (voted on by the PMC) before they are > >> > put into repositories. The 0.9.6 release was put into the > >> > incubating repository only after it was approved by the IPMC. > >> > > >> > I'm really asking that the 0.9.7 release that we plan to put into > >> > the incubating repository needs to be put to a vote at the same > >> > time as we release the other artifacts. The pom.xml and the > >> openjpa- > >> > all.0.9.7-incubating.jar should be part of the vote and available > >> > in the staging repository. > >> > > >> > Craig > >> > > >> > On Apr 13, 2007, at 12:09 PM, Marc Prud'hommeaux wrote: > >> > > >> >> Craig- > >> >> > >> >>> I thought we were going to also release a maven download for the > >> >>> jar file containing all the openjpa stuff and a pom that contains > >> >>> the dependencies. This would enable folks using maven to simply > >> >>> put the five lines of code naming the dependency into their pom > >> >>> and put the incubating repository into their maven repositories > >> >>> list and they would be done. > >> >> > >> >> Note that they can do that already with the existing artifacts, > >> >> since Maven downloads transitive dependencies. For example, this > >> >> pom.xml works fine for me in that it downloads and uses all of the > >> >> OpenJPA libraries and dependencies: > >> >> > >> >> > >> >> > >> >> 4.0.0 > >> >> some-project > >> >> some-artifact > >> >> jar > >> >> My
Re: [RESCINDED] [VOTE] publish openjpa 0.9.7-incubating release
Unfortunately I just deleted them - it'll take a few minutes to re-publish. On 4/14/07, Eddie O'Neil <[EMAIL PROTECTED]> wrote: Mike-- Thanks; is there any chance that the old artifacts are still around somewhere? I was going to give them a review this weekend which could save us a release round trip if any issues crop up. If they're around somewhere, send along a link. Thanks. Eddie On 4/14/07, Michael Dick <[EMAIL PROTECTED]> wrote: > I'm rescinding this vote due to issues with the license header included in > the source files. > > Thanks Craig for finding the problem. I've removed the artifacts from my > home directory on people.apache.org - I'll publish a new release candidate > early this week. > > On 4/13/07, Craig L Russell <[EMAIL PROTECTED]> wrote: > > > > Hi Mike, > > > > I now understand that your message only mentioned a subset of the > > artifacts that we're planning on publishing for the release of 0.9.7. > > > > On Apr 13, 2007, at 1:54 PM, Michael Dick wrote: > > > > > Marc beat me to it, but in case this helps here's the xml that can > > > be used > > > to access the staging repository : > > > > > > > > > > > >staging-repository > > >mikedd's staging repository > > > > > > > > > http://people.apache.org/~mikedd/staging-repository > > people.apache.org/%7Emikedd/staging-repository> > > > > > > > > >. . . > > > > > > > > > > > > All the OpenJPA artifacts can be accessed this way (at least I was > > > able to > > > download them). If there are other artifacts that we need to > > > publish then > > > I'll go ahead and put them on people.apache.org/~mikedd too. Maybe > > > we just > > > need to include these instructions in the email that we send out > > > for the > > > vote? > > > > Yes, I think this would make it clear that we're not releasing just > > the binary and source zip files but the binary maven jar and pom > > artifacts as well. It was the message not the staging of the > > artifacts that threw me off. > > > > Thanks! > > > > Craig > > > > > > Thanks, > > > > > > > > > On 4/13/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: > > >> > > >> Craig- > > >> > > >> > I'm really asking that the 0.9.7 release that we plan to put into > > >> > the incubating repository needs to be put to a vote at the same > > >> > time as we release the other artifacts. The pom.xml and the > > >> openjpa- > > >> > all.0.9.7-incubating.jar should be part of the vote and available > > >> > in the staging repository. > > >> > > >> I'm not sure I completely understand your issue, but I am guessing > > >> you are either asking whether other maven-friendly jar artifacts were > > >> created for the release, or else whether those jar artifacts need to > > >> be listed and voted on. > > >> > > >> In the previous release, we just voted on the final binary (http:// > > >> people.apache.org/~mikedd/staging-repository/org/apache/openjpa/ > > >> openjpa-project/0.9.7-incubating/openjpa-project-0.9.7-incubating- > > >> binary.zip). The deploy process does also deploy the other module > > >> jars (e.g., see http://people.apache.org/~mikedd/staging-repository/ > > >> org/apache/openjpa/openjpa-all/0.9.7-incubating/), so you should be > > >> able access them in a pom.xml just like any repository. > > >> > > >> AFAIK, this is how all the other projects that use Maven have done it > > >> (e.g., ActiveMQ). Since the other deployed artifacts are either > > >> identical to, or derivative from, the binary assembly, it seems to me > > >> that listing every uploaded artifact might be needlessly cumbersome. > > >> > > >> > > >> Please let me know if I have mis-understood your issue. > > >> > > >> > > >> > > >> > > >> > > >> On Apr 13, 2007, at 12:40 PM, Craig L Russell wrote: > > >> > > >> > Hi Marc, > > >> > > > >> > Artifacts need to be approved (voted on by the PMC) before they are > > >> > put into repositories. The 0.9.6 release was put into the > > >> > incubating repository only after it was approved by the IPMC. > > >> > > > >> > I'm really asking that the 0.9.7 release that we plan to put into > > >> > the incubating repository needs to be put to a vote at the same > > >> > time as we release the other artifacts. The pom.xml and the > > >> openjpa- > > >> > all.0.9.7-incubating.jar should be part of the vote and available > > >> > in the staging repository. > > >> > > > >> > Craig > > >> > > > >> > On Apr 13, 2007, at 12:09 PM, Marc Prud'hommeaux wrote: > > >> > > > >> >> Craig- > > >> >> > > >> >>> I thought we were going to also release a maven download for the > > >> >>> jar file containing all the openjpa stuff and a pom that contains > > >> >>> the dependencies. This would enable folks using maven to simply > > >> >>> put the five lines of code naming the dependency into their pom > > >> >>> and put the incubating repository into their maven repositories > > >> >>> list and they would be done. > > >> >> > > >> >> Note that th
Re: [RESCINDED] [VOTE] publish openjpa 0.9.7-incubating release
Eh -- either way. If it's easy or they're cached somewhere, go for it, but if not, go enjoy y our Saturday evening and we'll look at a new release candidate next week. Eddie On 4/14/07, Michael Dick <[EMAIL PROTECTED]> wrote: Unfortunately I just deleted them - it'll take a few minutes to re-publish. On 4/14/07, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > > Mike-- > > Thanks; is there any chance that the old artifacts are still around > somewhere? I was going to give them a review this weekend which could > save us a release round trip if any issues crop up. If they're around > somewhere, send along a link. > > Thanks. > Eddie > > > > On 4/14/07, Michael Dick <[EMAIL PROTECTED]> wrote: > > I'm rescinding this vote due to issues with the license header included > in > > the source files. > > > > Thanks Craig for finding the problem. I've removed the artifacts from my > > home directory on people.apache.org - I'll publish a new release > candidate > > early this week. > > > > On 4/13/07, Craig L Russell <[EMAIL PROTECTED]> wrote: > > > > > > Hi Mike, > > > > > > I now understand that your message only mentioned a subset of the > > > artifacts that we're planning on publishing for the release of 0.9.7. > > > > > > On Apr 13, 2007, at 1:54 PM, Michael Dick wrote: > > > > > > > Marc beat me to it, but in case this helps here's the xml that can > > > > be used > > > > to access the staging repository : > > > > > > > > > > > > > > > >staging-repository > > > >mikedd's staging repository > > > > > > > > > > > > http://people.apache.org/~mikedd/staging-repository > > > people.apache.org/%7Emikedd/staging-repository> > > > > > > > > > > > >. . . > > > > > > > > > > > > > > > > All the OpenJPA artifacts can be accessed this way (at least I was > > > > able to > > > > download them). If there are other artifacts that we need to > > > > publish then > > > > I'll go ahead and put them on people.apache.org/~mikedd too. Maybe > > > > we just > > > > need to include these instructions in the email that we send out > > > > for the > > > > vote? > > > > > > Yes, I think this would make it clear that we're not releasing just > > > the binary and source zip files but the binary maven jar and pom > > > artifacts as well. It was the message not the staging of the > > > artifacts that threw me off. > > > > > > Thanks! > > > > > > Craig > > > > > > > > Thanks, > > > > > > > > > > > > On 4/13/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: > > > >> > > > >> Craig- > > > >> > > > >> > I'm really asking that the 0.9.7 release that we plan to put into > > > >> > the incubating repository needs to be put to a vote at the same > > > >> > time as we release the other artifacts. The pom.xml and the > > > >> openjpa- > > > >> > all.0.9.7-incubating.jar should be part of the vote and available > > > >> > in the staging repository. > > > >> > > > >> I'm not sure I completely understand your issue, but I am guessing > > > >> you are either asking whether other maven-friendly jar artifacts > were > > > >> created for the release, or else whether those jar artifacts need > to > > > >> be listed and voted on. > > > >> > > > >> In the previous release, we just voted on the final binary (http:// > > > >> people.apache.org/~mikedd/staging-repository/org/apache/openjpa/ > > > >> openjpa-project/0.9.7-incubating/openjpa-project-0.9.7-incubating- > > > >> binary.zip). The deploy process does also deploy the other module > > > >> jars (e.g., see > http://people.apache.org/~mikedd/staging-repository/ > > > >> org/apache/openjpa/openjpa-all/0.9.7-incubating/), so you should be > > > >> able access them in a pom.xml just like any repository. > > > >> > > > >> AFAIK, this is how all the other projects that use Maven have done > it > > > >> (e.g., ActiveMQ). Since the other deployed artifacts are either > > > >> identical to, or derivative from, the binary assembly, it seems to > me > > > >> that listing every uploaded artifact might be needlessly > cumbersome. > > > >> > > > >> > > > >> Please let me know if I have mis-understood your issue. > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> On Apr 13, 2007, at 12:40 PM, Craig L Russell wrote: > > > >> > > > >> > Hi Marc, > > > >> > > > > >> > Artifacts need to be approved (voted on by the PMC) before they > are > > > >> > put into repositories. The 0.9.6 release was put into the > > > >> > incubating repository only after it was approved by the IPMC. > > > >> > > > > >> > I'm really asking that the 0.9.7 release that we plan to put into > > > >> > the incubating repository needs to be put to a vote at the same > > > >> > time as we release the other artifacts. The pom.xml and the > > > >> openjpa- > > > >> > all.0.9.7-incubating.jar should be part of the vote and available > > > >> > in the staging repository. > > > >> > > > > >> > Craig > > > >> > > > > >> > On Apr 13, 2007, at 12:09 PM, Marc Prud'hommeaux wr
Re: [RESCINDED] [VOTE] publish openjpa 0.9.7-incubating release
No big deal, they're uploaded now. On 4/14/07, Eddie O'Neil <[EMAIL PROTECTED]> wrote: Eh -- either way. If it's easy or they're cached somewhere, go for it, but if not, go enjoy y our Saturday evening and we'll look at a new release candidate next week. Eddie On 4/14/07, Michael Dick <[EMAIL PROTECTED]> wrote: > Unfortunately I just deleted them - it'll take a few minutes to re-publish. > > On 4/14/07, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > > > > Mike-- > > > > Thanks; is there any chance that the old artifacts are still around > > somewhere? I was going to give them a review this weekend which could > > save us a release round trip if any issues crop up. If they're around > > somewhere, send along a link. > > > > Thanks. > > Eddie > > > > > > > > On 4/14/07, Michael Dick <[EMAIL PROTECTED]> wrote: > > > I'm rescinding this vote due to issues with the license header included > > in > > > the source files. > > > > > > Thanks Craig for finding the problem. I've removed the artifacts from my > > > home directory on people.apache.org - I'll publish a new release > > candidate > > > early this week. > > > > > > On 4/13/07, Craig L Russell <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi Mike, > > > > > > > > I now understand that your message only mentioned a subset of the > > > > artifacts that we're planning on publishing for the release of 0.9.7. > > > > > > > > On Apr 13, 2007, at 1:54 PM, Michael Dick wrote: > > > > > > > > > Marc beat me to it, but in case this helps here's the xml that can > > > > > be used > > > > > to access the staging repository : > > > > > > > > > > > > > > > > > > > >staging-repository > > > > >mikedd's staging repository > > > > > > > > > > > > > > > http://people.apache.org/~mikedd/staging-repository > > > > people.apache.org/%7Emikedd/staging-repository> > > > > > > > > > > > > > > >. . . > > > > > > > > > > > > > > > > > > > > All the OpenJPA artifacts can be accessed this way (at least I was > > > > > able to > > > > > download them). If there are other artifacts that we need to > > > > > publish then > > > > > I'll go ahead and put them on people.apache.org/~mikeddtoo. Maybe > > > > > we just > > > > > need to include these instructions in the email that we send out > > > > > for the > > > > > vote? > > > > > > > > Yes, I think this would make it clear that we're not releasing just > > > > the binary and source zip files but the binary maven jar and pom > > > > artifacts as well. It was the message not the staging of the > > > > artifacts that threw me off. > > > > > > > > Thanks! > > > > > > > > Craig > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > On 4/13/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: > > > > >> > > > > >> Craig- > > > > >> > > > > >> > I'm really asking that the 0.9.7 release that we plan to put into > > > > >> > the incubating repository needs to be put to a vote at the same > > > > >> > time as we release the other artifacts. The pom.xml and the > > > > >> openjpa- > > > > >> > all.0.9.7-incubating.jar should be part of the vote and available > > > > >> > in the staging repository. > > > > >> > > > > >> I'm not sure I completely understand your issue, but I am guessing > > > > >> you are either asking whether other maven-friendly jar artifacts > > were > > > > >> created for the release, or else whether those jar artifacts need > > to > > > > >> be listed and voted on. > > > > >> > > > > >> In the previous release, we just voted on the final binary (http:// > > > > >> people.apache.org/~mikedd/staging-repository/org/apache/openjpa/ > > > > >> openjpa-project/0.9.7-incubating/openjpa- project-0.9.7-incubating- > > > > >> binary.zip). The deploy process does also deploy the other module > > > > >> jars (e.g., see > > http://people.apache.org/~mikedd/staging-repository/ > > > > >> org/apache/openjpa/openjpa-all/0.9.7-incubating/), so you should be > > > > >> able access them in a pom.xml just like any repository. > > > > >> > > > > >> AFAIK, this is how all the other projects that use Maven have done > > it > > > > >> (e.g., ActiveMQ). Since the other deployed artifacts are either > > > > >> identical to, or derivative from, the binary assembly, it seems to > > me > > > > >> that listing every uploaded artifact might be needlessly > > cumbersome. > > > > >> > > > > >> > > > > >> Please let me know if I have mis-understood your issue. > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> On Apr 13, 2007, at 12:40 PM, Craig L Russell wrote: > > > > >> > > > > >> > Hi Marc, > > > > >> > > > > > >> > Artifacts need to be approved (voted on by the PMC) before they > > are > > > > >> > put into repositories. The 0.9.6 release was put into the > > > > >> > incubating repository only after it was approved by the IPMC. > > > > >> > > > > > >> > I'm really asking that the 0.9.7 release that we plan to put into > > > > >> > the incubating repositor
Re: [RESCINDED] [VOTE] publish openjpa 0.9.7-incubating release
Sorry, I meant to send this out sooner but I'm rescinding this vote. The docbook jar needs to be removed and we need to resolve the problem with DB2. On 4/19/07, Craig L Russell <[EMAIL PROTECTED]> wrote: Hi Kevin, I agree that the problem with sub-selects on DB2 seems significant enough to stop the release. Craig On Apr 19, 2007, at 7:52 AM, Kevin Sutter wrote: > Another alternative is to back out the changes for OPENJPA-182 > until we get > the complete solution.. But, looking at the changes for > OPENJPA-182, that > looks to be quite the job and I'm not sure how many of these parts > have been > touched since that commit... I would rather wait until OPENJPA-222 > tests > clean and then go forward with another vote... But, I am open to > other > suggestions. > > Kevin > > On 4/19/07, Kevin Sutter <[EMAIL PROTECTED]> wrote: >> >> Craig and others, >> Here's the scoop with OPENJPA-222... A couple of weeks ago, DaveW >> committed some changes to OPENJPA-182. Patrick reviewed the >> changes and >> through discussions on the dev mailing list and the Issue itself, >> re-worked >> and re-committed the changes. We dropped the ball and didn't >> sufficiently >> test these new changes against DB2 until recently. We are finding >> that >> basically any sub-selects will not work with DB2 with the changes for >> OPENJPA-182. The changes for OPENJPA-222 will resolve these issues. >> >> This problem (no sub-selects with DB2) seems severe enough to >> warrant a >> re-spin of the release. I know this pushes us out another couple >> of days, >> but I think from a "customer perspective", it's worth the effort. >> >> As far as this 0.9.7 being bundled with some significant >> release... We >> (IBM) were planning to use the 0.9.7 release with a refresh of the >> EJB3 >> Feature Pack. Our plans have since changed, so the urgency is no >> longer >> present. I just want any OpenJPA release to be usable and not >> regress >> expected function. >> >> Thanks, >> Kevin >> >> On 4/18/07, Craig L Russell <[EMAIL PROTECTED]> wrote: >> > >> > This isn't the last release of openjpa. What is the urgency for >> > fixing this before our major event (the last release before exiting >> > the incubator)? >> > >> > Is this release planned to be bundled with some other significant >> > release? >> > >> > Craig >> > >> > On Apr 18, 2007, at 4:40 PM, Michael Dick wrote: >> > >> > > I probably should have worded that differently since I haven't >> run >> > > the tests >> > > against DB2. I believe Dave's team has. >> > > >> > > Dave, can you comment on how big the impact of OpenJPA-222 is? >> > > >> > > On 4/18/07, Patrick Linskey <[EMAIL PROTECTED]> wrote: >> > >>> >> > >>> I'm a little nervous about OpenJPA-222. From talking with >> > >>> Dave it sounds like it has a large effect on DB2. I'd like to >> > >>> get that issue resolved if possible. >> > >> >> > >> I'm a little nervous about scope creep. Is there some good >> reason why >> > >> > >> OPENJPA-222 needs to be resolved now vs. later? >> > >> >> > >> -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: Michael Dick [mailto:[EMAIL PROTECTED] ] >> > >> > Sent: Wednesday, April 18, 2007 2:24 PM >> > >> > To: open-jpa-dev@incubator.apache.org >> > >> > Subject: Re: [VOTE] publish openjpa 0.9.7-incubating release >> > >> > >> > >> > On 4/18/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: >> > >> > > >> > >> > > Michael- >> > >> > > >> > >> > > On Apr 18, 2007, at 12:27 PM, Michael Dick wrote: >> > >> > > >> > >> > > > I'd rather not cut another release, but I think we do >> need to >> > >> > > > resolve the issue with the docbook jar. If we can live >> with the >> > >> > >> > > > extra jar then the vote can proceed. >> > >> > > >> > >> > > Personally, I think it is sufficiently ugly to release >> with the >> > >> > > docbook jar to justify starting another release. >> > >> > >> > >> > However, if others disagree, I'll happily accede to the >> > >> majority. For >> > >> > > now, my vote changes to +0. >> > >> > > >> > >> > > >> > >> > > I agree but like you I can be talked out of it. I'll take >> > >> > another look >> > >> > over everything and start another release tonight / tomorrow. >> > >> > >> > >> > I'm a little nervous about Ope
