You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by Stephen Mallette <sp...@gmail.com> on 2015/02/10 17:11:58 UTC
SNAPSHOT deployment
Mentors,
We've always deployed SNAPSHOT releases to Sonatype:
https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
Based on that, I have couple of questions:
1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did
find this page[1] - do we simply follow those instructions?
2. While under incubator, are we allowed to publish SNAPSHOT releases?
Thanks,
Stephen
[1] http://www.apache.org/dev/publishing-maven-artifacts.html
Re: SNAPSHOT deployment
Posted by Matt Franklin <m....@gmail.com>.
On Thu, Mar 19, 2015 at 1:50 PM Stephen Mallette <sp...@gmail.com>
wrote:
> Well, i wasn't successful...but I think the error message changed so maybe
> something is different. Wish I'd pasted the whole error message in my last
> post. Anyway, here's what I see now:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
> on project tinkerpop: Failed to deploy artifacts: Could not transfer
> artifact org.apache.tinkerpop:tinkerpop:pom:3.0.0-20150319.174245-21
> from/to apache.snapshots.https (
> https://repository.apache.org/content/repositories/snapshots): Access
> denied to:
> https://repository.apache.org/content/repositories/snapshots/org/apache/
> tinkerpop/tinkerpop/3.0.0-SNAPSHOT/tinkerpop-3.0.0-20150319.174245-21.pom,
> ReasonPhrase: Forbidden. -> [Help 1]
>
> I don't recall getting a "Forbidden" status - I thought I was
> "Unauthorized" last time, but again I could be wrong. It seems like it's
> trying to put the SNAPSHOT in the right place so I assume things are
> configured properly for us in the pom.xml. The only configuration change I
> made overall was to my settings.xml file for the apache snapshot repo
> <server> element - i didn't need anything else right?
>
Shouldn't be anything more. Add your error to a comment on my ticket.
https://issues.apache.org/jira/browse/INFRA-9293
>
>
>
>
> On Thu, Mar 19, 2015 at 1:30 PM, Matt Franklin <m....@gmail.com>
> wrote:
>
> > The issue is now marked as resolved. Try again.
> >
> > On Wed, Mar 18, 2015 at 9:53 AM Matt Franklin <m....@gmail.com>
> > wrote:
> >
> > > On Wed, Mar 18, 2015 at 9:14 AM Stephen Mallette <spmallette@gmail.com
> >
> > > wrote:
> > >
> > >> Hi Matt, I just tried to do a mvn deploy for the SNAPSHOT and got a
> > >> "Access
> > >> denied" error. I believe that i have my settings.xml set up properly
> > with
> > >> an appropriate entry like this (with username/password set of course):
> > >>
> > >> <server>
> > >> <id>apache.snapshots.https</id>
> > >> <username></username>
> > >> <password></password>
> > >> </server>
> > >>
> > >> so I assume that i just don't have rights to publish. Did you ever
> hear
> > >> anything from the infra list with respect to this? How should Marko
> > and I
> > >> go about getting the appropriate rights to deploy?
> > >>
> > >
> > > I didn't hear back, but since it isn't working, I just put in a support
> > > ticket:
> > >
> > > https://issues.apache.org/jira/browse/INFRA-9293
> > >
> > >
> > >>
> > >> Thanks,
> > >>
> > >> Stephen
> > >>
> > >>
> > >> On Thu, Mar 12, 2015 at 5:51 PM, Matt Franklin <
> > m.ben.franklin@gmail.com>
> > >> wrote:
> > >>
> > >> > On Wed, Mar 11, 2015 at 6:02 AM Stephen Mallette <
> > spmallette@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > Matt, thanks for setting that up. I like that SNAPSHOT deployment
> is
> > >> part
> > >> > > of the build process. I was wondering if you are able to share
> the
> > >> > > credentials for deploying SNAPSHOTs so that we could have the
> > >> flexibility
> > >> > > to deploy manually if needed, to setup deployment from another
> > >> external
> > >> > > build server, etc. Is that possible?
> > >> > >
> > >> >
> > >> > It is possible and will be required for the release manager (RM)
> when
> > >> the
> > >> > release is cut.
> > >> >
> > >> > At one point they were manually enabling authentication for
> incubator
> > >> > projects. I will send an e-mail to the infra list to verify that
> this
> > >> is
> > >> > not an issue. You could also attempt to do a mvn deploy, but in the
> > >> event
> > >> > it fails, it will lock your account out and you will have to reset
> the
> > >> > password through https://id.apache.org.
> > >> >
> > >> >
> > >> > >
> > >> > > On Wed, Mar 11, 2015 at 6:34 AM, pieter-gmail <
> > >> pieter.martin@gmail.com>
> > >> > > wrote:
> > >> > >
> > >> > > > Thanks
> > >> > > > Pieter
> > >> > > >
> > >> > > >
> > >> > > > On 10/03/2015 20:40, Matt Franklin wrote:
> > >> > > >
> > >> > > >> On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <
> > >> > m.ben.franklin@gmail.com>
> > >> > > >> wrote:
> > >> > > >>
> > >> > > >> I have configured the Jenkins build to publish SNAPSHOT
> > artifacts.
> > >> > > >>>
> > >> > > >>> If the build ever finishes, I will verify SNAPSHOTs got
> > published
> > >> and
> > >> > > let
> > >> > > >>> the list know.
> > >> > > >>>
> > >> > > >>> https://builds.apache.org/job/tinkerpop-master/8
> > >> > > >>>
> > >> > > >>> The build seems to hang on certain servers. I am going to
> > >> restrict
> > >> > > the
> > >> > > >> build to the machines that it has successfully completed on, or
> > >> hasn't
> > >> > > run
> > >> > > >> on yet. Assuming this works, we will have consistent snapshots
> > >> > > deployed.
> > >> > > >>
> > >> > > >> Build 9 did succeed and produced the following SNAPSHOTs
> > >> > > >>
> > >> > > >> https://repository.apache.org/content/groups/snapshots/org/
> > >> > > >> apache/tinkerpop/
> > >> > > >>
> > >> > > >>
> > >> > > >>
> > >> > > >>>
> > >> > > >>> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <
> > >> > m.ben.franklin@gmail.com
> > >> > > >
> > >> > > >>> wrote:
> > >> > > >>>
> > >> > > >>> Apologies on the delay. I have been out of the country on
> > >> business
> > >> > and
> > >> > > >>>> haven't had a free second. I will look into it this week.
> > >> > > >>>>
> > >> > > >>>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <
> > >> > pieter.martin@gmail.com
> > >> > > >
> > >> > > >>>> wrote:
> > >> > > >>>>
> > >> > > >>>> Hi,
> > >> > > >>>>>
> > >> > > >>>>> Is this going to happen?
> > >> > > >>>>> Makes live way easier for (cutting edge) projects that are
> > >> already
> > >> > > >>>>> developing against tp3.
> > >> > > >>>>>
> > >> > > >>>>> Thanks
> > >> > > >>>>> Pieter
> > >> > > >>>>>
> > >> > > >>>>> On 10/02/2015 18:11, Stephen Mallette wrote:
> > >> > > >>>>>
> > >> > > >>>>>> Mentors,
> > >> > > >>>>>>
> > >> > > >>>>>> We've always deployed SNAPSHOT releases to Sonatype:
> > >> > > >>>>>>
> > >> > > >>>>>> https://oss.sonatype.org/content/repositories/
> > >> > > >>>>>> snapshots/com/tinkerpop/
> > >> > > >>>>>>
> > >> > > >>>>>> Based on that, I have couple of questions:
> > >> > > >>>>>>
> > >> > > >>>>>> 1. Will we still deploy SNAPSHOT releases to Sonatype under
> > >> > Apache?
> > >> > > I
> > >> > > >>>>>>
> > >> > > >>>>> did
> > >> > > >>>>>
> > >> > > >>>>>> find this page[1] - do we simply follow those instructions?
> > >> > > >>>>>> 2. While under incubator, are we allowed to publish
> SNAPSHOT
> > >> > > releases?
> > >> > > >>>>>>
> > >> > > >>>>>> Thanks,
> > >> > > >>>>>>
> > >> > > >>>>>> Stephen
> > >> > > >>>>>>
> > >> > > >>>>>> [1]
> > http://www.apache.org/dev/publishing-maven-artifacts.html
> > >> > > >>>>>>
> > >> > > >>>>>>
> > >> > > >>>>>
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> >
>
Re: SNAPSHOT deployment
Posted by Stephen Mallette <sp...@gmail.com>.
Well, i wasn't successful...but I think the error message changed so maybe
something is different. Wish I'd pasted the whole error message in my last
post. Anyway, here's what I see now:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
on project tinkerpop: Failed to deploy artifacts: Could not transfer
artifact org.apache.tinkerpop:tinkerpop:pom:3.0.0-20150319.174245-21
from/to apache.snapshots.https (
https://repository.apache.org/content/repositories/snapshots): Access
denied to:
https://repository.apache.org/content/repositories/snapshots/org/apache/tinkerpop/tinkerpop/3.0.0-SNAPSHOT/tinkerpop-3.0.0-20150319.174245-21.pom,
ReasonPhrase: Forbidden. -> [Help 1]
I don't recall getting a "Forbidden" status - I thought I was
"Unauthorized" last time, but again I could be wrong. It seems like it's
trying to put the SNAPSHOT in the right place so I assume things are
configured properly for us in the pom.xml. The only configuration change I
made overall was to my settings.xml file for the apache snapshot repo
<server> element - i didn't need anything else right?
On Thu, Mar 19, 2015 at 1:30 PM, Matt Franklin <m....@gmail.com>
wrote:
> The issue is now marked as resolved. Try again.
>
> On Wed, Mar 18, 2015 at 9:53 AM Matt Franklin <m....@gmail.com>
> wrote:
>
> > On Wed, Mar 18, 2015 at 9:14 AM Stephen Mallette <sp...@gmail.com>
> > wrote:
> >
> >> Hi Matt, I just tried to do a mvn deploy for the SNAPSHOT and got a
> >> "Access
> >> denied" error. I believe that i have my settings.xml set up properly
> with
> >> an appropriate entry like this (with username/password set of course):
> >>
> >> <server>
> >> <id>apache.snapshots.https</id>
> >> <username></username>
> >> <password></password>
> >> </server>
> >>
> >> so I assume that i just don't have rights to publish. Did you ever hear
> >> anything from the infra list with respect to this? How should Marko
> and I
> >> go about getting the appropriate rights to deploy?
> >>
> >
> > I didn't hear back, but since it isn't working, I just put in a support
> > ticket:
> >
> > https://issues.apache.org/jira/browse/INFRA-9293
> >
> >
> >>
> >> Thanks,
> >>
> >> Stephen
> >>
> >>
> >> On Thu, Mar 12, 2015 at 5:51 PM, Matt Franklin <
> m.ben.franklin@gmail.com>
> >> wrote:
> >>
> >> > On Wed, Mar 11, 2015 at 6:02 AM Stephen Mallette <
> spmallette@gmail.com>
> >> > wrote:
> >> >
> >> > > Matt, thanks for setting that up. I like that SNAPSHOT deployment is
> >> part
> >> > > of the build process. I was wondering if you are able to share the
> >> > > credentials for deploying SNAPSHOTs so that we could have the
> >> flexibility
> >> > > to deploy manually if needed, to setup deployment from another
> >> external
> >> > > build server, etc. Is that possible?
> >> > >
> >> >
> >> > It is possible and will be required for the release manager (RM) when
> >> the
> >> > release is cut.
> >> >
> >> > At one point they were manually enabling authentication for incubator
> >> > projects. I will send an e-mail to the infra list to verify that this
> >> is
> >> > not an issue. You could also attempt to do a mvn deploy, but in the
> >> event
> >> > it fails, it will lock your account out and you will have to reset the
> >> > password through https://id.apache.org.
> >> >
> >> >
> >> > >
> >> > > On Wed, Mar 11, 2015 at 6:34 AM, pieter-gmail <
> >> pieter.martin@gmail.com>
> >> > > wrote:
> >> > >
> >> > > > Thanks
> >> > > > Pieter
> >> > > >
> >> > > >
> >> > > > On 10/03/2015 20:40, Matt Franklin wrote:
> >> > > >
> >> > > >> On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <
> >> > m.ben.franklin@gmail.com>
> >> > > >> wrote:
> >> > > >>
> >> > > >> I have configured the Jenkins build to publish SNAPSHOT
> artifacts.
> >> > > >>>
> >> > > >>> If the build ever finishes, I will verify SNAPSHOTs got
> published
> >> and
> >> > > let
> >> > > >>> the list know.
> >> > > >>>
> >> > > >>> https://builds.apache.org/job/tinkerpop-master/8
> >> > > >>>
> >> > > >>> The build seems to hang on certain servers. I am going to
> >> restrict
> >> > > the
> >> > > >> build to the machines that it has successfully completed on, or
> >> hasn't
> >> > > run
> >> > > >> on yet. Assuming this works, we will have consistent snapshots
> >> > > deployed.
> >> > > >>
> >> > > >> Build 9 did succeed and produced the following SNAPSHOTs
> >> > > >>
> >> > > >> https://repository.apache.org/content/groups/snapshots/org/
> >> > > >> apache/tinkerpop/
> >> > > >>
> >> > > >>
> >> > > >>
> >> > > >>>
> >> > > >>> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <
> >> > m.ben.franklin@gmail.com
> >> > > >
> >> > > >>> wrote:
> >> > > >>>
> >> > > >>> Apologies on the delay. I have been out of the country on
> >> business
> >> > and
> >> > > >>>> haven't had a free second. I will look into it this week.
> >> > > >>>>
> >> > > >>>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <
> >> > pieter.martin@gmail.com
> >> > > >
> >> > > >>>> wrote:
> >> > > >>>>
> >> > > >>>> Hi,
> >> > > >>>>>
> >> > > >>>>> Is this going to happen?
> >> > > >>>>> Makes live way easier for (cutting edge) projects that are
> >> already
> >> > > >>>>> developing against tp3.
> >> > > >>>>>
> >> > > >>>>> Thanks
> >> > > >>>>> Pieter
> >> > > >>>>>
> >> > > >>>>> On 10/02/2015 18:11, Stephen Mallette wrote:
> >> > > >>>>>
> >> > > >>>>>> Mentors,
> >> > > >>>>>>
> >> > > >>>>>> We've always deployed SNAPSHOT releases to Sonatype:
> >> > > >>>>>>
> >> > > >>>>>> https://oss.sonatype.org/content/repositories/
> >> > > >>>>>> snapshots/com/tinkerpop/
> >> > > >>>>>>
> >> > > >>>>>> Based on that, I have couple of questions:
> >> > > >>>>>>
> >> > > >>>>>> 1. Will we still deploy SNAPSHOT releases to Sonatype under
> >> > Apache?
> >> > > I
> >> > > >>>>>>
> >> > > >>>>> did
> >> > > >>>>>
> >> > > >>>>>> find this page[1] - do we simply follow those instructions?
> >> > > >>>>>> 2. While under incubator, are we allowed to publish SNAPSHOT
> >> > > releases?
> >> > > >>>>>>
> >> > > >>>>>> Thanks,
> >> > > >>>>>>
> >> > > >>>>>> Stephen
> >> > > >>>>>>
> >> > > >>>>>> [1]
> http://www.apache.org/dev/publishing-maven-artifacts.html
> >> > > >>>>>>
> >> > > >>>>>>
> >> > > >>>>>
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: SNAPSHOT deployment
Posted by Matt Franklin <m....@gmail.com>.
The issue is now marked as resolved. Try again.
On Wed, Mar 18, 2015 at 9:53 AM Matt Franklin <m....@gmail.com>
wrote:
> On Wed, Mar 18, 2015 at 9:14 AM Stephen Mallette <sp...@gmail.com>
> wrote:
>
>> Hi Matt, I just tried to do a mvn deploy for the SNAPSHOT and got a
>> "Access
>> denied" error. I believe that i have my settings.xml set up properly with
>> an appropriate entry like this (with username/password set of course):
>>
>> <server>
>> <id>apache.snapshots.https</id>
>> <username></username>
>> <password></password>
>> </server>
>>
>> so I assume that i just don't have rights to publish. Did you ever hear
>> anything from the infra list with respect to this? How should Marko and I
>> go about getting the appropriate rights to deploy?
>>
>
> I didn't hear back, but since it isn't working, I just put in a support
> ticket:
>
> https://issues.apache.org/jira/browse/INFRA-9293
>
>
>>
>> Thanks,
>>
>> Stephen
>>
>>
>> On Thu, Mar 12, 2015 at 5:51 PM, Matt Franklin <m....@gmail.com>
>> wrote:
>>
>> > On Wed, Mar 11, 2015 at 6:02 AM Stephen Mallette <sp...@gmail.com>
>> > wrote:
>> >
>> > > Matt, thanks for setting that up. I like that SNAPSHOT deployment is
>> part
>> > > of the build process. I was wondering if you are able to share the
>> > > credentials for deploying SNAPSHOTs so that we could have the
>> flexibility
>> > > to deploy manually if needed, to setup deployment from another
>> external
>> > > build server, etc. Is that possible?
>> > >
>> >
>> > It is possible and will be required for the release manager (RM) when
>> the
>> > release is cut.
>> >
>> > At one point they were manually enabling authentication for incubator
>> > projects. I will send an e-mail to the infra list to verify that this
>> is
>> > not an issue. You could also attempt to do a mvn deploy, but in the
>> event
>> > it fails, it will lock your account out and you will have to reset the
>> > password through https://id.apache.org.
>> >
>> >
>> > >
>> > > On Wed, Mar 11, 2015 at 6:34 AM, pieter-gmail <
>> pieter.martin@gmail.com>
>> > > wrote:
>> > >
>> > > > Thanks
>> > > > Pieter
>> > > >
>> > > >
>> > > > On 10/03/2015 20:40, Matt Franklin wrote:
>> > > >
>> > > >> On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <
>> > m.ben.franklin@gmail.com>
>> > > >> wrote:
>> > > >>
>> > > >> I have configured the Jenkins build to publish SNAPSHOT artifacts.
>> > > >>>
>> > > >>> If the build ever finishes, I will verify SNAPSHOTs got published
>> and
>> > > let
>> > > >>> the list know.
>> > > >>>
>> > > >>> https://builds.apache.org/job/tinkerpop-master/8
>> > > >>>
>> > > >>> The build seems to hang on certain servers. I am going to
>> restrict
>> > > the
>> > > >> build to the machines that it has successfully completed on, or
>> hasn't
>> > > run
>> > > >> on yet. Assuming this works, we will have consistent snapshots
>> > > deployed.
>> > > >>
>> > > >> Build 9 did succeed and produced the following SNAPSHOTs
>> > > >>
>> > > >> https://repository.apache.org/content/groups/snapshots/org/
>> > > >> apache/tinkerpop/
>> > > >>
>> > > >>
>> > > >>
>> > > >>>
>> > > >>> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <
>> > m.ben.franklin@gmail.com
>> > > >
>> > > >>> wrote:
>> > > >>>
>> > > >>> Apologies on the delay. I have been out of the country on
>> business
>> > and
>> > > >>>> haven't had a free second. I will look into it this week.
>> > > >>>>
>> > > >>>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <
>> > pieter.martin@gmail.com
>> > > >
>> > > >>>> wrote:
>> > > >>>>
>> > > >>>> Hi,
>> > > >>>>>
>> > > >>>>> Is this going to happen?
>> > > >>>>> Makes live way easier for (cutting edge) projects that are
>> already
>> > > >>>>> developing against tp3.
>> > > >>>>>
>> > > >>>>> Thanks
>> > > >>>>> Pieter
>> > > >>>>>
>> > > >>>>> On 10/02/2015 18:11, Stephen Mallette wrote:
>> > > >>>>>
>> > > >>>>>> Mentors,
>> > > >>>>>>
>> > > >>>>>> We've always deployed SNAPSHOT releases to Sonatype:
>> > > >>>>>>
>> > > >>>>>> https://oss.sonatype.org/content/repositories/
>> > > >>>>>> snapshots/com/tinkerpop/
>> > > >>>>>>
>> > > >>>>>> Based on that, I have couple of questions:
>> > > >>>>>>
>> > > >>>>>> 1. Will we still deploy SNAPSHOT releases to Sonatype under
>> > Apache?
>> > > I
>> > > >>>>>>
>> > > >>>>> did
>> > > >>>>>
>> > > >>>>>> find this page[1] - do we simply follow those instructions?
>> > > >>>>>> 2. While under incubator, are we allowed to publish SNAPSHOT
>> > > releases?
>> > > >>>>>>
>> > > >>>>>> Thanks,
>> > > >>>>>>
>> > > >>>>>> Stephen
>> > > >>>>>>
>> > > >>>>>> [1] http://www.apache.org/dev/publishing-maven-artifacts.html
>> > > >>>>>>
>> > > >>>>>>
>> > > >>>>>
>> > > >
>> > >
>> >
>>
>
Re: SNAPSHOT deployment
Posted by Matt Franklin <m....@gmail.com>.
On Wed, Mar 18, 2015 at 9:14 AM Stephen Mallette <sp...@gmail.com>
wrote:
> Hi Matt, I just tried to do a mvn deploy for the SNAPSHOT and got a "Access
> denied" error. I believe that i have my settings.xml set up properly with
> an appropriate entry like this (with username/password set of course):
>
> <server>
> <id>apache.snapshots.https</id>
> <username></username>
> <password></password>
> </server>
>
> so I assume that i just don't have rights to publish. Did you ever hear
> anything from the infra list with respect to this? How should Marko and I
> go about getting the appropriate rights to deploy?
>
I didn't hear back, but since it isn't working, I just put in a support
ticket:
https://issues.apache.org/jira/browse/INFRA-9293
>
> Thanks,
>
> Stephen
>
>
> On Thu, Mar 12, 2015 at 5:51 PM, Matt Franklin <m....@gmail.com>
> wrote:
>
> > On Wed, Mar 11, 2015 at 6:02 AM Stephen Mallette <sp...@gmail.com>
> > wrote:
> >
> > > Matt, thanks for setting that up. I like that SNAPSHOT deployment is
> part
> > > of the build process. I was wondering if you are able to share the
> > > credentials for deploying SNAPSHOTs so that we could have the
> flexibility
> > > to deploy manually if needed, to setup deployment from another external
> > > build server, etc. Is that possible?
> > >
> >
> > It is possible and will be required for the release manager (RM) when the
> > release is cut.
> >
> > At one point they were manually enabling authentication for incubator
> > projects. I will send an e-mail to the infra list to verify that this is
> > not an issue. You could also attempt to do a mvn deploy, but in the
> event
> > it fails, it will lock your account out and you will have to reset the
> > password through https://id.apache.org.
> >
> >
> > >
> > > On Wed, Mar 11, 2015 at 6:34 AM, pieter-gmail <pieter.martin@gmail.com
> >
> > > wrote:
> > >
> > > > Thanks
> > > > Pieter
> > > >
> > > >
> > > > On 10/03/2015 20:40, Matt Franklin wrote:
> > > >
> > > >> On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <
> > m.ben.franklin@gmail.com>
> > > >> wrote:
> > > >>
> > > >> I have configured the Jenkins build to publish SNAPSHOT artifacts.
> > > >>>
> > > >>> If the build ever finishes, I will verify SNAPSHOTs got published
> and
> > > let
> > > >>> the list know.
> > > >>>
> > > >>> https://builds.apache.org/job/tinkerpop-master/8
> > > >>>
> > > >>> The build seems to hang on certain servers. I am going to
> restrict
> > > the
> > > >> build to the machines that it has successfully completed on, or
> hasn't
> > > run
> > > >> on yet. Assuming this works, we will have consistent snapshots
> > > deployed.
> > > >>
> > > >> Build 9 did succeed and produced the following SNAPSHOTs
> > > >>
> > > >> https://repository.apache.org/content/groups/snapshots/org/
> > > >> apache/tinkerpop/
> > > >>
> > > >>
> > > >>
> > > >>>
> > > >>> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <
> > m.ben.franklin@gmail.com
> > > >
> > > >>> wrote:
> > > >>>
> > > >>> Apologies on the delay. I have been out of the country on business
> > and
> > > >>>> haven't had a free second. I will look into it this week.
> > > >>>>
> > > >>>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <
> > pieter.martin@gmail.com
> > > >
> > > >>>> wrote:
> > > >>>>
> > > >>>> Hi,
> > > >>>>>
> > > >>>>> Is this going to happen?
> > > >>>>> Makes live way easier for (cutting edge) projects that are
> already
> > > >>>>> developing against tp3.
> > > >>>>>
> > > >>>>> Thanks
> > > >>>>> Pieter
> > > >>>>>
> > > >>>>> On 10/02/2015 18:11, Stephen Mallette wrote:
> > > >>>>>
> > > >>>>>> Mentors,
> > > >>>>>>
> > > >>>>>> We've always deployed SNAPSHOT releases to Sonatype:
> > > >>>>>>
> > > >>>>>> https://oss.sonatype.org/content/repositories/
> > > >>>>>> snapshots/com/tinkerpop/
> > > >>>>>>
> > > >>>>>> Based on that, I have couple of questions:
> > > >>>>>>
> > > >>>>>> 1. Will we still deploy SNAPSHOT releases to Sonatype under
> > Apache?
> > > I
> > > >>>>>>
> > > >>>>> did
> > > >>>>>
> > > >>>>>> find this page[1] - do we simply follow those instructions?
> > > >>>>>> 2. While under incubator, are we allowed to publish SNAPSHOT
> > > releases?
> > > >>>>>>
> > > >>>>>> Thanks,
> > > >>>>>>
> > > >>>>>> Stephen
> > > >>>>>>
> > > >>>>>> [1] http://www.apache.org/dev/publishing-maven-artifacts.html
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >
> > >
> >
>
Re: SNAPSHOT deployment
Posted by Stephen Mallette <sp...@gmail.com>.
Hi Matt, I just tried to do a mvn deploy for the SNAPSHOT and got a "Access
denied" error. I believe that i have my settings.xml set up properly with
an appropriate entry like this (with username/password set of course):
<server>
<id>apache.snapshots.https</id>
<username></username>
<password></password>
</server>
so I assume that i just don't have rights to publish. Did you ever hear
anything from the infra list with respect to this? How should Marko and I
go about getting the appropriate rights to deploy?
Thanks,
Stephen
On Thu, Mar 12, 2015 at 5:51 PM, Matt Franklin <m....@gmail.com>
wrote:
> On Wed, Mar 11, 2015 at 6:02 AM Stephen Mallette <sp...@gmail.com>
> wrote:
>
> > Matt, thanks for setting that up. I like that SNAPSHOT deployment is part
> > of the build process. I was wondering if you are able to share the
> > credentials for deploying SNAPSHOTs so that we could have the flexibility
> > to deploy manually if needed, to setup deployment from another external
> > build server, etc. Is that possible?
> >
>
> It is possible and will be required for the release manager (RM) when the
> release is cut.
>
> At one point they were manually enabling authentication for incubator
> projects. I will send an e-mail to the infra list to verify that this is
> not an issue. You could also attempt to do a mvn deploy, but in the event
> it fails, it will lock your account out and you will have to reset the
> password through https://id.apache.org.
>
>
> >
> > On Wed, Mar 11, 2015 at 6:34 AM, pieter-gmail <pi...@gmail.com>
> > wrote:
> >
> > > Thanks
> > > Pieter
> > >
> > >
> > > On 10/03/2015 20:40, Matt Franklin wrote:
> > >
> > >> On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <
> m.ben.franklin@gmail.com>
> > >> wrote:
> > >>
> > >> I have configured the Jenkins build to publish SNAPSHOT artifacts.
> > >>>
> > >>> If the build ever finishes, I will verify SNAPSHOTs got published and
> > let
> > >>> the list know.
> > >>>
> > >>> https://builds.apache.org/job/tinkerpop-master/8
> > >>>
> > >>> The build seems to hang on certain servers. I am going to restrict
> > the
> > >> build to the machines that it has successfully completed on, or hasn't
> > run
> > >> on yet. Assuming this works, we will have consistent snapshots
> > deployed.
> > >>
> > >> Build 9 did succeed and produced the following SNAPSHOTs
> > >>
> > >> https://repository.apache.org/content/groups/snapshots/org/
> > >> apache/tinkerpop/
> > >>
> > >>
> > >>
> > >>>
> > >>> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <
> m.ben.franklin@gmail.com
> > >
> > >>> wrote:
> > >>>
> > >>> Apologies on the delay. I have been out of the country on business
> and
> > >>>> haven't had a free second. I will look into it this week.
> > >>>>
> > >>>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <
> pieter.martin@gmail.com
> > >
> > >>>> wrote:
> > >>>>
> > >>>> Hi,
> > >>>>>
> > >>>>> Is this going to happen?
> > >>>>> Makes live way easier for (cutting edge) projects that are already
> > >>>>> developing against tp3.
> > >>>>>
> > >>>>> Thanks
> > >>>>> Pieter
> > >>>>>
> > >>>>> On 10/02/2015 18:11, Stephen Mallette wrote:
> > >>>>>
> > >>>>>> Mentors,
> > >>>>>>
> > >>>>>> We've always deployed SNAPSHOT releases to Sonatype:
> > >>>>>>
> > >>>>>> https://oss.sonatype.org/content/repositories/
> > >>>>>> snapshots/com/tinkerpop/
> > >>>>>>
> > >>>>>> Based on that, I have couple of questions:
> > >>>>>>
> > >>>>>> 1. Will we still deploy SNAPSHOT releases to Sonatype under
> Apache?
> > I
> > >>>>>>
> > >>>>> did
> > >>>>>
> > >>>>>> find this page[1] - do we simply follow those instructions?
> > >>>>>> 2. While under incubator, are we allowed to publish SNAPSHOT
> > releases?
> > >>>>>>
> > >>>>>> Thanks,
> > >>>>>>
> > >>>>>> Stephen
> > >>>>>>
> > >>>>>> [1] http://www.apache.org/dev/publishing-maven-artifacts.html
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >
> >
>
Re: SNAPSHOT deployment
Posted by Matt Franklin <m....@gmail.com>.
On Wed, Mar 11, 2015 at 6:02 AM Stephen Mallette <sp...@gmail.com>
wrote:
> Matt, thanks for setting that up. I like that SNAPSHOT deployment is part
> of the build process. I was wondering if you are able to share the
> credentials for deploying SNAPSHOTs so that we could have the flexibility
> to deploy manually if needed, to setup deployment from another external
> build server, etc. Is that possible?
>
It is possible and will be required for the release manager (RM) when the
release is cut.
At one point they were manually enabling authentication for incubator
projects. I will send an e-mail to the infra list to verify that this is
not an issue. You could also attempt to do a mvn deploy, but in the event
it fails, it will lock your account out and you will have to reset the
password through https://id.apache.org.
>
> On Wed, Mar 11, 2015 at 6:34 AM, pieter-gmail <pi...@gmail.com>
> wrote:
>
> > Thanks
> > Pieter
> >
> >
> > On 10/03/2015 20:40, Matt Franklin wrote:
> >
> >> On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <m....@gmail.com>
> >> wrote:
> >>
> >> I have configured the Jenkins build to publish SNAPSHOT artifacts.
> >>>
> >>> If the build ever finishes, I will verify SNAPSHOTs got published and
> let
> >>> the list know.
> >>>
> >>> https://builds.apache.org/job/tinkerpop-master/8
> >>>
> >>> The build seems to hang on certain servers. I am going to restrict
> the
> >> build to the machines that it has successfully completed on, or hasn't
> run
> >> on yet. Assuming this works, we will have consistent snapshots
> deployed.
> >>
> >> Build 9 did succeed and produced the following SNAPSHOTs
> >>
> >> https://repository.apache.org/content/groups/snapshots/org/
> >> apache/tinkerpop/
> >>
> >>
> >>
> >>>
> >>> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <m.ben.franklin@gmail.com
> >
> >>> wrote:
> >>>
> >>> Apologies on the delay. I have been out of the country on business and
> >>>> haven't had a free second. I will look into it this week.
> >>>>
> >>>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <pieter.martin@gmail.com
> >
> >>>> wrote:
> >>>>
> >>>> Hi,
> >>>>>
> >>>>> Is this going to happen?
> >>>>> Makes live way easier for (cutting edge) projects that are already
> >>>>> developing against tp3.
> >>>>>
> >>>>> Thanks
> >>>>> Pieter
> >>>>>
> >>>>> On 10/02/2015 18:11, Stephen Mallette wrote:
> >>>>>
> >>>>>> Mentors,
> >>>>>>
> >>>>>> We've always deployed SNAPSHOT releases to Sonatype:
> >>>>>>
> >>>>>> https://oss.sonatype.org/content/repositories/
> >>>>>> snapshots/com/tinkerpop/
> >>>>>>
> >>>>>> Based on that, I have couple of questions:
> >>>>>>
> >>>>>> 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache?
> I
> >>>>>>
> >>>>> did
> >>>>>
> >>>>>> find this page[1] - do we simply follow those instructions?
> >>>>>> 2. While under incubator, are we allowed to publish SNAPSHOT
> releases?
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> Stephen
> >>>>>>
> >>>>>> [1] http://www.apache.org/dev/publishing-maven-artifacts.html
> >>>>>>
> >>>>>>
> >>>>>
> >
>
Re: SNAPSHOT deployment
Posted by Stephen Mallette <sp...@gmail.com>.
Matt, thanks for setting that up. I like that SNAPSHOT deployment is part
of the build process. I was wondering if you are able to share the
credentials for deploying SNAPSHOTs so that we could have the flexibility
to deploy manually if needed, to setup deployment from another external
build server, etc. Is that possible?
On Wed, Mar 11, 2015 at 6:34 AM, pieter-gmail <pi...@gmail.com>
wrote:
> Thanks
> Pieter
>
>
> On 10/03/2015 20:40, Matt Franklin wrote:
>
>> On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <m....@gmail.com>
>> wrote:
>>
>> I have configured the Jenkins build to publish SNAPSHOT artifacts.
>>>
>>> If the build ever finishes, I will verify SNAPSHOTs got published and let
>>> the list know.
>>>
>>> https://builds.apache.org/job/tinkerpop-master/8
>>>
>>> The build seems to hang on certain servers. I am going to restrict the
>> build to the machines that it has successfully completed on, or hasn't run
>> on yet. Assuming this works, we will have consistent snapshots deployed.
>>
>> Build 9 did succeed and produced the following SNAPSHOTs
>>
>> https://repository.apache.org/content/groups/snapshots/org/
>> apache/tinkerpop/
>>
>>
>>
>>>
>>> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <m....@gmail.com>
>>> wrote:
>>>
>>> Apologies on the delay. I have been out of the country on business and
>>>> haven't had a free second. I will look into it this week.
>>>>
>>>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <pi...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> Is this going to happen?
>>>>> Makes live way easier for (cutting edge) projects that are already
>>>>> developing against tp3.
>>>>>
>>>>> Thanks
>>>>> Pieter
>>>>>
>>>>> On 10/02/2015 18:11, Stephen Mallette wrote:
>>>>>
>>>>>> Mentors,
>>>>>>
>>>>>> We've always deployed SNAPSHOT releases to Sonatype:
>>>>>>
>>>>>> https://oss.sonatype.org/content/repositories/
>>>>>> snapshots/com/tinkerpop/
>>>>>>
>>>>>> Based on that, I have couple of questions:
>>>>>>
>>>>>> 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I
>>>>>>
>>>>> did
>>>>>
>>>>>> find this page[1] - do we simply follow those instructions?
>>>>>> 2. While under incubator, are we allowed to publish SNAPSHOT releases?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Stephen
>>>>>>
>>>>>> [1] http://www.apache.org/dev/publishing-maven-artifacts.html
>>>>>>
>>>>>>
>>>>>
>
Re: SNAPSHOT deployment
Posted by pieter-gmail <pi...@gmail.com>.
Thanks
Pieter
On 10/03/2015 20:40, Matt Franklin wrote:
> On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <m....@gmail.com>
> wrote:
>
>> I have configured the Jenkins build to publish SNAPSHOT artifacts.
>>
>> If the build ever finishes, I will verify SNAPSHOTs got published and let
>> the list know.
>>
>> https://builds.apache.org/job/tinkerpop-master/8
>>
> The build seems to hang on certain servers. I am going to restrict the
> build to the machines that it has successfully completed on, or hasn't run
> on yet. Assuming this works, we will have consistent snapshots deployed.
>
> Build 9 did succeed and produced the following SNAPSHOTs
>
> https://repository.apache.org/content/groups/snapshots/org/apache/tinkerpop/
>
>
>>
>>
>> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <m....@gmail.com>
>> wrote:
>>
>>> Apologies on the delay. I have been out of the country on business and
>>> haven't had a free second. I will look into it this week.
>>>
>>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <pi...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Is this going to happen?
>>>> Makes live way easier for (cutting edge) projects that are already
>>>> developing against tp3.
>>>>
>>>> Thanks
>>>> Pieter
>>>>
>>>> On 10/02/2015 18:11, Stephen Mallette wrote:
>>>>> Mentors,
>>>>>
>>>>> We've always deployed SNAPSHOT releases to Sonatype:
>>>>>
>>>>> https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
>>>>>
>>>>> Based on that, I have couple of questions:
>>>>>
>>>>> 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I
>>>> did
>>>>> find this page[1] - do we simply follow those instructions?
>>>>> 2. While under incubator, are we allowed to publish SNAPSHOT releases?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Stephen
>>>>>
>>>>> [1] http://www.apache.org/dev/publishing-maven-artifacts.html
>>>>>
>>>>
Re: SNAPSHOT deployment
Posted by Matt Franklin <m....@gmail.com>.
On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <m....@gmail.com>
wrote:
> I have configured the Jenkins build to publish SNAPSHOT artifacts.
>
> If the build ever finishes, I will verify SNAPSHOTs got published and let
> the list know.
>
> https://builds.apache.org/job/tinkerpop-master/8
>
The build seems to hang on certain servers. I am going to restrict the
build to the machines that it has successfully completed on, or hasn't run
on yet. Assuming this works, we will have consistent snapshots deployed.
Build 9 did succeed and produced the following SNAPSHOTs
https://repository.apache.org/content/groups/snapshots/org/apache/tinkerpop/
>
>
>
> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <m....@gmail.com>
> wrote:
>
>> Apologies on the delay. I have been out of the country on business and
>> haven't had a free second. I will look into it this week.
>>
>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <pi...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Is this going to happen?
>>> Makes live way easier for (cutting edge) projects that are already
>>> developing against tp3.
>>>
>>> Thanks
>>> Pieter
>>>
>>> On 10/02/2015 18:11, Stephen Mallette wrote:
>>> > Mentors,
>>> >
>>> > We've always deployed SNAPSHOT releases to Sonatype:
>>> >
>>> > https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
>>> >
>>> > Based on that, I have couple of questions:
>>> >
>>> > 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I
>>> did
>>> > find this page[1] - do we simply follow those instructions?
>>> > 2. While under incubator, are we allowed to publish SNAPSHOT releases?
>>> >
>>> > Thanks,
>>> >
>>> > Stephen
>>> >
>>> > [1] http://www.apache.org/dev/publishing-maven-artifacts.html
>>> >
>>>
>>>
Re: SNAPSHOT deployment
Posted by Matt Franklin <m....@gmail.com>.
I have configured the Jenkins build to publish SNAPSHOT artifacts.
If the build ever finishes, I will verify SNAPSHOTs got published and let
the list know.
https://builds.apache.org/job/tinkerpop-master/8
On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <m....@gmail.com>
wrote:
> Apologies on the delay. I have been out of the country on business and
> haven't had a free second. I will look into it this week.
>
> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <pi...@gmail.com>
> wrote:
>
>> Hi,
>>
>> Is this going to happen?
>> Makes live way easier for (cutting edge) projects that are already
>> developing against tp3.
>>
>> Thanks
>> Pieter
>>
>> On 10/02/2015 18:11, Stephen Mallette wrote:
>> > Mentors,
>> >
>> > We've always deployed SNAPSHOT releases to Sonatype:
>> >
>> > https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
>> >
>> > Based on that, I have couple of questions:
>> >
>> > 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I
>> did
>> > find this page[1] - do we simply follow those instructions?
>> > 2. While under incubator, are we allowed to publish SNAPSHOT releases?
>> >
>> > Thanks,
>> >
>> > Stephen
>> >
>> > [1] http://www.apache.org/dev/publishing-maven-artifacts.html
>> >
>>
>>
Re: SNAPSHOT deployment
Posted by Matt Franklin <m....@gmail.com>.
Apologies on the delay. I have been out of the country on business and
haven't had a free second. I will look into it this week.
On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <pi...@gmail.com>
wrote:
> Hi,
>
> Is this going to happen?
> Makes live way easier for (cutting edge) projects that are already
> developing against tp3.
>
> Thanks
> Pieter
>
> On 10/02/2015 18:11, Stephen Mallette wrote:
> > Mentors,
> >
> > We've always deployed SNAPSHOT releases to Sonatype:
> >
> > https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
> >
> > Based on that, I have couple of questions:
> >
> > 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did
> > find this page[1] - do we simply follow those instructions?
> > 2. While under incubator, are we allowed to publish SNAPSHOT releases?
> >
> > Thanks,
> >
> > Stephen
> >
> > [1] http://www.apache.org/dev/publishing-maven-artifacts.html
> >
>
>
Re: SNAPSHOT deployment
Posted by pieter-gmail <pi...@gmail.com>.
Hi,
Is this going to happen?
Makes live way easier for (cutting edge) projects that are already
developing against tp3.
Thanks
Pieter
On 10/02/2015 18:11, Stephen Mallette wrote:
> Mentors,
>
> We've always deployed SNAPSHOT releases to Sonatype:
>
> https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
>
> Based on that, I have couple of questions:
>
> 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did
> find this page[1] - do we simply follow those instructions?
> 2. While under incubator, are we allowed to publish SNAPSHOT releases?
>
> Thanks,
>
> Stephen
>
> [1] http://www.apache.org/dev/publishing-maven-artifacts.html
>
Re: SNAPSHOT deployment
Posted by David Nalley <da...@gnsa.us>.
On Wed, Feb 11, 2015 at 9:03 AM, Matt Franklin <m....@gmail.com> wrote:
> On Tue Feb 10 2015 at 11:32:18 PM David Nalley <da...@gnsa.us> wrote:
>
>> On Tue, Feb 10, 2015 at 11:11 AM, Stephen Mallette <sp...@gmail.com>
>> wrote:
>> > Mentors,
>> >
>> > We've always deployed SNAPSHOT releases to Sonatype:
>> >
>> > https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
>> >
>> > Based on that, I have couple of questions:
>> >
>> > 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did
>> > find this page[1] - do we simply follow those instructions?
>> > 2. While under incubator, are we allowed to publish SNAPSHOT releases?
>> >
>>
>> Apache projects publish via our own Nexus instance.
>> Sonatype mirrors our 'released versions' (something that has been
>> officially released) but they do not mirror SNAPSHOTS.
>>
>
> Thanks David. I thought Sonatype mirrored the snapshots too, but good to
> know they don't.
Sonatype allows the publishing of SNAPSHOTs for a number of projects,
I believe that we have elected to to have them do that for us. I could
be wrong, though. I looked through a few projects that I know to have
SNAPSHOTs on repository.a.o and didn't see them on central.
--David
Re: SNAPSHOT deployment
Posted by Matt Franklin <m....@gmail.com>.
On Tue Feb 10 2015 at 11:32:18 PM David Nalley <da...@gnsa.us> wrote:
> On Tue, Feb 10, 2015 at 11:11 AM, Stephen Mallette <sp...@gmail.com>
> wrote:
> > Mentors,
> >
> > We've always deployed SNAPSHOT releases to Sonatype:
> >
> > https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
> >
> > Based on that, I have couple of questions:
> >
> > 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did
> > find this page[1] - do we simply follow those instructions?
> > 2. While under incubator, are we allowed to publish SNAPSHOT releases?
> >
>
> Apache projects publish via our own Nexus instance.
> Sonatype mirrors our 'released versions' (something that has been
> officially released) but they do not mirror SNAPSHOTS.
>
Thanks David. I thought Sonatype mirrored the snapshots too, but good to
know they don't.
>
> Apache projects are prohibited from promoting to their users
> SNAPSHOTs, but can promote them on their dev lists, and in other
> places that the developers (but not users) of their project will see.
>
> Just a terminology thing, but SNAPSHOT and release are two different
> things here. Releases are something that your project's PMC has
> vetted, voted on, and approved for release. SNAPSHOTs (here) are
> artifacts that are intended to only be seen by the developers of the
> project, or perhaps users who want to test what is going to be the
> next release. Some projects vote on things like alpha and beta
> releases, and then publish those with alpha and beta titles to set
> expectations for users but also allow them to widely promote the
> release.
>
> --David
>
>
> --David
>
Re: SNAPSHOT deployment
Posted by Stephen Mallette <sp...@gmail.com>.
Matt/James,
Has there been any opportunity for either of you to look into setting up
our ability to deploy SNAPSHOTs to repository.apache.org ?
Thanks,
Stephen
On Wed, Feb 11, 2015 at 7:27 AM, Stephen Mallette <sp...@gmail.com>
wrote:
> Thanks for all of your responses. I'd just like to summarize for my own
> benefit:
>
> 1. Matt/James are taking the task of setting up our ability to deploy to
> repository.apache.org - we look forward to hearing when that will be
> ready.
> 2. We deploy both full releases and SNAPSHOTs to this repository. When we
> deploy to this repository, such deployments are automatically mirrored to
> central. SNAPSHOTs are not mirrored anywhere and those wishing to
> experiment with them must get them from repository.apache.org.
> 3. We should never promote SNAPSHOT releases anywhere except the dev
> mailing list.
> 4. We are free to publish SNAPSHOTs while under incubator.
> 5. I think we understand the process of "release" at this point, but for
> completeness of all that was said, a "release" is determined by vote via
> the PMC. A "release" is meant to be public and promoted to users.
>
>
> On Tue, Feb 10, 2015 at 11:31 PM, David Nalley <da...@gnsa.us> wrote:
>
>> On Tue, Feb 10, 2015 at 11:11 AM, Stephen Mallette <sp...@gmail.com>
>> wrote:
>> > Mentors,
>> >
>> > We've always deployed SNAPSHOT releases to Sonatype:
>> >
>> > https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
>> >
>> > Based on that, I have couple of questions:
>> >
>> > 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I
>> did
>> > find this page[1] - do we simply follow those instructions?
>> > 2. While under incubator, are we allowed to publish SNAPSHOT releases?
>> >
>>
>> Apache projects publish via our own Nexus instance.
>> Sonatype mirrors our 'released versions' (something that has been
>> officially released) but they do not mirror SNAPSHOTS.
>>
>> Apache projects are prohibited from promoting to their users
>> SNAPSHOTs, but can promote them on their dev lists, and in other
>> places that the developers (but not users) of their project will see.
>>
>> Just a terminology thing, but SNAPSHOT and release are two different
>> things here. Releases are something that your project's PMC has
>> vetted, voted on, and approved for release. SNAPSHOTs (here) are
>> artifacts that are intended to only be seen by the developers of the
>> project, or perhaps users who want to test what is going to be the
>> next release. Some projects vote on things like alpha and beta
>> releases, and then publish those with alpha and beta titles to set
>> expectations for users but also allow them to widely promote the
>> release.
>>
>> --David
>>
>>
>> --David
>>
>
>
Re: SNAPSHOT deployment
Posted by Stephen Mallette <sp...@gmail.com>.
Thanks for all of your responses. I'd just like to summarize for my own
benefit:
1. Matt/James are taking the task of setting up our ability to deploy to
repository.apache.org - we look forward to hearing when that will be ready.
2. We deploy both full releases and SNAPSHOTs to this repository. When we
deploy to this repository, such deployments are automatically mirrored to
central. SNAPSHOTs are not mirrored anywhere and those wishing to
experiment with them must get them from repository.apache.org.
3. We should never promote SNAPSHOT releases anywhere except the dev
mailing list.
4. We are free to publish SNAPSHOTs while under incubator.
5. I think we understand the process of "release" at this point, but for
completeness of all that was said, a "release" is determined by vote via
the PMC. A "release" is meant to be public and promoted to users.
On Tue, Feb 10, 2015 at 11:31 PM, David Nalley <da...@gnsa.us> wrote:
> On Tue, Feb 10, 2015 at 11:11 AM, Stephen Mallette <sp...@gmail.com>
> wrote:
> > Mentors,
> >
> > We've always deployed SNAPSHOT releases to Sonatype:
> >
> > https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
> >
> > Based on that, I have couple of questions:
> >
> > 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did
> > find this page[1] - do we simply follow those instructions?
> > 2. While under incubator, are we allowed to publish SNAPSHOT releases?
> >
>
> Apache projects publish via our own Nexus instance.
> Sonatype mirrors our 'released versions' (something that has been
> officially released) but they do not mirror SNAPSHOTS.
>
> Apache projects are prohibited from promoting to their users
> SNAPSHOTs, but can promote them on their dev lists, and in other
> places that the developers (but not users) of their project will see.
>
> Just a terminology thing, but SNAPSHOT and release are two different
> things here. Releases are something that your project's PMC has
> vetted, voted on, and approved for release. SNAPSHOTs (here) are
> artifacts that are intended to only be seen by the developers of the
> project, or perhaps users who want to test what is going to be the
> next release. Some projects vote on things like alpha and beta
> releases, and then publish those with alpha and beta titles to set
> expectations for users but also allow them to widely promote the
> release.
>
> --David
>
>
> --David
>
Re: SNAPSHOT deployment
Posted by David Nalley <da...@gnsa.us>.
On Tue, Feb 10, 2015 at 11:11 AM, Stephen Mallette <sp...@gmail.com> wrote:
> Mentors,
>
> We've always deployed SNAPSHOT releases to Sonatype:
>
> https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
>
> Based on that, I have couple of questions:
>
> 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did
> find this page[1] - do we simply follow those instructions?
> 2. While under incubator, are we allowed to publish SNAPSHOT releases?
>
Apache projects publish via our own Nexus instance.
Sonatype mirrors our 'released versions' (something that has been
officially released) but they do not mirror SNAPSHOTS.
Apache projects are prohibited from promoting to their users
SNAPSHOTs, but can promote them on their dev lists, and in other
places that the developers (but not users) of their project will see.
Just a terminology thing, but SNAPSHOT and release are two different
things here. Releases are something that your project's PMC has
vetted, voted on, and approved for release. SNAPSHOTs (here) are
artifacts that are intended to only be seen by the developers of the
project, or perhaps users who want to test what is going to be the
next release. Some projects vote on things like alpha and beta
releases, and then publish those with alpha and beta titles to set
expectations for users but also allow them to widely promote the
release.
--David
--David
Re: SNAPSHOT deployment
Posted by James Carman <ja...@carmanconsulting.com>.
If like to help set this up if that's possible, Matt. I need to learn
about this. :)
On Tuesday, February 10, 2015, Matt Franklin <m....@gmail.com>
wrote:
> We can publish snapshots via repository.apache.org. These should get
> mirrored to central, the same as releases.
>
> There are some things we need to do in order to get you all setup to
> publish. I am mobile at the moment and will follow up with the specifics
> when I am able, unless someone beats me to it.
> On Tue, Feb 10, 2015 at 11:12 Stephen Mallette <spmallette@gmail.com
> <javascript:;>> wrote:
>
> > Mentors,
> >
> > We've always deployed SNAPSHOT releases to Sonatype:
> >
> > https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
> >
> > Based on that, I have couple of questions:
> >
> > 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did
> > find this page[1] - do we simply follow those instructions?
> > 2. While under incubator, are we allowed to publish SNAPSHOT releases?
> >
> > Thanks,
> >
> > Stephen
> >
> > [1] http://www.apache.org/dev/publishing-maven-artifacts.html
> >
>
Re: SNAPSHOT deployment
Posted by Matt Franklin <m....@gmail.com>.
We can publish snapshots via repository.apache.org. These should get
mirrored to central, the same as releases.
There are some things we need to do in order to get you all setup to
publish. I am mobile at the moment and will follow up with the specifics
when I am able, unless someone beats me to it.
On Tue, Feb 10, 2015 at 11:12 Stephen Mallette <sp...@gmail.com> wrote:
> Mentors,
>
> We've always deployed SNAPSHOT releases to Sonatype:
>
> https://oss.sonatype.org/content/repositories/snapshots/com/tinkerpop/
>
> Based on that, I have couple of questions:
>
> 1. Will we still deploy SNAPSHOT releases to Sonatype under Apache? I did
> find this page[1] - do we simply follow those instructions?
> 2. While under incubator, are we allowed to publish SNAPSHOT releases?
>
> Thanks,
>
> Stephen
>
> [1] http://www.apache.org/dev/publishing-maven-artifacts.html
>