Currently if you check out a mavenized module eclipse will fail to recognize the "omod" project as a java project. This is because we have "packaging" set to "omod" in the pom.xml. If packaging is "jar" eclipse is ok with things and everything works out of the box/checkout with eclipse.
The openmrs module maven plugin that Matt and Co wrote looks at this packaging type and so knows what files to put into the generated target/moduleid.omod. Matt looked into a solution and modified the plugin and pom slightly to allow for the pom.xml packaging to be "jar". *Question:* After the modification, when the module is packaged both a jar and an omod file is put into omod/target. Is this an acceptable trade-off to people to make module startup easier for folks? Ben _________________________________________ 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]
