Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

following getting-started-guide, hitting NoClassDefFoundError: org/jboss/logging/Logger #541

Closed
jmtd opened this issue Jan 16, 2019 · 9 comments
Labels
triage/invalid This doesn't seem right

Comments

@jmtd
Copy link
Contributor

jmtd commented Jan 16, 2019

Possibly related to #516. Similar set up: manually created pom.xml and hello world stuff. mvn compile shamrock:dev results in

[INFO] 
[INFO] --------------------< org.acme:shamrock-quickstart >--------------------
[INFO] Building shamrock-quickstart 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ shamrock-quickstart ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory /home/ce/protean-hello/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ shamrock-quickstart ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- shamrock-maven-plugin:0.5.0:dev (default-cli) @ shamrock-quickstart ---
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger
	at org.jboss.shamrock.dev.DevModeMain.<clinit>(DevModeMain.java:40)
Caused by: java.lang.ClassNotFoundException: org.jboss.logging.Logger
	at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 1 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  10.781 s
[INFO] Finished at: 2019-01-16T16:17:34Z
[INFO] ------------------------------------------------------------------------

Two problems

  • it didn't work
  • it said it did (BUILD SUCCESS)

I've hit this in a RHEL 7.6 VM and a colleague has hit this on macOS, in both cases with Maven 3.6.0.

I'm building a fresh RHEL 7.6 VM so I have a totally clean environment to start over and document exactly the steps I followed (might also be able to share VM images of troublesome environments)

@gsmet
Copy link
Member

gsmet commented Jan 16, 2019

@cescoffier btw, why don't we use the shamrock-maven-plugin:create magic in the getting started guide?

It looks like it would be simpler and give a better introduction to our tools.

That doesn't prevent us from explaining in details the content of the created elements.

@cescoffier
Copy link
Member

cescoffier commented Jan 16, 2019 via email

@gsmet
Copy link
Member

gsmet commented Jan 16, 2019

@jmtd can you try with 0.6? I was able to follow the guide and create/access the REST resource with 0.6.

@markeastman
Copy link

Nor sure what the 0,6 refers to, but if it is the shamrock version I tried changing the pom to have 0.6.0 as the shamrock version and that has not improved anything. Build fails in the same way

@kenfinnigan
Copy link
Member

@markeastman, try 0.7.0, that's the latest

@jmtd
Copy link
Contributor Author

jmtd commented Feb 7, 2019

I'll leave this open until @markeastman can confirm it's fixed for him too, but I am not hitting this problem now, following the updated getting-started guide that uses org.jboss.shamrock:shamrock-maven-plugin:0.8.0:create

@jmtd
Copy link
Contributor Author

jmtd commented Feb 13, 2019

pretty sure this is addressed now

@jmtd jmtd closed this as completed Feb 13, 2019
@cescoffier cescoffier added triage/invalid This doesn't seem right and removed area/documentation labels Feb 14, 2019
@tandraschko
Copy link
Contributor

still hitting the same issue - doesnt matter if generated via the guide or using the getting-started example on github.

@dmlloyd
Copy link
Member

dmlloyd commented Mar 11, 2019

Make sure you're up to date and have #1391 included in your build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

7 participants