commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Byron K. Appelt (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DAEMON-166) Support for wildcards in classpath equivalent to Java 6 launcher
Date Mon, 02 Aug 2010 16:45:17 GMT

    [ https://issues.apache.org/jira/browse/DAEMON-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894592#action_12894592
] 

Byron K. Appelt commented on DAEMON-166:
----------------------------------------

The fix version on this issue should actually be 1.0.3, shouldn't it?

> Support for wildcards in classpath equivalent to Java 6 launcher
> ----------------------------------------------------------------
>
>                 Key: DAEMON-166
>                 URL: https://issues.apache.org/jira/browse/DAEMON-166
>             Project: Commons Daemon
>          Issue Type: Improvement
>          Components: Procrun
>    Affects Versions: 1.0.2
>         Environment: Any
>            Reporter: Antony Scerri
>            Priority: Minor
>             Fix For: 1.0.2
>
>
> As of Java 6 the launcher supports basic wildcards in the classpath, at the end of a
path a '*' will match any jar found in that directory, and it will be expanded appropriately
before the java application is launched. It would be nice to have this support in procrun
(and probably the unix version if not already). A modification to the apxJavaInitialize method
in javajni.c could do similar expansion to that found in the java launcher code prior to setting
the VM option.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message