Barrie Treloar [EMAIL PROTECTED] schrieb am 13.12.2006 01:47:02:
Running mvn in debug mode so I can attach eclipse to the running
instance.
How do you do that?
Regards,
--
Aaron Digulla
-
To unsubscribe, e-mail: [EMAIL
On 12/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Barrie Treloar [EMAIL PROTECTED] schrieb am 13.12.2006 01:47:02:
Running mvn in debug mode so I can attach eclipse to the running
instance.
How do you do that?
Copy your mvn script to something like mvn-debug.{bat|.sh}
Then find the
did you find what was causing it? :-)
Barrie Treloar wrote:
On 12/13/06, Rahul Thakur [EMAIL PROTECTED] wrote:
If i remember correct from what I saw in the m-e-p sources last week,
maven-eclipse-plugin-test is created by the Plugin unit tests and then
installed to a *test* repo local to the
On 12/14/06, Rahul Thakur [EMAIL PROTECTED] wrote:
did you find what was causing it? :-)
Not yet.
I think the problem is in ProjectTool.manglePomForTesting
but I need to do more investigating.
I am looking into why internal_plugins dont work and this is higher
priority for me at the
See http://jira.codehaus.org/browse/MECLIPSE-192
I also see these messages with similar problems:
* http://www.mail-archive.com/users@maven.apache.org/msg56535.html
I'm running mvn eclipse:eclipse (with an internal release of the
snapshot version)
And I get a build failure like:
[INFO] Failed
It's odd that mvn eclipse:clean works, but eclipse:eclipse does not...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
And that the failure is only for reactor builds.
Running in the modules themselves works fine.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I have created a junk Mojo to spit out debug to see if I can see whats wrong.
This junk mojo works fine when run within the module (as expected).
When run in a reactor build this junk mojo is executed for the root
project but when when it attempts to go into a module it then fails
with the same
Starting to get somewhere.
Running mvn in debug mode so I can attach eclipse to the running instance.
One thing I am noticing is that the attached sources don't match
exactly what is being run by maven. The eclipse plugin defines the
dependency on version 2.0.1 but I think the version being
eclipse-jar!/META-INF/maven/plugin.xml
plugin
descriptionInternal release from subversion revision r485327.
Applied patches:
* http://jira.codehaus.org/browse/MECLIPSE-206
* parent version now 4 instead of 4-SNAPSHOT/description
groupIdorg.apache.maven.plugins/groupId
Manually hacking the jar to set the version correctly resolves the problem.
Now to find out why the jar is being created incorrectly...
Running mvn package will incorrectly create a test version for the
real version jar.
I just noticed that there are two jars in here:
*
If i remember correct from what I saw in the m-e-p sources last week,
maven-eclipse-plugin-test is created by the Plugin unit tests and then
installed to a *test* repo local to the Eclipse project.
Not sure why is your build seeing the -test version. Do you have
maven-eclipse-plugin sources
On 12/13/06, Rahul Thakur [EMAIL PROTECTED] wrote:
If i remember correct from what I saw in the m-e-p sources last week,
maven-eclipse-plugin-test is created by the Plugin unit tests and then
installed to a *test* repo local to the Eclipse project.
Not sure why is your build seeing the -test
13 matches
Mail list logo
