Hello maven users,
User wsmoak on irc, after helping me to solve this issue, asked me to
share my little story with you guys.
Basically we have some documentation that is maintained in a wiki, and
we want to include it in plain text in our software distribution. So I
put a section in <build> that uses the exec-maven-plugin to run "lynx
-dump" on the url during the "package" phase, and placed it above the
maven-assembly-plugin bit that builds the tar.gz so that it ran first
and would be included in the distro. That worked fine.
Except that we need the build to work if the system doesn't have lynx.
So I moved the lynx piece to a profile with
<activation><file><exists>/usr/bin/lynx</exists></file></activation>.
However, even though I put the <profiles> section above the <build>
section, the tar.gz was getting built before lynx -dump ran.
I noticed in the docs that maven 2.1.x has a "prepare-package" phase
which should solve everything. But I'm stuck on 2.0, so what I did to
get around this build order problem was to put the .tar.gz assembly
piece in a profile with a contrived activation that always succeeds
(*not* the confusingly named <activeByDefault>), and place that profile
below the lynx one. That seems to work.
So it seems that executions in profiles are executed after those in
<build>. Perhaps this (or whatever the actual behavior really is) could
be documented.
Noah
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
