commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <>
Subject [jira] Commented: (COMMONSSITE-26) Add a /distributionManagement/site element
Date Fri, 21 Mar 2008 22:17:25 GMT


Rahul Akolkar commented on COMMONSSITE-26:

I believe the general solution to that is having more "robust" sites (as I mentioned before
on the mailing list). Also staging and deploying require different mvn commands so we have
to ask / document folks to be a little (more?) aware.

And I wasn't thinking about adding it to any profile. In fact, the more I look at the parent
pom, I don't think the distributionManagement sections should be in profiles at all :-)

Since I haven't followed m2 discussions lately, I followed the profiles through the archives.
They came to life in r439540:

The release profile's original purpose was to deploy to the rsync repo. This is not of interest
anymore. This point, as it happens, has been raised before :-)  

We should move the distributionManagement section out of profiles, see said section in this
pom, for example:

Lets suspend this for a few, and I will post a process-level email to the dev list first.

> Add a /distributionManagement/site element
> ------------------------------------------
>                 Key: COMMONSSITE-26
>                 URL:
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Parent Pom
>            Reporter: Rahul Akolkar
> To enable sites to be deployed using the m2 site plugin, we should add this to the Commons
Parent POM:
> {code:xml}
> <distributionManagement>
>   <site>
>     <id>apache-site</id>
>     <name>Apache Commons Website</name>
>     <url>${commons.deployment.protocol}://${commons.componentid}</url>
>   </site>
> </distributionManagement>
> {code}

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message