BestSolution-at / e4-efxclipse-maven-sample

Sample using pure maven for e4 application
5 stars 9 forks source link

Unable to build example with Java 11 #13

Closed MarceloRuiz closed 4 years ago

MarceloRuiz commented 4 years ago

Hi, I am trying to run the example with Java 11 but I can't make it work. Even after updating the example's version for the artifact 'at.bestsolution.efxclipse.rt.release' from '3.5.0-SNAPSHOT' to '3.6.0' I cannot run the program:

mvn -f launch/pom.xml test -P netbeans WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [INFO] [INFO] -------------------------< sample.mvn:launch >-------------------------- [INFO] Building launch 0.0.1-SNAPSHOT [INFO] --------------------------------[ jar ]--------------------------------- [WARNING] The POM for sample.mvn:sample.mvn.feature:jar:0.0.1-SNAPSHOT is missing, no dependency information available [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.353 s [INFO] Finished at: 2020-04-13T17:33:17-04:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project launch: Could not resolve dependencies for project sample.mvn:launch:jar:0.0.1-SNAPSHOT: Failure to find sample.mvn:sample.mvn.feature:jar:0.0.1-SNAPSHOT in http://maven.bestsolution.at/efxclipse-releases/ was cached in the local repository, resolution will not be reattempted until the update interval of efxclipse-releases has elapsed or updates are forced -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException There is no 3.7.0-SNAPSHOT in the repository to try with that version (but I don't know if that will solve the problem). Any ideas on how to make this work? Thanks!

tomsontom commented 4 years ago

what maven version are you running that on?

MarceloRuiz commented 4 years ago

Hi Tom, Thanks again for your help. Here is the info: mvn --version Apache Maven 3.6.0 Maven home: /usr/share/maven Java version: 13.0.2, vendor: AdoptOpenJDK, runtime: /usr/lib/jvm/adoptopenjdk-13-openj9-amd64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.4.28-050428-generic", arch: "amd64", family: "unix"

tomsontom commented 4 years ago

IIRC Maven 3.6.0 and tycho don't like each other please use maven 3.5.x or better upgrade to maven 3.6.3

MarceloRuiz commented 4 years ago

I still have the same problem:

mvn --version Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /opt/maven Java version: 13.0.2, vendor: AdoptOpenJDK, runtime: /usr/lib/jvm/adoptopenjdk-13-openj9-amd64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.4.28-050428-generic", arch: "amd64", family: "unix"

` mvn -f launch/pom.xml test -P netbeans

[INFO] Scanning for projects... [INFO] [INFO] -------------------------< sample.mvn:launch >-------------------------- [INFO] Building launch 0.0.1-SNAPSHOT [INFO] --------------------------------[ jar ]--------------------------------- [WARNING] The POM for sample.mvn:sample.mvn.feature:jar:0.0.1-SNAPSHOT is missing, no dependency information available [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.418 s [INFO] Finished at: 2020-04-14T16:52:31-04:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project launch: Could not resolve dependencies for project sample.mvn:launch:jar:0.0.1-SNAPSHOT: Failure to find sample.mvn:sample.mvn.feature:jar:0.0.1-SNAPSHOT in http://maven.bestsolution.at/efxclipse-releases/ was cached in the local repository, resolution will not be reattempted until the update interval of efxclipse-releases has elapsed or updates are forced -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException`

tomsontom commented 4 years ago

hm i think the Readme.md is wrong. You first need to run mvn clean install followed by mvn -f launch/pom.xml test -Pnetbeans - looking at the change history the modifications have been contributed by @FlorianKirmaier

MarceloRuiz commented 4 years ago

Well, I guess it was both things, because with maven 3.6.0 installed I kept getting the same error. Now that I tried with 3.6.3 it works from the command line. When trying to run it from Eclipse with the MVN OSGi Launcher, I get a NullPointerException but nothing more than that:

An internal error occurred during: "Launching Sample". java.lang.NullPointerException Edit: After opening the dependent projects, all of them have an error marked in their pom.xml files:

Plugin execution not covered by lifecycle configuration: biz.aQute.bnd:bnd-maven-plugin:3.4.0:bnd-process (execution: default-bnd-process, phase: process-classes)

MarceloRuiz commented 4 years ago

Could this problem be related to this: https://github.com/bndtools/bnd/issues/2904 ?

MarceloRuiz commented 4 years ago

I am getting closer. I decided to start from scratch (even uninstalled eclipse). After cloning the project, installing the maven dependencies and running maven clean install, I can run the program from eclipse by executing the 'Sample' run configuration.

If I modify anything, llike adding the following to the parent pom's properties section: <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> then saving, updating the maven project and refreshing the project, when I try to run the project again by executing the 'Sample' run configuration I get the following error:

!SESSION 2020-04-15 19:31:27.177 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=11.0.6+10
JRE 11 Linux amd64-64-Bit Compressed References 20200122_441 (JIT enabled, AOT enabled)
OpenJ9   - 51a5857d2
OMR      - 7a1b0239a
JCL      - da35e0c380 based on jdk-11.0.6+10
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -product sample.mvn.app.product -clearPersistedState
Command-line arguments:  -console -consoleLog -product sample.mvn.app.product -clearPersistedState -clean

!ENTRY org.eclipse.equinox.app 0 0 2020-04-15 19:31:28.963
!MESSAGE Product sample.mvn.app.product could not be found.

!ENTRY openjfx.graphics.win32_64 2 0 2020-04-15 19:31:29.140
!MESSAGE Could not resolve module: openjfx.graphics.win32_64 [33]
  Unresolved requirement: Require-Capability: eclipse.platform; filter:="(& (osgi.os=win32) (osgi.arch=x86_64) )"

!ENTRY org.eclipse.fx.osgi 2 0 2020-04-15 19:31:29.141
!MESSAGE Could not resolve module: org.eclipse.fx.osgi [67]
  Unresolved requirement: Fragment-Host: org.eclipse.osgi; bundle-version="3.10.0"

!ENTRY org.osgi.service.component.annotations 2 0 2020-04-15 19:31:29.142
!MESSAGE Could not resolve module: org.osgi.service.component.annotations [55]
  Unresolved requirement: Require-Capability: osgi.compile.time.only; filter:="(&(must.not.resolve=*)(!(must.not.resolve=*)))"

!ENTRY openjfx.graphics.mac 2 0 2020-04-15 19:31:29.142
!MESSAGE Could not resolve module: openjfx.graphics.mac [70]
  Unresolved requirement: Require-Capability: eclipse.platform; filter:="(& (osgi.os=macosx) (osgi.arch=x86_64) )"

!ENTRY org.eclipse.osgi 4 0 2020-04-15 19:31:29.142
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: No application id has been found.
    at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:245)
    at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:32)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1474)
osgi> An error has occurred. See the log file
/tmp/launch/configuration/1586993487349.log.

Of course the log file doesn't give me any more information that the console output.

Maybe this is the reason I have been hitting my head against the wall so many times trying to run the app from Eclipse.

By the way, it always runs fine from the command line (even after editing a file) when I use:

mvn -f launch/pom.xml test -Pnetbeans

What is going on inside Eclipse? Shouldn't be editing a single file a relative painless process? Am I missing anything? Thanks!

tomsontom commented 4 years ago

To run from inside Eclipse you don't have to do a mvn clean install. On the resolve errors:

So we are left with the org.eclipse.fx.osgi which is not good as it says it can not find the osgi-framework. I'll see if I can find the time to run that stuff myself.

tomsontom commented 4 years ago

I just tried it myself and it works perfectly fine for me - I'm on Eclipse "2019-12" but I doubt this makes a difference

MarceloRuiz commented 4 years ago

Hi Tom, Thanks for taking the time to look into this. It is driving me insane. I have two specific questions for you:

MarceloRuiz commented 4 years ago

Hi again Tom. I don't know why this keeps happening to me. It is always a new error and they happen randomly. Sometimes the build is fine, sometimes it fails. Now it is failing again from the command line:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for sample.mvn.parent 0.0.1-SNAPSHOT:
[INFO] 
[INFO] sample.mvn.parent .................................. SUCCESS [  0.649 s]
[INFO] sample.mvn.lib ..................................... SUCCESS [  2.716 s]
[INFO] sample.mvn.app ..................................... SUCCESS [  2.402 s]
[INFO] sample.mvn.feature ................................. FAILURE [  0.007 s]
[INFO] sample.mvn.product ................................. SKIPPED
[INFO] launch ............................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  12.206 s
[INFO] Finished at: 2020-04-16T19:48:46-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin at.bestsolution:maven-osgi-package-plugin:0.0.2-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact at.bestsolution:maven-osgi-package-plugin:jar:0.0.2-SNAPSHOT -> [Help 1]
org.apache.maven.plugin.PluginResolutionException: Plugin at.bestsolution:maven-osgi-package-plugin:0.0.2-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact at.bestsolution:maven-osgi-package-plugin:jar:0.0.2-SNAPSHOT
    at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve (DefaultPluginDependenciesResolver.java:131)
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor (DefaultMavenPluginManager.java:182)
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor (DefaultMavenPluginManager.java:286)
    at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor (DefaultBuildPluginManager.java:244)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleMappingDelegate.calculateLifecycleMappings (DefaultLifecycleMappingDelegate.java:116)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings (DefaultLifecycleExecutionPlanCalculator.java:265)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions (DefaultLifecycleExecutionPlanCalculator.java:217)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:126)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:144)
    at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan (BuilderCommon.java:97)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:111)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:567)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact at.bestsolution:maven-osgi-package-plugin:jar:0.0.2-SNAPSHOT
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:424)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact (DefaultArtifactResolver.java:207)
    at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact (DefaultRepositorySystem.java:262)
    at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve (DefaultPluginDependenciesResolver.java:127)
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor (DefaultMavenPluginManager.java:182)
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor (DefaultMavenPluginManager.java:286)
    at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor (DefaultBuildPluginManager.java:244)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleMappingDelegate.calculateLifecycleMappings (DefaultLifecycleMappingDelegate.java:116)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings (DefaultLifecycleExecutionPlanCalculator.java:265)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions (DefaultLifecycleExecutionPlanCalculator.java:217)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:126)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:144)
    at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan (BuilderCommon.java:97)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:111)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:567)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact at.bestsolution:maven-osgi-package-plugin:jar:0.0.2-SNAPSHOT
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:414)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:229)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact (DefaultArtifactResolver.java:207)
    at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact (DefaultRepositorySystem.java:262)
    at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve (DefaultPluginDependenciesResolver.java:127)
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor (DefaultMavenPluginManager.java:182)
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor (DefaultMavenPluginManager.java:286)
    at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor (DefaultBuildPluginManager.java:244)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleMappingDelegate.calculateLifecycleMappings (DefaultLifecycleMappingDelegate.java:116)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings (DefaultLifecycleExecutionPlanCalculator.java:265)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions (DefaultLifecycleExecutionPlanCalculator.java:217)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:126)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:144)
    at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan (BuilderCommon.java:97)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:111)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:567)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR] 
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

The worst part is that I see the artifacts in your repository. I even deleted the local maven cache, but still no luck.

tomsontom commented 4 years ago

does that still happen?

MarceloRuiz commented 4 years ago

This is not happening anymore... I will close it for now and reopen it if does.