Yes, I'm trying to do what I can to improve the situation. That's why I
spent 3 hours yesterday merging the site files over from trunk to the
3.x branch.
Some things are hard for me to do though, such as document code written
by someone else or putting back code that isn't working, when I don't
kn
> May I suggest that you do not deploy the site for Site plugin 3.0-beta-1
> at all, since it doesn't contain anything that isn't already published
> in the 2.1.1 site.
>
> Instead of putting the plugin URL in the release notes e-mail, you could
> use the URL to wiki page that you wrote. Perhaps li
Try and help make all the fixes you think are necessary to make a higher
quality release and we'll just release it again.
On Aug 10, 2010, at 4:19 PM, Dennis Lundberg wrote:
> On 2010-08-10 13:03, Olivier Lamy wrote:
>> Hi,
>> Thanks for review.
>>
>> So here it looks I have two choices :
>> *
On 2010-08-10 13:03, Olivier Lamy wrote:
> Hi,
> Thanks for review.
>
> So here it looks I have two choices :
> * delay again having a site plugin for maven3 (as I'm not available
> for 2 weeks : it could be delayed for 3/4 weeks)
> * push a release with a -1 vote (which it's not blocker).
>
> So
Hi,
The vote has passed with the following result :
+1 (binding) Hervé Boutemy, Benjamin Bentmann, Arnaud Héritier, Lukas
Theussl, Vincent Siveton, Olivier Lamy
+1 (non-binding) Nicolas De Loof, Tony Chemit
-1 (binding) : Dennis Lundberg
I will continue the release process.
Thanks for reviewing,
I just checked: http://bit.ly/dsx5l1
Releases may not be vetoed
>
I had forgotten that one!
-Stephen
On 9 August 2010 23:01, Dennis Lundberg wrote:
> I vote -1 to release the Site Plugin as it is staged.
>
> Here are my reasons:
>
> * The site for 3.0-beta-1 is hopelessly outdated. It's files
Hi,
Thanks for review.
So here it looks I have two choices :
* delay again having a site plugin for maven3 (as I'm not available
for 2 weeks : it could be delayed for 3/4 weeks)
* push a release with a -1 vote (which it's not blocker).
So currently, I choose the second option and will push an oth
On Tue, Aug 10, 2010 at 12:45 PM, Stephen Connolly
wrote:
> is a -1 really called for on a beta release with this criteria?
>
> you could just vote -0.
>
> it's only a beta
I agree with you regarding the deficiencies in the site and in the
Javadoc, but if these are tru
is a -1 really called for on a beta release with this criteria?
you could just vote -0.
it's only a beta
On 9 August 2010 23:01, Dennis Lundberg wrote:
> I vote -1 to release the Site Plugin as it is staged.
>
> Here are my reasons:
>
> * The site for 3.0-beta-1 is
I vote -1 to release the Site Plugin as it is staged.
Here are my reasons:
* The site for 3.0-beta-1 is hopelessly outdated. It's files are from
before the 2.1 version was released. This means that important pointers
about the Doxia upgrade is missing. The POM snippets has hardcoded
versions (2.0
So a proposal release note is available here http://goo.gl/Z16v
Please folks comment and/or fix stuff.
Thanks
2010/8/9 Dennis Lundberg :
> 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
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 :
On 2010-08-08 20:07, Olivier Lamy wrote:
> 2010/8/8 Tony Chemit :
>> +1 (I'd like to work only with maven 3 an
+1
Vincent
Le 2010-08-09 à 02:20, Lukas Theussl a écrit :
+1
-Lukas
Olivier Lamy wrote:
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/sec
+1
-Lukas
Olivier Lamy wrote:
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:
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 :
>>> On 2010-08-08 20:07, Olivier Lamy wrote:
2010/8/8 Tony Chemit :
> +1 (I'd like to work only with maven 3 and the site plugin is the last
> break for it)
>>
On 2010-08-08 23:30, Olivier Lamy wrote:
> 2010/8/8 Dennis Lundberg :
>> On 2010-08-08 20:07, Olivier Lamy wrote:
>>> 2010/8/8 Tony Chemit :
+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 w
2010/8/8 Dennis Lundberg :
> On 2010-08-08 20:07, Olivier Lamy wrote:
>> 2010/8/8 Tony Chemit :
>>> +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
>>
+1
Arnaud
On Aug 7, 2010, at 9:54 PM, Olivier Lamy wrote:
> 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?project
On 2010-08-08 20:07, Olivier Lamy wrote:
> 2010/8/8 Tony Chemit :
>> +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 o
Hi,
After the release, I wanted to ask others devs on what to do with
branch and trunk. But it's an other step.
Currently this branch should work as last 2.x release (except issues sure :-) )
So we have put in the wiki some informations regarding changes for
configuration and reporting plugin compa
I don't find any information regarding how the plugin's site is going to be
managed. As there will be two active branches of the plugin (right?), having
just one site could be confusing I think.
/Anders
On Sat, Aug 7, 2010 at 21:54, Olivier Lamy wrote:
> Hi,
> In order to have a good companion
2010/8/8 Tony Chemit :
> +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
+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
Olivier Lamy wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-070/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.o
+1 (non binding)
Nicolas
2010/8/7 Olivier Lamy
> 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&v
+1
Hervé
Le samedi 07 août 2010, Olivier Lamy 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=111
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/conten
27 matches
Mail list logo
