I will (try). thanks.

On Dec 20, 2007 11:38 AM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote:

> Benny Sadeh wrote:
> >
> >     What I think happen in your case is that you have your jars in
> Eclipse
> >     classpath, so JDT can compile classes, and if it compiles into the
> >     same
> >     dir as Maven, it won't recompile them, hence don't need any
> >     dependencies. "mvn clean" would bring things back to obvious.
> >
> >
> > you're correct Eugene: after "mvn clean" I catch the failure right
> > away in:
> >
> > [INFO] compiler:compile
> > [INFO] Compiling 94 source files to C:\projects\utilities\target\classes
> > org.apache.maven.plugin.CompilationFailureException: Compilation failure
> >     at org.apache.maven.plugin.AbstractCompilerMojo.execute
> > (AbstractCompilerMojo.java:516)
> >     at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java
> :114)
> >     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)
> >
> > I wonder if it's possible to indicate to the user more precisley of
> > what went wrong ...
>  Can you please create small test project that would fail with this
> error and create new JIRA issue for that? This will save us some time
> and we can use it in out test suite as well.
>
> >       Maven solution for jars that are not in the local repository is
> >     to use
> >     <system> scope and specify <location> element for such
> >     dependencies, but
> >     they still should be listed in pom.xml. That is not specific to
> >     m2eclipse but general Maven feature.
> >
> >
> > thanks for the education Eugene, I didn't know of that feature.
> > I guess I will actually have to learn Maven in greater depth after all
> ;-)
> >
> > your quick responding is fantastic!
> > how much do I owe you for that ?-)
>  Well, you you can create that test project above, that would be a huge
> help and greatly appreciated. :-)
>
>  Thanks
>
>  Eugene
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

Reply via email to