+1
Am 10.08.2019 um 16:42 schrieb Gary Gregory:
Hi all,
It seems to me the commons-parent should cause the RAT check to run for all
builds, say in the... validate phase?
Gary
-
To unsubscribe, e-mail:
Some times I add tasks to the maven default target, or move things to the
verify stage, but I still run `mvn clean test install etc` out of habit (: it
is normally redundant and works fine... this is probably the first time I had
an error like this.
But +1 on worrying about this build issue
On Mon, Aug 12, 2019 at 6:28 PM Bruno P. Kinoshita wrote:
> I am not sure.
> I tried `mvn clean test` (building from tag FWIW) and it passed on $work
> notebook (same version of Ubuntu and Java, but in virtualbox hosted on
> win10pro).
>
I like building RCs from tags as well, it feels like the
I am not sure.
I tried `mvn clean test` (building from tag FWIW) and it passed on $work
notebook (same version of Ubuntu and Java, but in virtualbox hosted on
win10pro).
The tried `mvn clean install site -P japicmp`, and got the same error as
yesterday.
Tried the same command two times more,
Ok, I just wasn’t sure.
+1 from me
On August 12, 2019 at 10:01:26, Gary Gregory (garydgreg...@gmail.com) wrote:
I see " [ERROR] 'distributionManagement.status' must not be specified. @
line 417, column 13" but the site build, it probably is missing some
details. I think I saw the same thing
I see " [ERROR] 'distributionManagement.status' must not be specified. @
line 417, column 13" but the site build, it probably is missing some
details. I think I saw the same thing fly by for me but I am not going to
worry about it for this site for now.
Gary
On Mon, Aug 12, 2019 at 9:50 AM Otto
FWIW, we already have plenty of Checkstyle issues, not a showstopper IMO:
https://commons.apache.org/proper/commons-vfs/checkstyle-aggregate.html
Gary
On Mon, Aug 12, 2019 at 9:50 AM Otto Fowler wrote:
> I have had this build pass twice, running
>
> mvn -V clean install site -P japicmp
>
>
Could you be having access rights issues? The build 'mvn -V clean test'
passes for me under VirtualBox with:
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 11.0.4, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name:
I have had this build pass twice, running
mvn -V clean install site -P japicmp
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
2019-04-04T15:00:29-04:00)
Maven home: /usr/local/Cellar/maven/3.6.1/libexec
Java version: 1.8.0_171, vendor: Oracle Corporation, runtime:
Hello.
Le lun. 12 août 2019 à 14:48, Gary Gregory a écrit :
>
> Hi All,
>
> I'm thinking that our components source repo page
Do you mean that page:
http://commons.apache.org/proper/commons-rng/developers.html
?
> should also include a
> link to the GitHub version of the repo.
+1
And the
Hi All,
I'm thinking that our components source repo page should also include a
link to the GitHub version of the repo.
Thoughts?
Gary
Is this "random" or is it repeatable for your setup?
Gary
On Mon, Aug 12, 2019, 05:47 Bruno P. Kinoshita wrote:
> Hi Gary,
> >I have tested this with 'mvn -V clean install site -P japicmp' using:
> It failed with `mvn clean test install site`, then tried the command
> above, and failed the
Hi Gary,
>I have tested this with 'mvn -V clean install site -P japicmp' using:
It failed with `mvn clean test install site`, then tried the command above, and
failed the same way. My env:
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home:
13 matches
Mail list logo
