You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Tim Morrow (JIRA)" <ji...@apache.org> on 2007/04/06 18:02:34 UTC
[jira] Created: (AMQ-1224) Maven build doesn't fail even when maven
plugin fails to start broker
Maven build doesn't fail even when maven plugin fails to start broker
---------------------------------------------------------------------
Key: AMQ-1224
URL: https://issues.apache.org/activemq/browse/AMQ-1224
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 4.2.0
Reporter: Tim Morrow
Priority: Minor
Original post here: http://www.nabble.com/Maven-build-doesn%27t-fail-even-when-maven-plugin-fails-to-start-broker-tf3537412s2354.html
If the maven plugin fails to start the broker for whatever reason (e.g. there is already a process listening on the broker port) the error is logged but the maven build proceeds. I would have expected the maven build to error out.
It would appear that this is because the class that the plugin invokes (org.apache.activemq.console.Main) sucks up all throwables.
Reproduce by simply starting something on port 61616 then trying to run the broker via the maven plugin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1224) Maven build doesn't fail even when
maven plugin fails to start broker
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Strachan reassigned AMQ-1224:
-----------------------------------
Assignee: Adrian Co
any chance you could take a look at this when you get chance?
> Maven build doesn't fail even when maven plugin fails to start broker
> ---------------------------------------------------------------------
>
> Key: AMQ-1224
> URL: https://issues.apache.org/activemq/browse/AMQ-1224
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Tim Morrow
> Assignee: Adrian Co
> Priority: Minor
>
> Original post here: http://www.nabble.com/Maven-build-doesn%27t-fail-even-when-maven-plugin-fails-to-start-broker-tf3537412s2354.html
> If the maven plugin fails to start the broker for whatever reason (e.g. there is already a process listening on the broker port) the error is logged but the maven build proceeds. I would have expected the maven build to error out.
> It would appear that this is because the class that the plugin invokes (org.apache.activemq.console.Main) sucks up all throwables.
> Reproduce by simply starting something on port 61616 then trying to run the broker via the maven plugin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1224) Maven build doesn't fail even when
maven plugin fails to start broker
Posted by "Adrian Co (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Co resolved AMQ-1224.
----------------------------
Resolution: Fixed
Fix Version/s: 5.0.0
Fixed in - http://svn.apache.org/viewvc?view=rev&rev=547575
> Maven build doesn't fail even when maven plugin fails to start broker
> ---------------------------------------------------------------------
>
> Key: AMQ-1224
> URL: https://issues.apache.org/activemq/browse/AMQ-1224
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Tim Morrow
> Assignee: Adrian Co
> Priority: Minor
> Fix For: 5.0.0
>
>
> Original post here: http://www.nabble.com/Maven-build-doesn%27t-fail-even-when-maven-plugin-fails-to-start-broker-tf3537412s2354.html
> If the maven plugin fails to start the broker for whatever reason (e.g. there is already a process listening on the broker port) the error is logged but the maven build proceeds. I would have expected the maven build to error out.
> It would appear that this is because the class that the plugin invokes (org.apache.activemq.console.Main) sucks up all throwables.
> Reproduce by simply starting something on port 61616 then trying to run the broker via the maven plugin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.