://jira.codehaus.org/browse/MECLIPSE-3
More a quicker in a multi-modules project is : mvn
-Dmaven.test.skip=true clean compile eclipse:clean eclipse:eclipse
- Olivier
-Message d'origine-
De : Matt McGill [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 31 mars 2006 17:35
À : Maven Users
I think I was just hung up on the same problem, but I want to clarify
to make sure. When you say that eclipse:eclipse requires you to
install before generating the .project and .classpath files, you mean
before generating the *correct* .project and .classpath files, right?
That's what's bee
I have a multi-module project, and for various reasons only want to
execute maven on the parent pom. However, I have a plugin that only
makes sense to configure/execute on some of the child modules. The
plugin target I want to execute shouldn't really be attached to a
phase in the build lif
n of the parent
pom, maven executes the plugin target on the parent, which is also
undesireable. Is there a way to configure things such that executing
'mvn my-plugin:fitnesse-test' on the root pom will only result in
that target being run for those child projects whic
,
shell script)?
If it's in sub-process, kill it because if you don't kill it, it
will be a zombie process. If your project is always "In Progress",
restart Continuum.
If it's in Continuum, restart Continuum.
All status are cleaned at continuum startup.
Emmanuel
M
I've got a build that has hung, leaving Continuum to permanently
display "In Progress..." for its status. I read in a previous message
to this list that it was somehow possible in 1.0.2 to clear the
offending build out of the database without doing it manually, but
I'm unsure of how to do s
