Hi Robert,

thank you for your answer! I've read that blog, it confirms somehow my
intuition that xerces comes in play when it shouldn't hence causing the
exception.. Unfortunately it refers to the Maven Site Plugin.. In my case,
(I do not make use of the site plugin yet) I should try to understand which
package makes use of xerces..

I had a look at the dependencies for JAXB2 plugin (
http://mojo.codehaus.org/jaxb2-maven-plugin/dependencies.html<http://mojo.codehaus.org/jaxb2-maven-plugin/dependencies.html>)
but didn't find any explicit dependency to xerces.. So I tried to
incrementally add the exclusion for each 1-st level dependency listed there:
<pluginManagement>
<plugins>
<plugin>
                    <groupId>org.codehaus.mojo</groupId>
                    <artifactId>jaxb2-maven-plugin</artifactId>
                    <version>1.3.1</version>
                    <dependencies>
                        <dependency>
                            <groupId>org.apache.maven</groupId>
                            <artifactId>maven-plugin-api</artifactId>
                            <version>2.0</version>
                            <exclusions>
                                <exclusion>
                                    <groupId>xerces</groupId>
                                    <artifactId>xercesImpl</artifactId>
                                </exclusion>
                            </exclusions>
                        </dependency>
                        <dependency>
                            <groupId>org.apache.maven</groupId>
                            <artifactId>maven-artifact</artifactId>
                            <version>2.0.10</version>
                            <exclusions>
                                <exclusion>
                                    <groupId>xerces</groupId>
                                    <artifactId>xercesImpl</artifactId>
                                </exclusion>
                            </exclusions>
                        </dependency>
                        <dependency>
                            <groupId>org.apache.maven</groupId>
                            <artifactId>maven-project</artifactId>
                            <version>2.0.10</version>
                            <exclusions>
                                <exclusion>
                                    <groupId>xerces</groupId>
                                    <artifactId>xercesImpl</artifactId>
                                </exclusion>
                            </exclusions>
                        </dependency>
                        <dependency>
                            <groupId>org.apache.maven</groupId>
                            <artifactId>maven-model</artifactId>
                            <version>2.0.10</version>
                            <exclusions>
                                <exclusion>
                                    <groupId>xerces</groupId>
                                    <artifactId>xercesImpl</artifactId>
                                </exclusion>
                            </exclusions>
                        </dependency>
                        <dependency>
                            <groupId>com.sun.xml.bind</groupId>
                            <artifactId>jaxb-xjc</artifactId>
                            <version>2.1.12</version>
                            <exclusions>
                                <exclusion>
                                    <groupId>xerces</groupId>
                                    <artifactId>xercesImpl</artifactId>
                                </exclusion>
                            </exclusions>
                        </dependency>
                        <dependency>

<groupId>org.apache.maven.plugin-testing</groupId>

<artifactId>maven-plugin-testing-harness</artifactId>
                            <version>1.2</version>
                            <exclusions>
                                <exclusion>
                                    <groupId>xerces</groupId>
                                    <artifactId>xercesImpl</artifactId>
                                </exclusion>
                            </exclusions>
                        </dependency>
                        <dependency>
                            <groupId>org.codehaus.plexus</groupId>
                            <artifactId>plexus-compiler-api</artifactId>
                            <version>1.5.3</version>
                            <exclusions>
                                <exclusion>
                                    <groupId>xerces</groupId>
                                    <artifactId>xercesImpl</artifactId>
                                </exclusion>
                            </exclusions>
                        </dependency>
                        <dependency>
                            <groupId>org.codehaus.plexus</groupId>
                            <artifactId>plexus-utils</artifactId>
                            <version>1.5.5</version>
                            <exclusions>
                                <exclusion>
                                    <groupId>xerces</groupId>
                                    <artifactId>xercesImpl</artifactId>
                                </exclusion>
                            </exclusions>
                        </dependency>
                    </dependencies>
                </plugin>
.......
</plugins>
</pluginManagement>

This unfortunately didn't solve the problem, and I honestly don't know that
else may I try... Any further idea?

Thanks again,
bye,
Federico

2011/12/18 Robert Scholte [via Maven] <
[email protected]>

>
> Did you google?
>
>
>
> This blog explains the problem quite good:
>
> http://www.jsfblog.info/2010/04/maven-site-generation-error-dtddvfactoryimpl-does-not-extend-from-dtddvfactory/
>
>
>
>
> -Robert
>
>
> > Date: Sun, 18 Dec 2011 09:31:20 -0800
> > From: [hidden email]<http://user/SendEmail.jtp?type=node&node=5084149&i=0>
> > To: [hidden email]<http://user/SendEmail.jtp?type=node&node=5084149&i=1>
> > Subject: Re: Problem with jaxb2-maven-plugin 1.2
> >
> > I am really sorry that my reply was sent so many times.. Please forgive
> me,
> > it wasn't my intention to spam the mailing list!
> >
> > Does anybody can help me with my problem please? In the worst case, how
> can
> > I debug maven executing the JAXB2 plugin?
> >
> > Thanks a lot (and sorry again)
> >
> > 2011/12/16 Wayne Fay [via Maven] <[hidden 
> > email]<http://user/SendEmail.jtp?type=node&node=5084149&i=2>>
>
> >
> > > I *hate* Nabble...Can we just block it? Ugh.
> > >
> > > Wayne
> > >
> >
> >
> > --
> > View this message in context:
> http://maven.40175.n5.nabble.com/Problem-with-jaxb2-maven-plugin-1-2-tp5080568p5084141.html
>
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden 
> email]<http://user/SendEmail.jtp?type=node&node=5084149&i=3>
> For additional commands, e-mail: [hidden 
> email]<http://user/SendEmail.jtp?type=node&node=5084149&i=4>
>
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://maven.40175.n5.nabble.com/Problem-with-jaxb2-maven-plugin-1-2-tp5080568p5084149.html
>  To unsubscribe from Problem with jaxb2-maven-plugin 1.2, click 
> here<http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5080568&code=c21va2luZzgxQGdtYWlsLmNvbXw1MDgwNTY4fDUwNTI3NjkwMg==>
> .
> NAML<http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.InstantMailNamespace&breadcrumbs=instant+emails%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>


--
View this message in context: 
http://maven.40175.n5.nabble.com/Problem-with-jaxb2-maven-plugin-1-2-tp5080568p5085343.html
Sent from the Maven - Users mailing list archive at Nabble.com.

Reply via email to