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

Compile error, missing class: AbstractScanner #9

Closed
SeanRMunoz opened this issue Apr 25, 2016 · 6 comments
Closed

Compile error, missing class: AbstractScanner #9

SeanRMunoz opened this issue Apr 25, 2016 · 6 comments

Comments

@SeanRMunoz
Copy link

SeanRMunoz commented Apr 25, 2016

Our project was building fine on 4/22/16, now we are getting the following compile error:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 'org.zeroturnaround:jrebel-maven-plugin:1.1.6-SNAPSHOT:generate': Unable to load the mojo 'org.zeroturnaround:jrebel-maven-plugin:1.1.6-SNAPSHOT:generate' in the plugin 'org.zeroturnaround:jrebel-maven-plugin'. A required class is missing: org/codehaus/plexus/util/AbstractScanner
org.codehaus.plexus.util.AbstractScanner

It appears to be a transitive dependency issue, where we're getting the wrong version of plexus-utils.

[DEBUG] Plugin dependencies for:

org.zeroturnaround:jrebel-maven-plugin:1.1.6-SNAPSHOT

are:

org.sonatype.plexus:plexus-build-api:jar:0.0.7:runtime
org.apache.maven:maven-plugin-api:jar:2.0.6:runtime
org.apache.maven:maven-project:jar:2.0.6:runtime
commons-io:commons-io:jar:1.4:runtime
commons-lang:commons-lang:jar:2.4:runtime
org.codehaus.plexus:plexus-utils:jar:1.1:runtime
...
[DEBUG]   commons-io:commons-io:jar:1.4:runtime (selected for runtime)
[DEBUG]   commons-lang:commons-lang:jar:2.4:runtime (selected for runtime)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.5.8:runtime (removed - nearer found: 1.1)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected for runtime)

Our work-around has been to add the following explicit dependency to this project's pom, build and re-deploy to our local snapshot repo:

    <dependency>
      <groupId>org.codehaus.plexus</groupId>
      <artifactId>plexus-utils</artifactId>
      <version>1.5.8</version>
    </dependency>
@SeanRMunoz SeanRMunoz changed the title Compile error, missing class: InterpolationException Compile error, missing class: AbstractScanner Apr 26, 2016
@sander347
Copy link

JIRA mirror: JR-5837

Hi Sean!

Thanks for the report! Our engineers are already having a look into this.

@SeanRMunoz
Copy link
Author

Great, thank you.

@daniel-anjos-zeroturnaround
Copy link
Contributor

Hi Sean, sorry for the delay - we have added the transitive dependency - could you try the latest SNAPSHOT? Thanks

@SeanRMunoz
Copy link
Author

SeanRMunoz commented May 3, 2016

Hi Daniel,

Just attempted building with your latest SNAPSHOT (jrebel-maven-plugin-1.1.6-20160503.125737-6) and was stopped with the following, which is new for us:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error resolving version for 'org.zeroturnaround:jrebel-maven-plugin': Plugin requires Maven version 3.0
[INFO] ------------------------------------------------------------------------

Unfortunately, our project is running Maven v2.2.1. Is this a new requirement of the jrebel plugin?

UPDATE: Well, I just read the commit history and answered my own question about Maven v3 now being a requirement.

updated minimal supported version of Maven up to 3.0

Thanks,
Sean

@daniel-anjos-zeroturnaround
Copy link
Contributor

Thanks for your feedback - I believe this issue #9 was partially caused by the changes required to fix issue #3 (some new dependencies required upgrade to Maven +3.0). I believe the best way to keep using JRebel in your Maven 2 project is to keep using the 1.1.5 release.

We are working to release version 1.1.6 soon with only minor features - fix for #3 and updating rebel.xml to be generated under resources folder and following the new version (2.1) of XSD, but those changes required to drop maven 2 support.

Let me know if that suits you and your team.
Best wishes,
Daniel

@SeanRMunoz
Copy link
Author

Thank you for your help and clarification, Daniel. I have backed us down to version 1.1.5 and all seems well for the moment. Not sure why we were using 1.1.6-SNAPSHOT to begin with? Once we've upgraded to Maven 3.0+, we'll try going back to 1.1.6.

Love using JRebel and can't imagine my work day without it. Keep up the great work!

Thanks,
Sean

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants