I have taken the practice of not publishing snapshot websites. The
reason generatePom is not up on the site is because it isn't in the
released plugin. I think we should revert to the *released* sites (or
better yet, release those plugins - didn't John have votes up for them?)

Changing the parent doesn't hurt, but I don't recommend it. It upgrades
dependencies to 2.0.1 and if any of those apis are used it will cause
issues running under 2.0 (if this is required, you can add a
prerequisites tag).

If anyone cares about how to actually solve this problem of inheriting
deps vs metadata, please see the "POM Problems and Inheritence" mail I
sent on 30 Nov. I didn't get a lot of feedback, though I have discussed
it with some other developers just prior to ApacheCon but didn't come to
any conclusions to post. I'll try and pick it up again in the new year.

- Brett

Vincent Massol wrote:
>   
>> -----Original Message-----
>> From: Martin van den Bemt [mailto:[EMAIL PROTECTED]
>> Sent: vendredi 23 décembre 2005 21:11
>> To: Maven Developers List
>> Subject: Re: maven ear release 2.1 - web site not up to date
>>
>> It prevents running the plugin on maven 2.0 (for the clover plugin I
>> needed to install 2.0.1 when you changed that)
>>     
>
> Are you sure? 
>
> I think it's the fact that the Clover plugin requires Maven 2.0.1 that was
> the cause rather than using a 2.0.1 parent version.
>
> -Vincent
>
>   
>> Vincent Massol wrote:
>>     
>>>> -----Original Message-----
>>>> From: Arik Kfir [mailto:[EMAIL PROTECTED]
>>>> Sent: vendredi 23 décembre 2005 20:12
>>>> To: Maven Developers List
>>>> Subject: Re: maven ear release 2.1 - web site not up to date
>>>>
>>>> The same is with the deploy/install sites (the 'generatePom' arguments
>>>> are not there, for instance). They were last published in october...
>>>>         
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>     
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>   

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

Reply via email to