CDV ❯ maven 1.1.0-SNAPSHOT plugin fails to start

• Type: Bug
• Status: Closed
• Priority: 2 Major
• Resolution: Cannot Reproduce
• Component/s:
• Labels:

• Assignee: amiller
• Reporter: tgautier
• Created: April 24, 2008
• Votes: 0
• Watchers: 0
• Updated:

  July 27, 2012
• Resolved:

  April 24, 2008

Attachments

• tgautier (30.00 k) application/x-gzip tim-framework.tgz

Description

2008-04-24 06:46:24,481 INFO - Configuration loaded from the file at ‘/Users/tgautier/src/forge/projects/labs/tim-framework/trunk/samples/spider/tc-config.xml’. [INFO] Resolving modules: [] [INFO] ———————————————————————— [ERROR] FATAL ERROR [INFO] ———————————————————————— [INFO] com.tc.bundles.Resolver.([Ljava/net/URL;)V [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.NoSuchMethodError: com.tc.bundles.Resolver.([Ljava/net/URL;)V at org.terracotta.maven.plugins.tc.AbstractDsoMojo$MavenResolver.(AbstractDsoMojo.java:833) at org.terracotta.maven.plugins.tc.AbstractDsoMojo.resolveModuleArtifacts(AbstractDsoMojo.java:521) at org.terracotta.maven.plugins.tc.BootjarMojo.execute(BootjarMojo.java:59) at org.terracotta.maven.plugins.tc.DsoLifecycleMojo.execute(DsoLifecycleMojo.java:61) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) 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:585) 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)

Comments

Taylor Gautier 2008-04-24

To repro:

untar attached project

$ cd tim-framework/trunk $ mvn install $ cd samples/spider $ mvn tc:start

Alex Miller 2008-04-24

I can’t reproduce this locally but it will depend on what’s in your repo (mine was recently wiped so I have very little old stuff).

When I build the project though I see that it is downloading tc 2.5.2 stuff. The main pom.xml uses tim-parent 1.0.5 which uses tc-maven-plugin 1.0.5 which depends on tc 2.5.2.

However, your spider sample uses the latest tc-maven-plugin 1.1.0-SNAPSHOT which depends on 2.6.0-SNAPSHOT.

The constructor for Resolver has changed in 2.6.0 and there is a subclass of it in tc-maven-plugin, so you must be seeing a mismatch between the two, possibly based on an old snapshot in your repo?

Alex Miller 2008-04-24

Closing as not repro per Taylor