Niall Pemberton wrote: > On Tue, Mar 9, 2010 at 5:12 PM, Phil Steitz <[email protected]> wrote: >> Niall Pemberton wrote: >>> On Tue, Mar 9, 2010 at 3:15 AM, Phil Steitz <[email protected]> wrote: >>>> Niall Pemberton wrote: >>>>> Unfortunately the upgrade of the maven-site-plugin from 2.0.1 to 2.1 >>>>> has caused the site generation for Chain, Configuration and DBCP to >>>>> now fail. >>>> I fixed DBCP. Will look at the others. >> Spoke too soon. DBCP and math are now both broken (using maven >> 2.2.1), giving: >> >> [Fatal Error] configuration_1_1.dtd:1:3: The markup declarations >> contained or pointed to by the document type declaration must be >> well-formed. >> org.xml.sax.SAXParseException: The markup declarations contained or >> pointed to by the document type declaration must be well-formed. >> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) >> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) >> at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124) >> at >> net.sourceforge.pmd.RuleSetFactory.parseRuleSetNode(RuleSetFactory.java:190) > > I suspect this is related to the same problem with the site-plugin - > which I believe is caused by the new version of doxia. We could fix > this by removing the PMD report - but I think its better to downgrade > the site plugin version and do another release of commons parent. > >> I also notice now that as you say below, nothing now works using >> maven 2.0.x. I use 2.0.10 to build dbcp 1.3.x. > > It does now with commons-parent 14-SNAPSHOT which has restored compatibility. > > I checkout the DBCP 1.3 branch, changed the DBCP's pom.xml to use > commons-parent 14-SNAPSHOT and ran "site" and "install" using JDK 1.4 > and Maven 2.0.11 and ir worked OK. So I think we need to release > commons parent.
+1 Phil > >> I can't remember >> why, but I could never get maven 2.1.x to work. > > Maven 2.1 isn't recommended: > http://markmail.org/message/l6tgv2moyy2tvqji > http://markmail.org/message/5nalngtrjed4zhmt > > Niall > >> Phil >>> Commons Chain is because the cookbook.xml has two examples in the docs >>> which include <!DOCTYPE> elements - they're in CDATA sections and so >>> should be ignored - looks like a bug to me. Configuration is the same >>> - the userguide/howto_xml.xml also has an example showing a <!DOCTYPE> >>> element. This looks like a maven bug in the latest site plugin. >>> >>> Niall >>> >>> >>>> Phil >>>> I'm looking into this to see whether its something we can >>>>> fix in the components or whether we need to downgrade the site plugin >>>>> version. >>>>> >>>>> I have reverted the maven-bundle-plugin version to 1.4.3 and the >>>>> maven-remote-resources-plugin to 1.0 (version 1.1 inherited from >>>>> apache parent 7) - this restores JDK 1.4 compatibility for "mvn >>>>> package/install". >>>>> >>>>> http://svn.apache.org/viewvc?view=revision&revision=920607 >>>>> >>>>> maven-site-plugin 2.1 requires maven 2.1 to run (which AFAIK needs JDK >>>>> 1.5) - so currently the site won't generate using JDK 1.4 - reverting >>>>> to 2.0.1 of the site plugin is required to run under JDK 1.4 - do we >>>>> need that? >>>>> >>>>> Also I noticed in the apache parent the following comment for the >>>>> maven-javadoc-plugin: >>>>> "NOTE: 2.6.x is generally unusuable due to MJAVADOC-275" >>>>> http://jira.codehaus.org/browse/MJAVADOC-275 >>>>> >>>>> So probably we should revert to 2.5 for the javadoc plugin >>>>> >>>>> Niall >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
