How to install shaded fat/uber JAR with dependency-reduced POM

2020-06-30 Thread Alexander Kriegisch 
Situation (sorry for maybe explaining too much):

  -- I have a multi-module project with an aggregator POM which is also
 the parent for all dependent modules.
  -- The modules implement different byte code transformation features.
  -- In some modules I use Maven Shade in order build fat JARs which can
 be used as Java agents.
  -- Those Java agents add themselves to the bootstrap class path during
 start-up, utilising the "Boot-Class-Path" manifest entry. For that
 purpose, it is imperative that the Java agents are fat JARs because
 their dependencies also need to be on the bootstrap class path,
 because the byte code transformations can also target other
 bootstrap classes. This works very well, I have no issues with
 that.
  -- Besides, I also build compound source JARs for the shaded JARs,
 which also works nicely.
  -- For each JAR I also build a variant with third-party classes
 relocated to my own package name space, in case the user happens to
 use the same dependencies and has problems due to API changes which
 cannot be reconciled by dependency version management. Also here, I
 build compound source files with relocated source packages. This
 also works nicely.

Problems description:

I want users to be able to depend on the shaded agent JARs without
pulling other dependencies into their projects because the agent JARs
already contain all classes necessary to run them.

But if I declare the dependencies as optional in the module using Maven
Shade, dependent modules in my own project (e.g. integration test
modules) no longer compile in IntelliJ IDEA. This is not a Maven
problem, but still something I need to avoid for the sake of being able
to use my IDE.

As an alternative, I can urge the user to use something like this:

  
xxx
yyy

  
*
*
  

  

This is not nice and I do not wish to burden my users with that.

What I am currently doing is to use something like this in each module
building shaded JARs:

  
org.codehaus.mojo
flatten-maven-plugin
1.2.2

  
  
flatten
process-resources

  flatten


  oss
  
remove
  
  ${project.build.directory}
  flattened-pom.xml

  

  

This has the effect of creating a POM similar to the dependency-reduced
POM created by Maven Shade and installing it together with the uber JAR
artifact. Now the dependency graph looks "clean" to users of my
libraries. I know it is not the Maven way of managin dependencies, but
uber JARs with shaded dependencies exist in the real world and I
explained at the beginning how/why they are useful in my case.

BTW, IntelliJ IDEA still adds all dependencies to the classpath and
excludes the uber JAR, trying to be smarter than Maven itself but
getting it wrong. But that is not your problem, I can deal with that and
provide the path to the uber JAR in another way to my integration tests.
The most important thing is that Maven and IDEA do not see the
dependencies when using the uber JARs from other project outside of my
own multi-module project.

Questions:

  1. Is there any more canonical way of doing what I did, i.e. directly
 using the dependency-reduced POM generated by Maven Shade in order
 to replace the original JAR when installing my artifact? Then I
 could get rid of the Flatten plugin (which also removes other stuff
 and even empty lines from my POMs, making them look horrible) and
 just use Shade.

  2. Can I achieve a similar result in a better way altogether?

  3. Does anyone even happen to know a way to make this work within my
 multi-module project in connection with building and running tests
 with IntelliJ IDEA? BTW, I also experimented with attaching the
 shaded JARs to the original artifact with special classifiers. This
 again works with Maven, but not in IDEA.

Sorry for the lengthy post, thanks for bearing with me. I really wonder
if I am the only one having this kind of problem because I found nothing
useful on StackOverflow or doing a global web search. Maybe I did not
use the right search terms.

-- 
Alexander Kriegisch
https://scrum-master.de

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: 'mvn clean test' crashes

2020-06-30 Thread Enrico Olivelli 
Can you try to run one test at a time and see which test is crashing your
build?

Use
mvn test -Dtest=NameOfTheTestClass


Enrico

Il Mer 1 Lug 2020, 07:37 Mukul Gandhi  ha scritto:

> Hi Enrico,
>
> On Wed, Jul 1, 2020 at 10:47 AM Enrico Olivelli 
> wrote:
>
>
> > Are you walking System.exit or System.halt in your tests?
> >
>
> I'm not using either of System.exit or System.halt within my tests code.
> I'm also neither, using these two statements within my business logic code.
>
>
>
> --
> Regards,
> Mukul Gandhi
>

Re: 'mvn clean test' crashes

2020-06-30 Thread Mukul Gandhi 
Hi Bernd,

On Wed, Jul 1, 2020 at 10:50 AM Bernd Eckenfels 
wrote:

> Anything in the mentioned dump files?


When my command, 'mvn clean test' finishes (with an error that I mentioned
earlier), there are no file(s) with name *.dump* created on my workstation
(I'm looking, within my Maven project folder tree).


> Could be a environment variable problem or corrupted Java Home (less
> likely a problem in the test code).
>

I'm not sure, how to debug as per these aspects.

You can also try to specify -DskipTests to see if the rest of the Maven
> build works.
>

The command 'mvn clean package -DskipTests' results in successful build for
me.




-- 
Regards,
Mukul Gandhi

Re: 'mvn clean test' crashes

2020-06-30 Thread Mukul Gandhi 
Hi Enrico,

On Wed, Jul 1, 2020 at 10:47 AM Enrico Olivelli  wrote:


> Are you walking System.exit or System.halt in your tests?
>

I'm not using either of System.exit or System.halt within my tests code.
I'm also neither, using these two statements within my business logic code.



-- 
Regards,
Mukul Gandhi

Re: org.codehaus.mojo > mojohaus.org

2020-06-30 Thread Hervé BOUTEMY 
Le mardi 30 juin 2020, 15:27:37 CEST Charles Herrick a écrit :
> Thanks Greg, those urls do indeed resolve.
> 
> We are left with urls in the Maven online documentation that still have the
> old org.codehaus.mojo forms that do NOT resolve.
 
> Do we have a plan to edit these links in the documentation?
please point us to the pages containing the old links so we can fix what has 
not yet been fixed

Regards,

Hervé

> 
> e: charles.herr...@perficient.com
> t: Texas Time
> --
> Charles Herrick,  Technical Architect
> m: 512-289-0926 | NASDAQ: PRFT | Perficient.com
> 
> 
> -Original Message-
> From: Greg Chabala  
> Sent: Monday, June 29, 2020 5:25 PM
> To: Maven Users List 
> Subject: Re: org.codehaus.mojo > mojohaus.org
> 
> Never used it myself, but these might help:
> 
> https://linkcheck.perficient.com/?url=https%3A%2F%2Fsearch.maven.org%2Fsearc
> h%3Fq%3Dg%3Aorg.codehaus.mojo%2520a%3Aanimal-sniffer&id=1295&rcpt=charles.he
> rrick%40perficient.com&tss=1593469532&msgid=7119cc9d-ba57-11ea-b7ff-9914abf9
> d899&h=ffac72ad *
 
> https://linkcheck.perficient.com/?url=https%3A%2F%2Fwww.mojohaus.org%2Fanima
> l-sniffer%2Fanimal-sniffer-maven-plugin%2F&id=1295&rcpt=charles.herrick%40pe
> rficient.com&tss=1593469532&msgid=7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=03d
> 99ae5 
 
> https://linkcheck.perficient.com/?url=https%3A%2F%2Fgithub.com%2Fmojohaus%2F
> animal-sniffer&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&
> msgid=7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=340b712f 
 
> Cheers,
> Greg Chabala
> 
> On Mon, Jun 29, 2020 at 4:54 PM Charles Herrick <
> charles.herr...@perficient.com> wrote:
 
> 
> > Links still have the old org.codehaus.mojo form URL and thus are not 
> > reachable. I’m looking for the latest Animal Sniffer to plug into my
> > Maven+Eclipse.
> >
> >
> >
> >
> >
> > Am I missing something?
> >
> >
> >
> >
> >
> > Thanks,
> >
> >
> >
> > e: charles.herr...@perficient.com
> >
> >
> >
> > t: Texas Time
> >
> >
> >
> > --
> >
> >
> >
> > *Charles Herrick*,  Technical Architect
> >
> >
> >
> > m: 512-289-0926 | NASDAQ: PRFT | *Perficient.com
> >  > %2F&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msgid
> > =7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=08d4d972 >*
> >
> >
> >
> >
> >
> > [image: Logo Icon] 
> >  > %2F&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msgid
> > =7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=08d4d972 >
> >
> >
> >
> >
> >
> > [image: LinkedIn Icon]
> >  > ompany%2F165444&id=1295&rcpt=charles.herrick%40perficient.com&tss=15934695
> > 32&msgid=7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=56801d87 >   [image:
> > Twitter Icon]
> >  > ient&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msgid=71
> > 19cc9d-ba57-11ea-b7ff-9914abf9d899&h=a09f1b35 >  ​[image: Blog Icon]
> >  > 2F&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msgid=7119
> > cc9d-ba57-11ea-b7ff-9914abf9d899&h=b796ccbf >   [image: Facebook Icon]
> >  > erficient&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msg
> > id=7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=83999dcb >   [image: YouTube
> > Icon]
> >  > Fchannel%2FUCRUC3AbkGIH4Wud_PgKovug%2F&id=1295&rcpt=charles.herrick%40
> > perficient.com&tss=1593469532&msgid=7119cc9d-ba57-11ea-b7ff-9914abf9d8
> > 99&h=96bf08dd >
> >
> >
> >
> >





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: 'mvn clean test' crashes

2020-06-30 Thread Bernd Eckenfels 
Anything in the mentioned dump files? Could be a environment variable problem 
or corrupted Java Home (less likely a problem in the test code).

You can also try to specify -DskipTests to see if the rest of the Maven build 
works.

Gruss
Bernd


--
http://bernd.eckenfels.net

Von: Mukul Gandhi 
Gesendet: Wednesday, July 1, 2020 7:08:50 AM
An: users@maven.apache.org 
Betreff: 'mvn clean test' crashes

Hi all,
I've been facing some problem during last few weeks, when using the
'mvn clean test' command to run unit tests within my Maven project. At some
point before when this issue is creating problem for me, the 'mvn clean
test' command was working fine with me and all unit tests within my Maven
project were passing. But I'm yet unable to find the reason, why 'mvn clean
test' command is not working for me now.

When I run the command 'mvn clean test' now, my Maven build fails and
following error trace is emitted,

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time:  05:51 min
[INFO] Finished at: 2020-07-01T09:44:06+05:30
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test)
on project haldiram-restapis: There are test failures.
[ERROR]
[ERROR] Please refer to
F:\eclipseWorkspaces\haldiram_backend_sprint-19_sts\haldiram-backend\haldiram-restapis\target\surefire-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash
or System.exit called?
[ERROR] Command was cmd.exe /X /C "C:\jdk1.8.0_241\jre\bin\java -jar
C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817\surefirebooter5568422068326404815.jar
C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817
2020-07-01T09-38-42_797-jvmRun1 surefire5010876784124620015tmp
surefire_07470042422408053869tmp"
[ERROR] Process Exit Code: 0
[ERROR] Crashed tests:
[ERROR] com.haldiram.business.helper.test.ApplnHelperTest
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or
System.exit called?
[ERROR] Command was cmd.exe /X /C "C:\jdk1.8.0_241\jre\bin\java -jar
C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817\surefirebooter5568422068326404815.jar
C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817
2020-07-01T09-38-42_797-jvmRun1 surefire5010876784124620015tmp
surefire_07470042422408053869tmp"
[ERROR] Process Exit Code: 0
[ERROR] Crashed tests:
[ERROR] com.haldiram.business.helper.test.ApplnHelperTest
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
[ERROR] at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
[ERROR] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
[ERROR] at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[ERROR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeM

Re: 'mvn clean test' crashes

2020-06-30 Thread Enrico Olivelli 
Mukul
Are you walking System.exit or System.halt in your tests?


Enrico


Il Mer 1 Lug 2020, 07:09 Mukul Gandhi  ha scritto:

> Hi all,
> I've been facing some problem during last few weeks, when using the
> 'mvn clean test' command to run unit tests within my Maven project. At some
> point before when this issue is creating problem for me, the 'mvn clean
> test' command was working fine with me and all unit tests within my Maven
> project were passing. But I'm yet unable to find the reason, why 'mvn clean
> test' command is not working for me now.
>
> When I run the command 'mvn clean test' now, my Maven build fails and
> following error trace is emitted,
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  05:51 min
> [INFO] Finished at: 2020-07-01T09:44:06+05:30
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test)
> on project haldiram-restapis: There are test failures.
> [ERROR]
> [ERROR] Please refer to
>
> F:\eclipseWorkspaces\haldiram_backend_sprint-19_sts\haldiram-backend\haldiram-restapis\target\surefire-reports
> for the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump,
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash
> or System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\jdk1.8.0_241\jre\bin\java -jar
>
> C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817\surefirebooter5568422068326404815.jar
> C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817
> 2020-07-01T09-38-42_797-jvmRun1 surefire5010876784124620015tmp
> surefire_07470042422408053869tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] com.haldiram.business.helper.test.ApplnHelperTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\jdk1.8.0_241\jre\bin\java -jar
>
> C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817\surefirebooter5568422068326404815.jar
> C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817
> 2020-07-01T09-38-42_797-jvmRun1 surefire5010876784124620015tmp
> surefire_07470042422408053869tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] com.haldiram.business.helper.test.ApplnHelperTest
> [ERROR] at
>
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
> [ERROR] at
>
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
> [ERROR] at
>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [ERROR] at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
>
> sun.reflect.DelegatingMethodAccessorImpl.invo

'mvn clean test' crashes

2020-06-30 Thread Mukul Gandhi 
Hi all,
I've been facing some problem during last few weeks, when using the
'mvn clean test' command to run unit tests within my Maven project. At some
point before when this issue is creating problem for me, the 'mvn clean
test' command was working fine with me and all unit tests within my Maven
project were passing. But I'm yet unable to find the reason, why 'mvn clean
test' command is not working for me now.

When I run the command 'mvn clean test' now, my Maven build fails and
following error trace is emitted,

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time:  05:51 min
[INFO] Finished at: 2020-07-01T09:44:06+05:30
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test)
on project haldiram-restapis: There are test failures.
[ERROR]
[ERROR] Please refer to
F:\eclipseWorkspaces\haldiram_backend_sprint-19_sts\haldiram-backend\haldiram-restapis\target\surefire-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash
or System.exit called?
[ERROR] Command was cmd.exe /X /C "C:\jdk1.8.0_241\jre\bin\java -jar
C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817\surefirebooter5568422068326404815.jar
C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817
2020-07-01T09-38-42_797-jvmRun1 surefire5010876784124620015tmp
surefire_07470042422408053869tmp"
[ERROR] Process Exit Code: 0
[ERROR] Crashed tests:
[ERROR] com.haldiram.business.helper.test.ApplnHelperTest
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or
System.exit called?
[ERROR] Command was cmd.exe /X /C "C:\jdk1.8.0_241\jre\bin\java -jar
C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817\surefirebooter5568422068326404815.jar
C:\Users\mukul\AppData\Local\Temp\surefire7064994840408638817
2020-07-01T09-38-42_797-jvmRun1 surefire5010876784124620015tmp
surefire_07470042422408053869tmp"
[ERROR] Process Exit Code: 0
[ERROR] Crashed tests:
[ERROR] com.haldiram.business.helper.test.ApplnHelperTest
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
[ERROR] at
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
[ERROR] at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
[ERROR] at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
[ERROR] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
[ERROR] at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[ERROR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
[ERROR] at
org.codehaus.plexus

RE: org.codehaus.mojo > mojohaus.org

2020-06-30 Thread Charles Herrick 
Thanks Greg, those urls do indeed resolve.

We are left with urls in the Maven online documentation that still have the old 
org.codehaus.mojo forms that do NOT resolve.

Do we have a plan to edit these links in the documentation?

e: charles.herr...@perficient.com
t: Texas Time
--
Charles Herrick,  Technical Architect
m: 512-289-0926 | NASDAQ: PRFT | Perficient.com


-Original Message-
From: Greg Chabala  
Sent: Monday, June 29, 2020 5:25 PM
To: Maven Users List 
Subject: Re: org.codehaus.mojo > mojohaus.org

Never used it myself, but these might help:

https://linkcheck.perficient.com/?url=https%3A%2F%2Fsearch.maven.org%2Fsearch%3Fq%3Dg%3Aorg.codehaus.mojo%2520a%3Aanimal-sniffer&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msgid=7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=ffac72ad
 *

https://linkcheck.perficient.com/?url=https%3A%2F%2Fwww.mojohaus.org%2Fanimal-sniffer%2Fanimal-sniffer-maven-plugin%2F&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msgid=7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=03d99ae5
 

https://linkcheck.perficient.com/?url=https%3A%2F%2Fgithub.com%2Fmojohaus%2Fanimal-sniffer&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msgid=7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=340b712f
 

Cheers,
Greg Chabala

On Mon, Jun 29, 2020 at 4:54 PM Charles Herrick < 
charles.herr...@perficient.com> wrote:

> Links still have the old org.codehaus.mojo form URL and thus are not 
> reachable. I’m looking for the latest Animal Sniffer to plug into my
> Maven+Eclipse.
>
>
>
> Am I missing something?
>
>
>
> Thanks,
>
> e: charles.herr...@perficient.com
>
> t: Texas Time
>
> --
>
> *Charles Herrick*,  Technical Architect
>
> m: 512-289-0926 | NASDAQ: PRFT | *Perficient.com
>  %2F&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msgid
> =7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=08d4d972 >*
>
>
>
> [image: Logo Icon] 
>  %2F&id=1295&rcpt=charles.herrick%40perficient.com&tss=1593469532&msgid
> =7119cc9d-ba57-11ea-b7ff-9914abf9d899&h=08d4d972 >
>
>
>
> [image: LinkedIn Icon] 
>   >   [image:
> Twitter Icon] 
>   >  ​[image: Blog Icon]
>   >   [image: Facebook Icon]
>   >   [image: YouTube Icon]
>  Fchannel%2FUCRUC3AbkGIH4Wud_PgKovug%2F&id=1295&rcpt=charles.herrick%40
> perficient.com&tss=1593469532&msgid=7119cc9d-ba57-11ea-b7ff-9914abf9d8
> 99&h=96bf08dd >
>
>
>

Re: (Negative) impact of Jansi

2020-06-30 Thread Tibor Digana 
>> we started seeing Surefire JVM fork crashes on various Windows 10
workstations when Jansi was active

Can you show me the log how it crashed, and maybe the dump file from
target/surefire-reports?

On Sun, Jun 28, 2020 at 7:29 PM Falko Modler  wrote:

> Hi everyone!
>
> I recently ran into problems when trying to get colored log output from
> Quarkus tests (via Surefire):
> https://github.com/fusesource/jansi/issues/171
>
> Coincidentally, we started seeing Surefire JVM fork crashes on various
> Windows 10 workstations when Jansi was active (sorry, I do not have more
> details at the moment).
>
> I also found out that building Quarkus (651 modules) is 40% faster with
> -Djansi.passthrough=true (using Git Bash on Windows 10 & TERM=cygwin,
> and I guess also with xterm-256color).
>
> Given these three observations, I am wondering whether it would be
> better if Maven actively used -Djansi.passthrough=true for TERM variants
> that are known to handle coloring on their own?
> Or at least document this?
>
> Best regards,
>
> Falko
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>