On Dec 22, 2008, at 3:51 PM, Todd Thiessen wrote:
On top of that, executing the site phase triggers
other phases to run, such as "install", which has still more
plugins bound to it, such as a bytecode obfuscation plugin.
These also take a long time to run.
Not so. The site lifecycle is not bound to the default lifecycle
unless
you make it so. So executing the mvn site phase does not trigger an
install.
Sorry, now that I examine our POM, I see that the bytecode obfuscation
goal is bound to the process-classes phase, not the install phase. But
my point was that executing the site phase does cause other phases to
run (resource:resources, compiler:compile), which adds to the time
spent waiting.
It sounds like your documentation is seperate and should be in a
different module. You can site the seperate module independantly from
the rest. You will probably get other benefits from this too.
Good idea; I'll look into it.
Trevor
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
