You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Antony Scerri (JIRA)" <ji...@apache.org> on 2010/06/25 22:14:51 UTC

[jira] Created: (DAEMON-166) Support for wildcards in classpath equivalent to Java 6 launcher

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


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.


[jira] Commented: (DAEMON-166) Support for wildcards in classpath equivalent to Java 6 launcher

Posted by "Antonio Angelino (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DAEMON-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891510#action_12891510 ] 

Antonio Angelino commented on DAEMON-166:
-----------------------------------------

Thank you; wildcards are really useful :)

> 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
>
> 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.


[jira] Commented: (DAEMON-166) Support for wildcards in classpath equivalent to Java 6 launcher

Posted by "Byron K. Appelt (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (DAEMON-166) Support for wildcards in classpath equivalent to Java 6 launcher

Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DAEMON-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891502#action_12891502 ] 

Mladen Turk commented on DAEMON-166:
------------------------------------

Implemented for jsvc. Will do the same for procrun.

> 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
>
> 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.


[jira] Resolved: (DAEMON-166) Support for wildcards in classpath equivalent to Java 6 launcher

Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DAEMON-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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 character.
Intermediate wild cards are supported only for unix version and the '.jar' suffix is added automatically.
foo:dir/*:bar will expand all .jar files, and the final path will look as:
foo:dir/1.jar:dir/2.jar:/dir/N.jar:bar
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: 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.


[jira] Updated: (DAEMON-166) Support for wildcards in classpath equivalent to Java 6 launcher

Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DAEMON-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mladen Turk updated DAEMON-166:
-------------------------------

    Fix Version/s: 1.0.3
                       (was: 1.0.2)

> 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.3
>
>
> 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.