Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of anders.g.hammar@gmail.com
 designates 209.85.215.45 as permitted sender)
MIME-Version: 1.0
Sender: anders.g.hammar@gmail.com
Date: Fri, 21 Dec 2012 11:20:39 +0100
Message-ID: 
 <CAKDUN1uUO3aFMahqkAhMaHhFtg7pX739xOF+-RYxLhW1edtnFA@mail.gmail.com>
Subject: Should I add tools.jar to my internal repo?
From: Anders Hammar <anders@hammar.net>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=f46d0421a78bfb510a04d15a3234

--f46d0421a78bfb510a04d15a3234
Content-Type: text/plain; charset=ISO-8859-1

So far I've managed the few situations where tools.jar (included in the
JDK) is needed by using the deprecated system scope and point at a local
tools.jar file. Up until now it's just been used in build time by plugins,
but now I've run into a case where it's an actual dependency and therefore
it could cause issues.

Normally, artifacts should be in the repo but I'm wondering if there are
any problems adding this one to an internal repo? Is it platform neutral
for example?
It's a strictly internal repo so I think we can ignore any license problems
by adding it to the repo.

/Anders

--f46d0421a78bfb510a04d15a3234--