Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.6
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Maven 1.0.2
maven-multiproject-plugin-1.5.jar
maven-idea-plugin-1.6.jar
-
Number of attachments :
Description
My general project structure is something like this:
Toplevel project with no artifacts.
Tier 2 children of toplevel project are subprojects that inherit from the toplevel project and are of 2 types (jar or ejb).
Tier 3 children of tier 2 projects are subprojects of tier 2 projects and are all of type jar.
The idea:multiproject task fails and generates a truncated module file as seen below. v1.5 of the IDEA plugin does not have this problem, but fails in other ways that also makes it unsuitable for me.
Output:
[CUT-REMOVED ARTIFACT DOWNLOAD OUTPUT]
[echo] DEPRECATED: the use of dependency-handle is deprecated. Please use maven:get/set to modify properties of the multiproject plugin
build:start:
idea:init:
war:load:
[echo] DEPRECATED: war:load is deprecated, please use maven:get tags
idea:module:
[echo] Creating c:\repo\Products\Wolverine\WorkflowServices/WolverineWorkflowServices.iml ...
BUILD FAILED
File...... C:\Documents and Settings\jwan.21TECHNOLOGIES\.maven\cache\maven-idea-plugin-1.6\plugin.jelly
Element... j:import
Line...... 78
Column.... 79
file:/C:/Documents and Settings/jwan.21TECHNOLOGIES/.maven/cache/maven-idea-plugin-1.6/plugin-resources/templates/v4/module.jelly:41:106: <maven:makeRelativePath> You must define an attribute called 'path' for this tag.
Total time: 3 seconds
Finished at: Fri Oct 06 11:42:00 CDT 2006
Generated Module file:
<?xml version="1.0" encoding="UTF-8"?>
<module version="4" relativePaths="true" type="J2EE_EJB_MODULE">
<component name="EjbModuleBuildComponent">
<setting name="EXPLODED_URL" value="file://">
</setting>
<setting name="EXPLODED_ENABLED" value="false">
</setting>
<setting name="JAR_URL" value="file://$MODULE_DIR$/target/<IRRELEVANT INFO>.jar">
</setting>
<setting name="JAR_ENABLED" value="true">
</setting>
</component>
<component name="EjbModuleProperties">
The problem appears to be emanating from line 41 in templates/v4/module.jelly:
<maven:makeRelativePath var="value" basedir="${basedir}" path="${maven.ejb.src}" separator="/" />
maven.ejb.src is considered an optional property for the EJB plugin. As such, it is likely not present.
From EJB plugin notes:
"Root of files to be included within the ejb-jar. The same directory structure will be followed within the assembled jar file. Please note this is not for your java code or class files, these are other resources. Alternatively, you can use the resources element of the project.xml to specify resource across various directories, just as you would for a jar or war project."