it actually just happened to me as well ... and I think I've isolated the scenario in which it happens
the context: migrating an existing ant-based project to be maven-based (using m2eclipse) my approach was: I have all the dependent libraries in a .../lib directory. for each dependency in lib, I find the same in the maven repository, add it to the pom, then delete it from lib. at some point, cglib-nodep-2.1_3.jar was in lib but no in the pom, and that's when I got the exact same trace, and it happens in the test-compile stage (goal?). (and yes, I'm using that library while testing) why it happens, I don't know, but maybe you can shed some light ;-) once I added cglib-nodep-2.1_3 to the pom (and removed it from lib), that problem disappeared, and I'm happy with that. but I still have a problem which relates to that, which is more general and I could use some help with it. please. pretty please. the general scenario is: if one has a library that is not in the maven repository, but is stored locally (under some lib directory), the m2eclipse and java builders seems to be happy and content, until we get to the testing stage. at that point running the tests via eclipse (Run As) succeeds, but running same test via m2 Maven(Run As) fails. without tracing it (don't know how), I postulate that it is because m2eclipse can not find those "special" libraries (they are not under its dependency graph). the specific scenario I have is using jboss-serialization.jar within an ObjectSerializer, and while running ObjectSerializerTest I get: ... Running mindsmiths.util.io.ObjectSerializerTest Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.047 sec <<< FAILURE! ... Results : Tests in error: ... simpleObjects(mindsmiths.util.io.ObjectSerializerTest) aggregateObjects(mindsmiths.util.io.ObjectSerializerTest) nestedAggregateObjects(mindsmiths.util.io.ObjectSerializerTest) nestedObjects(mindsmiths.util.io.ObjectSerializerTest) I understand that I can install any library in the local Maven repository using Maven directly, but that is not an acceptable solution, and I believe you can understand why. so, in general, I does one overcomes such obstacles in a transparent way? your advice would be appreciated. thanks, Benny On Dec 18, 2007 3:36 PM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > Baptiste, > > I personally haven't seen such error and it is hard to guess what it > could be without seeing the actual project. You can try to turn "Debug > Output" on from the Maven preferences and see if it will show more > detailed errors. > > If you have chance, can you please try to reproduce it on a smaller > scale and create a test project that we could use to reproduce this > issue? If so, please create a JIRA issue and attach it up there. See > some hints at the wiki page at > http://docs.codehaus.org/display/M2ECLIPSE/Home > > regards, > Eugene > > > [EMAIL PROTECTED] wrote: > > > > I have recently installed Eclipse Europa with the Maven 2 eclipse > plugin, > > > > I'm using the same workspace as with my previous IDE (Borland Together > > 2007) so I have the same projects (they compiled in Together). > > > > When I run the 'test-compile' target in Europa the following > > exceptions appear: > > > > [INFO] Scanning for projects... > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > [INFO] Building InfoMagic Platform Server Admin Model > > > > [INFO] task-segment: [test-compile] > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > [INFO] resources:resources > > > > [INFO] Using default encoding to copy filtered resources. > > > > [INFO] compiler:compile > > > > [INFO] Nothing to compile - all classes are up to date > > > > [INFO] resources:testResources > > > > [INFO] Using default encoding to copy filtered resources. > > > > _org.apache.maven.plugin.CompilationFailureException_: Compilation > failure > > > > at > > org.apache.maven.plugin.AbstractCompilerMojo.execute > (_AbstractCompilerMojo.java:516_) > > > > at > > org.apache.maven.plugin.TestCompilerMojo.execute > (_TestCompilerMojo.java:102_) > > > > at > > org.apache.maven.plugin.DefaultPluginManager.executeMojo > (_DefaultPluginManager.java:578_) > > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures > (_DefaultLifecycleExecutor.java:508_) > > > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments > (_DefaultLifecycleExecutor.java:328_) > > > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute > (_DefaultLifecycleExecutor.java:151_) > > > > at org.apache.maven.DefaultMaven.execute(_DefaultMaven.java:220_) > > > > at > > org.apache.maven.embedder.MavenEmbedder.execute > (_MavenEmbedder.java:813_) > > > > at > > org.maven.ide.eclipse.embedder.Maven2Executor.main > (_Maven2Executor.java:85_) > > > > [INFO] compiler:testCompile > > > > [INFO] Compiling 21 source files to > > D:\workspace\imp-server-admin-model\target\test-classes > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > [ERROR] BUILD FAILURE > > com.thales.imp:imp-server-admin-model:jar:0.07-SNAPSHOT ( > > task-segment: [test-compile] ) > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > [INFO] Build for project: > > com.thales.imp:imp-server-admin-model:jar:0.07-SNAPSHOT failed during > > execution of mojo: > > org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > [INFO] Total time: 3 second > > > > [INFO] Finished at: Tue Dec 18 13:17:43 CET 2007 > > > > [INFO] Memory 5M/15M > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > [ERROR] BUILD FAILURE > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > [INFO] Build for project: > > com.thales.imp:imp-server-admin-model:jar:0.07-SNAPSHOT failed during > > execution of mojo: > > org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > [INFO] Total time: 3 second > > > > [INFO] Finished at: Tue Dec 18 13:17:43 CET 2007 > > > > [INFO] Memory 5M/15M > > > > [INFO] > > > ---------------------------------------------------------------------------- > > > > The structure of my project is made of a root POM and severable modules: > > > > <modules> > > > > . . . > > > > <module>../imp-server-admin-model</module> > > > > . . . > > > > </modules> > > > > The exception does not appear with each project (module), the > > compilation successfully completed if I run maven without Eclipse. > > > > Do you know how to solve this problem ? The exception is not very > > explicit, is their any solution to see more logs ? > > > > Thanks. > > > > Baptiste GAILLARD > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > >
