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 release if the site fails or not??? I guess its a sometimes
> yes/no situation. Anyway, I gotta work out how to change the phase the
> plugin is now bound too.
>
> On Tue, Sep 2, 2008 at 12:03 PM, Andrew Hughes <[EMAIL PROTECTED]> wrote:
>
>> 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 repository yet
>> (during release) before the site:site occurs. Hence, the skin is not
>> available, can not be applied and the release barfs.
>>
>> These are all wild claims on my part and I have no idea how to resolve
>> them. The skin belongs under the organization pom, and the organization
>> pom
>> needs the skin.... I'd rather not duplicate the organization pom's config.
>>
>>
>>
>> On Tue, Sep 2, 2008 at 10:54 AM, Andrew Hughes <[EMAIL PROTECTED]> wrote:
>>
>>> Hi All,
>>>
>>> I have
>>>
>>> company/pom.xml  (module = skin)
>>> company/skin/pom.xml  (parent = company)
>>>
>>> Also, the company/src/site/site.xml (skin = comany-skin).. this is what
>>> sets the organizational skinning of site's.
>>>
>>> When I do a release... the company site fails to build because it can't
>>> locate the site skin in any repo. I'm guessing that the deploy of the
>>> release is AFTER the site - hence the skin can never be applied until the
>>> module is deployed.
>>>
>>> yes/no... I'm having a guess either way.
>>>
>>> Cheers.
>>>
>>>
>>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to