Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of kot.begemot@gmail.com
 designates 64.233.166.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=A+S7sh6F6TR2TCLVdA/Y7aQx5RO0XmCW0X8wBfxm6c8OF5UR///v71DiY7m9yRxLZN
         ys3B7OoZwkeJXsrXSO1xUA+ZJ6BZR586tpax28QJ4+srYYLhI8k6Vkkt4+WcG6nFwMV3
         Lq+pXcMEqg2qnYqwcPqgv46A62x+b3bBsjLSw=
Message-ID: <6e8974e40807080038u4ff2fc79ha65a3af6764ca4ba@mail.gmail.com>
Date: Tue, 8 Jul 2008 00:38:30 -0700
From: "Vadim Chekan" <kot.begemot@gmail.com>
To: camel-user@activemq.apache.org
Subject: Re: Can not compile examples from 1.4 snapshot
In-Reply-To: <4872DFAA.80608@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4C1FB9C00D24A140906239533638C4D204BD7EBE@EXVS04.exserver.dk>
	 <4870AC9C.1080606@die-schneider.net> <4871D9E7.8050104@gmail.com>
	 <487254A9.3020401@die-schneider.net>
	 <6e8974e40807071239o571ab2fch23a34f32fde2d135@mail.gmail.com>
	 <4872DFAA.80608@gmail.com>

Thanks,
I've compiled it at home (ubuntu) and will try to upgrade windows at work.

Vadim.

On Mon, Jul 7, 2008 at 8:31 PM, Willem Jiang <willem.jiang@gmail.com> wrote:
> Hi
>
> You may need to upgrade your JDK, or put the JAXB 2.1 jars into the JDK
> endorse directory.
>
> For JDK6, Updates 1-3, JAXB 2.0 is used by default, Updates 4+ JAXB 2.1 is
> used.
> In Camel 1.4-snapshot ,we are using JAXB 2.1.
> If you are using JDK 1.5 , we may not meet this problem, since JAXB only
> shipped with JDK 1.6 or up.
>
> Willem
>
>
> Vadim Chekan wrote:
>>
>> I'm having problems with comiling camel/trunk too.
>> java version "1.6.0_02"
>> Java(TM) SE Runtime Environment (build 1.6.0_02-b06)
>> Java HotSpot(TM) Client VM (build 1.6.0_02-b06, mixed mode, sharing)
>>
>> [INFO] [bundle:bundle]
>> [WARNING] Warning building bundle
>> org.apache.camel:camel-csv:bundle:1.4-SNAPSHOT : Did not find matching
>> referal for !ja
>> vax.xml.bind.annotation.adapters
>> [INFO] [install:install]
>> [INFO] Installing
>>
>> C:\Projects\Experimental\Camel\trunk\components\camel-csv\target\camel-csv-1.4-SNAPSHOT.jar
>> to C:\Docu
>> ments and
>> Settings\vchekan\.m2\repository\org\apache\camel\camel-csv\1.4-SNAPSHOT\camel-csv-1.4-SNAPSHOT.jar
>> [INFO] [bundle:install]
>> [INFO] Parsing
>> file:/C:/Documents%20and%20Settings/vchekan/.m2/repository/repository.xml
>> [INFO] Installing
>> org/apache/camel/camel-csv/1.4-SNAPSHOT/camel-csv-1.4-SNAPSHOT.jar
>> [INFO] Writing OBR metadata
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Camel :: CXF
>> [INFO]    task-segment: [install]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [cxf-codegen:wsdl2java {execution: generate-test-sources}]
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> On Mon, Jul 7, 2008 at 10:38 AM, Christian Schneider
>> <chris@die-schneider.net> wrote:
>>
>>>
>>> Hmm ... but when I only have the binary distribution there is no parent
>>> pom.
>>> Any idea how we can change this? Does it make sense to ditribute the
>>> parent
>>> pom in the binary distributrion or is there a better way to solve the
>>> problem?
>>>
>>> However this can be solved I think the examples should work using maven
>>> without compiling from source.
>>>
>>> Greetings
>>>
>>> Christian
>>>
>>> Willem Jiang schrieb:
>>>
>>>>
>>>> FYI the below snapshot repository is in the camel-parent pom.xml for a
>>>> long time :)
>>>>
>>>> Willem
>>>>
>>>> Christian Schneider wrote:
>>>>
>>>>>
>>>>> Could this repository simply be added to the normal pom? Then people
>>>>> who
>>>>> try the snapshot would have no problems with this.
>>>>> On the other hand the repository entry could be removed for release
>>>>> builds.
>>>>>
>>>>> Greetings
>>>>>
>>>>> Christian
>>>>>
>>>>> Claus Ibsen schrieb:
>>>>>
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Yes it does take time to do a clean rebuild ;) And you need to
>>>>>> increase
>>>>>> the memory settings on Maven to let it be able to compile it all.
>>>>>>
>>>>>> The snapshorts is deployed on a public maven server
>>>>>> http://activemq.apache.org/camel/download.html
>>>>>>
>>>>>> Apache snapshots
>>>>>> http://people.apache.org/repo/m2-snapshot-repository
>>>>>>
>>>>>>
>>>>>>
>>>>>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/camel/apache-camel/
>>>>>>
>>>>>> So you can add the apache m2 snapshot in your pom.xml and you are off
>>>>>> to
>>>>>> go.
>>>>>>
>>>>>>   <repository>
>>>>>>     <id>apache.snapshots</id>
>>>>>>     <name>Apache Development Snapshot Repository</name>
>>>>>>     <url>http://people.apache.org/repo/m2-snapshot-repository</url>
>>>>>>     <releases>
>>>>>>       <enabled>false</enabled>
>>>>>>     </releases>
>>>>>>     <snapshots>
>>>>>>       <enabled>true</enabled>
>>>>>>     </snapshots>
>>>>>>   </repository>
>>>>>>
>>>>>>
>>>>>>
>>>
>>>
>>
>>
>>
>>
>
>


-- 
>From RFC 2631: In ASN.1, EXPLICIT tagging is implicit unless IMPLICIT
is explicitly specified