On 2010-08-09 00:59, Jason van Zyl wrote:
> 
> On Aug 8, 2010, at 5:47 PM, Dennis Lundberg wrote:
> 
>> On 2010-08-08 23:30, Olivier Lamy wrote:
>>> 2010/8/8 Dennis Lundberg <[email protected]>:
>>>> On 2010-08-08 20:07, Olivier Lamy wrote:
>>>>> 2010/8/8 Tony Chemit <[email protected]>:
>>>>>> +1 (I'd like to work only with maven 3 and the site plugin is the last 
>>>>>> break for it)
>>>>>>
>>>>>> but some stuff seems not to be any longer possible with this version.
>>>>>>
>>>>>> 1) merging reporting
>>>>>>
>>>>>> I configured in two profiles a old way reporting section and activate 
>>>>>> them when generating the site : all reports are generated.
>>>>>>
>>>>>> When using new configuration, it does not works the same. As we are now 
>>>>>> configuring inside a plugin, the merge is no more possible of reports.
>>>>>>
>>>>>> Is there a way to do it ?
>>>>> Sounds like an issue. (not blocker IMHO).
>>>>> Can you provide a sample project and attach it in a jira issue.
>>>>>>
>>>>>> 2) deploying site.xml
>>>>>>
>>>>>> Before the site descriptor was always deployed, but now I need to use a 
>>>>>> specific goal site:attach-descriptor.
>>>>>>
>>>>>> Can you confirm me this point ?
>>>>> Yes I confirm (have a look here http://goo.gl/CVgs)
>>>>
>>>> I have noticed this too.
>>>> Is this because of a change in Maven 3 or the Site Plugin 3?
>>>
>>> Maven 3 core.
>>
>> I read the wiki page you linked to above, but I don't understand why it
>> was necessary to remove a life-cycle execution. Can someone explain the
>> reasoning behind that?
>>
> 
> The site plugin is not special. Any number of specific domains like 
> reporting, or release management may want to have their own lifecycle. You 
> should easily be able to contribute one to the core at runtime. If that can 
> be done easily now then we'll fix that. But reporting of any sort in the core 
> is polluting the core. Something goes wrong with the reporting lifecycle and 
> users have to wait until the core is release. That's a bad coupling. You 
> should be able to do anything you want with/from from your own domain. The 
> site plugin in this case.

Sorry, I misread the wiki page. I thought it was a lifecycle phase that
was removed, when in fact it is a plugin execution bound to the
lifecycle that was removed.

Now it makes sense, although we will still need to be *very* clear about
this removal in the site for the Site Plugin.

>> Decouple Doxia and reporting I understand, but won't "arbitrary
>> reporting systems" all go through the Site plugin?
>>
> 
> No. Who knows what someone else may create.

Okey

> 
>> I think this will be the subject of many complaints. It also means that
>> people just switch from Maven 2 + Site Plugin 2 to Maven 3 + Site Plugin
>> 3 without changing their configuration.
>>
>>>
>>>>
>>>>>>
>>>>>> Any way great job :) works fine except for this two points.
>>>>>>
>>>>>> Tony.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Le Sat, 7 Aug 2010 21:54:12 +0200,
>>>>>> Olivier Lamy <[email protected]> a écrit :
>>>>>>
>>>>>>> Hi,
>>>>>>> In order to have a good companion to the coming Apache Maven 3.0-beta-2 
>>>>>>> release.
>>>>>>> I'd like to release Maven Site Plugin 3.0-beta-1 for maven 3.
>>>>>>> We solved 10 issues :
>>>>>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146&version=15554
>>>>>>>
>>>>>>> Staging repo:
>>>>>>> https://repository.apache.org/content/repositories/maven-070/
>>>>>>>
>>>>>>> Guide to testing staged releases:
>>>>>>> http://maven.apache.org/guides/development/guide-testing-releases.html
>>>>>>>
>>>>>>> Notes :
>>>>>>> * this release has been build using the staged Apache Maven 3.0-beta-2
>>>>>>> (so you must use the staged repository [1] )
>>>>>>> * some informations can be found [2], specially how to configure your
>>>>>>> pom in order to be able to continue building site with both maven 2.x
>>>>>>> and maven 3.
>>>>>>>
>>>>>>>
>>>>>>> Vote open for 72 hours.
>>>>>>>
>>>>>>> [ ] +1
>>>>>>> [ ] +0
>>>>>>> [ ] -1
>>>>>>>
>>>>>>> +1 from me
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Tony Chemit
>>>>>> --------------------
>>>>>> tél: +33 (0) 2 40 50 29 28
>>>>>> email: [email protected]
>>>>>> http://www.codelutin.com
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>> For additional commands, e-mail: [email protected]
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Dennis Lundberg
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> -- 
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
> 
> You are never dedicated to something you have complete confidence in.
> No one is fanatically shouting that the sun is going to rise tomorrow.
> They know it is going to rise tomorrow. When people are fanatically
> dedicated to political or religious faiths or any other kind of 
> dogmas or goals, it's always because these dogmas or
> goals are in doubt.
> 
>   -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
> 
> 
> 
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to