Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
Hello We only need to be ready to answer to the same question *a lot* :-) -- Olivier Le 25 juil. 2011 00:26, Hervé BOUTEMY herve.bout...@free.fr a écrit : ok, I added a doc to add a protocol and improved the error message [1] I think we can safely do the change proposed in MSITE-598: users won't be lost (of course, they'll need to read the error message...) Regards, Hervé [1] http://jira.codehaus.org/browse/MSITE-599 Le dimanche 24 juillet 2011, Benson Margulies a écrit : A thought: since 'extensions' has no 'management' or inheritance control, the use of it is actually harder and more obscure when people want to use other versions. It's far easier to just manage dependencies of the site plugin via pluginManagement. So, I'm in favor of using and documenting dependencies rather than extensions. On Sun, Jul 24, 2011 at 4:33 PM, Robert Scholte rfscho...@codehaus.org wrote: I've already made a jira-issue for it, MSITE-598 [1]. I think we should stay consistent: specify wagons with extensions.We just need to document this very well, both on the site and the failure-message, including the required xml to add to the pom. -Robert [1] http://jira.codehaus.org/browse/MSITE-598 From: herve.bout...@free.fr To: dev@maven.apache.org Subject: Re: Is Maven Site Plugin 3.0-beta-4 ready for release? Date: Sun, 24 Jul 2011 21:56:22 +0200 one last decision/documentation point about m-site-p 3 with Maven 3 we had a discussion on IRC yesterday with Robert, Mark and Benjamin about wagon and its change in M3 [1]. It was about the way we promote configuring wagon protocols in plugins: - in m-deploy-p, we promote using extensions (and the plugin doesn't add any wagon provider other that what is available from Maven core) - in m-site-p 3, we actually added a lot of wagon providers as dependencies (ssh, ftp, webdav, scm:svn), thus they are automagically available for end user, but this disables extension mecanisms for every providers added: if you want to change a wagon provider version, for example, defining it in extension won't work for m-site-p So we have to do a choice between 2 options: 1. be consistent with other plugins, remove every wagon provider from m-site-p and promote/document configuration done by end-users (either as extension or dependency). This will be needed notably for scp (which works automagically in M2) and ftp or scm:svn (which were added in m-site-p 3.0-beta*): I suppose we need to create a dedicated example. 2. let the multiple wagon providers in m-site-p, which will work automagically for a lot of protocols, but downloads a lot of artifacts and disables extensions definition for these protocols: this needs at least documentation So what should we do: 1. pure, with good explanations to help users understand what to do 2. magic at the beginning, but downloads the internet and more complex later ? Please correct if I misunderstood something... Regards, Hervé [1] https://cwiki.apache.org/MAVEN/maven-3x-compatibility- notes.html#Maven3.xCompatibilityNotes-TransportProtocols%2528Wagons%2529 Le vendredi 22 juillet 2011, Dennis Lundberg a écrit : On 2011-07-22 00:48, Hervé BOUTEMY wrote: Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Thanks for all your work Hervé! Now that we plan for 3.0 to be the main version of the plugin, there are a couple of things I'd like to do: 1. Remove any references to the 3.x Subversion branch in the docs. I'll do this. 2. Document the difference between Maven 2 and Maven 3 with regards to inheritance that was recently discovered, if it hasn't already been done. I'll check this. 3. Switch the URLs for the deployed sites. We currently have these redirects: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/ I'd like to change them to this: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin-2.3/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin/$1 This would also require changing the plugins/index page to point to /plugins/maven-site-plugin-2.x/ and /plugins/maven-site-plugin/ respectively for versions 2 and 3. 4. Change the deploy site URL in both POMs. 5. Move the current maven/plugins/trunk/maven-site-plugin/ to maven/plugins/branches/maven-site-plugin-2.x 6. Move maven/plugins/branches/maven-site-plugin-3.x to maven/plugins/trunk/maven-site-plugin/ I'll get on 1 and 2 right now. 3 I'd like to do after the release, once the deployed
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
A thought: since 'extensions' has no 'management' or inheritance control, the use of it is actually harder and more obscure when people want to use other versions. It's far easier to just manage dependencies of the site plugin via pluginManagement. So, I'm in favor of using and documenting dependencies rather than extensions. +1 from me on this, totally agree with Benson here (tho a bit late to the thread) Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
one last decision/documentation point about m-site-p 3 with Maven 3 we had a discussion on IRC yesterday with Robert, Mark and Benjamin about wagon and its change in M3 [1]. It was about the way we promote configuring wagon protocols in plugins: - in m-deploy-p, we promote using extensions (and the plugin doesn't add any wagon provider other that what is available from Maven core) - in m-site-p 3, we actually added a lot of wagon providers as dependencies (ssh, ftp, webdav, scm:svn), thus they are automagically available for end user, but this disables extension mecanisms for every providers added: if you want to change a wagon provider version, for example, defining it in extension won't work for m-site-p So we have to do a choice between 2 options: 1. be consistent with other plugins, remove every wagon provider from m-site-p and promote/document configuration done by end-users (either as extension or dependency). This will be needed notably for scp (which works automagically in M2) and ftp or scm:svn (which were added in m-site-p 3.0-beta*): I suppose we need to create a dedicated example. 2. let the multiple wagon providers in m-site-p, which will work automagically for a lot of protocols, but downloads a lot of artifacts and disables extensions definition for these protocols: this needs at least documentation So what should we do: 1. pure, with good explanations to help users understand what to do 2. magic at the beginning, but downloads the internet and more complex later ? Please correct if I misunderstood something... Regards, Hervé [1] https://cwiki.apache.org/MAVEN/maven-3x-compatibility- notes.html#Maven3.xCompatibilityNotes-TransportProtocols%2528Wagons%2529 Le vendredi 22 juillet 2011, Dennis Lundberg a écrit : On 2011-07-22 00:48, Hervé BOUTEMY wrote: Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Thanks for all your work Hervé! Now that we plan for 3.0 to be the main version of the plugin, there are a couple of things I'd like to do: 1. Remove any references to the 3.x Subversion branch in the docs. I'll do this. 2. Document the difference between Maven 2 and Maven 3 with regards to inheritance that was recently discovered, if it hasn't already been done. I'll check this. 3. Switch the URLs for the deployed sites. We currently have these redirects: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/ I'd like to change them to this: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin-2.3/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin/$1 This would also require changing the plugins/index page to point to /plugins/maven-site-plugin-2.x/ and /plugins/maven-site-plugin/ respectively for versions 2 and 3. 4. Change the deploy site URL in both POMs. 5. Move the current maven/plugins/trunk/maven-site-plugin/ to maven/plugins/branches/maven-site-plugin-2.x 6. Move maven/plugins/branches/maven-site-plugin-3.x to maven/plugins/trunk/maven-site-plugin/ I'll get on 1 and 2 right now. 3 I'd like to do after the release, once the deployed site is in place. 4 needs to be done before the release. 5 and 6 can be done either before or after the release, I'd prefer to do it before. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: Is Maven Site Plugin 3.0-beta-4 ready for release?
I've already made a jira-issue for it, MSITE-598 [1]. I think we should stay consistent: specify wagons with extensions.We just need to document this very well, both on the site and the failure-message, including the required xml to add to the pom. -Robert [1] http://jira.codehaus.org/browse/MSITE-598 From: herve.bout...@free.fr To: dev@maven.apache.org Subject: Re: Is Maven Site Plugin 3.0-beta-4 ready for release? Date: Sun, 24 Jul 2011 21:56:22 +0200 one last decision/documentation point about m-site-p 3 with Maven 3 we had a discussion on IRC yesterday with Robert, Mark and Benjamin about wagon and its change in M3 [1]. It was about the way we promote configuring wagon protocols in plugins: - in m-deploy-p, we promote using extensions (and the plugin doesn't add any wagon provider other that what is available from Maven core) - in m-site-p 3, we actually added a lot of wagon providers as dependencies (ssh, ftp, webdav, scm:svn), thus they are automagically available for end user, but this disables extension mecanisms for every providers added: if you want to change a wagon provider version, for example, defining it in extension won't work for m-site-p So we have to do a choice between 2 options: 1. be consistent with other plugins, remove every wagon provider from m-site-p and promote/document configuration done by end-users (either as extension or dependency). This will be needed notably for scp (which works automagically in M2) and ftp or scm:svn (which were added in m-site-p 3.0-beta*): I suppose we need to create a dedicated example. 2. let the multiple wagon providers in m-site-p, which will work automagically for a lot of protocols, but downloads a lot of artifacts and disables extensions definition for these protocols: this needs at least documentation So what should we do: 1. pure, with good explanations to help users understand what to do 2. magic at the beginning, but downloads the internet and more complex later ? Please correct if I misunderstood something... Regards, Hervé [1] https://cwiki.apache.org/MAVEN/maven-3x-compatibility- notes.html#Maven3.xCompatibilityNotes-TransportProtocols%2528Wagons%2529 Le vendredi 22 juillet 2011, Dennis Lundberg a écrit : On 2011-07-22 00:48, Hervé BOUTEMY wrote: Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Thanks for all your work Hervé! Now that we plan for 3.0 to be the main version of the plugin, there are a couple of things I'd like to do: 1. Remove any references to the 3.x Subversion branch in the docs. I'll do this. 2. Document the difference between Maven 2 and Maven 3 with regards to inheritance that was recently discovered, if it hasn't already been done. I'll check this. 3. Switch the URLs for the deployed sites. We currently have these redirects: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/ I'd like to change them to this: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin-2.3/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin/$1 This would also require changing the plugins/index page to point to /plugins/maven-site-plugin-2.x/ and /plugins/maven-site-plugin/ respectively for versions 2 and 3. 4. Change the deploy site URL in both POMs. 5. Move the current maven/plugins/trunk/maven-site-plugin/ to maven/plugins/branches/maven-site-plugin-2.x 6. Move maven/plugins/branches/maven-site-plugin-3.x to maven/plugins/trunk/maven-site-plugin/ I'll get on 1 and 2 right now. 3 I'd like to do after the release, once the deployed site is in place. 4 needs to be done before the release. 5 and 6 can be done either before or after the release, I'd prefer to do it before. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
A thought: since 'extensions' has no 'management' or inheritance control, the use of it is actually harder and more obscure when people want to use other versions. It's far easier to just manage dependencies of the site plugin via pluginManagement. So, I'm in favor of using and documenting dependencies rather than extensions. On Sun, Jul 24, 2011 at 4:33 PM, Robert Scholte rfscho...@codehaus.org wrote: I've already made a jira-issue for it, MSITE-598 [1]. I think we should stay consistent: specify wagons with extensions.We just need to document this very well, both on the site and the failure-message, including the required xml to add to the pom. -Robert [1] http://jira.codehaus.org/browse/MSITE-598 From: herve.bout...@free.fr To: dev@maven.apache.org Subject: Re: Is Maven Site Plugin 3.0-beta-4 ready for release? Date: Sun, 24 Jul 2011 21:56:22 +0200 one last decision/documentation point about m-site-p 3 with Maven 3 we had a discussion on IRC yesterday with Robert, Mark and Benjamin about wagon and its change in M3 [1]. It was about the way we promote configuring wagon protocols in plugins: - in m-deploy-p, we promote using extensions (and the plugin doesn't add any wagon provider other that what is available from Maven core) - in m-site-p 3, we actually added a lot of wagon providers as dependencies (ssh, ftp, webdav, scm:svn), thus they are automagically available for end user, but this disables extension mecanisms for every providers added: if you want to change a wagon provider version, for example, defining it in extension won't work for m-site-p So we have to do a choice between 2 options: 1. be consistent with other plugins, remove every wagon provider from m-site-p and promote/document configuration done by end-users (either as extension or dependency). This will be needed notably for scp (which works automagically in M2) and ftp or scm:svn (which were added in m-site-p 3.0-beta*): I suppose we need to create a dedicated example. 2. let the multiple wagon providers in m-site-p, which will work automagically for a lot of protocols, but downloads a lot of artifacts and disables extensions definition for these protocols: this needs at least documentation So what should we do: 1. pure, with good explanations to help users understand what to do 2. magic at the beginning, but downloads the internet and more complex later ? Please correct if I misunderstood something... Regards, Hervé [1] https://cwiki.apache.org/MAVEN/maven-3x-compatibility- notes.html#Maven3.xCompatibilityNotes-TransportProtocols%2528Wagons%2529 Le vendredi 22 juillet 2011, Dennis Lundberg a écrit : On 2011-07-22 00:48, Hervé BOUTEMY wrote: Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Thanks for all your work Hervé! Now that we plan for 3.0 to be the main version of the plugin, there are a couple of things I'd like to do: 1. Remove any references to the 3.x Subversion branch in the docs. I'll do this. 2. Document the difference between Maven 2 and Maven 3 with regards to inheritance that was recently discovered, if it hasn't already been done. I'll check this. 3. Switch the URLs for the deployed sites. We currently have these redirects: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/ I'd like to change them to this: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin-2.3/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin/$1 This would also require changing the plugins/index page to point to /plugins/maven-site-plugin-2.x/ and /plugins/maven-site-plugin/ respectively for versions 2 and 3. 4. Change the deploy site URL in both POMs. 5. Move the current maven/plugins/trunk/maven-site-plugin/ to maven/plugins/branches/maven-site-plugin-2.x 6. Move maven/plugins/branches/maven-site-plugin-3.x to maven/plugins/trunk/maven-site-plugin/ I'll get on 1 and 2 right now. 3 I'd like to do after the release, once the deployed site is in place. 4 needs to be done before the release. 5 and 6 can be done either before or after the release, I'd prefer to do it before. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
ok, I added a doc to add a protocol and improved the error message [1] I think we can safely do the change proposed in MSITE-598: users won't be lost (of course, they'll need to read the error message...) Regards, Hervé [1] http://jira.codehaus.org/browse/MSITE-599 Le dimanche 24 juillet 2011, Benson Margulies a écrit : A thought: since 'extensions' has no 'management' or inheritance control, the use of it is actually harder and more obscure when people want to use other versions. It's far easier to just manage dependencies of the site plugin via pluginManagement. So, I'm in favor of using and documenting dependencies rather than extensions. On Sun, Jul 24, 2011 at 4:33 PM, Robert Scholte rfscho...@codehaus.org wrote: I've already made a jira-issue for it, MSITE-598 [1]. I think we should stay consistent: specify wagons with extensions.We just need to document this very well, both on the site and the failure-message, including the required xml to add to the pom. -Robert [1] http://jira.codehaus.org/browse/MSITE-598 From: herve.bout...@free.fr To: dev@maven.apache.org Subject: Re: Is Maven Site Plugin 3.0-beta-4 ready for release? Date: Sun, 24 Jul 2011 21:56:22 +0200 one last decision/documentation point about m-site-p 3 with Maven 3 we had a discussion on IRC yesterday with Robert, Mark and Benjamin about wagon and its change in M3 [1]. It was about the way we promote configuring wagon protocols in plugins: - in m-deploy-p, we promote using extensions (and the plugin doesn't add any wagon provider other that what is available from Maven core) - in m-site-p 3, we actually added a lot of wagon providers as dependencies (ssh, ftp, webdav, scm:svn), thus they are automagically available for end user, but this disables extension mecanisms for every providers added: if you want to change a wagon provider version, for example, defining it in extension won't work for m-site-p So we have to do a choice between 2 options: 1. be consistent with other plugins, remove every wagon provider from m-site-p and promote/document configuration done by end-users (either as extension or dependency). This will be needed notably for scp (which works automagically in M2) and ftp or scm:svn (which were added in m-site-p 3.0-beta*): I suppose we need to create a dedicated example. 2. let the multiple wagon providers in m-site-p, which will work automagically for a lot of protocols, but downloads a lot of artifacts and disables extensions definition for these protocols: this needs at least documentation So what should we do: 1. pure, with good explanations to help users understand what to do 2. magic at the beginning, but downloads the internet and more complex later ? Please correct if I misunderstood something... Regards, Hervé [1] https://cwiki.apache.org/MAVEN/maven-3x-compatibility- notes.html#Maven3.xCompatibilityNotes-TransportProtocols%2528Wagons%2529 Le vendredi 22 juillet 2011, Dennis Lundberg a écrit : On 2011-07-22 00:48, Hervé BOUTEMY wrote: Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Thanks for all your work Hervé! Now that we plan for 3.0 to be the main version of the plugin, there are a couple of things I'd like to do: 1. Remove any references to the 3.x Subversion branch in the docs. I'll do this. 2. Document the difference between Maven 2 and Maven 3 with regards to inheritance that was recently discovered, if it hasn't already been done. I'll check this. 3. Switch the URLs for the deployed sites. We currently have these redirects: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/ I'd like to change them to this: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin-2.3/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin/$1 This would also require changing the plugins/index page to point to /plugins/maven-site-plugin-2.x/ and /plugins/maven-site-plugin/ respectively for versions 2 and 3. 4. Change the deploy site URL in both POMs. 5. Move the current maven/plugins/trunk/maven-site-plugin/ to maven/plugins/branches/maven-site-plugin-2.x 6. Move maven/plugins/branches/maven-site-plugin-3.x to maven/plugins/trunk/maven-site-plugin/ I'll get on 1 and 2 right now. 3 I'd like to do after the release, once the deployed site is in place. 4 needs to be done before the release. 5 and 6 can be done either before or after
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
green light from here, thanks Herve for the updates! -Lukas On 07/22/2011 12:48 AM, Hervé BOUTEMY wrote: Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
On 2011-07-22 00:48, Hervé BOUTEMY wrote: Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Thanks for all your work Hervé! Now that we plan for 3.0 to be the main version of the plugin, there are a couple of things I'd like to do: 1. Remove any references to the 3.x Subversion branch in the docs. I'll do this. 2. Document the difference between Maven 2 and Maven 3 with regards to inheritance that was recently discovered, if it hasn't already been done. I'll check this. 3. Switch the URLs for the deployed sites. We currently have these redirects: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/ I'd like to change them to this: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin-2.3/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin/$1 This would also require changing the plugins/index page to point to /plugins/maven-site-plugin-2.x/ and /plugins/maven-site-plugin/ respectively for versions 2 and 3. 4. Change the deploy site URL in both POMs. 5. Move the current maven/plugins/trunk/maven-site-plugin/ to maven/plugins/branches/maven-site-plugin-2.x 6. Move maven/plugins/branches/maven-site-plugin-3.x to maven/plugins/trunk/maven-site-plugin/ I'll get on 1 and 2 right now. 3 I'd like to do after the release, once the deployed site is in place. 4 needs to be done before the release. 5 and 6 can be done either before or after the release, I'd prefer to do it before. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
nice team work, guys, I like it :) yes, please go with this release and switch plan: the release was expected for a long time, the result should really be a big step forward to full Maven 3 support even for the whole release process with docs Regards, Hervé Le vendredi 22 juillet 2011, Dennis Lundberg a écrit : On 2011-07-22 00:48, Hervé BOUTEMY wrote: Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Thanks for all your work Hervé! Now that we plan for 3.0 to be the main version of the plugin, there are a couple of things I'd like to do: 1. Remove any references to the 3.x Subversion branch in the docs. I'll do this. 2. Document the difference between Maven 2 and Maven 3 with regards to inheritance that was recently discovered, if it hasn't already been done. I'll check this. 3. Switch the URLs for the deployed sites. We currently have these redirects: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/ I'd like to change them to this: RedirectMatch ^/plugins/maven-site-plugin-2.x/(.*)$ /plugins/maven-site-plugin-2.3/$1 RedirectMatch ^/plugins/maven-site-plugin-3.x/(.*)$ http://maven.apache.org/plugins/maven-site-plugin/$1 This would also require changing the plugins/index page to point to /plugins/maven-site-plugin-2.x/ and /plugins/maven-site-plugin/ respectively for versions 2 and 3. 4. Change the deploy site URL in both POMs. 5. Move the current maven/plugins/trunk/maven-site-plugin/ to maven/plugins/branches/maven-site-plugin-2.x 6. Move maven/plugins/branches/maven-site-plugin-3.x to maven/plugins/trunk/maven-site-plugin/ I'll get on 1 and 2 right now. 3 I'd like to do after the release, once the deployed site is in place. 4 needs to be done before the release. 5 and 6 can be done either before or after the release, I'd prefer to do it before. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
Maven Site Plugin 3.0 is now ready for release (with its documentation) for me If anybody still has something to change, please explain what so we can fix it and release ASAP Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
On Tue, 12 Jul 2011 13:55:31 +0200 Lukas Theussl ltheu...@apache.org wrote: Tony Chemit wrote: On Thu, 7 Jul 2011 21:22:43 +0200 Hervé BOUTEMYherve.bout...@free.fr wrote: I forgot we had this great Jenkins instance with lots of OSes and configuration combinations, and improved ITs to cover a lot of cases (more than +50% over 3.0-beta-3) Then I'm now confident that we can release a good quality even without a lot of users having done tests themselves. +1 for 3.0 final: it won't be over-estimated! Something was detected as a regression in last stable version of version 2.3 of the site plugin Lukas added a IT for this case [1] and has also a ticket [2]. If this is not ok, this is for my part a none reason to a final release ? I don't know the difficulty to fix this problem... [1] http://svn.apache.org/viewvc?rev=1126420view=rev [2] http://jira.codehaus.org/browse/MSITE-585 I have committed a fix for the issue, however, I am not sure if it fixes your exact use-case and it probably still requires adjustment of your project (the parent pom requires default values for all variables). I have deployed snapshots (2.4-SNAPSHOT and 3.0-beta-4-SNAPSHOT), please check if it helps anything. I tried the SNAPSHOT version, but it does not helps me for some reasons I found with a fresh checkout of the branch. 1) In the deploy mojo, to obtain the site id and site url, the getRootSite method is used but does not do the magic work I want, beacuse the final pom does not use the same site server than the root project site :( 2) I fix do a little fix for that (testing as soon as site server id changed), I had after this the correct site url and id discovered. A new problem happens then : As the parent project site is NOT the same than the root project, the relative url computed before the push method invocation is not correct at all. I will give you a little project to explain all this when I will have more time. Cheers, Tony - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
Tony Chemit wrote: On Thu, 7 Jul 2011 21:22:43 +0200 Hervé BOUTEMYherve.bout...@free.fr wrote: I forgot we had this great Jenkins instance with lots of OSes and configuration combinations, and improved ITs to cover a lot of cases (more than +50% over 3.0-beta-3) Then I'm now confident that we can release a good quality even without a lot of users having done tests themselves. +1 for 3.0 final: it won't be over-estimated! Something was detected as a regression in last stable version of version 2.3 of the site plugin Lukas added a IT for this case [1] and has also a ticket [2]. If this is not ok, this is for my part a none reason to a final release ? I don't know the difficulty to fix this problem... [1] http://svn.apache.org/viewvc?rev=1126420view=rev [2] http://jira.codehaus.org/browse/MSITE-585 I have committed a fix for the issue, however, I am not sure if it fixes your exact use-case and it probably still requires adjustment of your project (the parent pom requires default values for all variables). I have deployed snapshots (2.4-SNAPSHOT and 3.0-beta-4-SNAPSHOT), please check if it helps anything. cheers, -Lukas - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
Hervé BOUTEMY wrote: the rationale behind not going directly to 3.0 was that site plugin is hard to test, particularly now that it is both compatible with Maven 2 and Maven 3, which is something really new and probably tested by only a few of us I don't quite agree with this rationale. Ease of testing is not a criterion for version naming IMO. The main criterion is how many *known* bugs and missing features there are left. So what are the open issues that we are aware about? If there are none or only a few, then let's call it final. If the people who are working on the release feel that the stuff is stable (which I do) then why not release it as such? sure, 3.0-beta-4 should at least be 3.0-RC-1, but perhaps not 3.0 immediately: I'm pretty sure we'll find some important problems when a lot of people try it seriously The most efficient way to get people to test something, is to release it! :) There are real important factors to test, which makes a lot of combinations: - Maven version: 2.2.x, 3.x - OS - phases: site, site-deploy, site:stage-deploy (run? jar?) should all be covered by our ITs: https://builds.apache.org/job/maven-site-plugin-2.x/ https://builds.apache.org/job/maven-site-plugin-3.x/ https://builds.apache.org/job/maven-site-plugin-3.x-m2/ I am aware that there are some important differences though, (some ITs are skipped with m3, or executed with different parameters), which would be important to review and document I guess. - deploy protocol: scp, webdav not really a site-plugin concern, rather wagon - report plugins used: I don't know how to describe without being a mess... We (devs) cannot test everything, even the more important it is to get user feedback. But at least, with maven-site-plugin 2.3 being out and almost equivalent (particularly when it comes to Doxia and Doxia Site Tools), we have a clear line to check if a problem with 3.0 is a regression from 2.3 or not so this would rather be an argument in favour of 3.0...? Then I'd better be for 3.0-RC-1 for the moment. I will support whatever the release manager decides, but I would prefer 3.0-final with a number of bug fix releases following, rather than an open interval of [RC-1, RC-2,...). More people will test the final release and there will be more pressure on us to push for bug-fix versions (which is good! :) ). -Lukas Such a discussion happened a lot of time in the past: 3.0 and 3.0-RC-1 are good choices, but not 3.0-beta-4 The release manager can choose and I'll be with him. But IMHO we need to ask for people to tell what conditions they tested. Regards, Hervé Le mercredi 6 juillet 2011, Olivier Lamy a écrit : No objections from me. beta cycle has started long time ago. 2011/7/6 Lukas Theusslltheu...@apache.org: Any objections to making this 3.0-final? AFAICT the plugin is functionally (almost) equivalent to the 2.x trunk version (only exception is MSITE-484?), so why keep the beta? -Lukas Dennis Lundberg wrote: Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
Lukas Theussl wrote: Hervé BOUTEMY wrote: the rationale behind not going directly to 3.0 was that site plugin is hard to test, particularly now that it is both compatible with Maven 2 and Maven 3, which is something really new and probably tested by only a few of us I don't quite agree with this rationale. Ease of testing is not a criterion for version naming IMO. The main criterion is how many *known* bugs and missing features there are left. So what are the open issues that we are aware about? If there are none or only a few, then let's call it final. If the people who are working on the release feel that the stuff is stable (which I do) then why not release it as such? sure, 3.0-beta-4 should at least be 3.0-RC-1, but perhaps not 3.0 immediately: I'm pretty sure we'll find some important problems when a lot of people try it seriously The most efficient way to get people to test something, is to release it! :) There are real important factors to test, which makes a lot of combinations: - Maven version: 2.2.x, 3.x - OS - phases: site, site-deploy, site:stage-deploy (run? jar?) should all be covered by our ITs: https://builds.apache.org/job/maven-site-plugin-2.x/ https://builds.apache.org/job/maven-site-plugin-3.x/ https://builds.apache.org/job/maven-site-plugin-3.x-m2/ I am aware that there are some important differences though, (some ITs are skipped with m3, or executed with different parameters), which would be important to review and document I guess. - deploy protocol: scp, webdav not really a site-plugin concern, rather wagon - report plugins used: I don't know how to describe without being a mess... We (devs) cannot test everything, even the more important it is to get user feedback. But at least, with maven-site-plugin 2.3 being out and almost equivalent (particularly when it comes to Doxia and Doxia Site Tools), we have a clear line to check if a problem with 3.0 is a regression from 2.3 or not so this would rather be an argument in favour of 3.0...? Then I'd better be for 3.0-RC-1 for the moment. I will support whatever the release manager decides, but I would prefer 3.0-final with a number of bug fix releases following, rather than an open interval of [RC-1, RC-2,...). More people will test the final release and there will be more pressure on us to push for bug-fix versions (which is good! :) ). From user's perspective: +1 Especially since this is the first version that can be used by M3 and M2. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
We've been running the beta for (I don't know how many) months, and works better than it ever has. I agree with Lukas; release it. On Thu, Jul 7, 2011 at 2:26 AM, Lukas Theussl ltheu...@apache.org wrote: Hervé BOUTEMY wrote: the rationale behind not going directly to 3.0 was that site plugin is hard to test, particularly now that it is both compatible with Maven 2 and Maven 3, which is something really new and probably tested by only a few of us I don't quite agree with this rationale. Ease of testing is not a criterion for version naming IMO. The main criterion is how many *known* bugs and missing features there are left. So what are the open issues that we are aware about? If there are none or only a few, then let's call it final. If the people who are working on the release feel that the stuff is stable (which I do) then why not release it as such? sure, 3.0-beta-4 should at least be 3.0-RC-1, but perhaps not 3.0 immediately: I'm pretty sure we'll find some important problems when a lot of people try it seriously The most efficient way to get people to test something, is to release it! :) There are real important factors to test, which makes a lot of combinations: - Maven version: 2.2.x, 3.x - OS - phases: site, site-deploy, site:stage-deploy (run? jar?) should all be covered by our ITs: https://builds.apache.org/job/maven-site-plugin-2.x/ https://builds.apache.org/job/maven-site-plugin-3.x/ https://builds.apache.org/job/maven-site-plugin-3.x-m2/ I am aware that there are some important differences though, (some ITs are skipped with m3, or executed with different parameters), which would be important to review and document I guess. - deploy protocol: scp, webdav not really a site-plugin concern, rather wagon - report plugins used: I don't know how to describe without being a mess... We (devs) cannot test everything, even the more important it is to get user feedback. But at least, with maven-site-plugin 2.3 being out and almost equivalent (particularly when it comes to Doxia and Doxia Site Tools), we have a clear line to check if a problem with 3.0 is a regression from 2.3 or not so this would rather be an argument in favour of 3.0...? Then I'd better be for 3.0-RC-1 for the moment. I will support whatever the release manager decides, but I would prefer 3.0-final with a number of bug fix releases following, rather than an open interval of [RC-1, RC-2,...). More people will test the final release and there will be more pressure on us to push for bug-fix versions (which is good! :) ). -Lukas Such a discussion happened a lot of time in the past: 3.0 and 3.0-RC-1 are good choices, but not 3.0-beta-4 The release manager can choose and I'll be with him. But IMHO we need to ask for people to tell what conditions they tested. Regards, Hervé Le mercredi 6 juillet 2011, Olivier Lamy a écrit : No objections from me. beta cycle has started long time ago. 2011/7/6 Lukas Theusslltheu...@apache.org: Any objections to making this 3.0-final? AFAICT the plugin is functionally (almost) equivalent to the 2.x trunk version (only exception is MSITE-484?), so why keep the beta? -Lukas Dennis Lundberg wrote: Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
I forgot we had this great Jenkins instance with lots of OSes and configuration combinations, and improved ITs to cover a lot of cases (more than +50% over 3.0-beta-3) Then I'm now confident that we can release a good quality even without a lot of users having done tests themselves. +1 for 3.0 final: it won't be over-estimated! Regards, Hervé Le jeudi 7 juillet 2011, Lukas Theussl a écrit : Hervé BOUTEMY wrote: the rationale behind not going directly to 3.0 was that site plugin is hard to test, particularly now that it is both compatible with Maven 2 and Maven 3, which is something really new and probably tested by only a few of us I don't quite agree with this rationale. Ease of testing is not a criterion for version naming IMO. The main criterion is how many *known* bugs and missing features there are left. So what are the open issues that we are aware about? If there are none or only a few, then let's call it final. If the people who are working on the release feel that the stuff is stable (which I do) then why not release it as such? sure, 3.0-beta-4 should at least be 3.0-RC-1, but perhaps not 3.0 immediately: I'm pretty sure we'll find some important problems when a lot of people try it seriously The most efficient way to get people to test something, is to release it! :) There are real important factors to test, which makes a lot of combinations: - Maven version: 2.2.x, 3.x - OS - phases: site, site-deploy, site:stage-deploy (run? jar?) should all be covered by our ITs: https://builds.apache.org/job/maven-site-plugin-2.x/ https://builds.apache.org/job/maven-site-plugin-3.x/ https://builds.apache.org/job/maven-site-plugin-3.x-m2/ I am aware that there are some important differences though, (some ITs are skipped with m3, or executed with different parameters), which would be important to review and document I guess. - deploy protocol: scp, webdav not really a site-plugin concern, rather wagon - report plugins used: I don't know how to describe without being a mess... We (devs) cannot test everything, even the more important it is to get user feedback. But at least, with maven-site-plugin 2.3 being out and almost equivalent (particularly when it comes to Doxia and Doxia Site Tools), we have a clear line to check if a problem with 3.0 is a regression from 2.3 or not so this would rather be an argument in favour of 3.0...? Then I'd better be for 3.0-RC-1 for the moment. I will support whatever the release manager decides, but I would prefer 3.0-final with a number of bug fix releases following, rather than an open interval of [RC-1, RC-2,...). More people will test the final release and there will be more pressure on us to push for bug-fix versions (which is good! :) ). -Lukas Such a discussion happened a lot of time in the past: 3.0 and 3.0-RC-1 are good choices, but not 3.0-beta-4 The release manager can choose and I'll be with him. But IMHO we need to ask for people to tell what conditions they tested. Regards, Hervé Le mercredi 6 juillet 2011, Olivier Lamy a écrit : No objections from me. beta cycle has started long time ago. 2011/7/6 Lukas Theusslltheu...@apache.org: Any objections to making this 3.0-final? AFAICT the plugin is functionally (almost) equivalent to the 2.x trunk version (only exception is MSITE-484?), so why keep the beta? -Lukas Dennis Lundberg wrote: Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
On Thu, 7 Jul 2011 21:22:43 +0200 Hervé BOUTEMY herve.bout...@free.fr wrote: I forgot we had this great Jenkins instance with lots of OSes and configuration combinations, and improved ITs to cover a lot of cases (more than +50% over 3.0-beta-3) Then I'm now confident that we can release a good quality even without a lot of users having done tests themselves. +1 for 3.0 final: it won't be over-estimated! Something was detected as a regression in last stable version of version 2.3 of the site plugin Lukas added a IT for this case [1] and has also a ticket [2]. If this is not ok, this is for my part a none reason to a final release ? I don't know the difficulty to fix this problem... [1] http://svn.apache.org/viewvc?rev=1126420view=rev [2] http://jira.codehaus.org/browse/MSITE-585 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
Any objections to making this 3.0-final? AFAICT the plugin is functionally (almost) equivalent to the 2.x trunk version (only exception is MSITE-484?), so why keep the beta? -Lukas Dennis Lundberg wrote: Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
No objections from me. beta cycle has started long time ago. 2011/7/6 Lukas Theussl ltheu...@apache.org: Any objections to making this 3.0-final? AFAICT the plugin is functionally (almost) equivalent to the 2.x trunk version (only exception is MSITE-484?), so why keep the beta? -Lukas Dennis Lundberg wrote: Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy | http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
the rationale behind not going directly to 3.0 was that site plugin is hard to test, particularly now that it is both compatible with Maven 2 and Maven 3, which is something really new and probably tested by only a few of us sure, 3.0-beta-4 should at least be 3.0-RC-1, but perhaps not 3.0 immediately: I'm pretty sure we'll find some important problems when a lot of people try it seriously There are real important factors to test, which makes a lot of combinations: - Maven version: 2.2.x, 3.x - OS - phases: site, site-deploy, site:stage-deploy (run? jar?) - deploy protocol: scp, webdav - report plugins used: I don't know how to describe without being a mess... But at least, with maven-site-plugin 2.3 being out and almost equivalent (particularly when it comes to Doxia and Doxia Site Tools), we have a clear line to check if a problem with 3.0 is a regression from 2.3 or not Then I'd better be for 3.0-RC-1 for the moment. Such a discussion happened a lot of time in the past: 3.0 and 3.0-RC-1 are good choices, but not 3.0-beta-4 The release manager can choose and I'll be with him. But IMHO we need to ask for people to tell what conditions they tested. Regards, Hervé Le mercredi 6 juillet 2011, Olivier Lamy a écrit : No objections from me. beta cycle has started long time ago. 2011/7/6 Lukas Theussl ltheu...@apache.org: Any objections to making this 3.0-final? AFAICT the plugin is functionally (almost) equivalent to the 2.x trunk version (only exception is MSITE-484?), so why keep the beta? -Lukas Dennis Lundberg wrote: Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
On 2011-07-04 20:11, Dennis Lundberg wrote: On 2011-07-03 00:14, Hervé BOUTEMY wrote: AFAIK, code is ok: I'm closing MSITE-560 Great, thanks! the only thing to confirm is the documentation: there is a TODO in maven-3.apt.vm that we should check carefully: I'm personnally lost on this one. I'll have a look at it. From what I can tell a reportSets/reportSet/reports/report and reports/report are treated as equals in maven-reporting-exec. I don't know whether they are both supported in Maven 2. Perhaps Olivier knows? To pull off this release we must also make a first release of maven-reporting-exec, right? Since you have done most of the work on it, would you like to release it? If not I can do it. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
2011/7/5 Dennis Lundberg denn...@apache.org: On 2011-07-04 20:11, Dennis Lundberg wrote: On 2011-07-03 00:14, Hervé BOUTEMY wrote: AFAIK, code is ok: I'm closing MSITE-560 Great, thanks! the only thing to confirm is the documentation: there is a TODO in maven-3.apt.vm that we should check carefully: I'm personnally lost on this one. I'll have a look at it. From what I can tell a reportSets/reportSet/reports/report and reports/report are treated as equals in maven-reporting-exec. I don't know whether they are both supported in Maven 2. Perhaps Olivier knows? Yup correct. I don't really understand the TODO here. Maybe to explain that something is not (yet) supported in site plugin for m3. This syntax (same plugin but different configuration for report : The complex xml tree with reportSet was in place for that.) : reportSets reportSet configuration wineBordeaux/wine /configuration reports reportfoo/report /reports /reportSet reportSet configuration wineAnjou/wine /configuration reports reportbar/report /reports /reportSet /reportSets To pull off this release we must also make a first release of maven-reporting-exec, right? Since you have done most of the work on it, would you like to release it? If not I can do it. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy | http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
On 2011-07-05 22:00, Olivier Lamy wrote: 2011/7/5 Dennis Lundberg denn...@apache.org: On 2011-07-04 20:11, Dennis Lundberg wrote: On 2011-07-03 00:14, Hervé BOUTEMY wrote: AFAIK, code is ok: I'm closing MSITE-560 Great, thanks! the only thing to confirm is the documentation: there is a TODO in maven-3.apt.vm that we should check carefully: I'm personnally lost on this one. I'll have a look at it. From what I can tell a reportSets/reportSet/reports/report and reports/report are treated as equals in maven-reporting-exec. I don't know whether they are both supported in Maven 2. Perhaps Olivier knows? Yup correct. I don't really understand the TODO here. Maybe to explain that something is not (yet) supported in site plugin for m3. This syntax (same plugin but different configuration for report : The complex xml tree with reportSet was in place for that.) : reportSets reportSet configuration wineBordeaux/wine /configuration reports reportfoo/report /reports /reportSet reportSet configuration wineAnjou/wine /configuration reports reportbar/report /reports /reportSet /reportSets I seems to me that the reportSets syntax has more ways of applying configuration than reports do. It can have configuration on several different levels, and also have different configurations for different reports. That said, we should have an example that shows how to do the same thing in Maven 2 and Maven 3. Not two different things, like it is now. I'll try to revise the examples so that it compares apples to apples, and not apples to oranges. To avoid getting into configuration madness, I'll try to keep them as simple as possible. To pull off this release we must also make a first release of maven-reporting-exec, right? Since you have done most of the work on it, would you like to release it? If not I can do it. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
I worked on IRC with Olivier to understand more precisely what is available. Then added documentation to maven-reporting-exec and maven-site-plugin. I won't repeat what is in the doc: please ping if it is not clear Regards, Hervé Le mardi 5 juillet 2011, Dennis Lundberg a écrit : On 2011-07-05 22:00, Olivier Lamy wrote: 2011/7/5 Dennis Lundberg denn...@apache.org: On 2011-07-04 20:11, Dennis Lundberg wrote: On 2011-07-03 00:14, Hervé BOUTEMY wrote: AFAIK, code is ok: I'm closing MSITE-560 Great, thanks! the only thing to confirm is the documentation: there is a TODO in maven-3.apt.vm that we should check carefully: I'm personnally lost on this one. I'll have a look at it. From what I can tell a reportSets/reportSet/reports/report and reports/report are treated as equals in maven-reporting-exec. I don't know whether they are both supported in Maven 2. Perhaps Olivier knows? Yup correct. I don't really understand the TODO here. Maybe to explain that something is not (yet) supported in site plugin for m3. This syntax (same plugin but different configuration for report : The complex xml tree with reportSet was in place for that.) : reportSets reportSet configuration wineBordeaux/wine /configuration reports reportfoo/report /reports /reportSet reportSet configuration wineAnjou/wine /configuration reports reportbar/report /reports /reportSet /reportSets I seems to me that the reportSets syntax has more ways of applying configuration than reports do. It can have configuration on several different levels, and also have different configurations for different reports. That said, we should have an example that shows how to do the same thing in Maven 2 and Maven 3. Not two different things, like it is now. I'll try to revise the examples so that it compares apples to apples, and not apples to oranges. To avoid getting into configuration madness, I'll try to keep them as simple as possible. To pull off this release we must also make a first release of maven-reporting-exec, right? Since you have done most of the work on it, would you like to release it? If not I can do it. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
Thanks ! :-) 2011/7/6 Hervé BOUTEMY herve.bout...@free.fr: I worked on IRC with Olivier to understand more precisely what is available. Then added documentation to maven-reporting-exec and maven-site-plugin. I won't repeat what is in the doc: please ping if it is not clear Regards, Hervé Le mardi 5 juillet 2011, Dennis Lundberg a écrit : On 2011-07-05 22:00, Olivier Lamy wrote: 2011/7/5 Dennis Lundberg denn...@apache.org: On 2011-07-04 20:11, Dennis Lundberg wrote: On 2011-07-03 00:14, Hervé BOUTEMY wrote: AFAIK, code is ok: I'm closing MSITE-560 Great, thanks! the only thing to confirm is the documentation: there is a TODO in maven-3.apt.vm that we should check carefully: I'm personnally lost on this one. I'll have a look at it. From what I can tell a reportSets/reportSet/reports/report and reports/report are treated as equals in maven-reporting-exec. I don't know whether they are both supported in Maven 2. Perhaps Olivier knows? Yup correct. I don't really understand the TODO here. Maybe to explain that something is not (yet) supported in site plugin for m3. This syntax (same plugin but different configuration for report : The complex xml tree with reportSet was in place for that.) : reportSets reportSet configuration wineBordeaux/wine /configuration reports reportfoo/report /reports /reportSet reportSet configuration wineAnjou/wine /configuration reports reportbar/report /reports /reportSet /reportSets I seems to me that the reportSets syntax has more ways of applying configuration than reports do. It can have configuration on several different levels, and also have different configurations for different reports. That said, we should have an example that shows how to do the same thing in Maven 2 and Maven 3. Not two different things, like it is now. I'll try to revise the examples so that it compares apples to apples, and not apples to oranges. To avoid getting into configuration madness, I'll try to keep them as simple as possible. To pull off this release we must also make a first release of maven-reporting-exec, right? Since you have done most of the work on it, would you like to release it? If not I can do it. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy | http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
On 2011-07-03 00:14, Hervé BOUTEMY wrote: AFAIK, code is ok: I'm closing MSITE-560 Great, thanks! the only thing to confirm is the documentation: there is a TODO in maven-3.apt.vm that we should check carefully: I'm personnally lost on this one. I'll have a look at it. To pull off this release we must also make a first release of maven-reporting-exec, right? Since you have done most of the work on it, would you like to release it? If not I can do it. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
Hello, 2011/7/4 Dennis Lundberg denn...@apache.org: On 2011-07-03 00:14, Hervé BOUTEMY wrote: AFAIK, code is ok: I'm closing MSITE-560 Great, thanks! the only thing to confirm is the documentation: there is a TODO in maven-3.apt.vm that we should check carefully: I'm personnally lost on this one. I'll have a look at it. To pull off this release we must also make a first release of maven-reporting-exec, right? Since you have done most of the work on it, would you like to release it? If not I can do it. So it looks Hervé just nominate myself as volunteer while chating on irc :-). I will release this component. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy | http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Is Maven Site Plugin 3.0-beta-4 ready for release?
Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
AFAIK, code is ok: I'm closing MSITE-560 the only thing to confirm is the documentation: there is a TODO in maven-3.apt.vm that we should check carefully: I'm personnally lost on this one. Regards, Hervé Le samedi 2 juillet 2011, Dennis Lundberg a écrit : Hi What's the status on this? I know Hervé worked on extracting a shared component (maven-reporting-exec) for the Maven 3 specific parts of the plugin. Did you finish with that? I would like to push for a release of Site Plugin 3 shortly. The only issue left according to JIRA is this one: http://jira.codehaus.org/browse/MSITE-560 There are a lot stuff fixed already, and we need to get this out so that Maven 3 users can benefit from them. Do we want/need to add anything more before the release? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
