separate your inheritance from your aggregation
On 9/2/08, Andrew Hughes <[EMAIL PROTECTED]> wrote:
> Indeed this is the case.
>
> I need to change the site so that it runs AFTER the deploy of the released
> artifacts. Perhaps this should be 'normal' behaviour for maven... do you
> want to fail a
Indeed this is the case.
I need to change the site so that it runs AFTER the deploy of the released
artifacts. Perhaps this should be 'normal' behaviour for maven... do you
want to fail a release if the site fails or not??? I guess its a sometimes
yes/no situation. Anyway, I gotta work out how to
Thanks Martin,
I don't think that's the problem here... the problem appears to that the
site plugin can not obtain my module skin/jar from any repository. Now I
begin to make assumptions... but this would most likely happen because the
released artifacts/module/skin has not been deployed into a re
from the module's perspective |-- my-module | `-- pom.xml `-- parent `--
pom.xml
The Solution
To address this directory structure (or any other directory structure), we
would have to add the element to our parent section.
com.mycompany.app
my-app
1
.../parent/pom.xml
