SVNAdaptor from Tigris

[Ian Young]

On 30 Dec 2013, at 21:10, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 12/30/13, 3:49 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>> 
>> When we talked I was thinking about "Coping with Sun JARs" [1], but
>> "provided" really means provided by the JDK or container which is not
>> exactly our use case.
> 
> I assumed it meant "provided by not us", but ok.

Right: "provided" means:

"indicates you expect the JDK or a container to provide the dependency at runtime"

as mentioned in:

http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

This is *not* our use case, which is why I was/am pushing back against the use of "provided".

What we have here is an optional dependency, as described here:

http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html

"Why use optional dependencies?

It's not only important to declare optional dependencies in order to save space/memory/etc. It's vital to control the list of actual dependencies a person needs in order to use a project, since these jars may eventually make it into a WAR, EAR, EJB, etc. Inclusion of the wrong jars may violate a license agreement, cause classpath issues, etc."

This, it seems to me, is *exactly* our use case.

Bringing this up one more time as Rod has just checked in his code...

	-- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5943 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/dev/attachments/20140102/cf336c49/attachment.bin