So you should vote for http://jira.codehaus.org/browse/MECLIPSE-252 too :P
Regards,
Marcin
Dan Tran wrote:
You poms are fine. I have seen this in my projects too.
-D
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
to configure skip individually per child project.
-D
On 8/28/07, Marcin Waldowski [EMAIL PROTECTED] wrote:
Dan, thanks for response.
I've reproduced it in two simple as possible module set. See atachement.
One is an ejb packaging project and the second is ear packaging project.
The second one use
Dan,
Thanks for your continuous help. I think it is a subject for another
thread...
Regards,
Marcin
Dan Tran wrote:
I ran into the same thing, and ended up to run
mvn installfirst
then
mvn eclipse:eclipse
-D
On 8/29/07, Marcin Waldowski [EMAIL PROTECTED] wrote:
Dan, thanks
Hello.
I created 2 module simple example which can be downloaded from:
http://www.nabble.com/attachment/12381781/0/example.zip
When I execute 'mvn package' everything works ok. But when I execute mvn
eclipse:eclipse I ended up with error:
[DEBUG] Unable to download the artifact from any
plugin requires
your ejb3 module installed on you local repo, this is a bug. So the
work around is
to run 'mvn install' at eleast once before invoking 'mvn eclipse:eclipse'
please file an issue against eclipse plugin
On 8/30/07, Marcin Waldowski [EMAIL PROTECTED] wrote:
Hello.
I created 2
skiptrue/skip
...
/configuration
/plugin
But when I executed 'mvn eclipse:eclipse' (in derictory with top level
POM) plugin did not skip one of my module.
What I did wrong?
Regards, Marcin
Marcin Waldowski wrote:
Hello.
I have a Multiple Module Projects (with top level POM
Dan Tran wrote:
The patch for this enhancement has been applied. The release of new
eclipse
plugin is coming very soon.
-D
Great. Many thanks.
On 6/21/07, Dan Tran [EMAIL PROTECTED] wrote:
please vote for this enhencement request
http://jira.codehaus.org/browse/MECLIPSE-271
I
Heinrich Nirschl wrote:
Sometimes, you can work around this problem by running 'mvn install'
before.
- Henry
That's true. But I just want to provide functionality as simple as
possible to other people from my team, without explanation why they need
to run mvn install to make it work
Hello.
I have a Multiple Module Projects (with top level POM and modules). One
of module has ear type (packagingear/packaging) and I don't want to
make eclipse project from it.
Is it possible to exclude this module from execution of
mvn eclipse:eclipse
in directory with top level POM?
is
well, or not?
Hth,
Nick Stolwijk
[1] http://maven.apache.org/plugins/maven-eclipse-plugin/
Marcin Waldowski wrote:
Hello.
I have a Multiple Module Projects (with top level POM and modules).
One of module has ear type (packagingear/packaging) and I don't
want to make eclipse project from
10 matches
Mail list logo
