You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2009/10/18 20:13:50 UTC
[jira] Created: (TILES-480) Use release:stage goal when releasing
Use release:stage goal when releasing
-------------------------------------
Key: TILES-480
URL: https://issues.apache.org/struts/browse/TILES-480
Project: Tiles
Issue Type: Improvement
Components: building
Affects Versions: 2.1.3
Reporter: Antonio Petrelli
Fix For: 2.2.2
Currently the deployment repository points to a staging directory, to make the "release:perform" goal work.
However, now it is possible to use the release:stage goal, that allows to deploy to a staging plugin and then copy it to the repository later.
It should be configured to work correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TILES-480) Use release:stage goal when releasing
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli updated TILES-480:
-----------------------------------
Assignee: Antonio Petrelli
> Use release:stage goal when releasing
> -------------------------------------
>
> Key: TILES-480
> URL: https://issues.apache.org/struts/browse/TILES-480
> Project: Tiles
> Issue Type: Improvement
> Components: building
> Affects Versions: 2.1.3
> Reporter: Antonio Petrelli
> Assignee: Antonio Petrelli
> Fix For: 2.2.2
>
>
> Currently the deployment repository points to a staging directory, to make the "release:perform" goal work.
> However, now it is possible to use the release:stage goal, that allows to deploy to a staging plugin and then copy it to the repository later.
> It should be configured to work correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TILES-480) Use release:stage goal when releasing
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli closed TILES-480.
----------------------------------
Resolution: Fixed
> Use release:stage goal when releasing
> -------------------------------------
>
> Key: TILES-480
> URL: https://issues.apache.org/struts/browse/TILES-480
> Project: Tiles
> Issue Type: Improvement
> Components: building
> Affects Versions: 2.1.3
> Reporter: Antonio Petrelli
> Assignee: Antonio Petrelli
> Fix For: 2.2.2
>
>
> Currently the deployment repository points to a staging directory, to make the "release:perform" goal work.
> However, now it is possible to use the release:stage goal, that allows to deploy to a staging plugin and then copy it to the repository later.
> It should be configured to work correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TILES-480) Use release:stage goal when releasing
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli updated TILES-480:
-----------------------------------
Changed repository and configured the staging repository to be used with release:stage goal.
> Use release:stage goal when releasing
> -------------------------------------
>
> Key: TILES-480
> URL: https://issues.apache.org/struts/browse/TILES-480
> Project: Tiles
> Issue Type: Improvement
> Components: building
> Affects Versions: 2.1.3
> Reporter: Antonio Petrelli
> Assignee: Antonio Petrelli
> Fix For: 2.2.2
>
>
> Currently the deployment repository points to a staging directory, to make the "release:perform" goal work.
> However, now it is possible to use the release:stage goal, that allows to deploy to a staging plugin and then copy it to the repository later.
> It should be configured to work correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.