[
https://issues.apache.org/jira/browse/SLING-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592830#action_12592830
]
Carsten Ziegeler commented on SLING-190:
----------------------------------------
I'm not 100% sure, but as the launcher uses some other Sling modules which are
built against 1.5 it might not be possible to load the launcher even if we are
able to built just the launcher for 1.4.
I agree that the error you get when trying to run a 1.5 app with 1.4 is not
very intuitiv, but I think this is out of our scope. It would be great if we
could add a manifest entry to the jar, indicating that this only runs on 1.5+
> The Sling class of the launcher should verify minimum JDK requirement and
> fail properly
> ---------------------------------------------------------------------------------------
>
> Key: SLING-190
> URL: https://issues.apache.org/jira/browse/SLING-190
> Project: Sling
> Issue Type: Improvement
> Components: Launcher
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently, there is no check for the minimum Java Runtime environment
> required by Sling so, Sling will just fail with nasty exceptions if the
> requirement is not met. The Sling launcher (standalone app and web app)
> should be modified to fail gently in such cases:
> * The launcher is built agains JDK 1.4
> * The launcher checks for the required runtime version
> * If the runtime version is not correct, Sling should be terminated:
> -> standalone should just write the message to stderr and terminate
> the VM
> -> web app should log a message to the servlet container and throw
> a permanent UnavailableException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
