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 :)
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
> On Dec 19, 2018, at 8:29 AM, Maxim Solodovnik 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
The build was successful
Staging repo is closed
Thanks a lot for the help!
On Wed, 19 Dec 2018 at 08:54, Rob Tompkins wrote:
>
>
> > On Dec 18, 2018, at 7:51 PM, Maxim Solodovnik
> wrote:
> >
> > Is it possible staging-distribution fails because there is already
> 4.2-RC1/
> > at dist-dev?
>
>
> On Dec 18, 2018, at 7:51 PM, Maxim Solodovnik 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:
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 wrote:
> Now I'm getting:
>
> [ERROR] Failed to execute goal
> org.apache.commons:commons-release-plugin:1.3:stage-distributions
> (stage-distributions) on proj
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.
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 proj
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 wrote:
> On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik
> wrote:
>
On Tue, 18 Dec 2018 at 23:37, Maxim Solodovnik 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 "co
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.
[E
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 wrote:
>
> Thanks a lot for the
Thanks a lot for the help :)
Glad to check the release process ;)
On Tue, 18 Dec 2018 at 23:19, Gilles 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
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
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/
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
SendingKEYS
Transmitting file data .svn: E195023: Commit failed (details follow):
svn: E195023: Changing file
'/home/solomax/work/apa
It seems I'm unable to commit to SVN:
URL: https://dist.apache.org/repos/dist/release/commons
SendingKEYS
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:
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 wrote:
> Hi.
>
> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> > Hello Gilles,
> >
> > I read documentation and as far as I ca
18 matches
Mail list logo
