[
http://jira.codehaus.org/browse/MEAR-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229796#action_229796
]
Stephane Nicoll commented on MEAR-129:
--------------------------------------
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?
> ejb3Module broken and deprecated but not indicated as such in website
> documentation
> -----------------------------------------------------------------------------------
>
> Key: MEAR-129
> URL: http://jira.codehaus.org/browse/MEAR-129
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Reporter: David Wallace Croft
>
> 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)
--
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
