On Mon, Oct 26, 2020 at 9:51 AM Rob Tompkins wrote:
> The build worked for me on a different machine. So I would have been a +1.
>
Thanks Rob, that should make RC2 a breeze.
GHary
>
> > On Oct 21, 2020, at 8:20 AM, Rob Tompkins wrote:
> >
> > This looks similar to what Bruno is getting out o
The build worked for me on a different machine. So I would have been a +1.
> On Oct 21, 2020, at 8:20 AM, Rob Tompkins wrote:
>
> This looks similar to what Bruno is getting out of the build, but here’s what
> I’m seeing. It looks like a maven plugin issue. I wonder if there are some
> updates
Thanks Bruno, I'll cut RC2 tomorrow.
Gary
On Sun, Oct 25, 2020, 23:29 Bruno P. Kinoshita wrote:
> Hi Gary,
>
> The release branch worked for me. All the four commands in your first
> e-mail worked,
>
> commit 182bdf6f95a7ce9416a5a55b72b82d8a7a49a000 (HEAD -> release,
> upstream/release)
> Auth
Hi Gary,
The release branch worked for me. All the four commands in your first e-mail
worked,
commit 182bdf6f95a7ce9416a5a55b72b82d8a7a49a000 (HEAD -> release,
upstream/release)
Author: Gary Gregory
Date: Sun Oct 25 14:47:06 2020 -0400
Ignore log files that the build may produce.
Che
On Mon, Oct 19, 2020 at 3:03 AM Bruno P. Kinoshita wrote:
> Checked signatures, and inspected files in the dist area. No issues.
>
> Tried building following instructions in `BUILDING.txt` but it failed due
> to files without license when RAT report was executed.
>
> Tried again with the command
This looks similar to what Bruno is getting out of the build, but here’s what
I’m seeing. It looks like a maven plugin issue. I wonder if there are some
updates we could perform in the plugin zone that could potentially sort this
out.
-Rob
---
From the tag commons-vfs-2.7.0-RC1
kinow@ranma:~/Development/java/apache/commons-vfs$ git log -n 1
commit 8a34d82ead0780a9ee1f78fd9702e5dbd663070a (HEAD, tag:
commons-vfs-2.7.0-RC1, upstream/release)
Author: Gary Gregory
Date: Sun Oct 18 23:10:57 2020 -0400
Update POM version numbers fo
Are working from the tag or the zip or tar?
Gary
On Tue, Oct 20, 2020, 18:52 Bruno P. Kinoshita wrote:
> >Overall, I would not say this is a blocker. WDYT?
>
> If others are able to build it I'd say it's not a blocker.
>
> I tried the commands you sent below. I think they are the same ones I
>
>Overall, I would not say this is a blocker. WDYT?
If others are able to build it I'd say it's not a blocker.
I tried the commands you sent below. I think they are the same ones I tried
before, from your first message.
`mvn -V -Ptest-deploy -Prelease clean install -DskipTests` runs OK. `git
s
Hi Bruno,
The files in BUILDING.txt are not up to date with what I do to test an RC
build, so I'll update those with:
mvn -V -Ptest-deploy -Prelease clean install -DskipTests
mvn -V -Ptest-deploy -Prelease -P japicmp -P jacoco site
mvn -V -Ptest-deploy -Prelease deploy
mvn -V -Ptest-deploy -Prele
Checked signatures, and inspected files in the dist area. No issues.
Tried building following instructions in `BUILDING.txt` but it failed due to
files without license when RAT report was executed.
Tried again with the commands in the body of your e-mail Gary, but it failed
again on: mvn -V -P
We have fixed a few bugs and added some enhancements since Apache Commons
VFS Project 2.6.0 was released, so I would like to release Apache Commons
VFS Project 2.7.0.
Apache Commons VFS Project 2.7.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/vfs/2.7.0-RC1
12 matches
Mail list logo
