db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Monroe" <Greg.Mon...@DukeCE.com>
Subject maven-xdoc-plugin version 1.10 causes maven jar:install problems
Date Mon, 20 Nov 2006 20:02:00 GMT
I was doing a fresh build from SVN for testing purposes and
found an odd problem.  All of the subproject jar:install
tasks that I tried (templates, generator, runtime) gave a
BUILD FAILED status with the message:
File...... C:\Documents and
Element... artifact:artifact-install
Line...... 62
Column.... 9
Error getting the project as a string
After a lot of comparing, adding recent changes back in 
until it died, I found that the problem was the version 
change from maven-xdoc-plugin version 1.9.2 to 1.10.  If 
I rolled the version back in all the subprojects 
common/project.xml files, the build worked fine.
Funny thing is that the main project install still works
with the old version.
I'm not sure why this is happening but googling for the 
error message and maven brought up a lot of things 
related to maven-artifact-plugin 1.5.2.  Probably the
correct fix for 1.0.2 is to downgrade this but this
might have Maven2 issues.  Seems easier just to stay
with xdocs 1.9.2.
I wonder if this is the source of the gump build 
Greg Monroe <Monroe@DukeCE.com> (919)680-5050
C&IS Solutions Team Lead
Duke Corporate Education, Inc.
333 Liggett St.
Durham, NC 27701


Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are confidential communication
or may otherwise be privileged or confidential and are intended solely for the individual
or entity to whom they are addressed.  If you are not the intended recipient you may not rely
on the contents of this email or any attachments, and we ask that you  please not read, copy
or retransmit this communication, but reply to the sender and destroy the email, its contents,
and all copies thereof immediately.  Any unauthorized dissemination, distribution or copying
of this communication is strictly prohibited.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message