Il dom 13 ago 2017, 17:31 Tibor Digana ha
scritto:
> I found an issue. JDK printed this on std/out:
> WARNING: Using incubator modules: jdk.incubator.httpclient
>
IMHO This is because we are importing all system modules. Maybe importing
only java.se.ee would cover
You will need the same tricks at runtime for the command line that Maven
might hide at build time... :-( I guess hacks like --add-modules ALL-SYSTEM
will become part of our daily grind...
Gary
On Tue, Aug 15, 2017 at 9:07 AM, Enrico Olivelli
wrote:
> Il mar 15 ago 2017,
I'm guessing that all the pain of doing this will not be fully known until
Maven is Java 9-ified.
Gary
On Tue, Aug 15, 2017 at 10:16 AM, Enrico Olivelli
wrote:
> Il mar 15 ago 2017, 17:51 Gary Gregory ha
> scritto:
>
> > You will need the same
On Tue, 15 Aug 2017 19:57:37 +0200, Gary Gregory
wrote:
I'm guessing that all the pain of doing this will not be fully known
until
Maven is Java 9-ified.
Not sure what you mean by this. Maven itself can run on Java 9, most
plugins work with Java 9, most Java 9
Il mar 15 ago 2017, 00:03 Tibor Digana ha
scritto:
> I do not want to be too pessimistic but the inheritance of modules is
> crucial for all the world.
>
> The common sense tells me that I should not release Java 9 on September,
> 2017 unless Java EE application
Il mar 15 ago 2017, 17:51 Gary Gregory ha scritto:
> You will need the same tricks at runtime for the command line that Maven
> might hide at build time... :-( I guess hacks like --add-modules ALL-SYSTEM
> will become part of our daily grind...
>
Gary, I think you are
Can you give me pls an example with "invoker" in Jenkinsfile showing test
reports in "Test result" screen from maven-invoker-plugin.
This should be something similar to "junit"
success {
junit healthScaleFactor: 0.0, allowEmptyResults: true,
keepLongStdio: true, testResults:
Hi Karl Heinz,
I think it makes sense to have these packaging plugins.
Haven't looked at the code yet, but you can start with the preparations.
I hope Brian is available to make this Jira projects.
thanks,
Robert
On Sun, 13 Aug 2017 21:19:55 +0200, Karl Heinz Marbaise
Github user mkrizmanic commented on the issue:
https://github.com/apache/maven-integration-testing/pull/21
already merged
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
I need to work an the plexus-java performance issue and also think of a
way to preserve the extra JPMS arguments used during compilation so they
can be available at runtime as well (= MCOMPILER-296).
As far as I know these are the final open issues required to have a
complete Java 9
Github user mkrizmanic closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/21
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Hi Robert,
I've taken a the liberaty to create INFRA[1] ticket which seemed be
already working on...
Kind regards
Karl Heinz Marbaise
[1]: https://issues.apache.org/jira/browse/INFRA-14878
On 15/08/17 22:10, Robert Scholte wrote:
Hi Karl Heinz,
I think it makes sense to have these
Hi Gary,
as Robert already pointed out Maven can run fine on JDK 9...for a very
long time..
I'm working on support for jlink, jmod to support creation of run time
images with Maven simple (currently in its alpha states if this is
appropriate) ...which can be looked at the currenty example
Hi dev,
In ASF/Maven we have this build [1] which uses Jenkinsfile and Pipeline.
Compiling the project fails with error [2].
Do you know what we are doing wrong and how to fix it?
[1]:
https://builds.apache.org/view/M-R/view/Maven/job/maven-surefire-pipeline/job/master/57/console
[2]:
[ERROR]
Hi Robert,
would you think we should do another release for maven-compiler-plugin ?
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
No I updated Jenkinsfile [1] and the result is better but still strange
with this error:
/bin/sh: 1: /bin/java: not found
[1]:
https://github.com/apache/maven-surefire/commit/5f70c371c6be09d5599b713490d9d1a77b3f809f
On Wed, Aug 16, 2017 at 12:16 AM, Tibor Digana
Hi Enrico,
It does not appear on console output however it is stored as native std/out
in target/surefire-reports/2017-08-13T23-52-13_184.dumpstream
On Tue, Aug 15, 2017 at 5:51 PM, Enrico Olivelli [via Maven] <
ml+s40175n5912520...@n5.nabble.com> wrote:
> Il dom 13 ago 2017, 17:31 Tibor Digana
Ok guys, I am glad too that you are satisfied, so I will push the branch to
master, and thank you very much for working with me.
Enrico, I know that you are on vacation right now but I would like to
kindly ask you to join us on IRC channel, maybe after your vacation.
Thx.
On Tue, Aug 15, 2017 at
Il mar 15 ago 2017, 14:25 Tibor Digana ha
scritto:
> Ok guys, I am glad too that you are satisfied, so I will push the branch to
> master, and thank you very much for working with me.
> Enrico, I know that you are on vacation right now but I would like to
> kindly
+1 for me
I have checked out branch SUREFIRE-1403 and I was able to run tests of an
application which uses java.sql.Timestamp without changes in code, just but
upgrading surefire to 21.1-SNAPSHOT
Unfortunately I do not use the failsafe plugin so I have to real world
project to test
I did a brief
20 matches
Mail list logo