You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Babak Vahdat <ba...@swissonline.ch> on 2012/02/26 20:44:56 UTC
About Camel source which doesn't build under Maven 3.0.4
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 <currentVersion> instead of <version> inside this
POM, but maybe there're some other issues inside this POM as well:
c:\dev\workspace\camel\components\camel-msv>mvn clean install
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Camel :: MSV 2.10-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[WARNING] The POM for
org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:jar:1.0 is
invalid, transitive dependencies (if any) will not be available, en
able debug logging for more details
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ camel-msv ---
[INFO] Deleting c:\dev\workspace\camel\components\camel-msv\target
[INFO]
[INFO] --- maven-antrun-plugin:1.6:run (create-prop) @ camel-msv ---
[INFO] Executing tasks
main:
[echo] Maven version: 2.10-SNAPSHOT
[echo] OSGi version: 2.10.0.SNAPSHOT
[INFO] Executed tasks
[INFO]
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties
(default) @ camel-msv ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ camel-msv
---
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1.810s
[INFO] Finished at: Sun Feb 26 19:29:58 CET 2012
[INFO] Final Memory: 11M/494M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process (default)
on project camel-msv: Execution default of goal org.
apache.maven.plugins:maven-remote-resources-plugin:1.1:process failed: For
artifact
{org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:null:jar}: The
version cannot be empty. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
Running Maven with the -X option brings up the following:
...
...
Caused by: org.apache.maven.artifact.InvalidArtifactRTException: For
artifact
{org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:null:jar}: The
version cannot be empty.
at
org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:148)
at
org.apache.maven.artifact.DefaultArtifact.<init>(DefaultArtifact.java:123)
...
...
Suggestions:
1 - Do fix the POM on the central-repo to be POM 4.0 complaint, however I
don't know the procedure for it by Apache: who is allowed to edit that POM
and how?
2 - Make use of the POM the SMX folks have already generated [2] using the
"mvn install:install-file"
BTW, msv itself is not active anymore since ages [3].
Any thoughts?
[1]
http://repo1.maven.org/maven2/org/iso_relax/verifier/jaxp/validation/isorelax-jaxp-bridge/1.0/isorelax-jaxp-bridge-1.0.pom
[2]
http://svn.apache.org/repos/asf/servicemix/m2-repo/org/iso_relax/verifier/jaxp/validation/isorelax-jaxp-bridge/1.0/isorelax-jaxp-bridge-1.0.pom
[3] http://java.net/downloads/msv/releases/
Babak
--
View this message in context: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5517301.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
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: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5521163.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
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.
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Daniel Kulp <dk...@apache.org>.
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 path identifier ''
>
> Also using the -F & -i options didn't help as well.
Fixed. The last person to merge didn't resolve a conflict there so the
properties were corrupt.
Also, if you want, you can try my latest DoMerges script in the CXF
trunk/bin. It should walk you through things fairly easily. The latest
version does NOT require the svnmerge.py script. It also will work with a
git clone instead of an svn co.
Dan
>
> Babak
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-
> under-Maven-3-0-4-tp5517301p5687838.html Sent from the Camel Development
> mailing list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
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 well.
Babak
--
View this message in context: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5687838.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
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.
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Claus Ibsen <cl...@gmail.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
<ba...@swissonline.ch> 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 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 branches, however the output of:
>
> svnmerge.py avail
>
> on the 2.9.x branch doesn't contain the revision 1300914!
>
> Has anybody got an idea why?
>
> BTW using eclipse *does* show me the revision 1300914 for a possible merge
> candidate on the 2.9.x branch, however I prefer to stick the way I've done
> in the past as mentioned / recommended on the Wiki as well (svnmerge.py).
>
> Currently this's what I get:
>
> ~/dev/workspace/camel-2.9.x>svnmerge.py avail
> 1325230,1325232,1325307,1325371,1325613,1326077,1326084,1326145,1326148,1326294,1326314,1326330,1326343,1326467,1326470,1326514,1326526,1326531,1326557,1326560,1326746,1326761,1326773,1326775,1326900,1326914,1326929-1326930,1326935,1326939-1326940,1326994,1327058,1327100,1327131,1327396,1327430,1327537,1327546,1327565,1327883,1328185,1328446,1328462,1328676,1328685,1328832,1328834,1328836,1328850,1329360,1329531-1329533,1329581-1329582,1329730,1329798,1329969,1330016,1330053,1330102,1330570,1330586,1330643,1330657,1330727,1330789,1331224-1331225,1331237,1331241,1331249,1331270,1331288,1331294,1331307,1331350,1331354,1331358-1331359,1331370,1331455,1331467,1331699,1331718-1331719,1331780,1331877,1331887,1331914,1331967,1332008,1332052,1332060,1332173,1332586,1332591,1332649,1332698,1332889,1333009,1333018-1333019,1333074,1333308,1333821,1334006,1334366-1334367
>
> Babak
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5687709.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
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 branches, however the output of:
svnmerge.py avail
on the 2.9.x branch doesn't contain the revision 1300914!
Has anybody got an idea why?
BTW using eclipse *does* show me the revision 1300914 for a possible merge
candidate on the 2.9.x branch, however I prefer to stick the way I've done
in the past as mentioned / recommended on the Wiki as well (svnmerge.py).
Currently this's what I get:
~/dev/workspace/camel-2.9.x>svnmerge.py avail
1325230,1325232,1325307,1325371,1325613,1326077,1326084,1326145,1326148,1326294,1326314,1326330,1326343,1326467,1326470,1326514,1326526,1326531,1326557,1326560,1326746,1326761,1326773,1326775,1326900,1326914,1326929-1326930,1326935,1326939-1326940,1326994,1327058,1327100,1327131,1327396,1327430,1327537,1327546,1327565,1327883,1328185,1328446,1328462,1328676,1328685,1328832,1328834,1328836,1328850,1329360,1329531-1329533,1329581-1329582,1329730,1329798,1329969,1330016,1330053,1330102,1330570,1330586,1330643,1330657,1330727,1330789,1331224-1331225,1331237,1331241,1331249,1331270,1331288,1331294,1331307,1331350,1331354,1331358-1331359,1331370,1331455,1331467,1331699,1331718-1331719,1331780,1331877,1331887,1331914,1331967,1332008,1332052,1332060,1332173,1332586,1332591,1332649,1332698,1332889,1333009,1333018-1333019,1333074,1333308,1333821,1334006,1334366-1334367
Babak
--
View this message in context: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5687709.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
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.
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
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 version of his JAXP-Bridge [1] *if* possible.
However as he's currently still in Tokyo and "apologies in advance for
additional delay in e-mail" [2] I intend to wait a bit
longer for his (potential) reply.
> Or have someone repackage the *bridge* JAR and maybe host it in the SMX
> repo.
Yeah exactly, that was my second proposal by this thread which would resolve
the problem in case we would not get any help from
Kohsuke.
So please give me time until March 15th as the deadline and I will go either
for one or other approach. But no matter which approach
is taken, to avoid any potential problem, the Camel folks should then delete
their existing local m2 cache for this bridge before trying Maven 3.0.4.
And camel-msv is one of those component denoted by James! So I personally
prefer to keep on it, although as you said, probably not too much users make
use of it.
[1] http://java.net/projects/isorelax-jaxp-bridge/
[2] http://kohsuke.org/2012/02/16/this-week-in-tokyo/
Babak
--
View this message in context: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5527707.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Claus Ibsen <cl...@gmail.com>.
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 *bridge* JAR and maybe host it in the SMX repo.
Then we could switch to use that JAR instead.
On Tue, Feb 28, 2012 at 2:30 PM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> 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:
>
> <groupId>org.iso_relax.verifier.jaxp.validation</groupId>
> <artifactId>isorelax-jaxp-bridge</artifactId>
>
> In order to use MSV as a RELAX NG validator through the *standard* Java
> Validation API which is part of JAXP. And now the problem is that the
> isorelax-jaxp-bridge POM is *not* POM 4.0.0 complaint!
>
> I took a look at the CXF code itself and there MSV is triggered through the
> Woodstox which is huge difference to how MSV is triggered inside Camel ;-)
>
> [1]
> http://weblogs.java.net/blog/2006/02/10/validate-xml-using-relax-ng-and-jaxp-13
>
> Babak
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5521822.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
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:
<groupId>org.iso_relax.verifier.jaxp.validation</groupId>
<artifactId>isorelax-jaxp-bridge</artifactId>
In order to use MSV as a RELAX NG validator through the *standard* Java
Validation API which is part of JAXP. And now the problem is that the
isorelax-jaxp-bridge POM is *not* POM 4.0.0 complaint!
I took a look at the CXF code itself and there MSV is triggered through the
Woodstox which is huge difference to how MSV is triggered inside Camel ;-)
[1]
http://weblogs.java.net/blog/2006/02/10/validate-xml-using-relax-ng-and-jaxp-13
Babak
--
View this message in context: http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5521822.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: About Camel source which doesn't build under Maven 3.0.4
Posted by Daniel Kulp <dk...@apache.org>.
Or suggestion number 3:
3) Flip to using the more recently maintained version of MSV at the new
coordinates in central at:
<groupId>net.java.dev.msv</groupId>
<artifactId>msv-core</artifactId>
That's what CXF did long ago. :-)
Dan
On Sunday, February 26, 2012 11:44:56 AM Babak Vahdat wrote:
> 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 <currentVersion> instead of <version> inside this POM,
> but maybe there're some other issues inside this POM as well:
>
> c:\dev\workspace\camel\components\camel-msv>mvn clean install
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Camel :: MSV 2.10-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [WARNING] The POM for
> org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:jar:1.0 is
> invalid, transitive dependencies (if any) will not be available, en
> able debug logging for more details
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ camel-msv ---
> [INFO] Deleting c:\dev\workspace\camel\components\camel-msv\target
> [INFO]
> [INFO] --- maven-antrun-plugin:1.6:run (create-prop) @ camel-msv ---
> [INFO] Executing tasks
>
> main:
> [echo] Maven version: 2.10-SNAPSHOT
> [echo] OSGi version: 2.10.0.SNAPSHOT
> [INFO] Executed tasks
> [INFO]
> [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties
> (default) @ camel-msv ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ camel-msv
> ---
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 1.810s
> [INFO] Finished at: Sun Feb 26 19:29:58 CET 2012
> [INFO] Final Memory: 11M/494M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process (default)
> on project camel-msv: Execution default of goal org.
> apache.maven.plugins:maven-remote-resources-plugin:1.1:process failed: For
> artifact
> {org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:null:jar}: The
> version cannot be empty. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
>
>
> Running Maven with the -X option brings up the following:
>
> ...
> ...
> Caused by: org.apache.maven.artifact.InvalidArtifactRTException: For
> artifact
> {org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:null:jar}: The
> version cannot be empty.
> at
> org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.j
> ava:148) at
> org.apache.maven.artifact.DefaultArtifact.<init>(DefaultArtifact.java:123)
> ...
> ...
>
> Suggestions:
>
> 1 - Do fix the POM on the central-repo to be POM 4.0 complaint, however I
> don't know the procedure for it by Apache: who is allowed to edit that POM
> and how?
> 2 - Make use of the POM the SMX folks have already generated [2] using the
> "mvn install:install-file"
>
> BTW, msv itself is not active anymore since ages [3].
>
> Any thoughts?
>
> [1]
> http://repo1.maven.org/maven2/org/iso_relax/verifier/jaxp/validation/isorela
> x-jaxp-bridge/1.0/isorelax-jaxp-bridge-1.0.pom [2]
> http://svn.apache.org/repos/asf/servicemix/m2-repo/org/iso_relax/verifier/ja
> xp/validation/isorelax-jaxp-bridge/1.0/isorelax-jaxp-bridge-1.0.pom [3]
> http://java.net/downloads/msv/releases/
>
> Babak
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-un
> der-Maven-3-0-4-tp5517301p5517301.html Sent from the Camel Development
> mailing list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com