[jira] Commented: (MDEP-128) Support ability to specify multiple "includeScope" parameters
[ http://jira.codehaus.org/browse/MDEP-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158605#action_158605 ] Matthew Lieder commented on MDEP-128: - While that makes sense, it is still counter-intuitive and I believe it would help a lot of people if what you just said could be documented somewhere (ideally with some notes added to the includeScope/excludeScope attributes on the goal). > Support ability to specify multiple "includeScope" parameters > - > > Key: MDEP-128 > URL: http://jira.codehaus.org/browse/MDEP-128 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement >Affects Versions: 2.0-alpha-4 >Reporter: Bryan Stopp >Assignee: Brian Fox > > You can only configure the plugin with either one includeScope or one > excludeScope. When executing the plugin to copy dependencies with the > following configuration: > >org.apache.maven.plugins >maven-dependency-plugin > > > copy-dependencies > validate > > copy-dependencies > > > > > /src/main/webapp/WEB-INF/lib > false > true > true > provided > > > It does exclude the provided scope, but it includes the test scope [easymock, > dbunit, and junit appear in the output directory]. I tried to correct this > problem by replacing the excludeScope parameter with two includeScope > parameters, one for compile one for runtime, but only the first parameter was > actually used. > I also tried to exclude test but got an error, something like, "Can't exclude > tests as that would exclude everything!". > The goal is to be able to recreate the default copy functionality that is > accomplished when executing a "mvn package" command, but be able to specify a > maven-dependency-plugin configuration. When specifying this configuration, it > overrides the default settings throughout the entire build life-cycle (as it > should). But it is impossible to configure the plugin in the exact same was > as the default settings. > This is needed to support copying dependencies into the WEB-INF/lib folder > within Eclipse workspaces, to support embedded application-server deployment. -- 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: (MNG-3228) Maven profile activation does not work when profile is defined in inherited 'parent' pom
[ http://jira.codehaus.org/browse/MNG-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157737#action_157737 ] Matthew Lieder edited comment on MNG-3228 at 12/11/08 9:59 AM: --- I can confirm this problem still exists in Maven 2.1.0-M1. Any chance of it being fixed in M2? was (Author: igx89): dfsdfsdf > Maven profile activation does not work when profile is defined in inherited > 'parent' pom > > > Key: MNG-3228 > URL: http://jira.codehaus.org/browse/MNG-3228 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: tony nys > Fix For: Reviewed Pending Version Assignment > > > The goal is to activate a maven profile based on OS user name. > When I create a standalone project with a profile activation, it works, > however, when I define the profile in a "parent" pom, it is never activated. > this works: > ... > > TONY > > > user.name > WINTONY > > > > > > So in this case, my profile is activated based on my OS user name > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'help'. > [INFO] > > [INFO] Building Proj1 > [INFO] task-segment: [help:active-profiles] (aggregator-style) > [INFO] > > [INFO] [help:active-profiles] > [INFO] > Active Profiles for Project 'com.capgemini.be.proj1:parent:pom:4.0.2': > The following profiles are active: > - TONY (source: pom) > -- > However, if I now have the profiles definition in the "parent" pom, it > doesn't work when I build a child project > So the child project references the parent pom containing the profiles and > the activation, but when it is built, > the profile is not activated > PARENT POM: > ... > > > TONY > > > user.name > WINTONY > > > > ... > CHILD POM (the one being built) > > > com.capgemini.be.proj1 > parent > 4.0.2 > > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'help'. > [INFO] > > [INFO] Building Proj1 Application > [INFO] task-segment: [help:active-profiles] (aggregator-style) > [INFO] > > [INFO] [help:active-profiles] > [INFO] > Active Profiles for Project 'com.capgemini.be.proj1:proj1-webapp:jar:4.0.2': > There are no active profiles. -- 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: (MNG-3228) Maven profile activation does not work when profile is defined in inherited 'parent' pom
[ http://jira.codehaus.org/browse/MNG-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157737#action_157737 ] Matthew Lieder commented on MNG-3228: - dfsdfsdf > Maven profile activation does not work when profile is defined in inherited > 'parent' pom > > > Key: MNG-3228 > URL: http://jira.codehaus.org/browse/MNG-3228 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: tony nys > Fix For: Reviewed Pending Version Assignment > > > The goal is to activate a maven profile based on OS user name. > When I create a standalone project with a profile activation, it works, > however, when I define the profile in a "parent" pom, it is never activated. > this works: > ... > > TONY > > > user.name > WINTONY > > > > > > So in this case, my profile is activated based on my OS user name > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'help'. > [INFO] > > [INFO] Building Proj1 > [INFO] task-segment: [help:active-profiles] (aggregator-style) > [INFO] > > [INFO] [help:active-profiles] > [INFO] > Active Profiles for Project 'com.capgemini.be.proj1:parent:pom:4.0.2': > The following profiles are active: > - TONY (source: pom) > -- > However, if I now have the profiles definition in the "parent" pom, it > doesn't work when I build a child project > So the child project references the parent pom containing the profiles and > the activation, but when it is built, > the profile is not activated > PARENT POM: > ... > > > TONY > > > user.name > WINTONY > > > > ... > CHILD POM (the one being built) > > > com.capgemini.be.proj1 > parent > 4.0.2 > > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'help'. > [INFO] > > [INFO] Building Proj1 Application > [INFO] task-segment: [help:active-profiles] (aggregator-style) > [INFO] > > [INFO] [help:active-profiles] > [INFO] > Active Profiles for Project 'com.capgemini.be.proj1:proj1-webapp:jar:4.0.2': > There are no active profiles. -- 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
