> 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
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
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
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
On Mon, 17 Dec 2018 15:28:46 +0100, Gilles wrote:
Ping?
I found this:
https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=commitdiff;h=f73546863611e5dd850fd311277f2019259489ce;hp=288c8b5196ab29e0e2ca50182a28f217e0828833
Please confirm whether the fix is "manual".
Gilles
Is this a
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
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.
Hi.
On Tue, 18 Dec 2018 21:33:42 + (UTC), Bruno P. Kinoshita wrote:
Hi Gilles!
Sorry, just came back from a long holiday, speaking Portuguese only.
Semantic, vocabulary, etc, in English is a bit laggy right now.
On Tue, 18 Dec 2018 07:22:00 + (UTC), Bruno P. Kinoshita wrote:
From
Hi Gilles!
Sorry, just came back from a long holiday, speaking Portuguese only. Semantic,
vocabulary, etc, in English is a bit laggy right now.
>>On Tue, 18 Dec 2018 07:22:00 + (UTC), Bruno P. Kinoshita wrote:
>> From what I understood from the previous messages & discussion on
>> GitHub,
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 (
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:
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
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
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
Hi.
On Tue, 18 Dec 2018 07:22:00 + (UTC), Bruno P. Kinoshita wrote:
From what I understood from the previous messages & discussion on
GitHub, it would be more convenient for users to be able to have a
List instead of an Iterable,
Why "instead"?
The patch makes the class a subclass of
18 matches
Mail list logo
