NPE while auto-wiring values in a mojo

[snambi]

Hi All

I have the following mojo, but the values are NOT getting set, by maven
runtime.
The exception trace is provided below.
Have anyone faced the same problem before?

public class Assembler1PackageMojo extends AbstractMojo {

/**
* The Maven project.
*
* @parameter expression="${project}"
* @required
* @readonly
*/
private MavenProject project;

/**
* Location of the file.
*
* @parameter expression="${project.basedir}"
* @required
*/
private File projectDirectory;

/**
* Location of the file.
*
* @parameter expression="${project.build.directory}"
* @required
*/
private File targetDirectory;

/**
 * The application name is used by the packager to create a 
cronus
package.
 * @parameter expression="${assembler.applicationName}"
 * @required
 */
private String applicationName;

/**
 * Consumer Id (app Id).
 * Mandatory for the time being.
 * @parameter expression="${assembler.consumerId}" 
 * @required
 */
private String consumerId;

/**
 * @parameter  default-value="cronus-pkg"
 * @optional
 */
private String cronusFolder;


public void execute() throws MojoExecutionException{

getLog().info("Executing Assembler package mojo");

}

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 1.796s
[INFO] Finished at: Thu Dec 15 22:29:47 PST 2011
[INFO] Final Memory: 5M/109M
[INFO]

[ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
at
org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.NullPointerException
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:331)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:151)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:567)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:529)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:92)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:2

Re: Externalize POM file

[Anders Hammar]

You can't do like that. Please have a look here:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

/Anders

On Fri, Dec 16, 2011 at 08:37, KumarR  wrote:
> Thanks for the reply. Below is my POM script
>
> Parent Pom
> ---
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>  
>    com.unisys.my-parent
>    my-parent
>    1.0
>    ../JarDefinition/pom.xml
>  
>  4.0.0
>  com.unisys.SampleExample
>  Sample
>  jar
>  1.0-SNAPSHOT
>  Sample
>  
>  
>    
>      xyz
>      junit
>          ${currentVersion}
>    
>  
>  
> 
>
>
> Child POM
> 
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>  4.0.0
>  com.unisys.my-parent
>  my-parent
>  pom
>  1.0
>
>  
>    
>      xyz
>      junit
>
>          3.8.1
>    
>        
> 
>
>
> I am getting below error
> 
>
> Reason: Parse error reading POM. Reason: Unrecognised tag: 'properties'
> (position: START_TAG seen ... -->\r\n\t  ... @14:16)
> for project com.unisys.SampleExample:Sample at
> D:\Projects\LEIDA\LEIDA-Workspace\RnDWorkspace\JarDefinition\pom.xml
>
>
> [INFO]
> 
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Parse error reading POM.
> Reason: Unrecognised tag: 'properties' (position: START_TAG seen
> ... -->\r\n\t  ... @14:16)  for project
> com.unisys.SampleExample:Sample at
> D:\Projects\LEIDA\LEIDA-Workspace\RnDWorkspace\JarDefinition\pom.xml
>        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>        at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:592)
>        at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>        at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.InvalidProjectModelException: Parse
> error reading POM. Reason: Unrecognised tag: 'properties' (position:
> START_TAG seen ... -->\r\n\t  ... @14:16)  for project
> com.unisys.SampleExample:Sample at
> D:\Projects\LEIDA\LEIDA-Workspace\RnDWorkspace\JarDefinition\pom.xml
>        at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1610)
>        at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1571)
>        at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1320)
>        at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
>        at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
>        at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
>        at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
>        at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
>        at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
>        ... 12 more
> Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException:
> Unrecognised tag: 'properties' (position: START_TAG seen ...
> -->\r\n\t  ... @14:16)
>        at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseDependency(MavenXpp3Reader.java:1225)
>        at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2094)
>        at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:3912)
>        at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1606)
>
> Regards
> Kumar
>
> --
> View this message in context: 
> http://maven.40175.n5.nabble.com/Externalize-POM-file-tp5079337p5079564.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For 

Re: Setting values in a mojo

[Dirk Olmes]

On 12/16/2011 08:25 AM, Sankaran, Nambi wrote:
> Hi All
> 
> I have the following mojo, but the values are NOT getting set, by maven 
> runtime.
> The exception trace is provided below.
> Have anyone faced the same problem before?

Do you build your project using the maven-plugin packaging type? For the
injection to work the Maven runtime needs additional info that's
generated by the proper packaging type.

-dirk

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Solve my exception for mvn installtion

[Jeff MAURY]

It means the class files have geen generated using a JDK 1.5 and you are
running a pre 1.5 JDK with Maven.
You should probably check your JAVA_HOME.
What does java -version says ?

Regards
Jeff MAURY

On Fri, Dec 16, 2011 at 5:42 AM, ashishmemod  wrote:

> thank you for above reply...
>
> But I installed java 6 with update 24 in my system!!!
>
> So now what is meaning of this exception?
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Solve-my-exception-for-mvn-installtion-tp5076811p5079295.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

Re: Release plugin should tag the revision that was built in the prepare phase

[Olivier Lamy]

2011/12/15 Phillip Hellewell :
> So release:prepare does a compile first and then (modifies the pom and)
> creates the tag.  That makes sense, but...
>
> the problem is we have some artifacts that take a *long* time (up to an
> hour) to build.  During that time developers may check in more changes that
> they don't expect to be part of the build (since the build already started).
>
> The problem occurs because the tag gets created from the latest revision at
> the end of the compile.  Creating the tag at the end is fine, but it should
> create the tag from the revision that was built by release:prepare (e.g.,
> with svn you can specify an @REV for the source when doing an svn copy).

As you use svn, a possible solution is to use remoteTagging=false
(http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#remoteTagging)

which do svn cp . http://blbl/tags/


>
> Now you're going to say, "that's impossible, because we need to modify the
> pom first (version and scm connection)".  I knew you were going to say
> that.  But why not modify the pom upfront, before compiling?  Modify it to
> what it needs to be for the tag, check it in, and then revert it back and
> check that in.  Now there exists a revision in the SCM that is appropriate
> to tag from at the end of the release:prepare.
>
> I hope that makes sense.  The only downside here is a few unnecessary pom
> file checkins, but we'd rather have that than have builds with unexpected
> changes in them.  Not only that but this would avoid the problem that a
> breaking change slips in during the middle of release:prepare and you end
> up tagging the broken code and you end up with a worthless tag that can
> never be deployed.
>
> Phillip



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Solve my exception for mvn installtion

[ashishmemod]

I found the problem and now it is solved.

thank all who helped me.

On Fri, Dec 16, 2011 at 2:24 PM, Jeff MAURY [via Maven] <
ml-node+s40175n5079699...@n5.nabble.com> wrote:

> It means the class files have geen generated using a JDK 1.5 and you are
> running a pre 1.5 JDK with Maven.
> You should probably check your JAVA_HOME.
> What does java -version says ?
>
> Regards
> Jeff MAURY
>
> On Fri, Dec 16, 2011 at 5:42 AM, ashishmemod <[hidden 
> email]>
> wrote:
>
> > thank you for above reply...
> >
> > But I installed java 6 with update 24 in my system!!!
> >
> > So now what is meaning of this exception?
> >
> >
> >
> > --
> > View this message in context:
> >
> http://maven.40175.n5.nabble.com/Solve-my-exception-for-mvn-installtion-tp5076811p5079295.html
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >
> > -
> > To unsubscribe, e-mail: [hidden 
> > email]
> > For additional commands, e-mail: [hidden 
> > email]
> >
> >
>
>
> --
> "Legacy code" often differs from its suggested alternative by actually
> working and scaling.
>  - Bjarne Stroustrup
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.twitter.com/jeffmaury
>
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://maven.40175.n5.nabble.com/Solve-my-exception-for-mvn-installtion-tp5076811p5079699.html
>  To unsubscribe from Solve my exception for mvn installtion, click 
> here
> .
> NAML
>


--
View this message in context: 
http://maven.40175.n5.nabble.com/Solve-my-exception-for-mvn-installtion-tp5076811p5080262.html
Sent from the Maven - Users mailing list archive at Nabble.com.

RE: Release plugin should tag the revision that was built in the prepare phase

[Thiessen, Todd (Todd)]

http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html

If you look at the preperationGoal option of the prepare goal, you will see the 
default is clean verify.  If you change with to simple be clean, the prepare 
phase won't actually try and build the snapshot.

IMHO, your second concern isn't very severe if you have continuous integration 
in place. If you do, you will always know when your snapsnot is sane making the 
building of the snapshot during the prepare phase virtually useless.  You of 
course don't want to release if your CI shows the build to be broken.

> -Original Message-
> From: Phillip Hellewell [mailto:ssh...@gmail.com]
> Sent: Thursday, December 15, 2011 6:48 PM
> To: Maven Users List
> Subject: Re: Release plugin should tag the revision that was built in
> the prepare phase
> 
> On Thu, Dec 15, 2011 at 3:05 PM, Thiessen, Todd (Todd)
>  wrote:
> > You can skip the building of the snapshot by changing the goals in
> the prepare phase.  This will then jump you right to tag creation,
> checkout of the tag and building of the tag during the perform phase.
> 
> Thanks Todd; can you give me a hint on how to change the goals that
> get run by release:prepare?  Does that mean compiling my own special
> version of the release plugin?
> 
> I do kinda like the idea of skipping the build of the snapshot.  The
> only downside though is when a build is broken we would end up with a
> useless tag / unusable version, but maybe we could live with that...
> 
> Phillip
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

Re: Externalize POM file

[Ron Wheeler]

On 16/12/2011 2:25 AM, Anders Hammar wrote:

Using dependencyManagement in the parent to specify the version of
dependencies is also an option. IMHO that's the true Maven way, but
Ron's approach could be an option in some cases. I don't like that
approach though as it will create an incorrect dependency tree
(dependencies will be on the wrong level and there will likely be too
many dependencies).
It reduces the number of dependencies at the module level since there is 
a single provided dependency for all of Spring, Hibernate, MySQL and Tomcat.
Another for all of the stuff that is required for Faces, another for web 
services, another for Apache commons and other third party libraries 
(Jasper Reports, another for all of the libraries that we have made, etc..


The only downside is that there are a number of jars (about 10) that we 
make that have to be added to the Tomcat shared lib at runtime to get 
the 70+ libraries that we use.


It makes the module wars really small since they contain only the code 
that we wrote for the module.

That speeds up the builds tremendously.

It also makes it much easier for the developers to set up a module since 
they only have to depend on a few artifacts (usually about 5).
We are sure that their module is using the "correct" version of all of 
the little libraries that they need.
All of the exclusions to avoid version conflicts are done inside the 
shared jars so the developer does not have to worry about 2 versions of 
Spring getting called up.
This reduces the dependency tree for the module and avoids run-time 
library conflicts which was one of the problems that prompted us to 
implement this.


Ron




/Anders

On Fri, Dec 16, 2011 at 08:15, Ron Wheeler
  wrote:

http://blog.artifact-software.com/tech/?p=121

On 16/12/2011 12:17 AM, KumarR wrote:

Hi
   I am new to maven. I want to maintain a separate POM file for version of
the jar files. This will help in maintaining the versions of jar files.
For
eg: if we are using junit.jar, the version of the jar file should be
maintain in the separate POM file. This will help us in changing in only
one
POM rather than all the POM files if any version changes is there. Please
help me in this regard.

Regard
Kumar

--
View this message in context:
http://maven.40175.n5.nabble.com/Externalize-POM-file-tp5079337p5079337.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Problem with jaxb2-maven-plugin 1.2

[smoking81]

Hi there! I am new in the ML and also a new maven user.. I've hope anybody
here will kindly help me with a problem is letting me get crazy... :)

I will try to briefly describe it here:

I have a modular project in which, for every single module, I use
jaxb2-maven-plugin to compile XSD files with xjc. Now, suppose the modules
are compiled in the order A-->B. For A everything works fine (i.e. I get the
*XsdImpl.java), but for B I get the following:

/[INFO]

[ERROR] Failed to execute goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc
(model) on project B: DTD factory class
org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
DTDDVFactory. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc (model) on project B: DTD
factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend
from DTDDVFactory
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: DTD factory class
org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
DTDDVFactory.
at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:352)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.xerces.impl.dv.DVFactoryException: DTD factory class
org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
DTDDVFactory.
at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
Source)
at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
Source)
at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
Source)
at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
Source)
at org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
Source)
at org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.(Unknown
Source)
at
org.apache.xerces.jaxp.validation.XMLSchemaValidatorComponentManager.(Unknown
Source)
at
org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.(Unknown
Source)
at
org.apache.xerces.jaxp.validation.AbstractXMLSchema.newValidatorHandler(Unknown
Source)
at com.sun.tools.xjc.SchemaCache.newValidator(SchemaCache.java:47)
at
com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl$1$1.startElement(AnnotationParserFactoryImpl.java:136)
at
com.sun.xml.xsom.impl.parser.state.NGCCRuntime.startElement(NGCCRuntime.java:214)
at
org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527)
at
com.sun.tools.xjc.reader.ExtensionBindingChecker.startElement(ExtensionBindingChecker.java:271)
at
org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527)
at
com.sun.tools.xjc.reader.xmlschema.parser.IncorrectNamespaceURIChecker.startElement(IncorrectNamespaceURIChecker.java:9

Re: Problem with jaxb2-maven-plugin 1.2

[Anders Hammar]

What version of Maven are you using?

/Anders (mobile)
Den 16 dec 2011 16.37 skrev "smoking81" :

> Hi there! I am new in the ML and also a new maven user.. I've hope anybody
> here will kindly help me with a problem is letting me get crazy... :)
>
> I will try to briefly describe it here:
>
> I have a modular project in which, for every single module, I use
> jaxb2-maven-plugin to compile XSD files with xjc. Now, suppose the modules
> are compiled in the order A-->B. For A everything works fine (i.e. I get
> the
> *XsdImpl.java), but for B I get the following:
>
> /[INFO]
> 
> [ERROR] Failed to execute goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc
> (model) on project B: DTD factory class
> org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> DTDDVFactory. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc (model) on project B: DTD
> factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not
> extend
> from DTDDVFactory
>at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:597)
>at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: DTD factory
> class
> org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> DTDDVFactory.
>at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:352)
>at
>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>... 19 more
> Caused by: org.apache.xerces.impl.dv.DVFactoryException: DTD factory class
> org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> DTDDVFactory.
>at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> Source)
>at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> Source)
>at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> Source)
>at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> Source)
>at org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> Source)
>at org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> Source)
>at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown Source)
>at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown Source)
>at org.apache.xerces.impl.xs.XMLSchemaValidator.(Unknown
> Source)
>at
>
> org.apache.xerces.jaxp.validation.XMLSchemaValidatorComponentManager.(Unknown
> Source)
>at
> org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.(Unknown
> Source)
>at
>
> org.apache.xerces.jaxp.validation.AbstractXMLSchema.newValidatorHandler(Unknown
> Source)
>at com.sun.tools.xjc.SchemaCache.newValidator(SchemaCache.java:47)
>at
>
> com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl$1$1.startElement(AnnotationParserFactoryImpl.java:136)
>at
>
> com.sun.xml.xsom.impl.parser.state.NGCCRuntime.startElement(NGCCRuntime.java:214)
>at
> org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527)
>at
>
> com.sun.tools.

Re: Problem with jaxb2-maven-plugin 1.2

[smoking81]

Hi 3.0.2
Bye
Il giorno 16/dic/2011 16:56, "Anders Hammar [via Maven]" <
ml-node+s40175n5080629...@n5.nabble.com> ha scritto:
>
> What version of Maven are you using?
>
> /Anders (mobile)
> Den 16 dec 2011 16.37 skrev "smoking81" <[hidden email]>:
>
> > Hi there! I am new in the ML and also a new maven user.. I've hope
anybody
> > here will kindly help me with a problem is letting me get crazy... :)
> >
> > I will try to briefly describe it here:
> >
> > I have a modular project in which, for every single module, I use
> > jaxb2-maven-plugin to compile XSD files with xjc. Now, suppose the
modules
> > are compiled in the order A-->B. For A everything works fine (i.e. I
get
> > the
> > *XsdImpl.java), but for B I get the following:
> >
> > /[INFO]
> >

> > [ERROR] Failed to execute goal
org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc
> > (model) on project B: DTD factory class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory. -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute
> > goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc (model) on project B:
DTD
> > factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not
> > extend
> > from DTDDVFactory
> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

> >at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >
> >
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

> >at
> >
> >
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

> >at java.lang.reflect.Method.invoke(Method.java:597)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > Caused by: org.apache.maven.plugin.MojoExecutionException: DTD factory
> > class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:352)
> >at
> >
> >
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)

> >... 19 more
> > Caused by: org.apache.xerces.impl.dv.DVFactoryException: DTD factory
class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaValidator.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.XMLSchemaValidatorComponentManager.(Unknown

> > Source)
> >at
> > org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.AbstractXMLSchema.newValidatorHandler(Unknown

> > Source)
> >at
com.sun.tools.xjc.SchemaCache.newVal

Re: Problem with jaxb2-maven-plugin 1.2

[smoking81]

Hi 3.0.2
Bye
Il giorno 16/dic/2011 16:56, "Anders Hammar [via Maven]" <
ml-node+s40175n5080629...@n5.nabble.com> ha scritto:
>
> What version of Maven are you using?
>
> /Anders (mobile)
> Den 16 dec 2011 16.37 skrev "smoking81" <[hidden email]>:
>
> > Hi there! I am new in the ML and also a new maven user.. I've hope
anybody
> > here will kindly help me with a problem is letting me get crazy... :)
> >
> > I will try to briefly describe it here:
> >
> > I have a modular project in which, for every single module, I use
> > jaxb2-maven-plugin to compile XSD files with xjc. Now, suppose the
modules
> > are compiled in the order A-->B. For A everything works fine (i.e. I
get
> > the
> > *XsdImpl.java), but for B I get the following:
> >
> > /[INFO]
> >

> > [ERROR] Failed to execute goal
org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc
> > (model) on project B: DTD factory class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory. -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute
> > goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc (model) on project B:
DTD
> > factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not
> > extend
> > from DTDDVFactory
> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

> >at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >
> >
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

> >at
> >
> >
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

> >at java.lang.reflect.Method.invoke(Method.java:597)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > Caused by: org.apache.maven.plugin.MojoExecutionException: DTD factory
> > class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:352)
> >at
> >
> >
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)

> >... 19 more
> > Caused by: org.apache.xerces.impl.dv.DVFactoryException: DTD factory
class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaValidator.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.XMLSchemaValidatorComponentManager.(Unknown

> > Source)
> >at
> > org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.AbstractXMLSchema.newValidatorHandler(Unknown

> > Source)
> >at
com.sun.tools.xjc.SchemaCache.newVal

Re: Problem with jaxb2-maven-plugin 1.2

[smoking81]

Hi 3.0.2
Bye
Il giorno 16/dic/2011 16:56, "Anders Hammar [via Maven]" <
ml-node+s40175n5080629...@n5.nabble.com> ha scritto:
>
> What version of Maven are you using?
>
> /Anders (mobile)
> Den 16 dec 2011 16.37 skrev "smoking81" <[hidden email]>:
>
> > Hi there! I am new in the ML and also a new maven user.. I've hope
anybody
> > here will kindly help me with a problem is letting me get crazy... :)
> >
> > I will try to briefly describe it here:
> >
> > I have a modular project in which, for every single module, I use
> > jaxb2-maven-plugin to compile XSD files with xjc. Now, suppose the
modules
> > are compiled in the order A-->B. For A everything works fine (i.e. I
get
> > the
> > *XsdImpl.java), but for B I get the following:
> >
> > /[INFO]
> >

> > [ERROR] Failed to execute goal
org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc
> > (model) on project B: DTD factory class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory. -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute
> > goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc (model) on project B:
DTD
> > factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not
> > extend
> > from DTDDVFactory
> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

> >at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >
> >
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

> >at
> >
> >
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

> >at java.lang.reflect.Method.invoke(Method.java:597)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > Caused by: org.apache.maven.plugin.MojoExecutionException: DTD factory
> > class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:352)
> >at
> >
> >
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)

> >... 19 more
> > Caused by: org.apache.xerces.impl.dv.DVFactoryException: DTD factory
class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaValidator.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.XMLSchemaValidatorComponentManager.(Unknown

> > Source)
> >at
> > org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.AbstractXMLSchema.newValidatorHandler(Unknown

> > Source)
> >at
com.sun.tools.xjc.SchemaCache.newVal

Re: Problem with jaxb2-maven-plugin 1.2

[smoking81]

Hi 3.0.2
Bye
Il giorno 16/dic/2011 16:56, "Anders Hammar [via Maven]" <
ml-node+s40175n5080629...@n5.nabble.com> ha scritto:
>
> What version of Maven are you using?
>
> /Anders (mobile)
> Den 16 dec 2011 16.37 skrev "smoking81" <[hidden email]>:
>
> > Hi there! I am new in the ML and also a new maven user.. I've hope
anybody
> > here will kindly help me with a problem is letting me get crazy... :)
> >
> > I will try to briefly describe it here:
> >
> > I have a modular project in which, for every single module, I use
> > jaxb2-maven-plugin to compile XSD files with xjc. Now, suppose the
modules
> > are compiled in the order A-->B. For A everything works fine (i.e. I
get
> > the
> > *XsdImpl.java), but for B I get the following:
> >
> > /[INFO]
> >

> > [ERROR] Failed to execute goal
org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc
> > (model) on project B: DTD factory class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory. -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute
> > goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc (model) on project B:
DTD
> > factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not
> > extend
> > from DTDDVFactory
> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

> >at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >
> >
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

> >at
> >
> >
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

> >at java.lang.reflect.Method.invoke(Method.java:597)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > Caused by: org.apache.maven.plugin.MojoExecutionException: DTD factory
> > class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:352)
> >at
> >
> >
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)

> >... 19 more
> > Caused by: org.apache.xerces.impl.dv.DVFactoryException: DTD factory
class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaValidator.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.XMLSchemaValidatorComponentManager.(Unknown

> > Source)
> >at
> > org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.AbstractXMLSchema.newValidatorHandler(Unknown

> > Source)
> >at
com.sun.tools.xjc.SchemaCache.newVal

Re: Problem with jaxb2-maven-plugin 1.2

[smoking81]

Hi 3.0.2
Bye
Il giorno 16/dic/2011 16:56, "Anders Hammar [via Maven]" <
ml-node+s40175n5080629...@n5.nabble.com> ha scritto:
>
> What version of Maven are you using?
>
> /Anders (mobile)
> Den 16 dec 2011 16.37 skrev "smoking81" <[hidden email]>:
>
> > Hi there! I am new in the ML and also a new maven user.. I've hope
anybody
> > here will kindly help me with a problem is letting me get crazy... :)
> >
> > I will try to briefly describe it here:
> >
> > I have a modular project in which, for every single module, I use
> > jaxb2-maven-plugin to compile XSD files with xjc. Now, suppose the
modules
> > are compiled in the order A-->B. For A everything works fine (i.e. I
get
> > the
> > *XsdImpl.java), but for B I get the following:
> >
> > /[INFO]
> >

> > [ERROR] Failed to execute goal
org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc
> > (model) on project B: DTD factory class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory. -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute
> > goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc (model) on project B:
DTD
> > factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not
> > extend
> > from DTDDVFactory
> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

> >at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >
> >
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

> >at
> >
> >
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

> >at java.lang.reflect.Method.invoke(Method.java:597)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > Caused by: org.apache.maven.plugin.MojoExecutionException: DTD factory
> > class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:352)
> >at
> >
> >
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)

> >... 19 more
> > Caused by: org.apache.xerces.impl.dv.DVFactoryException: DTD factory
class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaValidator.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.XMLSchemaValidatorComponentManager.(Unknown

> > Source)
> >at
> > org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.AbstractXMLSchema.newValidatorHandler(Unknown

> > Source)
> >at
com.sun.tools.xjc.SchemaCache.newVal

Re: Problem with jaxb2-maven-plugin 1.2

[smoking81]

Hi 3.0.2
Bye
Il giorno 16/dic/2011 16:56, "Anders Hammar [via Maven]" <
ml-node+s40175n5080629...@n5.nabble.com> ha scritto:
>
> What version of Maven are you using?
>
> /Anders (mobile)
> Den 16 dec 2011 16.37 skrev "smoking81" <[hidden email]>:
>
> > Hi there! I am new in the ML and also a new maven user.. I've hope
anybody
> > here will kindly help me with a problem is letting me get crazy... :)
> >
> > I will try to briefly describe it here:
> >
> > I have a modular project in which, for every single module, I use
> > jaxb2-maven-plugin to compile XSD files with xjc. Now, suppose the
modules
> > are compiled in the order A-->B. For A everything works fine (i.e. I
get
> > the
> > *XsdImpl.java), but for B I get the following:
> >
> > /[INFO]
> >

> > [ERROR] Failed to execute goal
org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc
> > (model) on project B: DTD factory class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory. -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute
> > goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc (model) on project B:
DTD
> > factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not
> > extend
> > from DTDDVFactory
> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

> >at
> >
> >
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

> >at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >
> >
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

> >at
> >
> >
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

> >at java.lang.reflect.Method.invoke(Method.java:597)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >at
> >
> >
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

> >at
> >
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > Caused by: org.apache.maven.plugin.MojoExecutionException: DTD factory
> > class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:352)
> >at
> >
> >
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)

> >at
> >
> >
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)

> >... 19 more
> > Caused by: org.apache.xerces.impl.dv.DVFactoryException: DTD factory
class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at
org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
Source)
> >at org.apache.xerces.impl.xs.XMLSchemaValidator.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.XMLSchemaValidatorComponentManager.(Unknown

> > Source)
> >at
> > org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.(Unknown
> > Source)
> >at
> >
> >
org.apache.xerces.jaxp.validation.AbstractXMLSchema.newValidatorHandler(Unknown

> > Source)
> >at
com.sun.tools.xjc.SchemaCache.newVal

Re: Problem with jaxb2-maven-plugin 1.2

[smoking81]

3.0.2. Bye
Il giorno 16/dic/2011 16:56, "Anders Hammar [via Maven]" <
ml-node+s40175n5080629...@n5.nabble.com> ha scritto:

> What version of Maven are you using?
>
> /Anders (mobile)
> Den 16 dec 2011 16.37 skrev "smoking81" <[hidden 
> email]>:
>
>
> > Hi there! I am new in the ML and also a new maven user.. I've hope
> anybody
> > here will kindly help me with a problem is letting me get crazy... :)
> >
> > I will try to briefly describe it here:
> >
> > I have a modular project in which, for every single module, I use
> > jaxb2-maven-plugin to compile XSD files with xjc. Now, suppose the
> modules
> > are compiled in the order A-->B. For A everything works fine (i.e. I get
> > the
> > *XsdImpl.java), but for B I get the following:
> >
> > /[INFO]
> > 
> > [ERROR] Failed to execute goal
> org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc
> > (model) on project B: DTD factory class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory. -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> > goal org.codehaus.mojo:jaxb2-maven-plugin:1.2:xjc (model) on project B:
> DTD
> > factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not
> > extend
> > from DTDDVFactory
> >at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>
> >at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> >at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> >at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>
> >at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>
> >at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>
> >at
> >
> >
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>
> >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >at
> >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> >at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> >at java.lang.reflect.Method.invoke(Method.java:597)
> >at
> >
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>
> >at
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> >at
> >
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>
> >at
> >
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > Caused by: org.apache.maven.plugin.MojoExecutionException: DTD factory
> > class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:352)
> >at
> >
> >
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>
> >at
> >
> >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>
> >... 19 more
> > Caused by: org.apache.xerces.impl.dv.DVFactoryException: DTD factory
> class
> > org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from
> > DTDDVFactory.
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown
> > Source)
> >at
> org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at
> org.apache.xerces.impl.xs.opti.SchemaParsingConfig.(Unknown
> > Source)
> >at org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at org.apache.xerces.impl.xs.traversers.XSDHandler.(Unknown
> > Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
> Source)
> >at org.apache.xerces.impl.xs.XMLSchemaLoader.(Unknown
> Source)
> >at org.apache.xerces.impl.xs.XMLSchemaValidator.(Unknown
> > Source)
> >at
> >
> >
> org.apache.xerces.jaxp.validation.XMLSchemaValidatorComponentManager.(Unknown
>
> > Source)
> >at
> > org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.(Unknown
> > Source)
> >at
> >
> >
> org.apache.xerces.j

Re: Multi Module Project Failing - Help Me

[Daivish Shah]

Hi Barrie,

That's correct It's not MAVEN issue but i was thinking that whatever we
define in POM.XML file as dependency eclipse must find it automatically for
it's compilation yes this is working well for projects which doesn't have
SUB MODULEs for XSD projects.

But this is not working automatically only in the case, When there is XSD
Project as sub module project and that module depends internally with other
modules. Then i have to do manual job.

Yes you are right the only quickest and easiest solution is to add that JAR
as dependency manually. But i was looking for something automated solution.

But i really appreciate your help on this to understand it properly. I
always LOVE this MAVEN USER Group to resolve all my maven questions.

Thanks,
daivish.

On Thu, Dec 15, 2011 at 4:54 PM, Barrie Treloar  wrote:

> On Fri, Dec 16, 2011 at 5:24 AM, Daivish Shah 
> wrote:
> > Hi Barrie Treloar,
> >
> > You suggestions looks good to me, I tried your suggestion.
> >
> > And yes this is not working only XSD generated import statements in
> Module
> > 2. I have one DAO module too which is also generating some JAR file. And
> > that is also imported in Module2 but that import statements doesn't show
> X
> > as compilation error in Eclipse but i have only problem with XSD
> generated
> > files with my Eclipse. If i execute mvn install from Top level it means
> > MainProject then it doesn't show any compilation Error in execution log.
>
> So, great that Maven is working properly.
>
> > And yes XSD project is publishing JAR file and which is located under my
> > local repository correctly. and it has all generated classes in it. So
> if i
> > manually add that Depedancy in my Eclipse then all X sign as compilation
> > error gone, But ideally it should not be Manual. If i define as
> Dependency
> > it should automatically pickup that file.
> >
> > And this is only issue with Sub Module of Main Project and XSD module.
> And
> > in MAVEN Dependency list it's showing as FOLDER icon and all other
> > dependencies are showing as JAR icon and location of those JAR files are
> > showing as my LOCAL Repository of MAVEN.
> >
> > I tried using  build-helper-maven-plugin but it doesn't help to resolve
> my
> > COMPILATION error Icons in ECLIPSE so i am confused how to resolve this
> XSD
> > related problem. If any other suggestion or advice will really
> appreciated.
>
> This is not a Maven issue.  This is an Eclipse issue.
>
> What are you using to configure Eclipse?
> If you are using the maven-eclipse-plugin I can give guidance.
> If you are using something else then I can't.
>
> The first step is to manually fix the problem.
> Which you appear to have done by manually adding the jar file as a
> dependency.
>
> For my project, I am just manually adding the
> target/-.jar into that project's .classpath
> (Right click the jar file > build path > add to build path)
> And then export that jar file in the class file (Right click the
> project > build path > configure build path > order and export tab >
> enable jar > click ok)
>
> I haven't bothered to find a way to automate this yet.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Solve my exception for mvn installtion

[Barrie Treloar]

On Fri, Dec 16, 2011 at 11:54 PM, ashishmemod  wrote:
> I found the problem and now it is solved.
>
> thank all who helped me.

This reply makes me angry.

Please state what you problem actually was and what you did to solve it.

The next person who has the same problem as you will hate you for not
posting this information.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Multi Module Project Failing - Help Me

[Barrie Treloar]

On Sat, Dec 17, 2011 at 4:10 AM, Daivish Shah  wrote:
> Hi Barrie,
>
> That's correct It's not MAVEN issue but i was thinking that whatever we
> define in POM.XML file as dependency eclipse must find it automatically for
> it's compilation yes this is working well for projects which doesn't have
> SUB MODULEs for XSD projects.
>
> But this is not working automatically only in the case, When there is XSD
> Project as sub module project and that module depends internally with other
> modules. Then i have to do manual job.
>
> Yes you are right the only quickest and easiest solution is to add that JAR
> as dependency manually. But i was looking for something automated solution.
>
> But i really appreciate your help on this to understand it properly. I
> always LOVE this MAVEN USER Group to resolve all my maven questions.

Well, I'd appreciate an automated solution, but I've never cared
enough to hunt it down.
If this bugs you more than me and you would like to find the answer,
then that would help me and any others who want it in the future...

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Problem with jaxb2-maven-plugin 1.2

[Wayne Fay]

I *hate* Nabble...Can we just block it? Ugh.

Wayne

On 12/16/11, smoking81  wrote:
> 3.0.2. Bye
> Il giorno 16/dic/2011 16:56, "Anders Hammar [via Maven]" <
> ml-node+s40175n5080629...@n5.nabble.com> ha scritto:
>
>> What version of Maven are you using?
...
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Problem-with-jaxb2-maven-plugin-1-2-tp5080568p5080927.html
> Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Multi Module Project Failing - Help Me

[Daivish Shah]

Yes I am looking for automated solution because we have 100 projects and
almost all projects has XSD sub projects and we have to use this manual
technic for all projects.

So we can find something automated then it will make life easy. And we are
right now converting all projects from ANT to MAVEN so if we can find some
standard automated solution then it helps everybody in our team..

Thanks,
daivish.

On Fri, Dec 16, 2011 at 11:51 AM, Barrie Treloar  wrote:

> On Sat, Dec 17, 2011 at 4:10 AM, Daivish Shah 
> wrote:
> > Hi Barrie,
> >
> > That's correct It's not MAVEN issue but i was thinking that whatever we
> > define in POM.XML file as dependency eclipse must find it automatically
> for
> > it's compilation yes this is working well for projects which doesn't have
> > SUB MODULEs for XSD projects.
> >
> > But this is not working automatically only in the case, When there is XSD
> > Project as sub module project and that module depends internally with
> other
> > modules. Then i have to do manual job.
> >
> > Yes you are right the only quickest and easiest solution is to add that
> JAR
> > as dependency manually. But i was looking for something automated
> solution.
> >
> > But i really appreciate your help on this to understand it properly. I
> > always LOVE this MAVEN USER Group to resolve all my maven questions.
>
> Well, I'd appreciate an automated solution, but I've never cared
> enough to hunt it down.
> If this bugs you more than me and you would like to find the answer,
> then that would help me and any others who want it in the future...
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

maven-release-plugin: using git where do I see the tag used to build the release in the pom?

[Mirko Friedenhagen]

Hello,

I know that with SVN the developerConnection and connection are
updated to the "real" URL, that is when I invoke release:prepare with
a URL like:
https://SVNSERVER/svn/REPO/myproject/branches/release it will be
replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0
which is fine because now I know which revision to checkout for
building the release.

With git there is no such possibility to realize this with rewriting
the URL AFAIK. So I would have expected however, that maybe the 
element would be updated to reflect the fact, that the pom is the one
of release, either to the "symbolic name" myproject-1.0 or to the hash
of the tag.

Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Multi Module Project Failing - Help Me

[Stephen Connolly]

The automated solution is probably a patch to the xmlbeans plugin you
are using...

Given that the plugin is hosted at mojo, it should be easy for a well
structured patch with tests to get accepted. If you have issues
getting a well structured patch accepted, ping myself or Barry and I'm
sure we can help.

-Stephen

On 16 December 2011 20:51, Daivish Shah  wrote:
> Yes I am looking for automated solution because we have 100 projects and
> almost all projects has XSD sub projects and we have to use this manual
> technic for all projects.
>
> So we can find something automated then it will make life easy. And we are
> right now converting all projects from ANT to MAVEN so if we can find some
> standard automated solution then it helps everybody in our team..
>
> Thanks,
> daivish.
>
> On Fri, Dec 16, 2011 at 11:51 AM, Barrie Treloar  wrote:
>
>> On Sat, Dec 17, 2011 at 4:10 AM, Daivish Shah 
>> wrote:
>> > Hi Barrie,
>> >
>> > That's correct It's not MAVEN issue but i was thinking that whatever we
>> > define in POM.XML file as dependency eclipse must find it automatically
>> for
>> > it's compilation yes this is working well for projects which doesn't have
>> > SUB MODULEs for XSD projects.
>> >
>> > But this is not working automatically only in the case, When there is XSD
>> > Project as sub module project and that module depends internally with
>> other
>> > modules. Then i have to do manual job.
>> >
>> > Yes you are right the only quickest and easiest solution is to add that
>> JAR
>> > as dependency manually. But i was looking for something automated
>> solution.
>> >
>> > But i really appreciate your help on this to understand it properly. I
>> > always LOVE this MAVEN USER Group to resolve all my maven questions.
>>
>> Well, I'd appreciate an automated solution, but I've never cared
>> enough to hunt it down.
>> If this bugs you more than me and you would like to find the answer,
>> then that would help me and any others who want it in the future...
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Solve my exception for mvn installtion

[Graham Leggett]

On 16 Dec 2011, at 9:48 PM, Barrie Treloar wrote:

>> I found the problem and now it is solved.
>> 
>> thank all who helped me.
> 
> This reply makes me angry.
> 
> Please state what you problem actually was and what you did to solve it.
> 
> The next person who has the same problem as you will hate you for not
> posting this information.

+1.

Regards,
Graham
--


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Release Plugin 2.2.2 Released

[Stephen Connolly]

The Maven team is pleased to announce the release of the Maven XXX
Plugin, version Y.Z

This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps:
prepare and perform.

http://maven.apache.org/plugins/maven-release-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-release-plugin
  2.2.2


Release Notes - Maven 2.x Release Plugin - Version 2.2.2

** Bug
* [MRELEASE-354] - Versions defined in profiles are not updated
* [MRELEASE-454] - The Release-Plugin does not rewrite
dependencies in the DependencyManagement with scope "import"
* [MRELEASE-577] - release:prepare does not pass argument
"--settings" with current settings.xml to inner maven

** Improvement
* [MRELEASE-708] - upgrade to last scm 1.6 to integrate new scm
provider mks integrity

** New Feature
* [MRELEASE-467] - Release preparation should update version of
plugin dependencies


Enjoy,

-The Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org