Thanks Dan. now it worked.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5690331.html
Sent from the Camel Development mailing list archive at Nabble.com.
On Saturday, May 05, 2012 05:09:13 AM Babak Vahdat wrote:
> O.K. backporting to the 2.9.x worked well, however doing the same for the
> 2.8.x branch is not possible as to my understanding something on this
> branch is corrupted:
>
> ~/dev/workspace/camel-2.8.x>svnmerge.py avail
> svnmerge: Invalid
O.K. backporting to the 2.9.x worked well, however doing the same for the
2.8.x branch is not possible as to my understanding something on this branch
is corrupted:
~/dev/workspace/camel-2.8.x>svnmerge.py avail
svnmerge: Invalid path identifier ''
Also using the -F & -i options didn't help as wel
Thanks Dude! That did the trick...
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5687764.html
Sent from the Camel Development mailing list archive at Nabble.com.
There is a svnmerge.py unblock command. Maybe you need to do this first.
On Sat, May 5, 2012 at 12:22 PM, Babak Vahdat
wrote:
> Hi
>
> since yesterday I've seen one JIRA ticket & one question on the user forum
> about people having trouble to build the 2.9.x branch source using Maven
> 3.0.4. So
Hi
since yesterday I've seen one JIRA ticket & one question on the user forum
about people having trouble to build the 2.9.x branch source using Maven
3.0.4. So that I intend to backport the following revision:
http://svn.apache.org/viewvc?view=revision&revision=1300914
to both 2.9.x & 2.8.x bra
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-b
Hi Claus!
> Why couldn't they wait for Maven 3.1.0 to do this change.
Completly agree with you but that's how the real life is going on :-(
> We could @deprecated camel-msv and remove it from Camel 2.11 onwards.
I did contact Kohsuke *directly* and asked him to promote a POM 4.0.0
complaint vers
Well the problem is that Apache Maven do a patch release that is not
backwards compatible.
Why couldn't they wait for Maven 3.1.0 to do this change.
We could @deprecated camel-msv and remove it from Camel 2.11 onwards.
I do not assume many is using it.
Any thoughts?
Or have someone repackage the
Oops! My answer to your proposal was indeed too fast, as what you proposed
doesn't fix the problem we're facing by camel-msv.
Again, the problem is *not* MSV itself but the *bridge* [1] Kohsuke
Kawaguchi has provided for it:
org.iso_relax.verifier.jaxp.validation
isorelax-jaxp-bridge
Hi Dan,
Thanks for the hint!
I'll look into it and will upgrade the other required dependencies [1] as
well. Probabaly this will end up with some code changes by this component.
[1]
https://svn.apache.org/repos/asf/camel/trunk/components/camel-msv/pom.xml
Babak
--
View this message in context:
Or suggestion number 3:
3) Flip to using the more recently maintained version of MSV at the new
coordinates in central at:
net.java.dev.msv
msv-core
That's what CXF did long ago. :-)
Dan
On Sunday, February 26, 2012 11:44:56 AM Babak Vahdat wrote:
> Hi
>
> If y
Hi
If you would try to build Camel source under Maven 3.0.4 (recently released)
then it will fail @ camel-msv. The POM this component dependends on
is invalid [1] as it relies on the POM model definition version 3.0 and not
4.0. The problem is instead of inside this
POM, but maybe there're some
13 matches
Mail list logo
