[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wink-dev
Subject:    Re: slf4j-jdk14 (or other slf4j impls) should not be in the compile  scope
From:       Jason Dillon <jason () planet57 ! com>
Date:       2010-05-30 20:58:14
Message-ID: 2947ABD5-CBE6-4576-A633-F6B1F0C3CA69 () planet57 ! com
[Download RAW message or body]

On May 30, 2010, at 1:33 PM, Bryant Luk wrote:
> Do you recommend putting the jaxb dependencies in a profile for only
> Java 5 as well?  I don't know if that profile selection works in
> practice or not so was wondering if you've any experience here.

Profile selection based on jdk version works just fine.  So if you want to exclude \
those deps from the main build and only include them for java5 compat that should be \
fine.  But if you want your dist to be java5 compat, then leave them it... folks that \
want to use the jdk6's impl can exclude them.

I generally only use provides for the internal build needs, not for including jars in \
dependent builds based on a profile.  I guess it should work, but then when you \
generate your dist.zip's you have to be sure you are using a java5 vm to get those \
additional bits included as needed... ie. error prone.

I think the only problem is that older jdk6's did bitch and complain when it found \
multiple jaxb2 provider bits, but that has been fixed a while back.  But the solution \
is simple enough, either upgrade your jdk, or remove the jaxb2 stuff... both are user \
actives.

--jason


[prev in list] [next in list] [prev in thread] [next in thread]