Which are you talking about? The CLI tool eclipse:eclipse? Usually you
need to configure these to "linkModules" (the the idea:idea term, dunno
what eclipse would call it). It basically tell the plugin to create the
project with the modules having a "source-level" dependency on other
modules in the reactor, instead of binary dependencies.
Hardy Ferentschik wrote:
On Wed, 13 Jun 2007 17:46:10 +0200, Max Rydahl Andersen
<[EMAIL PROTECTED]> wrote:
With respect to eclipse and maven then the maven guys are just
"great" since mvn eclipse:eclipse and the m2 eclipse plugin of course
decides
to do things differently - basically making them incompatible.
http://jira.codehaus.org/browse/MECLIPSE-78
Unfortunately the eclipse plugin does not seem to handle profiles...
Not only that, but for me it refuses to do reactor builds :( At least
that's my experience from other projects.
The functionality is very basic and I basically just use it to have
the classpath properly setup. The actual build
I drive from the command line. Not perfect, but it works.
--Hardy
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
