You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2010/05/06 01:54:02 UTC
[jira] Commented: (COMMONSSITE-55) Enable deployment to local
folder
[ https://issues.apache.org/jira/browse/COMMONSSITE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864591#action_12864591 ]
Sebb commented on COMMONSSITE-55:
---------------------------------
For example, the following profile could be added to commons-parent:
{code}
<profile>
<id>localdeploy</id>
<properties>
<altDeploymentRepository>id::default::file:${user.home}/${commons.componentid}</altDeploymentRepository>
</properties>
</profile>
{code}
> Enable deployment to local folder
> ---------------------------------
>
> Key: COMMONSSITE-55
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-55
> Project: Commons All
> Issue Type: New Feature
> Components: Commons Parent Pom
> Reporter: Sebb
>
> The Maven deploy plugin supports the file: protocol.
> This would be very useful for testing deployment without needing to connect to people.a.o.
> If the artifacts look OK, they could then be packed and uploaded as described in http://commons.apache.org/releases/prepare.html#Create_the_Release_Candidate_Website, but with the benefit that the generated artifacts are guaranteed to be the same.
> Patch to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.