You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2017/10/17 21:53:00 UTC
[jira] [Closed] (BUILDR-733) java command: escape classpath entries
in the pathing jar manifest
[ https://issues.apache.org/jira/browse/BUILDR-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Donald closed BUILDR-733.
-------------------------------
Resolution: Fixed
> java command: escape classpath entries in the pathing jar manifest
> ------------------------------------------------------------------
>
> Key: BUILDR-733
> URL: https://issues.apache.org/jira/browse/BUILDR-733
> Project: Buildr
> Issue Type: Bug
> Components: Compilers
> Affects Versions: 1.4.25
> Environment: Windows
> Reporter: Glenn Croes
> Assignee: Peter Donald
> Priority: Minor
> Fix For: 1.4.25
>
>
> Hi,
> I noticed that the java command fails when using long classpaths on windows, while the classpath also has entries that contain spaces.
> The issue is that the manifest in the pathing jar uses space as a separator between classpath entries, and entries aren't URI-encoded. A classpath entry with a space in it is incorrectly treated as 2 entries.
> I created a PR on Github (https://github.com/apache/buildr/pull/29). It is for an older revision, as we use buildr 1.4 internally. It should be easy enough to merge though, as it's a one-liner fix.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)