A Mojo for running the application could be useful

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.0-alpha-2
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

If one could execute, e.g.
mvn webstart:run
to test the application locally (before deploying it), that would be very useful.

We currently use the following antrun configuration to execute the application:

<profiles>
<profile>
<id>run</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>install</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<tasks>
<java classname="${appMainClass}" failonerror="true" fork="true">
<sysproperty key="swing.aatext" value="true"/>
<classpath>
<path refid="maven.runtime.classpath"/>
</classpath>
</java>
</tasks>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jerome Lacoste added a comment -

Havard, is that something you would like to contribute ?

Show
Jerome Lacoste added a comment - Havard, is that something you would like to contribute ?
Hide
Permalink
Jerome Lacoste added a comment -

Havard, have you tried to use the exec mojo ? It can do everything you have above, and I can't see what a new mojo would bring in the webstart plugin.

Or do you need to run the javaws command ?

Show
Jerome Lacoste added a comment - Havard, have you tried to use the exec mojo ? It can do everything you have above, and I can't see what a new mojo would bring in the webstart plugin. Or do you need to run the javaws command ?
Hide
Permalink
Havard Bjastad added a comment -

I hadn't tried the exec mojo - until now. It didn't work (for some reason didn't pick up the ${appMainClass} that we have defined in sub-poms. I didn't bother spending more time on it, as it would only marginally improve what we have.

I guess what a new mojo in the webstart plugin would add, is simplicity - fewer lines of XML in the POM + fewer places to maintain configuration. But it's not a big deal. In fact, the antrun plugin works well enough - which is why I haven't implemented (and contributed) a solution yet. I still think it makes sense to do (because webstart plugin has all the needed configuration, so the new mojo would make life simpler for the webstart plugin users), so can we please keep it open until I find some time?

Show
Havard Bjastad added a comment - I hadn't tried the exec mojo - until now. It didn't work (for some reason didn't pick up the ${appMainClass} that we have defined in sub-poms. I didn't bother spending more time on it, as it would only marginally improve what we have. I guess what a new mojo in the webstart plugin would add, is simplicity - fewer lines of XML in the POM + fewer places to maintain configuration. But it's not a big deal. In fact, the antrun plugin works well enough - which is why I haven't implemented (and contributed) a solution yet. I still think it makes sense to do (because webstart plugin has all the needed configuration, so the new mojo would make life simpler for the webstart plugin users), so can we please keep it open until I find some time?
Hide
Permalink
Jerome Lacoste added a comment -

> can we please keep it open until I find some time?

sure

Show
Jerome Lacoste added a comment - > can we please keep it open until I find some time? sure

People

  • Assignee:
    Unassigned
    Reporter:
    Havard Bjastad
Vote (1)
Watch (1)

Dates

  • Created:
    Updated: