I agree with the rest of you all. Do not add it to the repo! In fact I
consider any project that has a dependency to tools.jar as broken.
Not only does tools.jar have different content depending on the version of
the jdk/jre but in fact on some it does not even exist. There is no such
thing as a t
Thanks! I believe I have to look into this project that has a dependency to
tools.jar. Most likely they should execute on a JDK (and not a JRE) instead
of bundling the tools jar.
/Anders
On Sun, Dec 23, 2012 at 10:32 PM, Benson Margulies wrote:
> 1. As Jeff says, it won't work.
>
> 2. It violat
1. As Jeff says, it won't work.
2. It violates the terms of the JDK license, most likely.
On Sun, Dec 23, 2012 at 1:17 PM, Jeff MAURY wrote:
> I don't think you should as there are probably some differences between
> versions of the JDK
>
> Regards
> Jeff MAURY
>
>
>
> On Fri, Dec 21, 2012 at
I don't think you should as there are probably some differences between
versions of the JDK
Regards
Jeff MAURY
On Fri, Dec 21, 2012 at 11:20 AM, Anders Hammar wrote:
> So far I've managed the few situations where tools.jar (included in the
> JDK) is needed by using the deprecated system scope
