I didn't check if it is needed or not, I just did what was not obvious
you can either test and do the upgrade if you have the problem, or just
upgrade to be sure since it is easy
Regards,
Hervé
Le mercredi 11 juillet 2012 08:17:33 Barrie Treloar a écrit :
> On Wed, Jul 11, 2012 at 7:48 AM, Herv
On Wed, Jul 11, 2012 at 7:48 AM, Hervé BOUTEMY wrote:
> I did the work on the plugin in r1359931 and prepared the htaccess in r1359934
Thanks.
I take it the "upgrade m-site-p to 3.1" wasn't needed?
I can't see it being specifically being defined so we are just
inheriting from maven-parent:21
--
I did the work on the plugin in r1359931 and prepared the htaccess in r1359934
Regards,
Hervé
Le mardi 10 juillet 2012 08:18:54 Hervé BOUTEMY a écrit :
> no stress, the update is easy
> just:
> 1. remove m-site-p plugin configuration from m-enforcer-p 's pom.xml
> 2. add a RedirectMatch rule int
no stress, the update is easy
just:
1. remove m-site-p plugin configuration from m-enforcer-p 's pom.xml
2. add a RedirectMatch rule into .htaccess [1] just after maven-archetype-
plugin rule (to sort alphabetically)
Et voilà :)
The plugin will be staged as a normal module, the redirect rule simply
On Tue, Jul 10, 2012 at 9:51 AM, Hervé BOUTEMY wrote:
> ah ok, I got it
> it's a specific configuration written in maven-enforcer-plugin
[del]
> IMHO, enforcer should switch. Tell me if you need help.
Ahh, my itch was to fix the bug and push a release.
I'm not sure if it stretches to upgrading :)
ah ok, I got it
it's a specific configuration written in maven-enforcer-plugin
IIUC, it's a try to handle the case where a project (defining its top level
directory) contains a plugin (published in /plugins/), with the question of
the staging directory.
This is a question common with archetype,
On Tue, Jul 10, 2012 at 6:24 AM, Hervé BOUTEMY wrote:
>> From what I can tell the automated steps now put things at
>> /www/maven.apache.org/staging
> no, there is no "staging" directory.
> Where did you get this info?
>From the command logs..
> mvn site site:stage-deploy -Preporting
...
INFO] -
Le lundi 9 juillet 2012 10:30:36 Barrie Treloar a écrit :
> Can someone have a look at the web page
> http://maven.apache.org/developers/release/maven-plugin-release.html
> and compare that automated results with the recommended manual steps.
>
> From what I can tell the automated steps now put th
Can someone have a look at the web page
http://maven.apache.org/developers/release/maven-plugin-release.html
and compare that automated results with the recommended manual steps.
>From what I can tell the automated steps now put things at
/www/maven.apache.org/staging
But the manual steps say
/www
2012/7/6 Barrie Treloar :
> Just following
> http://maven.apache.org/developers/release/maven-plugin-release.html
> and Staging the latest documentation.
>
> The stage completed successfully and its been a few hours since but
> the staging documentation is still not available.
> I have not verifie
Just following
http://maven.apache.org/developers/release/maven-plugin-release.html
and Staging the latest documentation.
The stage completed successfully and its been a few hours since but
the staging documentation is still not available.
I have not verified the folder permissions to 0775 and fi
11 matches
Mail list logo
