[ http://jira.codehaus.org/browse/MOJO-130?page=comments#action_58641 ]
Jimisola Laursen commented on MOJO-130: --------------------------------------- E.g. the xmlConfig element takes an attribute named implementation: <xmlConfig implementation="java.io.File">src/test/xmlbeans-xsd/lt_license.xsdconfig</xmlConfig> Are there other (configuration sub) elements that take attributes. > Can't change the schemaDirectory with xmlbeans plugin configuration > ------------------------------------------------------------------- > > Key: MOJO-130 > URL: http://jira.codehaus.org/browse/MOJO-130 > Project: Mojo > Type: Bug > Components: xmlbeans > Versions: 2.0-beta-1 > Environment: MACOSX, JDK 1.5 > Reporter: Nathan Sowatskey > Assignee: Corridor Software Developer > Fix For: 2.0 > > > If I run the xmlbeans plugin with this configuration: > plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>maven-xmlbeans-plugin</artifactId> > <version>2.0-beta-1</version> > <executions> > <execution> > <goals> > <goal>xmlbeans</goal> > </goals> > </execution> > </executions> > <inherited>true</inherited> > <configuration> > > <schemaDirectory>src/main/resources/xsd</schemaDirectory> > </configuration> > </plugin> > I get: > java.lang.NullPointerException > at > org.codehaus.mojo.xmlbeans.XmlBeansPlugin.getXsdFiles(XmlBeansPlugin.java:636) > at > org.codehaus.mojo.xmlbeans.ParameterAdapter.getCompilerParameters(ParameterAdapter.java:51) > at > org.codehaus.mojo.xmlbeans.XmlBeansPlugin.execute(XmlBeansPlugin.java:282) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:452) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > 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:585) > 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) > But if I copy the xsds to src/xsd and change the configuration to point > there, the xsd files are found. I suspect that the configuration is being > ignored. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
