[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-4188:
Fix Version/s: 3.2.1
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: 3.1.1
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: 3.2.1
>
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-4188:
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: 3.1.1
>Reporter: Christian Schulte
>Priority: Minor
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-4188:
Affects Version/s: (was: Issues to be reviewed for 3.x)
3.1.1
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: 3.1.1
>Reporter: Christian Schulte
>Priority: Minor
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-4188.
--
Resolution: Fixed
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: Issues to be reviewed for 3.x
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339943#comment-339943
]
Jason van Zyl commented on MNG-4188:
This is effectively true now with the addition of
AbstractMavenLifecycleParticipant#afterSessionEnd where you can hook in code at
the definitive end of the build.
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: Issues to be reviewed for 3.x
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339942#comment-339942
]
Jason van Zyl commented on MNG-4188:
We effectively have this now with
AbstractMavenLifecycleParticipant#afterSessionEnd but I think we need to clean
this up as part of 4.0.0
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: Issues to be reviewed for 3.x
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339852#comment-339852
]
Charlie Mordant edited comment on MNG-4188 at 1/23/14 3:17 AM:
---
What about a plugin xml element?
{code}
myPluginWhoNeedToExecuteAnOtherIfItFails
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsPhase
...
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsPhase
...
{code}
was (Author: tcharl):
What about a plugin xml element?
{code}
myPluginWhoNeedToExecuteAnOtherIfItFails
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
{code}
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: Issues to be reviewed for 3.x
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339852#comment-339852
]
Charlie Mordant edited comment on MNG-4188 at 1/23/14 3:15 AM:
---
What about a plugin xml element?
{quote}
myPluginWhoNeedToExecuteAnOtherIfItFails
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
{quote}
was (Author: tcharl):
What about a plugin xml element?
myPluginWhoNeedToExecuteAnOtherIfItFails
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: Issues to be reviewed for 3.x
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339852#comment-339852
]
Charlie Mordant edited comment on MNG-4188 at 1/23/14 3:16 AM:
---
What about a plugin xml element?
{code}
myPluginWhoNeedToExecuteAnOtherIfItFails
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
{code}
was (Author: tcharl):
What about a plugin xml element?
{quote}
myPluginWhoNeedToExecuteAnOtherIfItFails
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
{quote}
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: Issues to be reviewed for 3.x
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339852#comment-339852
]
Charlie Mordant commented on MNG-4188:
--
What about a plugin xml element?
myPluginWhoNeedToExecuteAnOtherIfItFails
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
myPluginOrExecutionIdWhichMuchBeExecutedIfBuildFailsAndThatWeHaveNotReachedItsConventionalRunPhase
...
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: Issues to be reviewed for 3.x
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-4188) Add a 'finally' phase.
[
https://jira.codehaus.org/browse/MNG-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319817#comment-319817
]
Robert Scholte commented on MNG-4188:
-
Maybe a {{finally}}-phase is not the right solution.
There are several phases which always belong together:
* pre-integration-test, integration-test, post-integration-test
* pre-clean, clean, post-clean
* pre-site, site, post-site
In all these cases it makes more sense to have the following construction:
{code}
try
{
// execute pre-
// execute
}
finally
{
// execute post-
}
{code}
But we would still need a mechanism for those users who really, really want to
execute up until the specified phase.
Maybe something like {{mvn integration-test.}} //notice the end-dot!
> Add a 'finally' phase.
> --
>
> Key: MNG-4188
> URL: https://jira.codehaus.org/browse/MNG-4188
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Plugins and Lifecycle
>Affects Versions: Issues to be reviewed for 3.x
>Reporter: Christian Schulte
>Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
>
> When Maven executes a lifecycle, it does not execute any phases succeeding a
> failing phase. It would be great if Maven supports a 'finally' phase, which
> is guaranteed to run regardless of the state of the lifecycle just like a
> Java 'finally' block. The use case I would need such a phase for is the
> following:
> {code}
>
> sourceforge-shell
>
> false
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> org.apache.ant
> ant-jsch
> 1.7.1
>
>
>
>
> create-sourceforge-shell
> validate
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> create-sourceforge-shell-site
> pre-site
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="create" timeout="30" />
>
>
>
>
> shutdown-sourceforge-shell
> deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
> shutdown-sourceforge-shell-site
> site-deploy
>
> run
>
>
>
> username="${sf.username},${sf.project}" password="${sf.password}"
> command="shutdown" timeout="30" />
>
>
>
>
>
>
>
>
>
>
> {code}
> I am currently using this profile when deploying to sourceforge. The problem
> is, that the shell won't get shutdown, whenever a build fails. It needs to
> get shutdown, so that a build for another SF project can succeed. In the
> example above, the two executions 'shutdown-sourceforge-shell' and
> 'shutdown-sourceforge-shell-site' could be bound to a 'finally' phase and
> could shutdown the shell regardless of the outcome of the build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
