Before Launch

I am trying out the 12 EAP and really love the new Before Launch
section. But it seems the before tasks are not finished before the launch starts which makes the whole thing kind of pointless!?! Am I missing something?

My "config" is: Run maven package target "before launch" and want to "deploy at the server startup" the maven package result (ear/war), but the deployment starts before the maven package is finished so the old version of package or nothing is deployed.

Any workarounf for this?

Thanks
/Olle

4 comments
Comment actions Permalink

The before launch feature works fine for me. I can run a maven package goal before starting Tomcat without any issue. I recommend you open a bug report. There might be something specific with your configuration that is causing a problem.

0
Comment actions Permalink

Order of "before launch" tasks make sense. Artefact deployment should be below artefact building. Please, check the order.

0
Comment actions Permalink

Sorry I don't understand what you mean.

I have the "Run JBoss Server" configuration in which you select something to deploy, in my case an ear file. I select before launch "maven package" (to build the the ear to deploy) so I do not specify Artefact deployment? I think the maven package start first but the JBoss server is started in parallell before the maven package is finished so the old ear is deployed before the new has been created.

But while writing this repsponse I tried Leda 123.23 and it seems to work correctly there! The JBoss start is delayed until after the maven package is finished (now I regret uninstalling 122.813 to verify the difference). :-)

0
Comment actions Permalink

I didn't notice that JBoss has it's own deployment settings. In "before launch" you can also specify some artefacts to deploy before or after maven build. It's common and generic part of UI for all types of run/debug configuration.
I see, it makes a mess of usability in case of JBoss.

0

Please sign in to leave a comment.