On 2012-08-22, wrote:
> Make Locator.fileToURL and replace its use by
> FileUtils.getFileUtils().getFileURL()
Doesn't this cause a dependency cycle between ant.jar and
ant-launcher.jar?
Stefan
-
To unsubscribe, e-mail: dev-un
Hi,
Our test suite seems to fail quite consistently on jar signing, but only with
the jvm 1.5, Windows or Ubuntu. I have tested locally on my Mac, it fails too.
With verbose turned on, here is what I see:
[au:antunit] Signing JAR:
/Users/hibou/dev/ant/svn/core/trunk/build/antunit/tmp/testoutpu
On 08/22/2012 02:30 PM, Nicolas Lalevée wrote:
I could not think we can put 4 slashes
file:server/share/path is the broken result of new File("server\\share\\path").toURI(). While new File(URI) works to round-trip it (IIRC), if you call
URI.normalize() or otherwise do any kind of inter
Le 22 août 2012 à 20:07, Jesse Glick a écrit :
>> As far I understand, such path reference some file on a remote computer. But
>> then why the host part of the URI being build is left to null?
>
> Line #3059 (JDK 7) would not be executed for a UNC path because you would
> have file://server/sha
On 08/22/2012 08:50 AM, Nicolas Lalevée wrote:
Don't understand the encoding issue there, since we are manipulating Strings.
But String's which represent pathnames on an OS which might natively represent pathnames as octet sequences in some encoding. Again I am not sure what the defining
examp
Le 22 août 2012 à 00:04, Jesse Glick a écrit :
> On 08/21/2012 03:13 PM, Nicolas Lalevée wrote:
>> Or is there some code which rely on the broken behavior?
>
> Not that I know of. See the various commented-out code blocks and "XXX"
> comments in this class; it has a long and messy history. I do
The Ivy-tests job now run on both Ubuntu and Windows:
https://builds.apache.org/pview/job/Ivy-tests/
Nicolas
Le 20 août 2012 à 23:23, Maarten Coene a écrit :
> Thanks Nicolas :-)
> I also think a build matrix for Ivy would be a good idea...
>
> Maarten
>
>
>
> ___
Just had a quick look at Project.
There are a lot of deprecated methods. However
I do not think that most of them are deprecated correctly.
Users of the api should not have to know about implementation
details and changes to implementation - for example the
FileUtils.getFileUtils().
I downloaded t
