[
http://jira.codehaus.org/browse/MJBOSS-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier closed MJBOSS-47.
---------------------------
Resolution: Fixed
Added the new mojo with some minor changes in
[r13288|http://fisheye.codehaus.org/changelog/mojo/trunk/mojo/jboss-maven-plugin?cs=13288].
Thanks for the contribution!
> Wait a given app to start
> -------------------------
>
> Key: MJBOSS-47
> URL: http://jira.codehaus.org/browse/MJBOSS-47
> Project: Maven 2.x JBoss Plugin
> Issue Type: New Feature
> Affects Versions: 1.4.0
> Reporter: Vinicius Kopcheski
> Assignee: Paul Gier
> Fix For: 1.5.0
>
> Attachments: WaitAppToStartMojo.java
>
>
> First of all, i'd to like to thank you for the great plugin. It has been very
> useful to me.
> I've been working on a environment using Hudson and this was one of the many
> plugin I found useful to me.
> I have many builds steps inside Hudson and one of them consist in copying
> (using hard-deploy goal) the EAR to jboss. After this copy, some functional
> tests are triggered.
> But the problem is functional tests starting immediately, so I a need a way
> to make Hudson wait until my EAR is started inside JBoss.
> One of the solutions was using the stop goal before hard-deploy, and then,
> start-and-wait. But it procudes a big overhead once I can have many EARs
> inside JBoss.
> So I write a goal called wait-app-to-start (attached) to suggest you a
> similar goal. This class ignores all the reusability and this plugin
> architecture, but it was the only way I found to write a new goal without
> making any change in the preexisting code.
> The earName parameter could be inferred from the fileName.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
