Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
Description
EAR configuration <ejb3Module> is listed in documentation as though it were still working:
http://maven.apache.org/plugins/maven-ear-plugin/modules.html#ejb3Module
User gets "Artifact[ejb3:*.*.*] is not a dependency of the project." error.
User, being new to Maven, spends a couple of hours trying to fix the error by tweaking his other POMs to set dependency type to EJB3, etc.
User turns to Google.
User discovers that ejb3Module is broken and deprecated and has been for over a year or two:
http://www.5341.com/msg/224841.html
http://jira.codehaus.org/browse/MEAR-40 (see comments)
I am confused by your report.
The http://maven.apache.org/plugins/maven-ear-plugin/modules.html#ejb3Module redirects to a page where it's stated
"ejb3Module (deprecated. ejbModule provides the same functionality)"
And, as far as I know, it's not broken. Why are you saying it's broken?