[
https://jira.codehaus.org/browse/MACR-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282621#comment-282621
]
Gustavo Orair commented on MACR-3:
----------------------------------
I already followed this link, but this link does not show a specific manifest
to application clients.
I think the fact that Java EE spec requires that app clients specify the main
class should should be considered and at least a simple specific manifest for
an application client example that specifies Main-Class should be provided.
Also, the doc may instruct users to specify manifest and Main-Class stating it
is required by Java EE spec.
This doc would improve user experience reducing risks of problems.
> Maven site should has an example with adding Main Class
> -------------------------------------------------------
>
> Key: MACR-3
> URL: https://jira.codehaus.org/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 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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
