FWIW, I already had that XML in my omod/pom.xml file. The error definitely occurs while running the install target on the omod module, and not when I "package" it.
Jeremy Keiper OpenMRS Core Developer AMPATH / IU-Kenya Support On Thu, Oct 20, 2011 at 7:00 AM, Ben Wolfe <[email protected]> wrote: > So the other fix could be to change the maven-openmrs-plugin in the parent > pom.xml to 1.0.1 instead of just 1.0 ? > > Why would this have broken all of a sudden for him though? > > Ben > > > On Thu, Oct 20, 2011 at 4:54 AM, Matthew Blanchette < > [email protected]> wrote: > >> Yes, this is a known issue with version 1.0 of the maven-openmrs-plugin. >> There was a bug in older versions of the plugin attempting to verify the >> config.xml. >> This is fixed in version 1.0.1. >> >> But as Ben mentioned, you most likely don't want to verify (set config >> param to false). >> Part of the verify checks that the classes referenced in config.xml exist, >> which could only useful in a single project setup (not multimodule). >> >> As a side note, based on IDE integration, versions of the archetype/module >> scripts may be created for a single module jar/omod project (since the omod >> packaging proved problematic with m2eclipse). >> >> I would also suggest to not depend on a SNAPSHOT version of the 1.8 >> openmrs artifacts since there are releases available (1.8.0, 1.8.1, 1.8.2). >> >> -Matt >> >> >> On Wed, Oct 19, 2011 at 2:45 PM, Ben Wolfe <[email protected]> wrote: >> >>> You can put an element in your module to not verify it: >>> <configuration> >>> <verifyOmod>false</verifyOmod> >>> </configuration> >>> >>> Did you remove that recently? Or set it to true? (cc'ing Matt so he >>> knows of this thread, he (and motech devs?) is the one that initially wrote >>> the maven plugin for building modules) >>> >>> Ben >>> >>> >>> On Wed, Oct 19, 2011 at 8:43 PM, Jeremy Keiper <[email protected]>wrote: >>> >>>> I am getting the following error when trying to "mvn install" my module. >>>> I already moved the ModuleActivator and Extension classes to the OMOD from >>>> the API as a result of previous errors from this maven plugin, but I do not >>>> know how to proceed from this point. Can someone involved in developing >>>> the >>>> openmrs:verify-module plugin give me some insight? >>>> >>>> ================================ >>>> >>>> [INFO] [openmrs:package-module {execution: default-package-module}] >>>> [INFO] Packaging OpenMRS module >>>> [INFO] Building jar: >>>> /home/jkeiper/NetBeansProjects/pcslabinterface-trunk/omod/target/pcslabinterface-0.5.1.omod >>>> [INFO] [openmrs:verify-module {execution: default-verify-module}] >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] FATAL ERROR >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] null >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Trace >>>> java.lang.NullPointerException >>>> at >>>> org.motech.openmrs.plugin.VerifyModuleMojo.execute(VerifyModuleMojo.java:123) >>>> at >>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) >>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) >>>> 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:597) >>>> 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) >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Total time: 27 seconds >>>> [INFO] Finished at: Wed Oct 19 13:36:23 EDT 2011 >>>> [INFO] Final Memory: 36M/350M >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> Jeremy Keiper >>>> OpenMRS Core Developer >>>> AMPATH / IU-Kenya Support >>>> ------------------------------ >>>> Click here to >>>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>>> OpenMRS Developers' mailing list >>> >>> >>> >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list >> > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
