[jira] Closed: (MEAR-62) scope "provided" not applied
[ http://jira.codehaus.org/browse/MEAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] johan Eltes closed MEAR-62. --- Resolution: Cannot Reproduce Requested feature already there. User error. > scope "provided" not applied > > > Key: MEAR-62 > URL: http://jira.codehaus.org/browse/MEAR-62 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: Any >Reporter: johan Eltes >Assignee: Stephane Nicoll > > When packaging an ear, the ear plugin does not exclude transitive > dependencies with scope "provided". A war or ejb project may declare > "provided"-scoped dependencies (e.g. j2ee apis). The purpose is to not > include these dependencies when packaging the archive. For enterprise > applications, the EAR project is responsible for doing the packaging of its > modules dependencies. Although scope packaging is defined for transitive > dependencies (dependencies declared by the module POMs), the ear plug-in > still includes these libraries in the produced ear. -- 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
[jira] Commented: (MEAR-62) scope "provided" not applied
[ http://jira.codehaus.org/browse/MEAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92724 ] johan Eltes commented on MEAR-62: - A clean-room project worked as expected. I cleaned the repository and rebuilt the real-world system. It made me discover inconsistent group names. I changed group namespace of my artifacts half through but left one depenency to the old binary which - of cause - had a POM missing the concerned scope elements. Sorry for spamming jira... Keep up the great work :-) > scope "provided" not applied > > > Key: MEAR-62 > URL: http://jira.codehaus.org/browse/MEAR-62 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: Any >Reporter: johan Eltes >Assignee: Stephane Nicoll > > When packaging an ear, the ear plugin does not exclude transitive > dependencies with scope "provided". A war or ejb project may declare > "provided"-scoped dependencies (e.g. j2ee apis). The purpose is to not > include these dependencies when packaging the archive. For enterprise > applications, the EAR project is responsible for doing the packaging of its > modules dependencies. Although scope packaging is defined for transitive > dependencies (dependencies declared by the module POMs), the ear plug-in > still includes these libraries in the produced ear. -- 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
[jira] Issue Comment Edited: (MEAR-61) Avoid the need for redundant specification of module type
[ http://jira.codehaus.org/browse/MEAR-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92713 ] johan Eltes edited comment on MEAR-61 at 4/12/07 7:57 AM: -- Aha..of cause. I'm actually naming the dependency by assigning the type element. Should have grasped that... was: Aha..of casue. I'm actually naming the dependency by assigning the type element. Should have grasped that... > Avoid the need for redundant specification of module type > - > > Key: MEAR-61 > URL: http://jira.codehaus.org/browse/MEAR-61 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: Any >Reporter: johan Eltes >Assignee: Stephane Nicoll > > The POMs of the modules to be packaged by the ear plugin, contain information > about module type (e.g. packaging). The ear plug-in does not read this > information. As a consequence, the ear POM has to redundantly define a type > element on the dependencies ear module dependencies: > ear POM: > > mywebapp > mywebapp > 1.0.0 > war <-- redundant information > > war POM: > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > mywebapp > mywebapp > war <-- Should be picked up from here -- 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
[jira] Commented: (MEAR-61) Avoid the need for redundant specification of module type
[ http://jira.codehaus.org/browse/MEAR-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92713 ] johan Eltes commented on MEAR-61: - Aha..of casue. I'm actually naming the dependency by assigning the type element. Should have grasped that... > Avoid the need for redundant specification of module type > - > > Key: MEAR-61 > URL: http://jira.codehaus.org/browse/MEAR-61 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: Any >Reporter: johan Eltes >Assignee: Stephane Nicoll > > The POMs of the modules to be packaged by the ear plugin, contain information > about module type (e.g. packaging). The ear plug-in does not read this > information. As a consequence, the ear POM has to redundantly define a type > element on the dependencies ear module dependencies: > ear POM: > > mywebapp > mywebapp > 1.0.0 > war <-- redundant information > > war POM: > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > mywebapp > mywebapp > war <-- Should be picked up from here -- 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
[jira] Created: (MEAR-62) scope "provided" not applied
scope "provided" not applied Key: MEAR-62 URL: http://jira.codehaus.org/browse/MEAR-62 Project: Maven 2.x Ear Plugin Issue Type: Bug Affects Versions: 2.3 Environment: Any Reporter: johan Eltes When packaging an ear, the ear plugin does not exclude transitive dependencies with scope "provided". A war or ejb project may declare "provided"-scoped dependencies (e.g. j2ee apis). The purpose is to not include these dependencies when packaging the archive. For enterprise applications, the EAR project is responsible for doing the packaging of its modules dependencies. Although scope packaging is defined for transitive dependencies (dependencies declared by the module POMs), the ear plug-in still includes these libraries in the produced ear. -- 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
[jira] Created: (MEAR-61) Avoid the need for redundant specification of module type
Avoid the need for redundant specification of module type - Key: MEAR-61 URL: http://jira.codehaus.org/browse/MEAR-61 Project: Maven 2.x Ear Plugin Issue Type: Improvement Affects Versions: 2.3 Environment: Any Reporter: johan Eltes The POMs of the modules to be packaged by the ear plugin, contain information about module type (e.g. packaging). The ear plug-in does not read this information. As a consequence, the ear POM has to redundantly define a type element on the dependencies ear module dependencies: ear POM: mywebapp mywebapp 1.0.0 war <-- redundant information war POM: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 mywebapp mywebapp war <-- Should be picked up from here -- 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
[jira] Commented: (MEJB-3) Add ejb bundle feature like in maven 1
[ http://jira.codehaus.org/browse/MEJB-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92148 ] johan Eltes commented on MEJB-3: I'm on Maven 2.0.5. Although I've added the ejb plugin configuration stated above... maven-ejb-plugin true ... my dependencies don't get listed in the ClassPath: entry of the generated MANIFEST.MF. Is there anything else I need to do? Any specific scope to be defined for the dependencies? > Add ejb bundle feature like in maven 1 > -- > > Key: MEJB-3 > URL: http://jira.codehaus.org/browse/MEJB-3 > Project: Maven 2.x Ejb Plugin > Issue Type: New Feature > Environment: windows >Reporter: Alexandre Vivien > > It could be nice if we could include dependencies in the ejb jar produce by > the ejb plugin. In fact, I think an ejb bundle feature like in Maven 1 will > be useful. We could use the dependencies scope or whatever. (Perhaps it can > be handy to add a new scope name "bundle" that could be use with ejb, war and > ear plugin ) > Thanks. > Alexandre Vivien -- 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
