"Bill Barker" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Setting debug="true" in the <ant /> tag should turn on verbose logging by > Ant. I've no idea if that will trigger more logging by the <m2 /> task > :). >
Ok, that's what I get from going off of the documentation instead of the code :). It shouldn't be that hard to patch (it's just missing checking the attribute during the xml parsing), but I'm unlikely to get around to it at least before the weekend sometime. <insert-vetos-here /> :). >> -----Original Message----- >> From: Steve Loughran [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, February 21, 2006 9:15 AM >> To: Gump code and data >> Subject: tracking down an m2-libraries related problem >> >> >> from the trace of smartfrog-xml >> >> m2: >> [m2-libraries] Resolving dependencies... >> unspecified:unspecified:jar:0.0 (selected) >> xerces:xmlParserAPIs:jar:2.6.2 (selected) >> xom:xom:jar:1.1 (selected) >> xom:xom:jar:1.0b3 (removed - causes a cycle in the graph) >> jaxen:jaxen:jar:1.1-beta-8 (selected) >> jaxen:jaxen:jar:1.0-FCS (removed - causes a cycle in the graph) >> jdom:jdom:jar:1.0 (selected) >> xalan:xalan:jar:2.5.0 (selected) >> xerces:xmlParserAPIs:jar:2.6.2 (removed - nearer found: 2.6.2) >> xerces:xercesImpl:jar:2.6.2 (selected) >> xalan:xalan:jar:2.7.0 (selected) >> >> BUILD FAILED >> /x1/gump/public/workspace/smartfrog/components/xml/build.xml:5 >> 4: Unable >> to resolve artifact >> >> >> Its pretty hard to determine failures here, primarily because the m2 >> tasks dont print enough out at the normal level of verbosity.It looks >> like its built a graph of xom1.1, jaxen1.1-beta-8 and >> xerces/xalan, but >> is failing to find one of these. >> >> Is there any way to turn on extra verbosity to get more detailed >> diagnostics? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > > This message is intended only for the use of the person(s) listed above as > the intended recipient(s), and may contain information that is PRIVILEGED > and CONFIDENTIAL. If you are not an intended recipient, you may not read, > copy, or distribute this message or any attachment. If you received this > communication in error, please notify us immediately by e-mail and then > delete all copies of this message and any attachments. > > In addition you should be aware that ordinary (unencrypted) e-mail sent > through the Internet is not secure. Do not send confidential or sensitive > information, such as social security numbers, account numbers, personal > identification numbers and passwords, to us via ordinary (unencrypted) > e-mail. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
