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  :
> > > > >
> > > > >    <repositories>
> > > > >        <repository>
> > > > >            <id>staging-repository</id>
> > > > >            <name>mikedd's staging repository</name>
> > > > >            <url>
> > > > >
> > > > > http://people.apache.org/~mikedd/staging-repository<http://
> > > > > people.apache.org/%7Emikedd/staging-repository>
> > > > >            </url>
> > > > >        </repository>
> > > > >        . . .
> > > > >    </repositories>
> > > > >
> > > > >
> > > > > 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 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:
> > > > >> >>
> > > > >> >> <?xml version="1.0" encoding="UTF-8"?>
> > > > >> >> <project>
> > > > >> >>     <modelVersion>4.0.0</modelVersion>
> > > > >> >>     <groupId>some-project</groupId>
> > > > >> >>     <artifactId>some-artifact</artifactId>
> > > > >> >>     <packaging>jar</packaging>
> > > > >> >>     <name>My Project</name>
> > > > >> >>     <version>1.0.0</version>
> > > > >> >>     <repositories>
> > > > >> >>         <repository>
> > > > >> >>             <id>apache-snapshots</id>
> > > > >> >>             <url>
http://people.apache.org/repo/m2-incubating-
> > > > >> >> repository</url>
> > > > >> >>         </repository>
> > > > >> >>     </repositories>
> > > > >> >>     <dependencies>
> > > > >> >>         <dependency>
> > > > >> >>             <groupId>org.apache.openjpa</groupId>
> > > > >> >>             <artifactId>openjpa-all</artifactId>
> > > > >> >>             <version>0.9.6-incubating</version>
> > > > >> >>         </dependency>
> > > > >> >>     </dependencies>
> > > > >> >> </project>
> > > > >> >>
> > > > >> >>
> > > > >> >> 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 it is
worth
> > > > >> >> the effort, especially for a project that is so component-
> > > > >> oriented.
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >> On Apr 13, 2007, at 11:55 AM, Craig L Russell wrote:
> > > > >> >>
> > > > >> >>> Hi Michael,
> > > > >> >>>
> > > > >> >>> Thanks for all the work.
> > > > >> >>>
> > > > >> >>> 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.
> > > > >> >>>
> > > > >> >>> Was I just dreaming this up?
> > > > >> >>>
> > > > >> >>> Thanks,
> > > > >> >>>
> > > > >> >>> Craig
> > > > >> >>>
> > > > >> >>> On Apr 12, 2007, at 3:20 PM, Michael Dick wrote:
> > > > >> >>>
> > > > >> >>>> OpenJPA People-
> > > > >> >>>>
> > > > >> >>>> In accordance with the Incubating Releases guidelines at
> > > > >> >>>> http://incubator.apache.org/incubation/
> > > > >> >>>> Incubation_Policy.html#Releases ,
> > > > >> >>>> I've taken a shot at making a release and start a vote on
> > > > >> >>>> publishing a "
> > > > >> >>>> 0.9.7-incubating" release of OpenJPA.
> > > > >> >>>>
> > > > >> >>>> The release candidate is at:
> > > > >> >>>>
> > 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 GPG signature and MD5 checksums are at:
> > > > >> >>>>
> > http://people.apache.org/~mikedd/staging-repository/org/apache/
> > > > >> >>>> openjpa/openjpa-project/0.9.7-incubating/openjpa-
project-0.9.7
> > -
> > > > >> >>>> incubating-binary.zip.asc
> > > > >> >>>>
> > http://people.apache.org/~mikedd/staging-repository/org/apache/
> > > > >> >>>> openjpa/openjpa-project/0.9.7-incubating/openjpa-
project-0.9.7
> > -
> > > > >> >>>> incubating-binary.zip.md5
> > > > >> >>>>
> > > > >> >>>> The sources, sources GPG signature and sources MD5
checksum
> > are
> > > > >> >>>> available
> > > > >> >>>> at:
> > > > >> >>>>
> > http://people.apache.org/~mikedd/staging-repository/org/apache/
> > > > >> >>>> openjpa/openjpa-project/0.9.7-incubating/openjpa-
project-0.9.7
> > -
> > > > >> >>>> incubating-source.zip
> > > > >> >>>>
> > http://people.apache.org/~mikedd/staging-repository/org/apache/
> > > > >> >>>> openjpa/openjpa-project/0.9.7-incubating/openjpa-
project-0.9.7
> > -
> > > > >> >>>> incubating-source.zip.asc
> > > > >> >>>>
> > http://people.apache.org/~mikedd/staging-repository/org/apache/
> > > > >> >>>> openjpa/openjpa-project/0.9.7-incubating/openjpa-
project-0.9.7
> > -
> > > > >> >>>> incubating-source.zip.md5
> > > > >> >>>>
> > > > >> >>>> I have tagged the sources at:
> > > > >> >>>>
https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.7-
> > > > >> >>>> incubating/
> > > > >> >>>>
> > > > >> >>>> Please vote to publish this incubating release on the
project
> > > > >> >>>> Web page:
> > > > >> >>>>
> > > > >> >>>>   http://cwiki.apache.org/openjpa/downloads.html
> > > > >> >>>>
> > > > >> >>>> This vote will remain open until 5:20 CST on Tuesday April
> > 17th
> > > > >> >>>> (three
> > > > >> >>>> business days).
> > > > >> >>>> A "+1" indicates that you approve of the release, a "-1"
> > > > >> >>>> indicates a
> > > > >> >>>> vote against making a release
> > > > >> >>>>
> > > > >> >>>> --
> > > > >> >>>> -Michael Dick
> > > > >> >>>
> > > > >> >>> Craig Russell
> > > > >> >>> Architect, Sun Java Enterprise System http://java.sun.com/
> > > > >> >>> products/jdo
> > > > >> >>> 408 276-5638 mailto:[EMAIL PROTECTED]
> > > > >> >>> P.S. A good JDO? O, Gasp!
> > > > >> >>>
> > > > >> >>
> > > > >> >
> > > > >> > Craig Russell
> > > > >> > Architect, Sun Java Enterprise System http://java.sun.com/
> > > > >> products/jdo
> > > > >> > 408 276-5638 mailto:[EMAIL PROTECTED]
> > > > >> > P.S. A good JDO? O, Gasp!
> > > > >> >
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > -Michael Dick
> > > >
> > > > Craig Russell
> > > > Architect, Sun Java Enterprise System
http://java.sun.com/products/jdo
> > > > 408 276-5638 mailto:[EMAIL PROTECTED]
> > > > P.S. A good JDO? O, Gasp!
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > -Michael Dick
> > >
> >
>
>
>
> --
> -Michael Dick
>




--
-Michael Dick

Reply via email to