You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gustavo Orair (JIRA)" <ji...@apache.org> on 2015/09/07 02:56:45 UTC
[jira] [Updated] (MACR-3) Maven site should has an example with
adding Main Class
[ https://issues.apache.org/jira/browse/MACR-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gustavo Orair updated MACR-3:
-----------------------------
Description:
Maven ACR plugin should confirm if the resulting Manifest contain a setting for Main-Class, because The Java EE spec requires that app clients specify the main class (http://www.java.net/forum/topic/glassfish/glassfish/problems-using-java-web-start-application-client-libraries-not-found).
If Manifest does not contain Main-Class a warning should be emitted.
Also, It would be worth if some examples specifying Main-Class are added to the site http://maven.apache.org/plugins/maven-acr-plugin/.
In actual configuration, users tend to create application clients without Main-Class and may get strange errors while trying to launch the application client. One example of these errors, may be accessed in:
http://www.java.net/forum/topic/glassfish/glassfish/problems-using-java-web-start-application-client-libraries-not-found
was:
Maven ACR plugin should confirm if the resulting Manifest contain a setting for Main-Class, because The Java EE spec requires that app clients specify the main class (http://www.java.net/forum/topic/glassfish/glassfish/problems-using-java-web-start-application-client-libraries-not-found).
If Manifest does not contain Main-Class a warning should be emitted.
Also, It would be very valuable if some examples specifying Main-Class are added to the site http://maven.apache.org/plugins/maven-acr-plugin/.
In actual configuration, users tend to create application clients without Main-Class and may get strange errors while trying to launch the application client. One example of these errors, may be accessed in:
http://www.java.net/forum/topic/glassfish/glassfish/problems-using-java-web-start-application-client-libraries-not-found
> Maven site should has an example with adding Main Class
> -------------------------------------------------------
>
> Key: MACR-3
> URL: https://issues.apache.org/jira/browse/MACR-3
> Project: Maven ACR Plugin
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Gustavo Orair
>
> Maven ACR plugin should confirm if the resulting Manifest contain a setting for Main-Class, because The Java EE spec requires that app clients specify the main class (http://www.java.net/forum/topic/glassfish/glassfish/problems-using-java-web-start-application-client-libraries-not-found).
> If Manifest does not contain Main-Class a warning should be emitted.
> Also, It would be worth if some examples specifying Main-Class are added to the site http://maven.apache.org/plugins/maven-acr-plugin/.
> In actual configuration, users tend to create application clients without Main-Class and may get strange errors while trying to launch the application client. One example of these errors, may be accessed in:
> http://www.java.net/forum/topic/glassfish/glassfish/problems-using-java-web-start-application-client-libraries-not-found
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)