Because of [1] and the input here in this mail thread, I added a "jdk1.7"
profile which is enabled by default on Java 7. With this profile, we use
JAXB api 2.2 und JAXB impl 2.2.5. With this, I got rid of the
NullpointerExceptions in multiple tests running with Java 7 [2].
Unfortunately we got some
Which in other words it means to go all that way consequently to the roots
you would also depend
on *other* JAX-WS 2.x (METRO) or JAXP 1.4 Impl-versions than the ones coming
along officially
with the *core* Java API *since* JDK 6 which is not what we do, do we?
Babak
--
View this message in conte
On Tuesday, March 13, 2012 09:01:28 AM Christian Müller wrote:
> I'm working on CAMEL-4955 to get our build running in Java 7. Because of
> an issue in JAXB 2.1.13 and 2.2.4u1 I need a newer version of JAXB impl.
> JAXB impl 2.1.14 is not released yet and I'm wondering whether we should
> upgrade t
On Tue, Mar 13, 2012 at 12:58 PM, Babak Vahdat
wrote:
> Claus
>
> What I was talking about was the camel-jaxb dependencies:
>
Ah yeah I think camel-jaxb should use the JDK stuff by default as its
part of JDK6+ now.
People can install a specific version of JAXB if they want to.
> ~/dev/workspace
dev@camel.apache.org
To
dev@camel.apache.org
cc
Subject
Re: Upgrading JAXB API/impl to 2.2.x
Bruno
Since Camel 2.7 [1] onwards JDK 1.5 is not supported anymore. And our
concern here is Camel 2.10 or maybe even 3.0.
[1] http://camel.apache.org/what-are-the-dependencies.html
Babak
--
View
Bruno
Since Camel 2.7 [1] onwards JDK 1.5 is not supported anymore. And our
concern here is Camel 2.10 or maybe even 3.0.
[1] http://camel.apache.org/what-are-the-dependencies.html
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Upgrading-JAXB-API-impl-to-2-2-x-tp55602
Claus
What I was talking about was the camel-jaxb dependencies:
~/dev/workspace/camel/components/camel-jaxb>mvn dependency:tree
[INFO] Scanning for projects...
[INFO]
[INFO]
--
Hi
camel-core does not have hardcoded dependencies on these JARs in Maven.
All we got is
- the google hashmap gets shaded directly into camel-core
- the slf4j JAR is the *only* 3rd party dependency we have
- osgi is not runtime dep, its set to provided (we use it to include
an OSGi activator in c
: +32 (0) 2 745 5606
www.toyota-europe.com
Babak Vahdat
13/03/2012 12:30
Please respond to
dev@camel.apache.org
To
dev@camel.apache.org
cc
Subject
Re: Upgrading JAXB API/impl to 2.2.x
Hi
IMHO we should completley *remove* both an explicit JAXB-API as well as
JAXB-IMPL dependencies
Hi
IMHO we should completley *remove* both an explicit JAXB-API as well as
JAXB-IMPL dependencies we claim to have. Let me shortly explain why:
As an example while running camel-jaxb's own unit-tests one would expect the
JVM to pick the JAXB classes from the jars (both API & IMPL) we claim to
be
I'm working on CAMEL-4955 to get our build running in Java 7. Because of an
issue in JAXB 2.1.13 and 2.2.4u1 I need a newer version of JAXB impl. JAXB
impl 2.1.14 is not released yet and I'm wondering whether we should upgrade
to JAXB API/impl 2.2.x. What are our constraints to upgrade Camel from J
11 matches
Mail list logo