Re: Help with migrating one of OpenJPA classes to commons-collections4

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
Moving conversation to dev@ list

I was able to create branch using gitbox remote
Will proceed,

Thanks for the tip


On Tue, 18 Dec 2018 at 21:14, Gilles <[hidden email]> wrote:

> Hi.
>
> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> > Hello Gilles,
> >
> > I read documentation and as far as I can see To perform release I
> > need
> > rights to create branch
> >
> > git remote -v
> > origin [hidden email]:apache/commons-collections.git (fetch)
> > origin [hidden email]:apache/commons-collections.git (push)
> >
> > git push -u origin 4.3-release
> > ERROR: Permission to apache/commons-collections.git denied to
> > solomax.
> > fatal: Could not read from remote repository.
> >
> > Please make sure you have the correct access rights
> > and the repository exists.
>
> The repository (at Apache) is here:
>    https://gitbox.apache.org/repos/asf?p=commons-collections.git
>
> We were told that it should now be possible to also write
> through GitHub, but I don't know if and how it should work.
>
> IMO, the easiest would be to clone the above, and try again
> with that.  [If it still does not work, then perhaps the issue
> is that the "all-Apache-committers-are-committers" resolution
> was not applied.]
>
> Gilles
>
> P.S. We should move this conversation over to the "dev" ML.
>
> >
> > Shall I use SVN? Or some other remote?
> >
> >
> >
> > On Tue, 18 Dec 2018 at 16:04, Maxim Solodovnik <[hidden email]>
> > wrote:
> >
> >> Thanks Gilles,
> >>
> >> will try to create RC tonight
> >>
> >> On Tue, 18 Dec 2018 at 15:55, Gilles <[hidden email]>
> >> wrote:
> >>
> >>> Hi.
> >>>
> >>> On Tue, 18 Dec 2018 09:52:15 +0700, Maxim Solodovnik wrote:
> >>> > I can create RC, no problem
> >>> > But
> >>> > 1) I need my signing key [1] to be added to official KEYS
> >>>
> >>> The file is here:
> >>>    https://dist.apache.org/repos/dist/release/commons/KEYS
> >>>
> >>> > 2) Do you have description of your release process? I was unable
> >>> to
> >>> > find one
> >>>
> >>> http://commons.apache.org/proper/commons-release-plugin/index.html
> >>>
> >>> Also, a step-by-step recipe is here:
> >>>
> >>>
> >>>
> >>>
> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt
> >>>
> >>> [It is for a multimodule maven project ("Commons RNG"); it
> >>> mentions problems with the release process that might need
> >>> manual adjustments.]
> >>>
> >>> If you encounter something that does not work as noted,
> >>> please report it here, and on the bug tracking system:
> >>>    https://issues.apache.org/jira/projects/COMMONSSITE
> >>>
> >>> > 3) most probably I will need some rights
> >>>
> >>> The "Commons" project has granted "write" access to all
> >>> Apache committers.
> >>> [But some repositories perhaps miss the actual settings
> >>> to make it work.  You'll have to try...]
> >>>
> >>> HTH,
> >>> Gilles
> >>>
> >>> > [1] https://github.com/apache/openmeetings/blob/master/KEYS#L88
> >>> >
> >>> > On Tue, 18 Dec 2018 at 01:06, sebb <[hidden email]> wrote:
> >>> >
> >>> >> On Mon, 17 Dec 2018 at 15:38, Gary Gregory
> >>> <[hidden email]>
> >>> >> wrote:
> >>> >> >
> >>> >> > I am on the road driving this week, my availability is
> >>> limited.
> >>> >> >
> >>> >> > WRT being a RM, I think you need PMC karma for that. Sebb
> >>> might be
> >>> >> able
> >>> >> to
> >>> >> > confirm.
> >>> >>
> >>> >> Creating the dist/dev release candidate only requires project
> >>> >> committer karma; Commons requires the same for dist/release
> >>> >>
> >>> >> I don't know about Nexus; I imagine at least LDAP commons
> >>> committer
> >>> >> membership is required.
> >>> >>
> >>> >> There's no harm in trying to create an RC.
> >>> >>
> >>> >> > Gary
> >>> >> >
> >>> >> > On Mon, Dec 17, 2018, 03:59 Gilles
> >>> <[hidden email]
> >>> >> wrote:
> >>> >> >
> >>> >> > > Hi.
> >>> >> > >
> >>> >> > > On Mon, 17 Dec 2018 15:12:16 +0700, Maxim Solodovnik wrote:
> >>> >> > > > Hello Gary,
> >>> >> > > >
> >>> >> > > > Is there any progress? :)
> >>> >> > >
> >>> >> > > Suggestion: Be the release manager of 4.3.
> >>> >> > >
> >>> >> > > Regards,
> >>> >> > > Gilles
> >>> >> > >
> >>> >> > > >
> >>> >> > > > On Tue, 4 Dec 2018 at 00:07, Gary Gregory
> >>> >> <[hidden email]>
> >>> >> > > > wrote:
> >>> >> > > >
> >>> >> > > >> [...]
> >>> >> > >
> >>> >> > >
> >>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
It seems I'm unable to commit to SVN:

URL: https://dist.apache.org/repos/dist/release/commons

Sending        KEYS
Transmitting file data .svn: E195023: Commit failed (details follow):
svn: E195023: Changing file
'/home/solomax/work/apache-dist/release/commons/KEYS' is forbidden by the
server
svn: E175013: Access to
'/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden

Can someone help me with access rights?

On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik <[hidden email]> wrote:

> Moving conversation to dev@ list
>
> I was able to create branch using gitbox remote
> Will proceed,
>
> Thanks for the tip
>
>
> On Tue, 18 Dec 2018 at 21:14, Gilles <[hidden email]> wrote:
>
>> Hi.
>>
>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
>> > Hello Gilles,
>> >
>> > I read documentation and as far as I can see To perform release I
>> > need
>> > rights to create branch
>> >
>> > git remote -v
>> > origin [hidden email]:apache/commons-collections.git (fetch)
>> > origin [hidden email]:apache/commons-collections.git (push)
>> >
>> > git push -u origin 4.3-release
>> > ERROR: Permission to apache/commons-collections.git denied to
>> > solomax.
>> > fatal: Could not read from remote repository.
>> >
>> > Please make sure you have the correct access rights
>> > and the repository exists.
>>
>> The repository (at Apache) is here:
>>    https://gitbox.apache.org/repos/asf?p=commons-collections.git
>>
>> We were told that it should now be possible to also write
>> through GitHub, but I don't know if and how it should work.
>>
>> IMO, the easiest would be to clone the above, and try again
>> with that.  [If it still does not work, then perhaps the issue
>> is that the "all-Apache-committers-are-committers" resolution
>> was not applied.]
>>
>> Gilles
>>
>> P.S. We should move this conversation over to the "dev" ML.
>>
>> >
>> > Shall I use SVN? Or some other remote?
>> >
>> >
>> >
>> > On Tue, 18 Dec 2018 at 16:04, Maxim Solodovnik <[hidden email]>
>> > wrote:
>> >
>> >> Thanks Gilles,
>> >>
>> >> will try to create RC tonight
>> >>
>> >> On Tue, 18 Dec 2018 at 15:55, Gilles <[hidden email]>
>> >> wrote:
>> >>
>> >>> Hi.
>> >>>
>> >>> On Tue, 18 Dec 2018 09:52:15 +0700, Maxim Solodovnik wrote:
>> >>> > I can create RC, no problem
>> >>> > But
>> >>> > 1) I need my signing key [1] to be added to official KEYS
>> >>>
>> >>> The file is here:
>> >>>    https://dist.apache.org/repos/dist/release/commons/KEYS
>> >>>
>> >>> > 2) Do you have description of your release process? I was unable
>> >>> to
>> >>> > find one
>> >>>
>> >>> http://commons.apache.org/proper/commons-release-plugin/index.html
>> >>>
>> >>> Also, a step-by-step recipe is here:
>> >>>
>> >>>
>> >>>
>> >>>
>> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt
>> >>>
>> >>> [It is for a multimodule maven project ("Commons RNG"); it
>> >>> mentions problems with the release process that might need
>> >>> manual adjustments.]
>> >>>
>> >>> If you encounter something that does not work as noted,
>> >>> please report it here, and on the bug tracking system:
>> >>>    https://issues.apache.org/jira/projects/COMMONSSITE
>> >>>
>> >>> > 3) most probably I will need some rights
>> >>>
>> >>> The "Commons" project has granted "write" access to all
>> >>> Apache committers.
>> >>> [But some repositories perhaps miss the actual settings
>> >>> to make it work.  You'll have to try...]
>> >>>
>> >>> HTH,
>> >>> Gilles
>> >>>
>> >>> > [1] https://github.com/apache/openmeetings/blob/master/KEYS#L88
>> >>> >
>> >>> > On Tue, 18 Dec 2018 at 01:06, sebb <[hidden email]> wrote:
>> >>> >
>> >>> >> On Mon, 17 Dec 2018 at 15:38, Gary Gregory
>> >>> <[hidden email]>
>> >>> >> wrote:
>> >>> >> >
>> >>> >> > I am on the road driving this week, my availability is
>> >>> limited.
>> >>> >> >
>> >>> >> > WRT being a RM, I think you need PMC karma for that. Sebb
>> >>> might be
>> >>> >> able
>> >>> >> to
>> >>> >> > confirm.
>> >>> >>
>> >>> >> Creating the dist/dev release candidate only requires project
>> >>> >> committer karma; Commons requires the same for dist/release
>> >>> >>
>> >>> >> I don't know about Nexus; I imagine at least LDAP commons
>> >>> committer
>> >>> >> membership is required.
>> >>> >>
>> >>> >> There's no harm in trying to create an RC.
>> >>> >>
>> >>> >> > Gary
>> >>> >> >
>> >>> >> > On Mon, Dec 17, 2018, 03:59 Gilles
>> >>> <[hidden email]
>> >>> >> wrote:
>> >>> >> >
>> >>> >> > > Hi.
>> >>> >> > >
>> >>> >> > > On Mon, 17 Dec 2018 15:12:16 +0700, Maxim Solodovnik wrote:
>> >>> >> > > > Hello Gary,
>> >>> >> > > >
>> >>> >> > > > Is there any progress? :)
>> >>> >> > >
>> >>> >> > > Suggestion: Be the release manager of 4.3.
>> >>> >> > >
>> >>> >> > > Regards,
>> >>> >> > > Gilles
>> >>> >> > >
>> >>> >> > > >
>> >>> >> > > > On Tue, 4 Dec 2018 at 00:07, Gary Gregory
>> >>> >> <[hidden email]>
>> >>> >> > > > wrote:
>> >>> >> > > >
>> >>> >> > > >> [...]
>> >>> >> > >
>> >>> >> > >
>> >>>
>> >>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: [hidden email]
>> >>> For additional commands, e-mail: [hidden email]
>> >>>
>> >>>
>> >>
>> >> --
>> >> WBR
>> >> Maxim aka solomax
>> >>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> --
> WBR
> Maxim aka solomax
>


--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Gilles Sadowski
On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:

> It seems I'm unable to commit to SVN:
>
> URL: https://dist.apache.org/repos/dist/release/commons
>
> Sending        KEYS
> Transmitting file data .svn: E195023: Commit failed (details follow):
> svn: E195023: Changing file
> '/home/solomax/work/apache-dist/release/commons/KEYS' is forbidden by
> the
> server
> svn: E175013: Access to
> '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden
>
> Can someone help me with access rights?

Not me.
But I've added your key (revision 31593).

Hope it gets you a little further,
Gilles

>
> On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik <[hidden email]>
> wrote:
>
>> Moving conversation to dev@ list
>>
>> I was able to create branch using gitbox remote
>> Will proceed,
>>
>> Thanks for the tip
>>
>>
>> On Tue, 18 Dec 2018 at 21:14, Gilles <[hidden email]>
>> wrote:
>>
>>> Hi.
>>>
>>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
>>> > Hello Gilles,
>>> >
>>> > I read documentation and as far as I can see To perform release I
>>> > need
>>> > rights to create branch
>>> >
>>> > git remote -v
>>> > origin [hidden email]:apache/commons-collections.git (fetch)
>>> > origin [hidden email]:apache/commons-collections.git (push)
>>> >
>>> > git push -u origin 4.3-release
>>> > ERROR: Permission to apache/commons-collections.git denied to
>>> > solomax.
>>> > fatal: Could not read from remote repository.
>>> >
>>> > Please make sure you have the correct access rights
>>> > and the repository exists.
>>>
>>> The repository (at Apache) is here:
>>>    https://gitbox.apache.org/repos/asf?p=commons-collections.git
>>>
>>> We were told that it should now be possible to also write
>>> through GitHub, but I don't know if and how it should work.
>>>
>>> IMO, the easiest would be to clone the above, and try again
>>> with that.  [If it still does not work, then perhaps the issue
>>> is that the "all-Apache-committers-are-committers" resolution
>>> was not applied.]
>>>
>>> Gilles
>>>
>>> P.S. We should move this conversation over to the "dev" ML.
>>>
>>> >
>>> > Shall I use SVN? Or some other remote?
>>> >
>>> >
>>> >
>>> > On Tue, 18 Dec 2018 at 16:04, Maxim Solodovnik
>>> <[hidden email]>
>>> > wrote:
>>> >
>>> >> Thanks Gilles,
>>> >>
>>> >> will try to create RC tonight
>>> >>
>>> >> On Tue, 18 Dec 2018 at 15:55, Gilles
>>> <[hidden email]>
>>> >> wrote:
>>> >>
>>> >>> Hi.
>>> >>>
>>> >>> On Tue, 18 Dec 2018 09:52:15 +0700, Maxim Solodovnik wrote:
>>> >>> > I can create RC, no problem
>>> >>> > But
>>> >>> > 1) I need my signing key [1] to be added to official KEYS
>>> >>>
>>> >>> The file is here:
>>> >>>    https://dist.apache.org/repos/dist/release/commons/KEYS
>>> >>>
>>> >>> > 2) Do you have description of your release process? I was
>>> unable
>>> >>> to
>>> >>> > find one
>>> >>>
>>> >>>
>>> http://commons.apache.org/proper/commons-release-plugin/index.html
>>> >>>
>>> >>> Also, a step-by-step recipe is here:
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>>
>>> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt
>>> >>>
>>> >>> [It is for a multimodule maven project ("Commons RNG"); it
>>> >>> mentions problems with the release process that might need
>>> >>> manual adjustments.]
>>> >>>
>>> >>> If you encounter something that does not work as noted,
>>> >>> please report it here, and on the bug tracking system:
>>> >>>    https://issues.apache.org/jira/projects/COMMONSSITE
>>> >>>
>>> >>> > 3) most probably I will need some rights
>>> >>>
>>> >>> The "Commons" project has granted "write" access to all
>>> >>> Apache committers.
>>> >>> [But some repositories perhaps miss the actual settings
>>> >>> to make it work.  You'll have to try...]
>>> >>>
>>> >>> HTH,
>>> >>> Gilles
>>> >>>
>>> >>> > [1]
>>> https://github.com/apache/openmeetings/blob/master/KEYS#L88
>>> >>> >
>>> >>> > On Tue, 18 Dec 2018 at 01:06, sebb <[hidden email]> wrote:
>>> >>> >
>>> >>> >> On Mon, 17 Dec 2018 at 15:38, Gary Gregory
>>> >>> <[hidden email]>
>>> >>> >> wrote:
>>> >>> >> >
>>> >>> >> > I am on the road driving this week, my availability is
>>> >>> limited.
>>> >>> >> >
>>> >>> >> > WRT being a RM, I think you need PMC karma for that. Sebb
>>> >>> might be
>>> >>> >> able
>>> >>> >> to
>>> >>> >> > confirm.
>>> >>> >>
>>> >>> >> Creating the dist/dev release candidate only requires
>>> project
>>> >>> >> committer karma; Commons requires the same for dist/release
>>> >>> >>
>>> >>> >> I don't know about Nexus; I imagine at least LDAP commons
>>> >>> committer
>>> >>> >> membership is required.
>>> >>> >>
>>> >>> >> There's no harm in trying to create an RC.
>>> >>> >>
>>> >>> >> > Gary
>>> >>> >> >
>>> >>> >> > On Mon, Dec 17, 2018, 03:59 Gilles
>>> >>> <[hidden email]
>>> >>> >> wrote:
>>> >>> >> >
>>> >>> >> > > Hi.
>>> >>> >> > >
>>> >>> >> > > On Mon, 17 Dec 2018 15:12:16 +0700, Maxim Solodovnik
>>> wrote:
>>> >>> >> > > > Hello Gary,
>>> >>> >> > > >
>>> >>> >> > > > Is there any progress? :)
>>> >>> >> > >
>>> >>> >> > > Suggestion: Be the release manager of 4.3.
>>> >>> >> > >
>>> >>> >> > > Regards,
>>> >>> >> > > Gilles
>>> >>> >> > >
>>> >>> >> > > >
>>> >>> >> > > > On Tue, 4 Dec 2018 at 00:07, Gary Gregory
>>> >>> >> <[hidden email]>
>>> >>> >> > > > wrote:
>>> >>> >> > > >
>>> >>> >> > > >> [...]
>>> >>> >> > >
>>> >>> >> > >
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: [hidden email]
>>> >>> For additional commands, e-mail: [hidden email]
>>> >>>
>>> >>>
>>> >>
>>> >> --
>>> >> WBR
>>> >> Maxim aka solomax
>>> >>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
Thanks a lot

Unfortunately the next error is: Failed to deploy artifacts: Could not
transfer artifact org.apache.commons:commons-collections4:jar:4.3 from/to
apache.releases.https (
https://repository.apache.org/service/local/staging/deploy/maven2): Access
denied to:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar

I'm release manger for Apache OpenMeetings and just double-check I can
access Staging Repos at repository.apache.org
, so I guess there are additional restrictions here

would appreciate any help/hint :)

On Tue, 18 Dec 2018 at 22:54, Gilles <[hidden email]> wrote:

> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:
> > It seems I'm unable to commit to SVN:
> >
> > URL: https://dist.apache.org/repos/dist/release/commons
> >
> > Sending        KEYS
> > Transmitting file data .svn: E195023: Commit failed (details follow):
> > svn: E195023: Changing file
> > '/home/solomax/work/apache-dist/release/commons/KEYS' is forbidden by
> > the
> > server
> > svn: E175013: Access to
> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden
> >
> > Can someone help me with access rights?
>
> Not me.
> But I've added your key (revision 31593).
>
> Hope it gets you a little further,
> Gilles
>
> >
> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik <[hidden email]>
> > wrote:
> >
> >> Moving conversation to dev@ list
> >>
> >> I was able to create branch using gitbox remote
> >> Will proceed,
> >>
> >> Thanks for the tip
> >>
> >>
> >> On Tue, 18 Dec 2018 at 21:14, Gilles <[hidden email]>
> >> wrote:
> >>
> >>> Hi.
> >>>
> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> >>> > Hello Gilles,
> >>> >
> >>> > I read documentation and as far as I can see To perform release I
> >>> > need
> >>> > rights to create branch
> >>> >
> >>> > git remote -v
> >>> > origin [hidden email]:apache/commons-collections.git (fetch)
> >>> > origin [hidden email]:apache/commons-collections.git (push)
> >>> >
> >>> > git push -u origin 4.3-release
> >>> > ERROR: Permission to apache/commons-collections.git denied to
> >>> > solomax.
> >>> > fatal: Could not read from remote repository.
> >>> >
> >>> > Please make sure you have the correct access rights
> >>> > and the repository exists.
> >>>
> >>> The repository (at Apache) is here:
> >>>    https://gitbox.apache.org/repos/asf?p=commons-collections.git
> >>>
> >>> We were told that it should now be possible to also write
> >>> through GitHub, but I don't know if and how it should work.
> >>>
> >>> IMO, the easiest would be to clone the above, and try again
> >>> with that.  [If it still does not work, then perhaps the issue
> >>> is that the "all-Apache-committers-are-committers" resolution
> >>> was not applied.]
> >>>
> >>> Gilles
> >>>
> >>> P.S. We should move this conversation over to the "dev" ML.
> >>>
> >>> >
> >>> > Shall I use SVN? Or some other remote?
> >>> >
> >>> >
> >>> >
> >>> > On Tue, 18 Dec 2018 at 16:04, Maxim Solodovnik
> >>> <[hidden email]>
> >>> > wrote:
> >>> >
> >>> >> Thanks Gilles,
> >>> >>
> >>> >> will try to create RC tonight
> >>> >>
> >>> >> On Tue, 18 Dec 2018 at 15:55, Gilles
> >>> <[hidden email]>
> >>> >> wrote:
> >>> >>
> >>> >>> Hi.
> >>> >>>
> >>> >>> On Tue, 18 Dec 2018 09:52:15 +0700, Maxim Solodovnik wrote:
> >>> >>> > I can create RC, no problem
> >>> >>> > But
> >>> >>> > 1) I need my signing key [1] to be added to official KEYS
> >>> >>>
> >>> >>> The file is here:
> >>> >>>    https://dist.apache.org/repos/dist/release/commons/KEYS
> >>> >>>
> >>> >>> > 2) Do you have description of your release process? I was
> >>> unable
> >>> >>> to
> >>> >>> > find one
> >>> >>>
> >>> >>>
> >>> http://commons.apache.org/proper/commons-release-plugin/index.html
> >>> >>>
> >>> >>> Also, a step-by-step recipe is here:
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>>
> >>>
> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt
> >>> >>>
> >>> >>> [It is for a multimodule maven project ("Commons RNG"); it
> >>> >>> mentions problems with the release process that might need
> >>> >>> manual adjustments.]
> >>> >>>
> >>> >>> If you encounter something that does not work as noted,
> >>> >>> please report it here, and on the bug tracking system:
> >>> >>>    https://issues.apache.org/jira/projects/COMMONSSITE
> >>> >>>
> >>> >>> > 3) most probably I will need some rights
> >>> >>>
> >>> >>> The "Commons" project has granted "write" access to all
> >>> >>> Apache committers.
> >>> >>> [But some repositories perhaps miss the actual settings
> >>> >>> to make it work.  You'll have to try...]
> >>> >>>
> >>> >>> HTH,
> >>> >>> Gilles
> >>> >>>
> >>> >>> > [1]
> >>> https://github.com/apache/openmeetings/blob/master/KEYS#L88
> >>> >>> >
> >>> >>> > On Tue, 18 Dec 2018 at 01:06, sebb <[hidden email]> wrote:
> >>> >>> >
> >>> >>> >> On Mon, 17 Dec 2018 at 15:38, Gary Gregory
> >>> >>> <[hidden email]>
> >>> >>> >> wrote:
> >>> >>> >> >
> >>> >>> >> > I am on the road driving this week, my availability is
> >>> >>> limited.
> >>> >>> >> >
> >>> >>> >> > WRT being a RM, I think you need PMC karma for that. Sebb
> >>> >>> might be
> >>> >>> >> able
> >>> >>> >> to
> >>> >>> >> > confirm.
> >>> >>> >>
> >>> >>> >> Creating the dist/dev release candidate only requires
> >>> project
> >>> >>> >> committer karma; Commons requires the same for dist/release
> >>> >>> >>
> >>> >>> >> I don't know about Nexus; I imagine at least LDAP commons
> >>> >>> committer
> >>> >>> >> membership is required.
> >>> >>> >>
> >>> >>> >> There's no harm in trying to create an RC.
> >>> >>> >>
> >>> >>> >> > Gary
> >>> >>> >> >
> >>> >>> >> > On Mon, Dec 17, 2018, 03:59 Gilles
> >>> >>> <[hidden email]
> >>> >>> >> wrote:
> >>> >>> >> >
> >>> >>> >> > > Hi.
> >>> >>> >> > >
> >>> >>> >> > > On Mon, 17 Dec 2018 15:12:16 +0700, Maxim Solodovnik
> >>> wrote:
> >>> >>> >> > > > Hello Gary,
> >>> >>> >> > > >
> >>> >>> >> > > > Is there any progress? :)
> >>> >>> >> > >
> >>> >>> >> > > Suggestion: Be the release manager of 4.3.
> >>> >>> >> > >
> >>> >>> >> > > Regards,
> >>> >>> >> > > Gilles
> >>> >>> >> > >
> >>> >>> >> > > >
> >>> >>> >> > > > On Tue, 4 Dec 2018 at 00:07, Gary Gregory
> >>> >>> >> <[hidden email]>
> >>> >>> >> > > > wrote:
> >>> >>> >> > > >
> >>> >>> >> > > >> [...]
> >>> >>> >> > >
> >>> >>> >> > >
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>> ---------------------------------------------------------------------
> >>> >>> To unsubscribe, e-mail: [hidden email]
> >>> >>> For additional commands, e-mail: [hidden email]
> >>> >>>
> >>> >>>
> >>> >>
> >>> >> --
> >>> >> WBR
> >>> >> Maxim aka solomax
> >>> >>
> >>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Gilles Sadowski
Hello.

On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:

> Thanks a lot
>
> Unfortunately the next error is: Failed to deploy artifacts: Could
> not
> transfer artifact org.apache.commons:commons-collections4:jar:4.3
> from/to
> apache.releases.https (
> https://repository.apache.org/service/local/staging/deploy/maven2): 
> Access
> denied to:
>
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
>
> I'm release manger for Apache OpenMeetings and just double-check I
> can
> access Staging Repos at repository.apache.org
> , so I guess there are additional restrictions here
>
> would appreciate any help/hint :)

I don't know how to change the permissions (I don't think I have
the privilege anyway), and the PMC chair is AFK for a couple more
days IIUC. :-(

Perhaps someone with a taller hat. :-}

Sorry for the inconvenience; it looks like you are first one to
try and exercise those privileges voted several years ago...

Gilles

>
> On Tue, 18 Dec 2018 at 22:54, Gilles <[hidden email]>
> wrote:
>
>> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:
>> > It seems I'm unable to commit to SVN:
>> >
>> > URL: https://dist.apache.org/repos/dist/release/commons
>> >
>> > Sending        KEYS
>> > Transmitting file data .svn: E195023: Commit failed (details
>> follow):
>> > svn: E195023: Changing file
>> > '/home/solomax/work/apache-dist/release/commons/KEYS' is forbidden
>> by
>> > the
>> > server
>> > svn: E175013: Access to
>> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden
>> >
>> > Can someone help me with access rights?
>>
>> Not me.
>> But I've added your key (revision 31593).
>>
>> Hope it gets you a little further,
>> Gilles
>>
>> >
>> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
>> <[hidden email]>
>> > wrote:
>> >
>> >> Moving conversation to dev@ list
>> >>
>> >> I was able to create branch using gitbox remote
>> >> Will proceed,
>> >>
>> >> Thanks for the tip
>> >>
>> >>
>> >> On Tue, 18 Dec 2018 at 21:14, Gilles
>> <[hidden email]>
>> >> wrote:
>> >>
>> >>> Hi.
>> >>>
>> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
>> >>> > Hello Gilles,
>> >>> >
>> >>> > I read documentation and as far as I can see To perform
>> release I
>> >>> > need
>> >>> > rights to create branch
>> >>> >
>> >>> > git remote -v
>> >>> > origin [hidden email]:apache/commons-collections.git (fetch)
>> >>> > origin [hidden email]:apache/commons-collections.git (push)
>> >>> >
>> >>> > git push -u origin 4.3-release
>> >>> > ERROR: Permission to apache/commons-collections.git denied to
>> >>> > solomax.
>> >>> > fatal: Could not read from remote repository.
>> >>> >
>> >>> > Please make sure you have the correct access rights
>> >>> > and the repository exists.
>> >>>
>> >>> The repository (at Apache) is here:
>> >>>    https://gitbox.apache.org/repos/asf?p=commons-collections.git
>> >>>
>> >>> We were told that it should now be possible to also write
>> >>> through GitHub, but I don't know if and how it should work.
>> >>>
>> >>> IMO, the easiest would be to clone the above, and try again
>> >>> with that.  [If it still does not work, then perhaps the issue
>> >>> is that the "all-Apache-committers-are-committers" resolution
>> >>> was not applied.]
>> >>>
>> >>> Gilles
>> >>>
>> >>> P.S. We should move this conversation over to the "dev" ML.
>> >>>
>> >>> >
>> >>> > Shall I use SVN? Or some other remote?
>> >>> >
>> >>> > [...]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
Thanks a lot for the help :)
Glad to check the release process ;)

On Tue, 18 Dec 2018 at 23:19, Gilles <[hidden email]> wrote:

> Hello.
>
> On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
> > Thanks a lot
> >
> > Unfortunately the next error is: Failed to deploy artifacts: Could
> > not
> > transfer artifact org.apache.commons:commons-collections4:jar:4.3
> > from/to
> > apache.releases.https (
> > https://repository.apache.org/service/local/staging/deploy/maven2):
> > Access
> > denied to:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
> >
> > I'm release manger for Apache OpenMeetings and just double-check I
> > can
> > access Staging Repos at repository.apache.org
> > , so I guess there are additional restrictions here
> >
> > would appreciate any help/hint :)
>
> I don't know how to change the permissions (I don't think I have
> the privilege anyway), and the PMC chair is AFK for a couple more
> days IIUC. :-(
>
> Perhaps someone with a taller hat. :-}
>
> Sorry for the inconvenience; it looks like you are first one to
> try and exercise those privileges voted several years ago...
>
> Gilles
>
> >
> > On Tue, 18 Dec 2018 at 22:54, Gilles <[hidden email]>
> > wrote:
> >
> >> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:
> >> > It seems I'm unable to commit to SVN:
> >> >
> >> > URL: https://dist.apache.org/repos/dist/release/commons
> >> >
> >> > Sending        KEYS
> >> > Transmitting file data .svn: E195023: Commit failed (details
> >> follow):
> >> > svn: E195023: Changing file
> >> > '/home/solomax/work/apache-dist/release/commons/KEYS' is forbidden
> >> by
> >> > the
> >> > server
> >> > svn: E175013: Access to
> >> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden
> >> >
> >> > Can someone help me with access rights?
> >>
> >> Not me.
> >> But I've added your key (revision 31593).
> >>
> >> Hope it gets you a little further,
> >> Gilles
> >>
> >> >
> >> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
> >> <[hidden email]>
> >> > wrote:
> >> >
> >> >> Moving conversation to dev@ list
> >> >>
> >> >> I was able to create branch using gitbox remote
> >> >> Will proceed,
> >> >>
> >> >> Thanks for the tip
> >> >>
> >> >>
> >> >> On Tue, 18 Dec 2018 at 21:14, Gilles
> >> <[hidden email]>
> >> >> wrote:
> >> >>
> >> >>> Hi.
> >> >>>
> >> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> >> >>> > Hello Gilles,
> >> >>> >
> >> >>> > I read documentation and as far as I can see To perform
> >> release I
> >> >>> > need
> >> >>> > rights to create branch
> >> >>> >
> >> >>> > git remote -v
> >> >>> > origin [hidden email]:apache/commons-collections.git (fetch)
> >> >>> > origin [hidden email]:apache/commons-collections.git (push)
> >> >>> >
> >> >>> > git push -u origin 4.3-release
> >> >>> > ERROR: Permission to apache/commons-collections.git denied to
> >> >>> > solomax.
> >> >>> > fatal: Could not read from remote repository.
> >> >>> >
> >> >>> > Please make sure you have the correct access rights
> >> >>> > and the repository exists.
> >> >>>
> >> >>> The repository (at Apache) is here:
> >> >>>    https://gitbox.apache.org/repos/asf?p=commons-collections.git
> >> >>>
> >> >>> We were told that it should now be possible to also write
> >> >>> through GitHub, but I don't know if and how it should work.
> >> >>>
> >> >>> IMO, the easiest would be to clone the above, and try again
> >> >>> with that.  [If it still does not work, then perhaps the issue
> >> >>> is that the "all-Apache-committers-are-committers" resolution
> >> >>> was not applied.]
> >> >>>
> >> >>> Gilles
> >> >>>
> >> >>> P.S. We should move this conversation over to the "dev" ML.
> >> >>>
> >> >>> >
> >> >>> > Shall I use SVN? Or some other remote?
> >> >>> >
> >> >>> > [...]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

sebb-2-2
I think the issue with dist/release/commons is that you need to be
listed as a project committer, i.e. you need to be a Commons
committer.

Possibly the same applies to Nexus.

I have added you as a Commons committer.

On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik <[hidden email]> wrote:

>
> Thanks a lot for the help :)
> Glad to check the release process ;)
>
> On Tue, 18 Dec 2018 at 23:19, Gilles <[hidden email]> wrote:
>
> > Hello.
> >
> > On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
> > > Thanks a lot
> > >
> > > Unfortunately the next error is: Failed to deploy artifacts: Could
> > > not
> > > transfer artifact org.apache.commons:commons-collections4:jar:4.3
> > > from/to
> > > apache.releases.https (
> > > https://repository.apache.org/service/local/staging/deploy/maven2):
> > > Access
> > > denied to:
> > >
> > >
> > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
> > >
> > > I'm release manger for Apache OpenMeetings and just double-check I
> > > can
> > > access Staging Repos at repository.apache.org
> > > , so I guess there are additional restrictions here
> > >
> > > would appreciate any help/hint :)
> >
> > I don't know how to change the permissions (I don't think I have
> > the privilege anyway), and the PMC chair is AFK for a couple more
> > days IIUC. :-(
> >
> > Perhaps someone with a taller hat. :-}
> >
> > Sorry for the inconvenience; it looks like you are first one to
> > try and exercise those privileges voted several years ago...
> >
> > Gilles
> >
> > >
> > > On Tue, 18 Dec 2018 at 22:54, Gilles <[hidden email]>
> > > wrote:
> > >
> > >> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:
> > >> > It seems I'm unable to commit to SVN:
> > >> >
> > >> > URL: https://dist.apache.org/repos/dist/release/commons
> > >> >
> > >> > Sending        KEYS
> > >> > Transmitting file data .svn: E195023: Commit failed (details
> > >> follow):
> > >> > svn: E195023: Changing file
> > >> > '/home/solomax/work/apache-dist/release/commons/KEYS' is forbidden
> > >> by
> > >> > the
> > >> > server
> > >> > svn: E175013: Access to
> > >> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden
> > >> >
> > >> > Can someone help me with access rights?
> > >>
> > >> Not me.
> > >> But I've added your key (revision 31593).
> > >>
> > >> Hope it gets you a little further,
> > >> Gilles
> > >>
> > >> >
> > >> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
> > >> <[hidden email]>
> > >> > wrote:
> > >> >
> > >> >> Moving conversation to dev@ list
> > >> >>
> > >> >> I was able to create branch using gitbox remote
> > >> >> Will proceed,
> > >> >>
> > >> >> Thanks for the tip
> > >> >>
> > >> >>
> > >> >> On Tue, 18 Dec 2018 at 21:14, Gilles
> > >> <[hidden email]>
> > >> >> wrote:
> > >> >>
> > >> >>> Hi.
> > >> >>>
> > >> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> > >> >>> > Hello Gilles,
> > >> >>> >
> > >> >>> > I read documentation and as far as I can see To perform
> > >> release I
> > >> >>> > need
> > >> >>> > rights to create branch
> > >> >>> >
> > >> >>> > git remote -v
> > >> >>> > origin [hidden email]:apache/commons-collections.git (fetch)
> > >> >>> > origin [hidden email]:apache/commons-collections.git (push)
> > >> >>> >
> > >> >>> > git push -u origin 4.3-release
> > >> >>> > ERROR: Permission to apache/commons-collections.git denied to
> > >> >>> > solomax.
> > >> >>> > fatal: Could not read from remote repository.
> > >> >>> >
> > >> >>> > Please make sure you have the correct access rights
> > >> >>> > and the repository exists.
> > >> >>>
> > >> >>> The repository (at Apache) is here:
> > >> >>>    https://gitbox.apache.org/repos/asf?p=commons-collections.git
> > >> >>>
> > >> >>> We were told that it should now be possible to also write
> > >> >>> through GitHub, but I don't know if and how it should work.
> > >> >>>
> > >> >>> IMO, the easiest would be to clone the above, and try again
> > >> >>> with that.  [If it still does not work, then perhaps the issue
> > >> >>> is that the "all-Apache-committers-are-committers" resolution
> > >> >>> was not applied.]
> > >> >>>
> > >> >>> Gilles
> > >> >>>
> > >> >>> P.S. We should move this conversation over to the "dev" ML.
> > >> >>>
> > >> >>> >
> > >> >>> > Shall I use SVN? Or some other remote?
> > >> >>> >
> > >> >>> > [...]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> --
> WBR
> Maxim aka solomax

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
Thanks a lot Sebb,

staging repo was created successfully.
`mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean site
site:stage deploy`

but I got following error during the build:
[WARNING] The requested profile "commons-collections" could not be
activated because it does not exist.
[ERROR] Failed to execute goal
org.apache.commons:commons-release-plugin:1.3:stage-distributions
(stage-distributions) on project commons-collections4: Failed to add files
to scm -> [Help 1]

It seems not important to me, would it be OK to ignore it and proceed with
RC1?

Another question: during release preparation I have created `4.3-release`
branch, it has zero commits, and I believe should be dropped (and in fact
shouln't be created)
Documentation states: "As branches deletion is now forbidden at
Apache, we will use a specific
release branch for every version"

Can I delete this useless branch and propose documentation update?

On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:

> I think the issue with dist/release/commons is that you need to be
> listed as a project committer, i.e. you need to be a Commons
> committer.
>
> Possibly the same applies to Nexus.
>
> I have added you as a Commons committer.
>
> On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik <[hidden email]>
> wrote:
> >
> > Thanks a lot for the help :)
> > Glad to check the release process ;)
> >
> > On Tue, 18 Dec 2018 at 23:19, Gilles <[hidden email]>
> wrote:
> >
> > > Hello.
> > >
> > > On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
> > > > Thanks a lot
> > > >
> > > > Unfortunately the next error is: Failed to deploy artifacts: Could
> > > > not
> > > > transfer artifact org.apache.commons:commons-collections4:jar:4.3
> > > > from/to
> > > > apache.releases.https (
> > > > https://repository.apache.org/service/local/staging/deploy/maven2):
> > > > Access
> > > > denied to:
> > > >
> > > >
> > >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
> > > >
> > > > I'm release manger for Apache OpenMeetings and just double-check I
> > > > can
> > > > access Staging Repos at repository.apache.org
> > > > , so I guess there are additional restrictions here
> > > >
> > > > would appreciate any help/hint :)
> > >
> > > I don't know how to change the permissions (I don't think I have
> > > the privilege anyway), and the PMC chair is AFK for a couple more
> > > days IIUC. :-(
> > >
> > > Perhaps someone with a taller hat. :-}
> > >
> > > Sorry for the inconvenience; it looks like you are first one to
> > > try and exercise those privileges voted several years ago...
> > >
> > > Gilles
> > >
> > > >
> > > > On Tue, 18 Dec 2018 at 22:54, Gilles <[hidden email]>
> > > > wrote:
> > > >
> > > >> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:
> > > >> > It seems I'm unable to commit to SVN:
> > > >> >
> > > >> > URL: https://dist.apache.org/repos/dist/release/commons
> > > >> >
> > > >> > Sending        KEYS
> > > >> > Transmitting file data .svn: E195023: Commit failed (details
> > > >> follow):
> > > >> > svn: E195023: Changing file
> > > >> > '/home/solomax/work/apache-dist/release/commons/KEYS' is forbidden
> > > >> by
> > > >> > the
> > > >> > server
> > > >> > svn: E175013: Access to
> > > >> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden
> > > >> >
> > > >> > Can someone help me with access rights?
> > > >>
> > > >> Not me.
> > > >> But I've added your key (revision 31593).
> > > >>
> > > >> Hope it gets you a little further,
> > > >> Gilles
> > > >>
> > > >> >
> > > >> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
> > > >> <[hidden email]>
> > > >> > wrote:
> > > >> >
> > > >> >> Moving conversation to dev@ list
> > > >> >>
> > > >> >> I was able to create branch using gitbox remote
> > > >> >> Will proceed,
> > > >> >>
> > > >> >> Thanks for the tip
> > > >> >>
> > > >> >>
> > > >> >> On Tue, 18 Dec 2018 at 21:14, Gilles
> > > >> <[hidden email]>
> > > >> >> wrote:
> > > >> >>
> > > >> >>> Hi.
> > > >> >>>
> > > >> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> > > >> >>> > Hello Gilles,
> > > >> >>> >
> > > >> >>> > I read documentation and as far as I can see To perform
> > > >> release I
> > > >> >>> > need
> > > >> >>> > rights to create branch
> > > >> >>> >
> > > >> >>> > git remote -v
> > > >> >>> > origin [hidden email]:apache/commons-collections.git (fetch)
> > > >> >>> > origin [hidden email]:apache/commons-collections.git (push)
> > > >> >>> >
> > > >> >>> > git push -u origin 4.3-release
> > > >> >>> > ERROR: Permission to apache/commons-collections.git denied to
> > > >> >>> > solomax.
> > > >> >>> > fatal: Could not read from remote repository.
> > > >> >>> >
> > > >> >>> > Please make sure you have the correct access rights
> > > >> >>> > and the repository exists.
> > > >> >>>
> > > >> >>> The repository (at Apache) is here:
> > > >> >>>
> https://gitbox.apache.org/repos/asf?p=commons-collections.git
> > > >> >>>
> > > >> >>> We were told that it should now be possible to also write
> > > >> >>> through GitHub, but I don't know if and how it should work.
> > > >> >>>
> > > >> >>> IMO, the easiest would be to clone the above, and try again
> > > >> >>> with that.  [If it still does not work, then perhaps the issue
> > > >> >>> is that the "all-Apache-committers-are-committers" resolution
> > > >> >>> was not applied.]
> > > >> >>>
> > > >> >>> Gilles
> > > >> >>>
> > > >> >>> P.S. We should move this conversation over to the "dev" ML.
> > > >> >>>
> > > >> >>> >
> > > >> >>> > Shall I use SVN? Or some other remote?
> > > >> >>> >
> > > >> >>> > [...]
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
> > --
> > WBR
> > Maxim aka solomax
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

sebb-2-2
On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik <[hidden email]> wrote:

>
> Thanks a lot Sebb,
>
> staging repo was created successfully.
> `mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean site
> site:stage deploy`
>
> but I got following error during the build:
> [WARNING] The requested profile "commons-collections" could not be
> activated because it does not exist.

That's because it does not exist.
Why did you add "-Pcommons-collections" to the command-line?
Is it documented to do so somewhere?

> [ERROR] Failed to execute goal
> org.apache.commons:commons-release-plugin:1.3:stage-distributions
> (stage-distributions) on project commons-collections4: Failed to add files
> to scm -> [Help 1]
>
> It seems not important to me, would it be OK to ignore it and proceed with
> RC1?

I don't use the release plugin so I don't know about that.

> Another question: during release preparation I have created `4.3-release`
> branch, it has zero commits, and I believe should be dropped (and in fact
> shouln't be created)
> Documentation states: "As branches deletion is now forbidden at
> Apache, we will use a specific
> release branch for every version"
>
> Can I delete this useless branch and propose documentation update?
>
> On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:
>
> > I think the issue with dist/release/commons is that you need to be
> > listed as a project committer, i.e. you need to be a Commons
> > committer.
> >
> > Possibly the same applies to Nexus.
> >
> > I have added you as a Commons committer.
> >
> > On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik <[hidden email]>
> > wrote:
> > >
> > > Thanks a lot for the help :)
> > > Glad to check the release process ;)
> > >
> > > On Tue, 18 Dec 2018 at 23:19, Gilles <[hidden email]>
> > wrote:
> > >
> > > > Hello.
> > > >
> > > > On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
> > > > > Thanks a lot
> > > > >
> > > > > Unfortunately the next error is: Failed to deploy artifacts: Could
> > > > > not
> > > > > transfer artifact org.apache.commons:commons-collections4:jar:4.3
> > > > > from/to
> > > > > apache.releases.https (
> > > > > https://repository.apache.org/service/local/staging/deploy/maven2):
> > > > > Access
> > > > > denied to:
> > > > >
> > > > >
> > > >
> > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
> > > > >
> > > > > I'm release manger for Apache OpenMeetings and just double-check I
> > > > > can
> > > > > access Staging Repos at repository.apache.org
> > > > > , so I guess there are additional restrictions here
> > > > >
> > > > > would appreciate any help/hint :)
> > > >
> > > > I don't know how to change the permissions (I don't think I have
> > > > the privilege anyway), and the PMC chair is AFK for a couple more
> > > > days IIUC. :-(
> > > >
> > > > Perhaps someone with a taller hat. :-}
> > > >
> > > > Sorry for the inconvenience; it looks like you are first one to
> > > > try and exercise those privileges voted several years ago...
> > > >
> > > > Gilles
> > > >
> > > > >
> > > > > On Tue, 18 Dec 2018 at 22:54, Gilles <[hidden email]>
> > > > > wrote:
> > > > >
> > > > >> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:
> > > > >> > It seems I'm unable to commit to SVN:
> > > > >> >
> > > > >> > URL: https://dist.apache.org/repos/dist/release/commons
> > > > >> >
> > > > >> > Sending        KEYS
> > > > >> > Transmitting file data .svn: E195023: Commit failed (details
> > > > >> follow):
> > > > >> > svn: E195023: Changing file
> > > > >> > '/home/solomax/work/apache-dist/release/commons/KEYS' is forbidden
> > > > >> by
> > > > >> > the
> > > > >> > server
> > > > >> > svn: E175013: Access to
> > > > >> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden
> > > > >> >
> > > > >> > Can someone help me with access rights?
> > > > >>
> > > > >> Not me.
> > > > >> But I've added your key (revision 31593).
> > > > >>
> > > > >> Hope it gets you a little further,
> > > > >> Gilles
> > > > >>
> > > > >> >
> > > > >> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
> > > > >> <[hidden email]>
> > > > >> > wrote:
> > > > >> >
> > > > >> >> Moving conversation to dev@ list
> > > > >> >>
> > > > >> >> I was able to create branch using gitbox remote
> > > > >> >> Will proceed,
> > > > >> >>
> > > > >> >> Thanks for the tip
> > > > >> >>
> > > > >> >>
> > > > >> >> On Tue, 18 Dec 2018 at 21:14, Gilles
> > > > >> <[hidden email]>
> > > > >> >> wrote:
> > > > >> >>
> > > > >> >>> Hi.
> > > > >> >>>
> > > > >> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> > > > >> >>> > Hello Gilles,
> > > > >> >>> >
> > > > >> >>> > I read documentation and as far as I can see To perform
> > > > >> release I
> > > > >> >>> > need
> > > > >> >>> > rights to create branch
> > > > >> >>> >
> > > > >> >>> > git remote -v
> > > > >> >>> > origin [hidden email]:apache/commons-collections.git (fetch)
> > > > >> >>> > origin [hidden email]:apache/commons-collections.git (push)
> > > > >> >>> >
> > > > >> >>> > git push -u origin 4.3-release
> > > > >> >>> > ERROR: Permission to apache/commons-collections.git denied to
> > > > >> >>> > solomax.
> > > > >> >>> > fatal: Could not read from remote repository.
> > > > >> >>> >
> > > > >> >>> > Please make sure you have the correct access rights
> > > > >> >>> > and the repository exists.
> > > > >> >>>
> > > > >> >>> The repository (at Apache) is here:
> > > > >> >>>
> > https://gitbox.apache.org/repos/asf?p=commons-collections.git
> > > > >> >>>
> > > > >> >>> We were told that it should now be possible to also write
> > > > >> >>> through GitHub, but I don't know if and how it should work.
> > > > >> >>>
> > > > >> >>> IMO, the easiest would be to clone the above, and try again
> > > > >> >>> with that.  [If it still does not work, then perhaps the issue
> > > > >> >>> is that the "all-Apache-committers-are-committers" resolution
> > > > >> >>> was not applied.]
> > > > >> >>>
> > > > >> >>> Gilles
> > > > >> >>>
> > > > >> >>> P.S. We should move this conversation over to the "dev" ML.
> > > > >> >>>
> > > > >> >>> >
> > > > >> >>> > Shall I use SVN? Or some other remote?
> > > > >> >>> >
> > > > >> >>> > [...]
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > > >
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> --
> WBR
> Maxim aka solomax

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
I found it here:
https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300

Shall I drop current staging repo and restart the build without this
profile?

On Wed, 19 Dec 2018 at 06:57, sebb <[hidden email]> wrote:

> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik <[hidden email]>
> wrote:
> >
> > Thanks a lot Sebb,
> >
> > staging repo was created successfully.
> > `mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean site
> > site:stage deploy`
> >
> > but I got following error during the build:
> > [WARNING] The requested profile "commons-collections" could not be
> > activated because it does not exist.
>
> That's because it does not exist.
> Why did you add "-Pcommons-collections" to the command-line?
> Is it documented to do so somewhere?
>
> > [ERROR] Failed to execute goal
> > org.apache.commons:commons-release-plugin:1.3:stage-distributions
> > (stage-distributions) on project commons-collections4: Failed to add
> files
> > to scm -> [Help 1]
> >
> > It seems not important to me, would it be OK to ignore it and proceed
> with
> > RC1?
>
> I don't use the release plugin so I don't know about that.
>
> > Another question: during release preparation I have created `4.3-release`
> > branch, it has zero commits, and I believe should be dropped (and in fact
> > shouln't be created)
> > Documentation states: "As branches deletion is now forbidden at
> > Apache, we will use a specific
> > release branch for every version"
> >
> > Can I delete this useless branch and propose documentation update?
> >
> > On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:
> >
> > > I think the issue with dist/release/commons is that you need to be
> > > listed as a project committer, i.e. you need to be a Commons
> > > committer.
> > >
> > > Possibly the same applies to Nexus.
> > >
> > > I have added you as a Commons committer.
> > >
> > > On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik <[hidden email]>
> > > wrote:
> > > >
> > > > Thanks a lot for the help :)
> > > > Glad to check the release process ;)
> > > >
> > > > On Tue, 18 Dec 2018 at 23:19, Gilles <[hidden email]>
> > > wrote:
> > > >
> > > > > Hello.
> > > > >
> > > > > On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
> > > > > > Thanks a lot
> > > > > >
> > > > > > Unfortunately the next error is: Failed to deploy artifacts:
> Could
> > > > > > not
> > > > > > transfer artifact org.apache.commons:commons-collections4:jar:4.3
> > > > > > from/to
> > > > > > apache.releases.https (
> > > > > >
> https://repository.apache.org/service/local/staging/deploy/maven2):
> > > > > > Access
> > > > > > denied to:
> > > > > >
> > > > > >
> > > > >
> > >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
> > > > > >
> > > > > > I'm release manger for Apache OpenMeetings and just double-check
> I
> > > > > > can
> > > > > > access Staging Repos at repository.apache.org
> > > > > > , so I guess there are additional restrictions here
> > > > > >
> > > > > > would appreciate any help/hint :)
> > > > >
> > > > > I don't know how to change the permissions (I don't think I have
> > > > > the privilege anyway), and the PMC chair is AFK for a couple more
> > > > > days IIUC. :-(
> > > > >
> > > > > Perhaps someone with a taller hat. :-}
> > > > >
> > > > > Sorry for the inconvenience; it looks like you are first one to
> > > > > try and exercise those privileges voted several years ago...
> > > > >
> > > > > Gilles
> > > > >
> > > > > >
> > > > > > On Tue, 18 Dec 2018 at 22:54, Gilles <
> [hidden email]>
> > > > > > wrote:
> > > > > >
> > > > > >> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:
> > > > > >> > It seems I'm unable to commit to SVN:
> > > > > >> >
> > > > > >> > URL: https://dist.apache.org/repos/dist/release/commons
> > > > > >> >
> > > > > >> > Sending        KEYS
> > > > > >> > Transmitting file data .svn: E195023: Commit failed (details
> > > > > >> follow):
> > > > > >> > svn: E195023: Changing file
> > > > > >> > '/home/solomax/work/apache-dist/release/commons/KEYS' is
> forbidden
> > > > > >> by
> > > > > >> > the
> > > > > >> > server
> > > > > >> > svn: E175013: Access to
> > > > > >> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS'
> forbidden
> > > > > >> >
> > > > > >> > Can someone help me with access rights?
> > > > > >>
> > > > > >> Not me.
> > > > > >> But I've added your key (revision 31593).
> > > > > >>
> > > > > >> Hope it gets you a little further,
> > > > > >> Gilles
> > > > > >>
> > > > > >> >
> > > > > >> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
> > > > > >> <[hidden email]>
> > > > > >> > wrote:
> > > > > >> >
> > > > > >> >> Moving conversation to dev@ list
> > > > > >> >>
> > > > > >> >> I was able to create branch using gitbox remote
> > > > > >> >> Will proceed,
> > > > > >> >>
> > > > > >> >> Thanks for the tip
> > > > > >> >>
> > > > > >> >>
> > > > > >> >> On Tue, 18 Dec 2018 at 21:14, Gilles
> > > > > >> <[hidden email]>
> > > > > >> >> wrote:
> > > > > >> >>
> > > > > >> >>> Hi.
> > > > > >> >>>
> > > > > >> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> > > > > >> >>> > Hello Gilles,
> > > > > >> >>> >
> > > > > >> >>> > I read documentation and as far as I can see To perform
> > > > > >> release I
> > > > > >> >>> > need
> > > > > >> >>> > rights to create branch
> > > > > >> >>> >
> > > > > >> >>> > git remote -v
> > > > > >> >>> > origin [hidden email]:apache/commons-collections.git
> (fetch)
> > > > > >> >>> > origin [hidden email]:apache/commons-collections.git
> (push)
> > > > > >> >>> >
> > > > > >> >>> > git push -u origin 4.3-release
> > > > > >> >>> > ERROR: Permission to apache/commons-collections.git
> denied to
> > > > > >> >>> > solomax.
> > > > > >> >>> > fatal: Could not read from remote repository.
> > > > > >> >>> >
> > > > > >> >>> > Please make sure you have the correct access rights
> > > > > >> >>> > and the repository exists.
> > > > > >> >>>
> > > > > >> >>> The repository (at Apache) is here:
> > > > > >> >>>
> > > https://gitbox.apache.org/repos/asf?p=commons-collections.git
> > > > > >> >>>
> > > > > >> >>> We were told that it should now be possible to also write
> > > > > >> >>> through GitHub, but I don't know if and how it should work.
> > > > > >> >>>
> > > > > >> >>> IMO, the easiest would be to clone the above, and try again
> > > > > >> >>> with that.  [If it still does not work, then perhaps the
> issue
> > > > > >> >>> is that the "all-Apache-committers-are-committers"
> resolution
> > > > > >> >>> was not applied.]
> > > > > >> >>>
> > > > > >> >>> Gilles
> > > > > >> >>>
> > > > > >> >>> P.S. We should move this conversation over to the "dev" ML.
> > > > > >> >>>
> > > > > >> >>> >
> > > > > >> >>> > Shall I use SVN? Or some other remote?
> > > > > >> >>> >
> > > > > >> >>> > [...]
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > > >
> > > > >
> > > >
> > > > --
> > > > WBR
> > > > Maxim aka solomax
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
> >
> > --
> > WBR
> > Maxim aka solomax
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Gilles Sadowski
On Wed, 19 Dec 2018 06:59:26 +0700, Maxim Solodovnik wrote:
> I found it here:
>
> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300
>
> Shall I drop current staging repo and restart the build without this
> profile?

Yes.
As I wrote, [RNG] is a modular project and "commons-rng-examples" is
one of its modules.
You can safely ignore any "-Pcommons-rng-examples" switch.  The rest
of the command line is fine.

For a non-modular project, you might be lucky to not hit the bugs of
the "release-plugin".

>
> On Wed, 19 Dec 2018 at 06:57, sebb <[hidden email]> wrote:
>
>> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik
>> <[hidden email]>
>> wrote:
>> >
>> > Thanks a lot Sebb,
>> >
>> > staging repo was created successfully.
>> > `mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean
>> site
>> > site:stage deploy`
>> >
>> > but I got following error during the build:
>> > [WARNING] The requested profile "commons-collections" could not be
>> > activated because it does not exist.
>>
>> That's because it does not exist.
>> Why did you add "-Pcommons-collections" to the command-line?
>> Is it documented to do so somewhere?
>>
>> > [ERROR] Failed to execute goal
>> > org.apache.commons:commons-release-plugin:1.3:stage-distributions
>> > (stage-distributions) on project commons-collections4: Failed to
>> add
>> files
>> > to scm -> [Help 1]
>> >
>> > It seems not important to me, would it be OK to ignore it and
>> proceed
>> with
>> > RC1?
>>
>> I don't use the release plugin so I don't know about that.
>>
>> > Another question: during release preparation I have created
>> `4.3-release`
>> > branch, it has zero commits, and I believe should be dropped (and
>> in fact
>> > shouln't be created)
>> > Documentation states: "As branches deletion is now forbidden at
>> > Apache, we will use a specific
>> > release branch for every version"

That's the convention followed up to now.
But we do delete feature and bugfix branches that were merged into
"master", or experimental branches that have become stale.

Gilles

>> >
>> > Can I delete this useless branch and propose documentation update?
>> >
>> > On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:
>> >
>> > > I think the issue with dist/release/commons is that you need to
>> be
>> > > listed as a project committer, i.e. you need to be a Commons
>> > > committer.
>> > >
>> > > Possibly the same applies to Nexus.
>> > >
>> > > I have added you as a Commons committer.
>> > >
>> > > On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik
>> <[hidden email]>
>> > > wrote:
>> > > >
>> > > > Thanks a lot for the help :)
>> > > > Glad to check the release process ;)
>> > > >
>> > > > On Tue, 18 Dec 2018 at 23:19, Gilles
>> <[hidden email]>
>> > > wrote:
>> > > >
>> > > > > Hello.
>> > > > >
>> > > > > On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
>> > > > > > Thanks a lot
>> > > > > >
>> > > > > > Unfortunately the next error is: Failed to deploy
>> artifacts:
>> Could
>> > > > > > not
>> > > > > > transfer artifact
>> org.apache.commons:commons-collections4:jar:4.3
>> > > > > > from/to
>> > > > > > apache.releases.https (
>> > > > > >
>> https://repository.apache.org/service/local/staging/deploy/maven2):
>> > > > > > Access
>> > > > > > denied to:
>> > > > > >
>> > > > > >
>> > > > >
>> > >
>>
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
>> > > > > >
>> > > > > > I'm release manger for Apache OpenMeetings and just
>> double-check
>> I
>> > > > > > can
>> > > > > > access Staging Repos at repository.apache.org
>> > > > > > , so I guess there are additional restrictions here
>> > > > > >
>> > > > > > would appreciate any help/hint :)
>> > > > >
>> > > > > I don't know how to change the permissions (I don't think I
>> have
>> > > > > the privilege anyway), and the PMC chair is AFK for a couple
>> more
>> > > > > days IIUC. :-(
>> > > > >
>> > > > > Perhaps someone with a taller hat. :-}
>> > > > >
>> > > > > Sorry for the inconvenience; it looks like you are first one
>> to
>> > > > > try and exercise those privileges voted several years ago...
>> > > > >
>> > > > > Gilles
>> > > > >
>> > > > > >
>> > > > > > On Tue, 18 Dec 2018 at 22:54, Gilles <
>> [hidden email]>
>> > > > > > wrote:
>> > > > > >
>> > > > > >> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik
>> wrote:
>> > > > > >> > It seems I'm unable to commit to SVN:
>> > > > > >> >
>> > > > > >> > URL: https://dist.apache.org/repos/dist/release/commons
>> > > > > >> >
>> > > > > >> > Sending        KEYS
>> > > > > >> > Transmitting file data .svn: E195023: Commit failed
>> (details
>> > > > > >> follow):
>> > > > > >> > svn: E195023: Changing file
>> > > > > >> > '/home/solomax/work/apache-dist/release/commons/KEYS'
>> is
>> forbidden
>> > > > > >> by
>> > > > > >> > the
>> > > > > >> > server
>> > > > > >> > svn: E175013: Access to
>> > > > > >> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS'
>> forbidden
>> > > > > >> >
>> > > > > >> > Can someone help me with access rights?
>> > > > > >>
>> > > > > >> Not me.
>> > > > > >> But I've added your key (revision 31593).
>> > > > > >>
>> > > > > >> Hope it gets you a little further,
>> > > > > >> Gilles
>> > > > > >>
>> > > > > >> >
>> > > > > >> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
>> > > > > >> <[hidden email]>
>> > > > > >> > wrote:
>> > > > > >> >
>> > > > > >> >> Moving conversation to dev@ list
>> > > > > >> >>
>> > > > > >> >> I was able to create branch using gitbox remote
>> > > > > >> >> Will proceed,
>> > > > > >> >>
>> > > > > >> >> Thanks for the tip
>> > > > > >> >>
>> > > > > >> >>
>> > > > > >> >> On Tue, 18 Dec 2018 at 21:14, Gilles
>> > > > > >> <[hidden email]>
>> > > > > >> >> wrote:
>> > > > > >> >>
>> > > > > >> >>> Hi.
>> > > > > >> >>>
>> > > > > >> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik
>> wrote:
>> > > > > >> >>> > Hello Gilles,
>> > > > > >> >>> >
>> > > > > >> >>> > I read documentation and as far as I can see To
>> perform
>> > > > > >> release I
>> > > > > >> >>> > need
>> > > > > >> >>> > rights to create branch
>> > > > > >> >>> >
>> > > > > >> >>> > git remote -v
>> > > > > >> >>> > origin
>> [hidden email]:apache/commons-collections.git
>> (fetch)
>> > > > > >> >>> > origin
>> [hidden email]:apache/commons-collections.git
>> (push)
>> > > > > >> >>> >
>> > > > > >> >>> > git push -u origin 4.3-release
>> > > > > >> >>> > ERROR: Permission to apache/commons-collections.git
>> denied to
>> > > > > >> >>> > solomax.
>> > > > > >> >>> > fatal: Could not read from remote repository.
>> > > > > >> >>> >
>> > > > > >> >>> > Please make sure you have the correct access rights
>> > > > > >> >>> > and the repository exists.
>> > > > > >> >>>
>> > > > > >> >>> The repository (at Apache) is here:
>> > > > > >> >>>
>> > > https://gitbox.apache.org/repos/asf?p=commons-collections.git
>> > > > > >> >>>
>> > > > > >> >>> We were told that it should now be possible to also
>> write
>> > > > > >> >>> through GitHub, but I don't know if and how it should
>> work.
>> > > > > >> >>>
>> > > > > >> >>> IMO, the easiest would be to clone the above, and try
>> again
>> > > > > >> >>> with that.  [If it still does not work, then perhaps
>> the
>> issue
>> > > > > >> >>> is that the "all-Apache-committers-are-committers"
>> resolution
>> > > > > >> >>> was not applied.]
>> > > > > >> >>>
>> > > > > >> >>> Gilles
>> > > > > >> >>>
>> > > > > >> >>> P.S. We should move this conversation over to the
>> "dev" ML.
>> > > > > >> >>>
>> > > > > >> >>> >
>> > > > > >> >>> > Shall I use SVN? Or some other remote?
>> > > > > >> >>> >
>> > > > > >> >>> > [...]
>> > > > >
>> > > > >
>> > > > >
>>
>> ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: [hidden email]
>> > > > > For additional commands, e-mail: [hidden email]
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > WBR
>> > > > Maxim aka solomax
>> > >
>> > >
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: [hidden email]
>> > > For additional commands, e-mail: [hidden email]
>> > >
>> > >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
Now I'm getting:

[ERROR] Failed to execute goal
org.apache.commons:commons-release-plugin:1.3:stage-distributions
(stage-distributions) on project commons-collections4: Failed to add files
to scm -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.commons:commons-release-plugin:1.3:stage-distributions
(stage-distributions) on project commons-collections4: Failed to add files
to scm

I can see no reasonable error message

Have tried to manually commit to
https://dist.apache.org/repos/dist/dev/commons/collections/ and commit was
successfull


On Wed, 19 Dec 2018 at 07:16, Gilles <[hidden email]> wrote:

> On Wed, 19 Dec 2018 06:59:26 +0700, Maxim Solodovnik wrote:
> > I found it here:
> >
> >
> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300
> >
> > Shall I drop current staging repo and restart the build without this
> > profile?
>
> Yes.
> As I wrote, [RNG] is a modular project and "commons-rng-examples" is
> one of its modules.
> You can safely ignore any "-Pcommons-rng-examples" switch.  The rest
> of the command line is fine.
>
> For a non-modular project, you might be lucky to not hit the bugs of
> the "release-plugin".
>
> >
> > On Wed, 19 Dec 2018 at 06:57, sebb <[hidden email]> wrote:
> >
> >> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik
> >> <[hidden email]>
> >> wrote:
> >> >
> >> > Thanks a lot Sebb,
> >> >
> >> > staging repo was created successfully.
> >> > `mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean
> >> site
> >> > site:stage deploy`
> >> >
> >> > but I got following error during the build:
> >> > [WARNING] The requested profile "commons-collections" could not be
> >> > activated because it does not exist.
> >>
> >> That's because it does not exist.
> >> Why did you add "-Pcommons-collections" to the command-line?
> >> Is it documented to do so somewhere?
> >>
> >> > [ERROR] Failed to execute goal
> >> > org.apache.commons:commons-release-plugin:1.3:stage-distributions
> >> > (stage-distributions) on project commons-collections4: Failed to
> >> add
> >> files
> >> > to scm -> [Help 1]
> >> >
> >> > It seems not important to me, would it be OK to ignore it and
> >> proceed
> >> with
> >> > RC1?
> >>
> >> I don't use the release plugin so I don't know about that.
> >>
> >> > Another question: during release preparation I have created
> >> `4.3-release`
> >> > branch, it has zero commits, and I believe should be dropped (and
> >> in fact
> >> > shouln't be created)
> >> > Documentation states: "As branches deletion is now forbidden at
> >> > Apache, we will use a specific
> >> > release branch for every version"
>
> That's the convention followed up to now.
> But we do delete feature and bugfix branches that were merged into
> "master", or experimental branches that have become stale.
>
> Gilles
>
> >> >
> >> > Can I delete this useless branch and propose documentation update?
> >> >
> >> > On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:
> >> >
> >> > > I think the issue with dist/release/commons is that you need to
> >> be
> >> > > listed as a project committer, i.e. you need to be a Commons
> >> > > committer.
> >> > >
> >> > > Possibly the same applies to Nexus.
> >> > >
> >> > > I have added you as a Commons committer.
> >> > >
> >> > > On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik
> >> <[hidden email]>
> >> > > wrote:
> >> > > >
> >> > > > Thanks a lot for the help :)
> >> > > > Glad to check the release process ;)
> >> > > >
> >> > > > On Tue, 18 Dec 2018 at 23:19, Gilles
> >> <[hidden email]>
> >> > > wrote:
> >> > > >
> >> > > > > Hello.
> >> > > > >
> >> > > > > On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
> >> > > > > > Thanks a lot
> >> > > > > >
> >> > > > > > Unfortunately the next error is: Failed to deploy
> >> artifacts:
> >> Could
> >> > > > > > not
> >> > > > > > transfer artifact
> >> org.apache.commons:commons-collections4:jar:4.3
> >> > > > > > from/to
> >> > > > > > apache.releases.https (
> >> > > > > >
> >> https://repository.apache.org/service/local/staging/deploy/maven2):
> >> > > > > > Access
> >> > > > > > denied to:
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > >
> >>
> >>
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
> >> > > > > >
> >> > > > > > I'm release manger for Apache OpenMeetings and just
> >> double-check
> >> I
> >> > > > > > can
> >> > > > > > access Staging Repos at repository.apache.org
> >> > > > > > , so I guess there are additional restrictions here
> >> > > > > >
> >> > > > > > would appreciate any help/hint :)
> >> > > > >
> >> > > > > I don't know how to change the permissions (I don't think I
> >> have
> >> > > > > the privilege anyway), and the PMC chair is AFK for a couple
> >> more
> >> > > > > days IIUC. :-(
> >> > > > >
> >> > > > > Perhaps someone with a taller hat. :-}
> >> > > > >
> >> > > > > Sorry for the inconvenience; it looks like you are first one
> >> to
> >> > > > > try and exercise those privileges voted several years ago...
> >> > > > >
> >> > > > > Gilles
> >> > > > >
> >> > > > > >
> >> > > > > > On Tue, 18 Dec 2018 at 22:54, Gilles <
> >> [hidden email]>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > >> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik
> >> wrote:
> >> > > > > >> > It seems I'm unable to commit to SVN:
> >> > > > > >> >
> >> > > > > >> > URL: https://dist.apache.org/repos/dist/release/commons
> >> > > > > >> >
> >> > > > > >> > Sending        KEYS
> >> > > > > >> > Transmitting file data .svn: E195023: Commit failed
> >> (details
> >> > > > > >> follow):
> >> > > > > >> > svn: E195023: Changing file
> >> > > > > >> > '/home/solomax/work/apache-dist/release/commons/KEYS'
> >> is
> >> forbidden
> >> > > > > >> by
> >> > > > > >> > the
> >> > > > > >> > server
> >> > > > > >> > svn: E175013: Access to
> >> > > > > >> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS'
> >> forbidden
> >> > > > > >> >
> >> > > > > >> > Can someone help me with access rights?
> >> > > > > >>
> >> > > > > >> Not me.
> >> > > > > >> But I've added your key (revision 31593).
> >> > > > > >>
> >> > > > > >> Hope it gets you a little further,
> >> > > > > >> Gilles
> >> > > > > >>
> >> > > > > >> >
> >> > > > > >> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
> >> > > > > >> <[hidden email]>
> >> > > > > >> > wrote:
> >> > > > > >> >
> >> > > > > >> >> Moving conversation to dev@ list
> >> > > > > >> >>
> >> > > > > >> >> I was able to create branch using gitbox remote
> >> > > > > >> >> Will proceed,
> >> > > > > >> >>
> >> > > > > >> >> Thanks for the tip
> >> > > > > >> >>
> >> > > > > >> >>
> >> > > > > >> >> On Tue, 18 Dec 2018 at 21:14, Gilles
> >> > > > > >> <[hidden email]>
> >> > > > > >> >> wrote:
> >> > > > > >> >>
> >> > > > > >> >>> Hi.
> >> > > > > >> >>>
> >> > > > > >> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik
> >> wrote:
> >> > > > > >> >>> > Hello Gilles,
> >> > > > > >> >>> >
> >> > > > > >> >>> > I read documentation and as far as I can see To
> >> perform
> >> > > > > >> release I
> >> > > > > >> >>> > need
> >> > > > > >> >>> > rights to create branch
> >> > > > > >> >>> >
> >> > > > > >> >>> > git remote -v
> >> > > > > >> >>> > origin
> >> [hidden email]:apache/commons-collections.git
> >> (fetch)
> >> > > > > >> >>> > origin
> >> [hidden email]:apache/commons-collections.git
> >> (push)
> >> > > > > >> >>> >
> >> > > > > >> >>> > git push -u origin 4.3-release
> >> > > > > >> >>> > ERROR: Permission to apache/commons-collections.git
> >> denied to
> >> > > > > >> >>> > solomax.
> >> > > > > >> >>> > fatal: Could not read from remote repository.
> >> > > > > >> >>> >
> >> > > > > >> >>> > Please make sure you have the correct access rights
> >> > > > > >> >>> > and the repository exists.
> >> > > > > >> >>>
> >> > > > > >> >>> The repository (at Apache) is here:
> >> > > > > >> >>>
> >> > > https://gitbox.apache.org/repos/asf?p=commons-collections.git
> >> > > > > >> >>>
> >> > > > > >> >>> We were told that it should now be possible to also
> >> write
> >> > > > > >> >>> through GitHub, but I don't know if and how it should
> >> work.
> >> > > > > >> >>>
> >> > > > > >> >>> IMO, the easiest would be to clone the above, and try
> >> again
> >> > > > > >> >>> with that.  [If it still does not work, then perhaps
> >> the
> >> issue
> >> > > > > >> >>> is that the "all-Apache-committers-are-committers"
> >> resolution
> >> > > > > >> >>> was not applied.]
> >> > > > > >> >>>
> >> > > > > >> >>> Gilles
> >> > > > > >> >>>
> >> > > > > >> >>> P.S. We should move this conversation over to the
> >> "dev" ML.
> >> > > > > >> >>>
> >> > > > > >> >>> >
> >> > > > > >> >>> > Shall I use SVN? Or some other remote?
> >> > > > > >> >>> >
> >> > > > > >> >>> > [...]
> >> > > > >
> >> > > > >
> >> > > > >
> >>
> >> ---------------------------------------------------------------------
> >> > > > > To unsubscribe, e-mail: [hidden email]
> >> > > > > For additional commands, e-mail: [hidden email]
> >> > > > >
> >> > > > >
> >> > > >
> >> > > > --
> >> > > > WBR
> >> > > > Maxim aka solomax
> >> > >
> >> > >
> >> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: [hidden email]
> >> > > For additional commands, e-mail: [hidden email]
> >> > >
> >> > >
> >> >
> >> > --
> >> > WBR
> >> > Maxim aka solomax
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
Is it possible staging-distribution fails because there is already 4.2-RC1/
at dist-dev?

On Wed, 19 Dec 2018 at 07:32, Maxim Solodovnik <[hidden email]> wrote:

> Now I'm getting:
>
> [ERROR] Failed to execute goal
> org.apache.commons:commons-release-plugin:1.3:stage-distributions
> (stage-distributions) on project commons-collections4: Failed to add files
> to scm -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.commons:commons-release-plugin:1.3:stage-distributions
> (stage-distributions) on project commons-collections4: Failed to add files
> to scm
>
> I can see no reasonable error message
>
> Have tried to manually commit to
> https://dist.apache.org/repos/dist/dev/commons/collections/ and commit
> was successfull
>
>
> On Wed, 19 Dec 2018 at 07:16, Gilles <[hidden email]> wrote:
>
>> On Wed, 19 Dec 2018 06:59:26 +0700, Maxim Solodovnik wrote:
>> > I found it here:
>> >
>> >
>> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300
>> >
>> > Shall I drop current staging repo and restart the build without this
>> > profile?
>>
>> Yes.
>> As I wrote, [RNG] is a modular project and "commons-rng-examples" is
>> one of its modules.
>> You can safely ignore any "-Pcommons-rng-examples" switch.  The rest
>> of the command line is fine.
>>
>> For a non-modular project, you might be lucky to not hit the bugs of
>> the "release-plugin".
>>
>> >
>> > On Wed, 19 Dec 2018 at 06:57, sebb <[hidden email]> wrote:
>> >
>> >> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik
>> >> <[hidden email]>
>> >> wrote:
>> >> >
>> >> > Thanks a lot Sebb,
>> >> >
>> >> > staging repo was created successfully.
>> >> > `mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean
>> >> site
>> >> > site:stage deploy`
>> >> >
>> >> > but I got following error during the build:
>> >> > [WARNING] The requested profile "commons-collections" could not be
>> >> > activated because it does not exist.
>> >>
>> >> That's because it does not exist.
>> >> Why did you add "-Pcommons-collections" to the command-line?
>> >> Is it documented to do so somewhere?
>> >>
>> >> > [ERROR] Failed to execute goal
>> >> > org.apache.commons:commons-release-plugin:1.3:stage-distributions
>> >> > (stage-distributions) on project commons-collections4: Failed to
>> >> add
>> >> files
>> >> > to scm -> [Help 1]
>> >> >
>> >> > It seems not important to me, would it be OK to ignore it and
>> >> proceed
>> >> with
>> >> > RC1?
>> >>
>> >> I don't use the release plugin so I don't know about that.
>> >>
>> >> > Another question: during release preparation I have created
>> >> `4.3-release`
>> >> > branch, it has zero commits, and I believe should be dropped (and
>> >> in fact
>> >> > shouln't be created)
>> >> > Documentation states: "As branches deletion is now forbidden at
>> >> > Apache, we will use a specific
>> >> > release branch for every version"
>>
>> That's the convention followed up to now.
>> But we do delete feature and bugfix branches that were merged into
>> "master", or experimental branches that have become stale.
>>
>> Gilles
>>
>> >> >
>> >> > Can I delete this useless branch and propose documentation update?
>> >> >
>> >> > On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:
>> >> >
>> >> > > I think the issue with dist/release/commons is that you need to
>> >> be
>> >> > > listed as a project committer, i.e. you need to be a Commons
>> >> > > committer.
>> >> > >
>> >> > > Possibly the same applies to Nexus.
>> >> > >
>> >> > > I have added you as a Commons committer.
>> >> > >
>> >> > > On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik
>> >> <[hidden email]>
>> >> > > wrote:
>> >> > > >
>> >> > > > Thanks a lot for the help :)
>> >> > > > Glad to check the release process ;)
>> >> > > >
>> >> > > > On Tue, 18 Dec 2018 at 23:19, Gilles
>> >> <[hidden email]>
>> >> > > wrote:
>> >> > > >
>> >> > > > > Hello.
>> >> > > > >
>> >> > > > > On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
>> >> > > > > > Thanks a lot
>> >> > > > > >
>> >> > > > > > Unfortunately the next error is: Failed to deploy
>> >> artifacts:
>> >> Could
>> >> > > > > > not
>> >> > > > > > transfer artifact
>> >> org.apache.commons:commons-collections4:jar:4.3
>> >> > > > > > from/to
>> >> > > > > > apache.releases.https (
>> >> > > > > >
>> >> https://repository.apache.org/service/local/staging/deploy/maven2):
>> >> > > > > > Access
>> >> > > > > > denied to:
>> >> > > > > >
>> >> > > > > >
>> >> > > > >
>> >> > >
>> >>
>> >>
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
>> >> > > > > >
>> >> > > > > > I'm release manger for Apache OpenMeetings and just
>> >> double-check
>> >> I
>> >> > > > > > can
>> >> > > > > > access Staging Repos at repository.apache.org
>> >> > > > > > , so I guess there are additional restrictions here
>> >> > > > > >
>> >> > > > > > would appreciate any help/hint :)
>> >> > > > >
>> >> > > > > I don't know how to change the permissions (I don't think I
>> >> have
>> >> > > > > the privilege anyway), and the PMC chair is AFK for a couple
>> >> more
>> >> > > > > days IIUC. :-(
>> >> > > > >
>> >> > > > > Perhaps someone with a taller hat. :-}
>> >> > > > >
>> >> > > > > Sorry for the inconvenience; it looks like you are first one
>> >> to
>> >> > > > > try and exercise those privileges voted several years ago...
>> >> > > > >
>> >> > > > > Gilles
>> >> > > > >
>> >> > > > > >
>> >> > > > > > On Tue, 18 Dec 2018 at 22:54, Gilles <
>> >> [hidden email]>
>> >> > > > > > wrote:
>> >> > > > > >
>> >> > > > > >> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik
>> >> wrote:
>> >> > > > > >> > It seems I'm unable to commit to SVN:
>> >> > > > > >> >
>> >> > > > > >> > URL: https://dist.apache.org/repos/dist/release/commons
>> >> > > > > >> >
>> >> > > > > >> > Sending        KEYS
>> >> > > > > >> > Transmitting file data .svn: E195023: Commit failed
>> >> (details
>> >> > > > > >> follow):
>> >> > > > > >> > svn: E195023: Changing file
>> >> > > > > >> > '/home/solomax/work/apache-dist/release/commons/KEYS'
>> >> is
>> >> forbidden
>> >> > > > > >> by
>> >> > > > > >> > the
>> >> > > > > >> > server
>> >> > > > > >> > svn: E175013: Access to
>> >> > > > > >> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS'
>> >> forbidden
>> >> > > > > >> >
>> >> > > > > >> > Can someone help me with access rights?
>> >> > > > > >>
>> >> > > > > >> Not me.
>> >> > > > > >> But I've added your key (revision 31593).
>> >> > > > > >>
>> >> > > > > >> Hope it gets you a little further,
>> >> > > > > >> Gilles
>> >> > > > > >>
>> >> > > > > >> >
>> >> > > > > >> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
>> >> > > > > >> <[hidden email]>
>> >> > > > > >> > wrote:
>> >> > > > > >> >
>> >> > > > > >> >> Moving conversation to dev@ list
>> >> > > > > >> >>
>> >> > > > > >> >> I was able to create branch using gitbox remote
>> >> > > > > >> >> Will proceed,
>> >> > > > > >> >>
>> >> > > > > >> >> Thanks for the tip
>> >> > > > > >> >>
>> >> > > > > >> >>
>> >> > > > > >> >> On Tue, 18 Dec 2018 at 21:14, Gilles
>> >> > > > > >> <[hidden email]>
>> >> > > > > >> >> wrote:
>> >> > > > > >> >>
>> >> > > > > >> >>> Hi.
>> >> > > > > >> >>>
>> >> > > > > >> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik
>> >> wrote:
>> >> > > > > >> >>> > Hello Gilles,
>> >> > > > > >> >>> >
>> >> > > > > >> >>> > I read documentation and as far as I can see To
>> >> perform
>> >> > > > > >> release I
>> >> > > > > >> >>> > need
>> >> > > > > >> >>> > rights to create branch
>> >> > > > > >> >>> >
>> >> > > > > >> >>> > git remote -v
>> >> > > > > >> >>> > origin
>> >> [hidden email]:apache/commons-collections.git
>> >> (fetch)
>> >> > > > > >> >>> > origin
>> >> [hidden email]:apache/commons-collections.git
>> >> (push)
>> >> > > > > >> >>> >
>> >> > > > > >> >>> > git push -u origin 4.3-release
>> >> > > > > >> >>> > ERROR: Permission to apache/commons-collections.git
>> >> denied to
>> >> > > > > >> >>> > solomax.
>> >> > > > > >> >>> > fatal: Could not read from remote repository.
>> >> > > > > >> >>> >
>> >> > > > > >> >>> > Please make sure you have the correct access rights
>> >> > > > > >> >>> > and the repository exists.
>> >> > > > > >> >>>
>> >> > > > > >> >>> The repository (at Apache) is here:
>> >> > > > > >> >>>
>> >> > > https://gitbox.apache.org/repos/asf?p=commons-collections.git
>> >> > > > > >> >>>
>> >> > > > > >> >>> We were told that it should now be possible to also
>> >> write
>> >> > > > > >> >>> through GitHub, but I don't know if and how it should
>> >> work.
>> >> > > > > >> >>>
>> >> > > > > >> >>> IMO, the easiest would be to clone the above, and try
>> >> again
>> >> > > > > >> >>> with that.  [If it still does not work, then perhaps
>> >> the
>> >> issue
>> >> > > > > >> >>> is that the "all-Apache-committers-are-committers"
>> >> resolution
>> >> > > > > >> >>> was not applied.]
>> >> > > > > >> >>>
>> >> > > > > >> >>> Gilles
>> >> > > > > >> >>>
>> >> > > > > >> >>> P.S. We should move this conversation over to the
>> >> "dev" ML.
>> >> > > > > >> >>>
>> >> > > > > >> >>> >
>> >> > > > > >> >>> > Shall I use SVN? Or some other remote?
>> >> > > > > >> >>> >
>> >> > > > > >> >>> > [...]
>> >> > > > >
>> >> > > > >
>> >> > > > >
>> >>
>> >> ---------------------------------------------------------------------
>> >> > > > > To unsubscribe, e-mail: [hidden email]
>> >> > > > > For additional commands, e-mail: [hidden email]
>> >> > > > >
>> >> > > > >
>> >> > > >
>> >> > > > --
>> >> > > > WBR
>> >> > > > Maxim aka solomax
>> >> > >
>> >> > >
>> >> ---------------------------------------------------------------------
>> >> > > To unsubscribe, e-mail: [hidden email]
>> >> > > For additional commands, e-mail: [hidden email]
>> >> > >
>> >> > >
>> >> >
>> >> > --
>> >> > WBR
>> >> > Maxim aka solomax
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [hidden email]
>> >> For additional commands, e-mail: [hidden email]
>> >>
>> >>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> --
> WBR
> Maxim aka solomax
>


--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Rob Tompkins


> On Dec 18, 2018, at 7:51 PM, Maxim Solodovnik <[hidden email]> wrote:
>
> Is it possible staging-distribution fails because there is already 4.2-RC1/
> at dist-dev?

Yes that does happen. I would make sure to delete the staging svn directory before going with the RC.

-Rob

>
>> On Wed, 19 Dec 2018 at 07:32, Maxim Solodovnik <[hidden email]> wrote:
>>
>> Now I'm getting:
>>
>> [ERROR] Failed to execute goal
>> org.apache.commons:commons-release-plugin:1.3:stage-distributions
>> (stage-distributions) on project commons-collections4: Failed to add files
>> to scm -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.apache.commons:commons-release-plugin:1.3:stage-distributions
>> (stage-distributions) on project commons-collections4: Failed to add files
>> to scm
>>
>> I can see no reasonable error message
>>
>> Have tried to manually commit to
>> https://dist.apache.org/repos/dist/dev/commons/collections/ and commit
>> was successfull
>>
>>
>>> On Wed, 19 Dec 2018 at 07:16, Gilles <[hidden email]> wrote:
>>>
>>>> On Wed, 19 Dec 2018 06:59:26 +0700, Maxim Solodovnik wrote:
>>>> I found it here:
>>>>
>>>>
>>> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300
>>>>
>>>> Shall I drop current staging repo and restart the build without this
>>>> profile?
>>>
>>> Yes.
>>> As I wrote, [RNG] is a modular project and "commons-rng-examples" is
>>> one of its modules.
>>> You can safely ignore any "-Pcommons-rng-examples" switch.  The rest
>>> of the command line is fine.
>>>
>>> For a non-modular project, you might be lucky to not hit the bugs of
>>> the "release-plugin".
>>>
>>>>
>>>>> On Wed, 19 Dec 2018 at 06:57, sebb <[hidden email]> wrote:
>>>>>
>>>>> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik
>>>>> <[hidden email]>
>>>>> wrote:
>>>>>>
>>>>>> Thanks a lot Sebb,
>>>>>>
>>>>>> staging repo was created successfully.
>>>>>> `mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean
>>>>> site
>>>>>> site:stage deploy`
>>>>>>
>>>>>> but I got following error during the build:
>>>>>> [WARNING] The requested profile "commons-collections" could not be
>>>>>> activated because it does not exist.
>>>>>
>>>>> That's because it does not exist.
>>>>> Why did you add "-Pcommons-collections" to the command-line?
>>>>> Is it documented to do so somewhere?
>>>>>
>>>>>> [ERROR] Failed to execute goal
>>>>>> org.apache.commons:commons-release-plugin:1.3:stage-distributions
>>>>>> (stage-distributions) on project commons-collections4: Failed to
>>>>> add
>>>>> files
>>>>>> to scm -> [Help 1]
>>>>>>
>>>>>> It seems not important to me, would it be OK to ignore it and
>>>>> proceed
>>>>> with
>>>>>> RC1?
>>>>>
>>>>> I don't use the release plugin so I don't know about that.
>>>>>
>>>>>> Another question: during release preparation I have created
>>>>> `4.3-release`
>>>>>> branch, it has zero commits, and I believe should be dropped (and
>>>>> in fact
>>>>>> shouln't be created)
>>>>>> Documentation states: "As branches deletion is now forbidden at
>>>>>> Apache, we will use a specific
>>>>>> release branch for every version"
>>>
>>> That's the convention followed up to now.
>>> But we do delete feature and bugfix branches that were merged into
>>> "master", or experimental branches that have become stale.
>>>
>>> Gilles
>>>
>>>>>>
>>>>>> Can I delete this useless branch and propose documentation update?
>>>>>>
>>>>>>> On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:
>>>>>>>
>>>>>>> I think the issue with dist/release/commons is that you need to
>>>>> be
>>>>>>> listed as a project committer, i.e. you need to be a Commons
>>>>>>> committer.
>>>>>>>
>>>>>>> Possibly the same applies to Nexus.
>>>>>>>
>>>>>>> I have added you as a Commons committer.
>>>>>>>
>>>>>>> On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik
>>>>> <[hidden email]>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Thanks a lot for the help :)
>>>>>>>> Glad to check the release process ;)
>>>>>>>>
>>>>>>>> On Tue, 18 Dec 2018 at 23:19, Gilles
>>>>> <[hidden email]>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hello.
>>>>>>>>>
>>>>>>>>>> On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
>>>>>>>>>> Thanks a lot
>>>>>>>>>>
>>>>>>>>>> Unfortunately the next error is: Failed to deploy
>>>>> artifacts:
>>>>> Could
>>>>>>>>>> not
>>>>>>>>>> transfer artifact
>>>>> org.apache.commons:commons-collections4:jar:4.3
>>>>>>>>>> from/to
>>>>>>>>>> apache.releases.https (
>>>>>>>>>>
>>>>> https://repository.apache.org/service/local/staging/deploy/maven2):
>>>>>>>>>> Access
>>>>>>>>>> denied to:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
>>>>>>>>>>
>>>>>>>>>> I'm release manger for Apache OpenMeetings and just
>>>>> double-check
>>>>> I
>>>>>>>>>> can
>>>>>>>>>> access Staging Repos at repository.apache.org
>>>>>>>>>> , so I guess there are additional restrictions here
>>>>>>>>>>
>>>>>>>>>> would appreciate any help/hint :)
>>>>>>>>>
>>>>>>>>> I don't know how to change the permissions (I don't think I
>>>>> have
>>>>>>>>> the privilege anyway), and the PMC chair is AFK for a couple
>>>>> more
>>>>>>>>> days IIUC. :-(
>>>>>>>>>
>>>>>>>>> Perhaps someone with a taller hat. :-}
>>>>>>>>>
>>>>>>>>> Sorry for the inconvenience; it looks like you are first one
>>>>> to
>>>>>>>>> try and exercise those privileges voted several years ago...
>>>>>>>>>
>>>>>>>>> Gilles
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, 18 Dec 2018 at 22:54, Gilles <
>>>>> [hidden email]>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik
>>>>> wrote:
>>>>>>>>>>>> It seems I'm unable to commit to SVN:
>>>>>>>>>>>>
>>>>>>>>>>>> URL: https://dist.apache.org/repos/dist/release/commons
>>>>>>>>>>>>
>>>>>>>>>>>> Sending        KEYS
>>>>>>>>>>>> Transmitting file data .svn: E195023: Commit failed
>>>>> (details
>>>>>>>>>>> follow):
>>>>>>>>>>>> svn: E195023: Changing file
>>>>>>>>>>>> '/home/solomax/work/apache-dist/release/commons/KEYS'
>>>>> is
>>>>> forbidden
>>>>>>>>>>> by
>>>>>>>>>>>> the
>>>>>>>>>>>> server
>>>>>>>>>>>> svn: E175013: Access to
>>>>>>>>>>>> '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS'
>>>>> forbidden
>>>>>>>>>>>>
>>>>>>>>>>>> Can someone help me with access rights?
>>>>>>>>>>>
>>>>>>>>>>> Not me.
>>>>>>>>>>> But I've added your key (revision 31593).
>>>>>>>>>>>
>>>>>>>>>>> Hope it gets you a little further,
>>>>>>>>>>> Gilles
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
>>>>>>>>>>> <[hidden email]>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Moving conversation to dev@ list
>>>>>>>>>>>>>
>>>>>>>>>>>>> I was able to create branch using gitbox remote
>>>>>>>>>>>>> Will proceed,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks for the tip
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, 18 Dec 2018 at 21:14, Gilles
>>>>>>>>>>> <[hidden email]>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik
>>>>> wrote:
>>>>>>>>>>>>>>> Hello Gilles,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I read documentation and as far as I can see To
>>>>> perform
>>>>>>>>>>> release I
>>>>>>>>>>>>>>> need
>>>>>>>>>>>>>>> rights to create branch
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> git remote -v
>>>>>>>>>>>>>>> origin
>>>>> [hidden email]:apache/commons-collections.git
>>>>> (fetch)
>>>>>>>>>>>>>>> origin
>>>>> [hidden email]:apache/commons-collections.git
>>>>> (push)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> git push -u origin 4.3-release
>>>>>>>>>>>>>>> ERROR: Permission to apache/commons-collections.git
>>>>> denied to
>>>>>>>>>>>>>>> solomax.
>>>>>>>>>>>>>>> fatal: Could not read from remote repository.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Please make sure you have the correct access rights
>>>>>>>>>>>>>>> and the repository exists.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The repository (at Apache) is here:
>>>>>>>>>>>>>>
>>>>>>> https://gitbox.apache.org/repos/asf?p=commons-collections.git
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We were told that it should now be possible to also
>>>>> write
>>>>>>>>>>>>>> through GitHub, but I don't know if and how it should
>>>>> work.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> IMO, the easiest would be to clone the above, and try
>>>>> again
>>>>>>>>>>>>>> with that.  [If it still does not work, then perhaps
>>>>> the
>>>>> issue
>>>>>>>>>>>>>> is that the "all-Apache-committers-are-committers"
>>>>> resolution
>>>>>>>>>>>>>> was not applied.]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Gilles
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> P.S. We should move this conversation over to the
>>>>> "dev" ML.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Shall I use SVN? Or some other remote?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [...]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> WBR
>>>>>>>> Maxim aka solomax
>>>>>>>
>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> WBR
>>>>>> Maxim aka solomax
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [hidden email]
>>>>> For additional commands, e-mail: [hidden email]
>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
The build was successful
Staging repo is closed

Thanks a lot for the help!

On Wed, 19 Dec 2018 at 08:54, Rob Tompkins <[hidden email]> wrote:

>
>
> > On Dec 18, 2018, at 7:51 PM, Maxim Solodovnik <[hidden email]>
> wrote:
> >
> > Is it possible staging-distribution fails because there is already
> 4.2-RC1/
> > at dist-dev?
>
> Yes that does happen. I would make sure to delete the staging svn
> directory before going with the RC.
>
> -Rob
>
> >
> >> On Wed, 19 Dec 2018 at 07:32, Maxim Solodovnik <[hidden email]>
> wrote:
> >>
> >> Now I'm getting:
> >>
> >> [ERROR] Failed to execute goal
> >> org.apache.commons:commons-release-plugin:1.3:stage-distributions
> >> (stage-distributions) on project commons-collections4: Failed to add
> files
> >> to scm -> [Help 1]
> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> >> goal org.apache.commons:commons-release-plugin:1.3:stage-distributions
> >> (stage-distributions) on project commons-collections4: Failed to add
> files
> >> to scm
> >>
> >> I can see no reasonable error message
> >>
> >> Have tried to manually commit to
> >> https://dist.apache.org/repos/dist/dev/commons/collections/ and commit
> >> was successfull
> >>
> >>
> >>> On Wed, 19 Dec 2018 at 07:16, Gilles <[hidden email]>
> wrote:
> >>>
> >>>> On Wed, 19 Dec 2018 06:59:26 +0700, Maxim Solodovnik wrote:
> >>>> I found it here:
> >>>>
> >>>>
> >>>
> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300
> >>>>
> >>>> Shall I drop current staging repo and restart the build without this
> >>>> profile?
> >>>
> >>> Yes.
> >>> As I wrote, [RNG] is a modular project and "commons-rng-examples" is
> >>> one of its modules.
> >>> You can safely ignore any "-Pcommons-rng-examples" switch.  The rest
> >>> of the command line is fine.
> >>>
> >>> For a non-modular project, you might be lucky to not hit the bugs of
> >>> the "release-plugin".
> >>>
> >>>>
> >>>>> On Wed, 19 Dec 2018 at 06:57, sebb <[hidden email]> wrote:
> >>>>>
> >>>>> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik
> >>>>> <[hidden email]>
> >>>>> wrote:
> >>>>>>
> >>>>>> Thanks a lot Sebb,
> >>>>>>
> >>>>>> staging repo was created successfully.
> >>>>>> `mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean
> >>>>> site
> >>>>>> site:stage deploy`
> >>>>>>
> >>>>>> but I got following error during the build:
> >>>>>> [WARNING] The requested profile "commons-collections" could not be
> >>>>>> activated because it does not exist.
> >>>>>
> >>>>> That's because it does not exist.
> >>>>> Why did you add "-Pcommons-collections" to the command-line?
> >>>>> Is it documented to do so somewhere?
> >>>>>
> >>>>>> [ERROR] Failed to execute goal
> >>>>>> org.apache.commons:commons-release-plugin:1.3:stage-distributions
> >>>>>> (stage-distributions) on project commons-collections4: Failed to
> >>>>> add
> >>>>> files
> >>>>>> to scm -> [Help 1]
> >>>>>>
> >>>>>> It seems not important to me, would it be OK to ignore it and
> >>>>> proceed
> >>>>> with
> >>>>>> RC1?
> >>>>>
> >>>>> I don't use the release plugin so I don't know about that.
> >>>>>
> >>>>>> Another question: during release preparation I have created
> >>>>> `4.3-release`
> >>>>>> branch, it has zero commits, and I believe should be dropped (and
> >>>>> in fact
> >>>>>> shouln't be created)
> >>>>>> Documentation states: "As branches deletion is now forbidden at
> >>>>>> Apache, we will use a specific
> >>>>>> release branch for every version"
> >>>
> >>> That's the convention followed up to now.
> >>> But we do delete feature and bugfix branches that were merged into
> >>> "master", or experimental branches that have become stale.
> >>>
> >>> Gilles
> >>>
> >>>>>>
> >>>>>> Can I delete this useless branch and propose documentation update?
> >>>>>>
> >>>>>>> On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:
> >>>>>>>
> >>>>>>> I think the issue with dist/release/commons is that you need to
> >>>>> be
> >>>>>>> listed as a project committer, i.e. you need to be a Commons
> >>>>>>> committer.
> >>>>>>>
> >>>>>>> Possibly the same applies to Nexus.
> >>>>>>>
> >>>>>>> I have added you as a Commons committer.
> >>>>>>>
> >>>>>>> On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik
> >>>>> <[hidden email]>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>> Thanks a lot for the help :)
> >>>>>>>> Glad to check the release process ;)
> >>>>>>>>
> >>>>>>>> On Tue, 18 Dec 2018 at 23:19, Gilles
> >>>>> <[hidden email]>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Hello.
> >>>>>>>>>
> >>>>>>>>>> On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
> >>>>>>>>>> Thanks a lot
> >>>>>>>>>>
> >>>>>>>>>> Unfortunately the next error is: Failed to deploy
> >>>>> artifacts:
> >>>>> Could
> >>>>>>>>>> not
> >>>>>>>>>> transfer artifact
> >>>>> org.apache.commons:commons-collections4:jar:4.3
> >>>>>>>>>> from/to
> >>>>>>>>>> apache.releases.https (
> >>>>>>>>>>
> >>>>> https://repository.apache.org/service/local/staging/deploy/maven2):
> >>>>>>>>>> Access
> >>>>>>>>>> denied to:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
> >>>>>>>>>>
> >>>>>>>>>> I'm release manger for Apache OpenMeetings and just
> >>>>> double-check
> >>>>> I
> >>>>>>>>>> can
> >>>>>>>>>> access Staging Repos at repository.apache.org
> >>>>>>>>>> , so I guess there are additional restrictions here
> >>>>>>>>>>
> >>>>>>>>>> would appreciate any help/hint :)
> >>>>>>>>>
> >>>>>>>>> I don't know how to change the permissions (I don't think I
> >>>>> have
> >>>>>>>>> the privilege anyway), and the PMC chair is AFK for a couple
> >>>>> more
> >>>>>>>>> days IIUC. :-(
> >>>>>>>>>
> >>>>>>>>> Perhaps someone with a taller hat. :-}
> >>>>>>>>>
> >>>>>>>>> Sorry for the inconvenience; it looks like you are first one
> >>>>> to
> >>>>>>>>> try and exercise those privileges voted several years ago...
> >>>>>>>>>
> >>>>>>>>> Gilles
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Tue, 18 Dec 2018 at 22:54, Gilles <
> >>>>> [hidden email]>
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik
> >>>>> wrote:
> >>>>>>>>>>>> It seems I'm unable to commit to SVN:
> >>>>>>>>>>>>
> >>>>>>>>>>>> URL: https://dist.apache.org/repos/dist/release/commons
> >>>>>>>>>>>>
> >>>>>>>>>>>> Sending        KEYS
> >>>>>>>>>>>> Transmitting file data .svn: E195023: Commit failed
> >>>>> (details
> >>>>>>>>>>> follow):
> >>>>>>>>>>>> svn: E195023: Changing file
> >>>>>>>>>>>> '/home/solomax/work/apache-dist/release/commons/KEYS'
> >>>>> is
> >>>>> forbidden
> >>>>>>>>>>> by
> >>>>>>>>>>>> the
> >>>>>>>>>>>> server
> >>>>>>>>>>>> svn: E175013: Access to
> >>>>>>>>>>>> '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS'
> >>>>> forbidden
> >>>>>>>>>>>>
> >>>>>>>>>>>> Can someone help me with access rights?
> >>>>>>>>>>>
> >>>>>>>>>>> Not me.
> >>>>>>>>>>> But I've added your key (revision 31593).
> >>>>>>>>>>>
> >>>>>>>>>>> Hope it gets you a little further,
> >>>>>>>>>>> Gilles
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
> >>>>>>>>>>> <[hidden email]>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Moving conversation to dev@ list
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I was able to create branch using gitbox remote
> >>>>>>>>>>>>> Will proceed,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks for the tip
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, 18 Dec 2018 at 21:14, Gilles
> >>>>>>>>>>> <[hidden email]>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Hi.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik
> >>>>> wrote:
> >>>>>>>>>>>>>>> Hello Gilles,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I read documentation and as far as I can see To
> >>>>> perform
> >>>>>>>>>>> release I
> >>>>>>>>>>>>>>> need
> >>>>>>>>>>>>>>> rights to create branch
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> git remote -v
> >>>>>>>>>>>>>>> origin
> >>>>> [hidden email]:apache/commons-collections.git
> >>>>> (fetch)
> >>>>>>>>>>>>>>> origin
> >>>>> [hidden email]:apache/commons-collections.git
> >>>>> (push)
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> git push -u origin 4.3-release
> >>>>>>>>>>>>>>> ERROR: Permission to apache/commons-collections.git
> >>>>> denied to
> >>>>>>>>>>>>>>> solomax.
> >>>>>>>>>>>>>>> fatal: Could not read from remote repository.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Please make sure you have the correct access rights
> >>>>>>>>>>>>>>> and the repository exists.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The repository (at Apache) is here:
> >>>>>>>>>>>>>>
> >>>>>>> https://gitbox.apache.org/repos/asf?p=commons-collections.git
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> We were told that it should now be possible to also
> >>>>> write
> >>>>>>>>>>>>>> through GitHub, but I don't know if and how it should
> >>>>> work.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> IMO, the easiest would be to clone the above, and try
> >>>>> again
> >>>>>>>>>>>>>> with that.  [If it still does not work, then perhaps
> >>>>> the
> >>>>> issue
> >>>>>>>>>>>>>> is that the "all-Apache-committers-are-committers"
> >>>>> resolution
> >>>>>>>>>>>>>> was not applied.]
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Gilles
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> P.S. We should move this conversation over to the
> >>>>> "dev" ML.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Shall I use SVN? Or some other remote?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [...]
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> WBR
> >>>>>>>> Maxim aka solomax
> >>>>>>>
> >>>>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> WBR
> >>>>>> Maxim aka solomax
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: [hidden email]
> >>>>> For additional commands, e-mail: [hidden email]
> >>>>>
> >>>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
WBR
Maxim aka solomax
Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Rob Tompkins


> On Dec 19, 2018, at 8:29 AM, Maxim Solodovnik <[hidden email]> wrote:
>
> The build was successful
> Staging repo is closed
>
> Thanks a lot for the help!

How were the docs on using the release plugin? Just curious…as I wrote the plugin and the docs.

-Rob

>
> On Wed, 19 Dec 2018 at 08:54, Rob Tompkins <[hidden email]> wrote:
>
>>
>>
>>> On Dec 18, 2018, at 7:51 PM, Maxim Solodovnik <[hidden email]>
>> wrote:
>>>
>>> Is it possible staging-distribution fails because there is already
>> 4.2-RC1/
>>> at dist-dev?
>>
>> Yes that does happen. I would make sure to delete the staging svn
>> directory before going with the RC.
>>
>> -Rob
>>
>>>
>>>> On Wed, 19 Dec 2018 at 07:32, Maxim Solodovnik <[hidden email]>
>> wrote:
>>>>
>>>> Now I'm getting:
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.apache.commons:commons-release-plugin:1.3:stage-distributions
>>>> (stage-distributions) on project commons-collections4: Failed to add
>> files
>>>> to scm -> [Help 1]
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute
>>>> goal org.apache.commons:commons-release-plugin:1.3:stage-distributions
>>>> (stage-distributions) on project commons-collections4: Failed to add
>> files
>>>> to scm
>>>>
>>>> I can see no reasonable error message
>>>>
>>>> Have tried to manually commit to
>>>> https://dist.apache.org/repos/dist/dev/commons/collections/ and commit
>>>> was successfull
>>>>
>>>>
>>>>> On Wed, 19 Dec 2018 at 07:16, Gilles <[hidden email]>
>> wrote:
>>>>>
>>>>>> On Wed, 19 Dec 2018 06:59:26 +0700, Maxim Solodovnik wrote:
>>>>>> I found it here:
>>>>>>
>>>>>>
>>>>>
>> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300
>>>>>>
>>>>>> Shall I drop current staging repo and restart the build without this
>>>>>> profile?
>>>>>
>>>>> Yes.
>>>>> As I wrote, [RNG] is a modular project and "commons-rng-examples" is
>>>>> one of its modules.
>>>>> You can safely ignore any "-Pcommons-rng-examples" switch.  The rest
>>>>> of the command line is fine.
>>>>>
>>>>> For a non-modular project, you might be lucky to not hit the bugs of
>>>>> the "release-plugin".
>>>>>
>>>>>>
>>>>>>> On Wed, 19 Dec 2018 at 06:57, sebb <[hidden email]> wrote:
>>>>>>>
>>>>>>> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik
>>>>>>> <[hidden email]>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Thanks a lot Sebb,
>>>>>>>>
>>>>>>>> staging repo was created successfully.
>>>>>>>> `mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean
>>>>>>> site
>>>>>>>> site:stage deploy`
>>>>>>>>
>>>>>>>> but I got following error during the build:
>>>>>>>> [WARNING] The requested profile "commons-collections" could not be
>>>>>>>> activated because it does not exist.
>>>>>>>
>>>>>>> That's because it does not exist.
>>>>>>> Why did you add "-Pcommons-collections" to the command-line?
>>>>>>> Is it documented to do so somewhere?
>>>>>>>
>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>> org.apache.commons:commons-release-plugin:1.3:stage-distributions
>>>>>>>> (stage-distributions) on project commons-collections4: Failed to
>>>>>>> add
>>>>>>> files
>>>>>>>> to scm -> [Help 1]
>>>>>>>>
>>>>>>>> It seems not important to me, would it be OK to ignore it and
>>>>>>> proceed
>>>>>>> with
>>>>>>>> RC1?
>>>>>>>
>>>>>>> I don't use the release plugin so I don't know about that.
>>>>>>>
>>>>>>>> Another question: during release preparation I have created
>>>>>>> `4.3-release`
>>>>>>>> branch, it has zero commits, and I believe should be dropped (and
>>>>>>> in fact
>>>>>>>> shouln't be created)
>>>>>>>> Documentation states: "As branches deletion is now forbidden at
>>>>>>>> Apache, we will use a specific
>>>>>>>> release branch for every version"
>>>>>
>>>>> That's the convention followed up to now.
>>>>> But we do delete feature and bugfix branches that were merged into
>>>>> "master", or experimental branches that have become stale.
>>>>>
>>>>> Gilles
>>>>>
>>>>>>>>
>>>>>>>> Can I delete this useless branch and propose documentation update?
>>>>>>>>
>>>>>>>>> On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:
>>>>>>>>>
>>>>>>>>> I think the issue with dist/release/commons is that you need to
>>>>>>> be
>>>>>>>>> listed as a project committer, i.e. you need to be a Commons
>>>>>>>>> committer.
>>>>>>>>>
>>>>>>>>> Possibly the same applies to Nexus.
>>>>>>>>>
>>>>>>>>> I have added you as a Commons committer.
>>>>>>>>>
>>>>>>>>> On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik
>>>>>>> <[hidden email]>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Thanks a lot for the help :)
>>>>>>>>>> Glad to check the release process ;)
>>>>>>>>>>
>>>>>>>>>> On Tue, 18 Dec 2018 at 23:19, Gilles
>>>>>>> <[hidden email]>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello.
>>>>>>>>>>>
>>>>>>>>>>>> On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
>>>>>>>>>>>> Thanks a lot
>>>>>>>>>>>>
>>>>>>>>>>>> Unfortunately the next error is: Failed to deploy
>>>>>>> artifacts:
>>>>>>> Could
>>>>>>>>>>>> not
>>>>>>>>>>>> transfer artifact
>>>>>>> org.apache.commons:commons-collections4:jar:4.3
>>>>>>>>>>>> from/to
>>>>>>>>>>>> apache.releases.https (
>>>>>>>>>>>>
>>>>>>> https://repository.apache.org/service/local/staging/deploy/maven2):
>>>>>>>>>>>> Access
>>>>>>>>>>>> denied to:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
>>>>>>>>>>>>
>>>>>>>>>>>> I'm release manger for Apache OpenMeetings and just
>>>>>>> double-check
>>>>>>> I
>>>>>>>>>>>> can
>>>>>>>>>>>> access Staging Repos at repository.apache.org
>>>>>>>>>>>> , so I guess there are additional restrictions here
>>>>>>>>>>>>
>>>>>>>>>>>> would appreciate any help/hint :)
>>>>>>>>>>>
>>>>>>>>>>> I don't know how to change the permissions (I don't think I
>>>>>>> have
>>>>>>>>>>> the privilege anyway), and the PMC chair is AFK for a couple
>>>>>>> more
>>>>>>>>>>> days IIUC. :-(
>>>>>>>>>>>
>>>>>>>>>>> Perhaps someone with a taller hat. :-}
>>>>>>>>>>>
>>>>>>>>>>> Sorry for the inconvenience; it looks like you are first one
>>>>>>> to
>>>>>>>>>>> try and exercise those privileges voted several years ago...
>>>>>>>>>>>
>>>>>>>>>>> Gilles
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, 18 Dec 2018 at 22:54, Gilles <
>>>>>>> [hidden email]>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik
>>>>>>> wrote:
>>>>>>>>>>>>>> It seems I'm unable to commit to SVN:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> URL: https://dist.apache.org/repos/dist/release/commons
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sending        KEYS
>>>>>>>>>>>>>> Transmitting file data .svn: E195023: Commit failed
>>>>>>> (details
>>>>>>>>>>>>> follow):
>>>>>>>>>>>>>> svn: E195023: Changing file
>>>>>>>>>>>>>> '/home/solomax/work/apache-dist/release/commons/KEYS'
>>>>>>> is
>>>>>>> forbidden
>>>>>>>>>>>>> by
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> server
>>>>>>>>>>>>>> svn: E175013: Access to
>>>>>>>>>>>>>> '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS'
>>>>>>> forbidden
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Can someone help me with access rights?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Not me.
>>>>>>>>>>>>> But I've added your key (revision 31593).
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hope it gets you a little further,
>>>>>>>>>>>>> Gilles
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
>>>>>>>>>>>>> <[hidden email]>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Moving conversation to dev@ list
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I was able to create branch using gitbox remote
>>>>>>>>>>>>>>> Will proceed,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks for the tip
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, 18 Dec 2018 at 21:14, Gilles
>>>>>>>>>>>>> <[hidden email]>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik
>>>>>>> wrote:
>>>>>>>>>>>>>>>>> Hello Gilles,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I read documentation and as far as I can see To
>>>>>>> perform
>>>>>>>>>>>>> release I
>>>>>>>>>>>>>>>>> need
>>>>>>>>>>>>>>>>> rights to create branch
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> git remote -v
>>>>>>>>>>>>>>>>> origin
>>>>>>> [hidden email]:apache/commons-collections.git
>>>>>>> (fetch)
>>>>>>>>>>>>>>>>> origin
>>>>>>> [hidden email]:apache/commons-collections.git
>>>>>>> (push)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> git push -u origin 4.3-release
>>>>>>>>>>>>>>>>> ERROR: Permission to apache/commons-collections.git
>>>>>>> denied to
>>>>>>>>>>>>>>>>> solomax.
>>>>>>>>>>>>>>>>> fatal: Could not read from remote repository.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Please make sure you have the correct access rights
>>>>>>>>>>>>>>>>> and the repository exists.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The repository (at Apache) is here:
>>>>>>>>>>>>>>>>
>>>>>>>>> https://gitbox.apache.org/repos/asf?p=commons-collections.git
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We were told that it should now be possible to also
>>>>>>> write
>>>>>>>>>>>>>>>> through GitHub, but I don't know if and how it should
>>>>>>> work.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> IMO, the easiest would be to clone the above, and try
>>>>>>> again
>>>>>>>>>>>>>>>> with that.  [If it still does not work, then perhaps
>>>>>>> the
>>>>>>> issue
>>>>>>>>>>>>>>>> is that the "all-Apache-committers-are-committers"
>>>>>>> resolution
>>>>>>>>>>>>>>>> was not applied.]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Gilles
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> P.S. We should move this conversation over to the
>>>>>>> "dev" ML.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Shall I use SVN? Or some other remote?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [...]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> WBR
>>>>>>>>>> Maxim aka solomax
>>>>>>>>>
>>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> WBR
>>>>>>>> Maxim aka solomax
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [hidden email]
>>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [hidden email]
>>>>> For additional commands, e-mail: [hidden email]
>>>>>
>>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> --
> WBR
> Maxim aka solomax


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Help with migrating one of OpenJPA classes to commons-collections4

Maxim Solodovnik
Hello Rob,

The instruction [1] is good but seems to me "too universal" it would
be easier to start with instruction specific to particular project :)
I was my first release of commons-collections so I was unsure on every step :))

[1] https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt

On Wed, 19 Dec 2018 at 21:19, Rob Tompkins <[hidden email]> wrote:

>
>
>
> > On Dec 19, 2018, at 8:29 AM, Maxim Solodovnik <[hidden email]> wrote:
> >
> > The build was successful
> > Staging repo is closed
> >
> > Thanks a lot for the help!
>
> How were the docs on using the release plugin? Just curious…as I wrote the plugin and the docs.
>
> -Rob
>
> >
> > On Wed, 19 Dec 2018 at 08:54, Rob Tompkins <[hidden email]> wrote:
> >
> >>
> >>
> >>> On Dec 18, 2018, at 7:51 PM, Maxim Solodovnik <[hidden email]>
> >> wrote:
> >>>
> >>> Is it possible staging-distribution fails because there is already
> >> 4.2-RC1/
> >>> at dist-dev?
> >>
> >> Yes that does happen. I would make sure to delete the staging svn
> >> directory before going with the RC.
> >>
> >> -Rob
> >>
> >>>
> >>>> On Wed, 19 Dec 2018 at 07:32, Maxim Solodovnik <[hidden email]>
> >> wrote:
> >>>>
> >>>> Now I'm getting:
> >>>>
> >>>> [ERROR] Failed to execute goal
> >>>> org.apache.commons:commons-release-plugin:1.3:stage-distributions
> >>>> (stage-distributions) on project commons-collections4: Failed to add
> >> files
> >>>> to scm -> [Help 1]
> >>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> >> execute
> >>>> goal org.apache.commons:commons-release-plugin:1.3:stage-distributions
> >>>> (stage-distributions) on project commons-collections4: Failed to add
> >> files
> >>>> to scm
> >>>>
> >>>> I can see no reasonable error message
> >>>>
> >>>> Have tried to manually commit to
> >>>> https://dist.apache.org/repos/dist/dev/commons/collections/ and commit
> >>>> was successfull
> >>>>
> >>>>
> >>>>> On Wed, 19 Dec 2018 at 07:16, Gilles <[hidden email]>
> >> wrote:
> >>>>>
> >>>>>> On Wed, 19 Dec 2018 06:59:26 +0700, Maxim Solodovnik wrote:
> >>>>>> I found it here:
> >>>>>>
> >>>>>>
> >>>>>
> >> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt#l300
> >>>>>>
> >>>>>> Shall I drop current staging repo and restart the build without this
> >>>>>> profile?
> >>>>>
> >>>>> Yes.
> >>>>> As I wrote, [RNG] is a modular project and "commons-rng-examples" is
> >>>>> one of its modules.
> >>>>> You can safely ignore any "-Pcommons-rng-examples" switch.  The rest
> >>>>> of the command line is fine.
> >>>>>
> >>>>> For a non-modular project, you might be lucky to not hit the bugs of
> >>>>> the "release-plugin".
> >>>>>
> >>>>>>
> >>>>>>> On Wed, 19 Dec 2018 at 06:57, sebb <[hidden email]> wrote:
> >>>>>>>
> >>>>>>> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik
> >>>>>>> <[hidden email]>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>> Thanks a lot Sebb,
> >>>>>>>>
> >>>>>>>> staging repo was created successfully.
> >>>>>>>> `mvn -Duser.name="solomax" -Pcommons-collections -Prelease clean
> >>>>>>> site
> >>>>>>>> site:stage deploy`
> >>>>>>>>
> >>>>>>>> but I got following error during the build:
> >>>>>>>> [WARNING] The requested profile "commons-collections" could not be
> >>>>>>>> activated because it does not exist.
> >>>>>>>
> >>>>>>> That's because it does not exist.
> >>>>>>> Why did you add "-Pcommons-collections" to the command-line?
> >>>>>>> Is it documented to do so somewhere?
> >>>>>>>
> >>>>>>>> [ERROR] Failed to execute goal
> >>>>>>>> org.apache.commons:commons-release-plugin:1.3:stage-distributions
> >>>>>>>> (stage-distributions) on project commons-collections4: Failed to
> >>>>>>> add
> >>>>>>> files
> >>>>>>>> to scm -> [Help 1]
> >>>>>>>>
> >>>>>>>> It seems not important to me, would it be OK to ignore it and
> >>>>>>> proceed
> >>>>>>> with
> >>>>>>>> RC1?
> >>>>>>>
> >>>>>>> I don't use the release plugin so I don't know about that.
> >>>>>>>
> >>>>>>>> Another question: during release preparation I have created
> >>>>>>> `4.3-release`
> >>>>>>>> branch, it has zero commits, and I believe should be dropped (and
> >>>>>>> in fact
> >>>>>>>> shouln't be created)
> >>>>>>>> Documentation states: "As branches deletion is now forbidden at
> >>>>>>>> Apache, we will use a specific
> >>>>>>>> release branch for every version"
> >>>>>
> >>>>> That's the convention followed up to now.
> >>>>> But we do delete feature and bugfix branches that were merged into
> >>>>> "master", or experimental branches that have become stale.
> >>>>>
> >>>>> Gilles
> >>>>>
> >>>>>>>>
> >>>>>>>> Can I delete this useless branch and propose documentation update?
> >>>>>>>>
> >>>>>>>>> On Wed, 19 Dec 2018 at 00:04, sebb <[hidden email]> wrote:
> >>>>>>>>>
> >>>>>>>>> I think the issue with dist/release/commons is that you need to
> >>>>>>> be
> >>>>>>>>> listed as a project committer, i.e. you need to be a Commons
> >>>>>>>>> committer.
> >>>>>>>>>
> >>>>>>>>> Possibly the same applies to Nexus.
> >>>>>>>>>
> >>>>>>>>> I have added you as a Commons committer.
> >>>>>>>>>
> >>>>>>>>> On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik
> >>>>>>> <[hidden email]>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Thanks a lot for the help :)
> >>>>>>>>>> Glad to check the release process ;)
> >>>>>>>>>>
> >>>>>>>>>> On Tue, 18 Dec 2018 at 23:19, Gilles
> >>>>>>> <[hidden email]>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Hello.
> >>>>>>>>>>>
> >>>>>>>>>>>> On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote:
> >>>>>>>>>>>> Thanks a lot
> >>>>>>>>>>>>
> >>>>>>>>>>>> Unfortunately the next error is: Failed to deploy
> >>>>>>> artifacts:
> >>>>>>> Could
> >>>>>>>>>>>> not
> >>>>>>>>>>>> transfer artifact
> >>>>>>> org.apache.commons:commons-collections4:jar:4.3
> >>>>>>>>>>>> from/to
> >>>>>>>>>>>> apache.releases.https (
> >>>>>>>>>>>>
> >>>>>>> https://repository.apache.org/service/local/staging/deploy/maven2):
> >>>>>>>>>>>> Access
> >>>>>>>>>>>> denied to:
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar
> >>>>>>>>>>>>
> >>>>>>>>>>>> I'm release manger for Apache OpenMeetings and just
> >>>>>>> double-check
> >>>>>>> I
> >>>>>>>>>>>> can
> >>>>>>>>>>>> access Staging Repos at repository.apache.org
> >>>>>>>>>>>> , so I guess there are additional restrictions here
> >>>>>>>>>>>>
> >>>>>>>>>>>> would appreciate any help/hint :)
> >>>>>>>>>>>
> >>>>>>>>>>> I don't know how to change the permissions (I don't think I
> >>>>>>> have
> >>>>>>>>>>> the privilege anyway), and the PMC chair is AFK for a couple
> >>>>>>> more
> >>>>>>>>>>> days IIUC. :-(
> >>>>>>>>>>>
> >>>>>>>>>>> Perhaps someone with a taller hat. :-}
> >>>>>>>>>>>
> >>>>>>>>>>> Sorry for the inconvenience; it looks like you are first one
> >>>>>>> to
> >>>>>>>>>>> try and exercise those privileges voted several years ago...
> >>>>>>>>>>>
> >>>>>>>>>>> Gilles
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, 18 Dec 2018 at 22:54, Gilles <
> >>>>>>> [hidden email]>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik
> >>>>>>> wrote:
> >>>>>>>>>>>>>> It seems I'm unable to commit to SVN:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> URL: https://dist.apache.org/repos/dist/release/commons
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Sending        KEYS
> >>>>>>>>>>>>>> Transmitting file data .svn: E195023: Commit failed
> >>>>>>> (details
> >>>>>>>>>>>>> follow):
> >>>>>>>>>>>>>> svn: E195023: Changing file
> >>>>>>>>>>>>>> '/home/solomax/work/apache-dist/release/commons/KEYS'
> >>>>>>> is
> >>>>>>> forbidden
> >>>>>>>>>>>>> by
> >>>>>>>>>>>>>> the
> >>>>>>>>>>>>>> server
> >>>>>>>>>>>>>> svn: E175013: Access to
> >>>>>>>>>>>>>> '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS'
> >>>>>>> forbidden
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Can someone help me with access rights?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Not me.
> >>>>>>>>>>>>> But I've added your key (revision 31593).
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hope it gets you a little further,
> >>>>>>>>>>>>> Gilles
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik
> >>>>>>>>>>>>> <[hidden email]>
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Moving conversation to dev@ list
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I was able to create branch using gitbox remote
> >>>>>>>>>>>>>>> Will proceed,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Thanks for the tip
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Tue, 18 Dec 2018 at 21:14, Gilles
> >>>>>>>>>>>>> <[hidden email]>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Hi.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik
> >>>>>>> wrote:
> >>>>>>>>>>>>>>>>> Hello Gilles,
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> I read documentation and as far as I can see To
> >>>>>>> perform
> >>>>>>>>>>>>> release I
> >>>>>>>>>>>>>>>>> need
> >>>>>>>>>>>>>>>>> rights to create branch
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> git remote -v
> >>>>>>>>>>>>>>>>> origin
> >>>>>>> [hidden email]:apache/commons-collections.git
> >>>>>>> (fetch)
> >>>>>>>>>>>>>>>>> origin
> >>>>>>> [hidden email]:apache/commons-collections.git
> >>>>>>> (push)
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> git push -u origin 4.3-release
> >>>>>>>>>>>>>>>>> ERROR: Permission to apache/commons-collections.git
> >>>>>>> denied to
> >>>>>>>>>>>>>>>>> solomax.
> >>>>>>>>>>>>>>>>> fatal: Could not read from remote repository.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Please make sure you have the correct access rights
> >>>>>>>>>>>>>>>>> and the repository exists.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> The repository (at Apache) is here:
> >>>>>>>>>>>>>>>>
> >>>>>>>>> https://gitbox.apache.org/repos/asf?p=commons-collections.git
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> We were told that it should now be possible to also
> >>>>>>> write
> >>>>>>>>>>>>>>>> through GitHub, but I don't know if and how it should
> >>>>>>> work.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> IMO, the easiest would be to clone the above, and try
> >>>>>>> again
> >>>>>>>>>>>>>>>> with that.  [If it still does not work, then perhaps
> >>>>>>> the
> >>>>>>> issue
> >>>>>>>>>>>>>>>> is that the "all-Apache-committers-are-committers"
> >>>>>>> resolution
> >>>>>>>>>>>>>>>> was not applied.]
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Gilles
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> P.S. We should move this conversation over to the
> >>>>>>> "dev" ML.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Shall I use SVN? Or some other remote?
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> [...]
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>
> >>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>>>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> WBR
> >>>>>>>>>> Maxim aka solomax
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>> ---------------------------------------------------------------------
> >>>>>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> WBR
> >>>>>>>> Maxim aka solomax
> >>>>>>>
> >>>>>>>
> >>>>>>> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: [hidden email]
> >>>>>>> For additional commands, e-mail: [hidden email]
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: [hidden email]
> >>>>> For additional commands, e-mail: [hidden email]
> >>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> WBR
> >>>> Maxim aka solomax
> >>>>
> >>>
> >>>
> >>> --
> >>> WBR
> >>> Maxim aka solomax
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
> >
> > --
> > WBR
> > Maxim aka solomax
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


--
WBR
Maxim aka solomax

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Release-plugin] Howto (Was: Help with migrating one of OpenJPA classes to commons-collections4)

Gilles Sadowski
Hello.

On Wed, 19 Dec 2018 23:19:57 +0700, Maxim Solodovnik wrote:

> Hello Rob,
>
> The instruction [1] is good but seems to me "too universal" it would
> be easier to start with instruction specific to particular project :)
> I was my first release of commons-collections so I was unsure on
> every step :))
>
> [1]
>
> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt

Rob was probably talking about this page:
     http://commons.apache.org/proper/commons-release-plugin/index.html

The reference [1] above is a recipe which I started to write for
"Commons Math" way back when following any of the documents would
get me stuck as I was tryiing to manage my first release.
Through asking on the list, we manage to fill all the dots.
Later, the "recipe" was adapted to "git" and then to "multimodule
maven" (when I started "Commons RNG").

Regards,
Gilles

> On Wed, 19 Dec 2018 at 21:19, Rob Tompkins <[hidden email]>
> wrote:
>>
>>
>>
>> > On Dec 19, 2018, at 8:29 AM, Maxim Solodovnik
>> <[hidden email]> wrote:
>> >
>> > The build was successful
>> > Staging repo is closed
>> >
>> > Thanks a lot for the help!
>>
>> How were the docs on using the release plugin? Just curious…as I
>> wrote the plugin and the docs.
>>
>> -Rob
>>
>> [... lots of OT stuff skipped ...]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]