8000 maven 2 compile error: Unable to locate surefire-booter in the list of plugin artifacts · Issue #326 · ClearTK/cleartk · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

maven 2 compile error: Unable to locate surefire-booter in the list of plugin artifacts #326

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.

Sign up for GitHub

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

Jump to bottom
Open
bethard opened this issue Apr 14, 2015 · 4 comments
Open

maven 2 compile error: Unable to locate surefire-booter in the list of plugin artifacts #326

bethard opened this issue Apr 14, 2015 · 4 comments
Labels
🐛 Bug Something isn't working Priority-Medium
Milestone
🐛 Bug backlog

Comments

@bethard
Copy link
Contributor
bethard commented Apr 14, 2015

Original issue 328 created by ClearTK on 2012-08-14T19:17:48.000Z:

Using code checked out from head of tree, and running mvn compile and/or mvn compile package with maven 2 is yielding compile errors. With maven 3, everything compiles without issue.

For mvn compile package, the error message complains about the surefire-booter plugin:
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to locate surefire-booter in the list of plugin artifacts
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.RuntimeException: Unable to locate surefire-booter in the list of plugin artifacts
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.getForkConfiguration(AbstractSurefireMojo.java:1152)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:655)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:647)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:606)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:569)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

For mvn compile, the error reads:

[INFO] [consistent-versions:check-version-consistency {execution: default}]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO]
Found multiple versions of commons-io:commons-io:jar:
commons-io:commons-io:jar:2.0.1 in de.tudarmstadt.ukp.dkpro.core:de.tudarmstadt.ukp.dkpro.core.api.resources-asl:jar:1.3.0 -> org.cleartk:cleartk-ml-crfsuite:jar:0.2.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-test-util:jar:1.2.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-stanford-corenlp:jar:0.7.0-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-ml:jar:1.2.0 -> org.cleartk:cleartk-ml-mallet:jar:1.2.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-named-entity:jar:0.6.3-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-semantic-roles:jar:0.6.2-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-ml:jar:1.2.0 -> org.cleartk:cleartk-ml-tksvmlight:jar:0.4.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-opennlp-tools:jar:0.10.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-examples:jar:0.6.2-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-ml:jar:1.2.0 -> org.cleartk:cleartk-ml-weka:jar:0.1.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-snowball:jar:0.9.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-timeml:jar:1.0.2-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-syntax:jar:0.6.2-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-maltparser:jar:0.8.0-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-eval:jar:0.9.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-berkeleyparser:jar:0.2.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-ml:jar:1.2.0 -> org.cleartk:cleartk-ml-opennlp-maxent:jar:1.1.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-token:jar:0.8.4-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-ml:jar:1.2.0 -> org.cleartk:cleartk-ml-libsvm:jar:1.1.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-ml:jar:1.2.0 -> org.cleartk:cleartk-ml-svmlight:jar:1.1.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-ml:jar:1.2.1-SNAPSHOT
commons-io:commons-io:jar:2.4 in org.cleartk:cleartk-util:jar:0.9.0 -> org.cleartk:cleartk-clearparser:jar:0.7.1-SNAPSHOT

I thought that this was somehow related to this question on stackoverflow
http://stackoverflow.com/questions/11793200/maven-failsafe-plugin-fails-with-unable-to-locate-surefire-booter
but changing the changing the maven-surefire-plugin version down to 2.12 didn't change anything.
@bethard
Copy link
Contributor Author
bethard commented Apr 14, 2015

Comment #1 originally posted by ClearTK on 2012-08-14T19:31:34.000Z:

The "mvn compile" error actually looks like a correct error message - cleartk-ml-crfsuite depends on dkpro which depends on commons-io:2.0.1, while the rest of our code depends on commons-io:2.4. Not sure why this isn't being caught in Maven 3. Probably we should be manually excluding the dkpro dependency on commons-io to force the use of 2.4 everywhere. Don't know whether that fixes the "mvn compile package" error though.

All that said, I don't care much about supporting Maven 2 as a build system. Everyone should be using Maven 3. (I do care that people can use the ClearTK jars from Maven 2, but I don't care if they can build ClearTK from source with Maven 2.)

@bethard
Copy link
Contributor Author
bethard commented Apr 14, 2015

Comment #2 originally posted by ClearTK on 2013-03-28T13:34:13.000Z:

<empty>

@bethard
Copy link
Contributor Author
bethard commented Apr 14, 2015

Comment #3 originally posted by ClearTK on 2013-05-03T08:44:33.000Z:

<empty>

@bethard
Copy link
Contributor Author
bethard commented Apr 14, 2015

Comment #4 originally posted by ClearTK on 2014-03-15T17:41:52.000Z:

<empty>

@bethard bethard modified the milestone: 2.2 Apr 16, 2015
@reckart reckart modified the milestones: 3.0.0, ⭐️ Feature backlog Nov 4, 2022
@reckart reckart added 🐛 Bug Something isn't working and removed Type-Defect labels Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐛 Bug Something isn't working Priority-Medium
Projects
None yet
Milestone
🐛 Bug backlog
Development

No branches or pull requests
2 participants
@bethard @reckart
0