Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Thu, 15 Mar 2012 04:17:47 -0700 (PDT)
From: Babak Vahdat <babak.vahdat@swissonline.ch>
To: dev@camel.apache.org
Message-ID: <1331810267767-5567688.post@n5.nabble.com>
In-Reply-To: <1330602820574-5527707.post@n5.nabble.com>
References: <1330285496378-5517301.post@n5.nabble.com>
 <2240451.mQtAPGvZFN@dilbert.dankulp.com>
 <1330435855315-5521822.post@n5.nabble.com>
 <CAGB5yN=p6uxahG3iJb6HDqZi9tFjTquzmc8MuN7U99mmTvb7=Q@mail.gmail.com>
 <1330602820574-5527707.post@n5.nabble.com>
Subject: Re: About Camel source which doesn't build under Maven 3.0.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi

My promised deadline was today so I did already fix it right before.

Unfortunately up to now I haven't got any reply from Kohsuke so
that I went for the plan [2] as I did already mention by my first
post in this thread.

In case Kohsuke would publish a POM 4.0.0 complaint version of
his jaxb-bridge (e.g. version 1.1) in the future I will go for [1].

In all cases please delete your .m2 cache entry for this artifact no
matter which version of Maven you currently make use of:

~/.m2/repository/org/iso_relax/verifier/jaxp/validation/isorelax-jaxp-bridge/1.0/*.*

and build camel-msv again on your workspace (mvn clean install) so
that the good POM get's picked up.

Babak


--
View this message in context: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5567688.html
Sent from the Camel Development mailing list archive at Nabble.com.