commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (JIRA)" <>
Subject [jira] Resolved: (DAEMON-166) Support for wildcards in classpath equivalent to Java 6 launcher
Date Fri, 23 Jul 2010 11:34:49 GMT


Mladen Turk resolved DAEMON-166.

    Fix Version/s: 1.0.2
       Resolution: Fixed

Fixed in the SVN.

Path expansion for classpath considers only the classpath parts that ends with the asterisk
Intermediate wild cards are supported only for unix version and the '.jar' suffix is added
foo:dir/*:bar will expand all .jar files, and the final path will look as:
In case dir/ does not contain any .jar files that part will be left empty and the final path
will be
fo::bar (note the empty part). This will also happen if the dir/ is not readable.
Same thing is done on windows with ';' as path separator 

> Support for wildcards in classpath equivalent to Java 6 launcher
> ----------------------------------------------------------------
>                 Key: DAEMON-166
>                 URL:
>             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.

View raw message