[jira] Updated: (MSHARED-162) actTransitively wildcard patterns can fail on pattern-based filters

[ http://jira.codehaus.org/browse/MSHARED-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MSHARED-162: --- Fix Version/s: maven-common-artifact-filters 1.3 > actTransitively wildcard patterns can fail on pattern-b

[jira] Created: (MSHARED-162) actTransitively wildcard patterns can fail on pattern-based filters

actTransitively wildcard patterns can fail on pattern-based filters --- Key: MSHARED-162 URL: http://jira.codehaus.org/browse/MSHARED-162 Project: Maven Shared Components Issue

[jira] Commented: (MCHECKSTYLE-135) Can't use a configFile with an URL

[ http://jira.codehaus.org/browse/MCHECKSTYLE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234915#action_234915 ] Rick Mangi commented on MCHECKSTYLE-135: Is this actually fixed with 2.6? I have the exa

[jira] Commented: (WAGON-257) java.lang.ArrayIndexOutOfBoundsException: 0 when deploying via scp

[ http://jira.codehaus.org/browse/WAGON-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234913#action_234913 ] Thomas Vandahl commented on WAGON-257: -- Yes, that's exactly the case. Thanks for the hint. Is tha

[jira] Commented: (MSITE-417) CLONE -The modules menu is not inherited if the parent project has no modules of its own

[ http://jira.codehaus.org/browse/MSITE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234895#action_234895 ] Michael Wenig commented on MSITE-417: - I made a workaround at our side by adding a dummy-module to

[jira] Commented: (MSITE-417) CLONE -The modules menu is not inherited if the parent project has no modules of its own

[ http://jira.codehaus.org/browse/MSITE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234896#action_234896 ] Michael Wenig commented on MSITE-417: - The problem is also present in 2.1.1! > CLONE -The modules

[jira] Created: (MNGSITE-119) French maven mirror proposal

French maven mirror proposal Key: MNGSITE-119 URL: http://jira.codehaus.org/browse/MNGSITE-119 Project: Maven 2 Project Web Site Issue Type: New Feature Reporter: Freddy munoz Please allow me introd

Re: Obsolete jars from WEB-INF/lib end up in war file

The current workaround: maven-clean-plugin WebContent/WEB-INF/lib Still curious why this happens.. -- View this message in context: http://maven.40175.n

Jars from WEB-INF/lib in war file

Hi there, We are working with RAD 7.5.3 and have the following problem: Our web project has no WEB-INF/lib folder. After Maven has successfully build a war file, it also creates a WEB-INF/lib folder with all the jars from the pom.xml. Now we exclude a jar using either scope provided or exclusi

[jira] Created: (WAGON-313) Upgrade httpclient to 4.x

Upgrade httpclient to 4.x - Key: WAGON-313 URL: http://jira.codehaus.org/browse/WAGON-313 Project: Maven Wagon Issue Type: Improvement Components: wagon-http, wagon-http-lightweight, wagon-webdav

[jira] Closed: (MNG-4805) Update default plugin versions used for built-in lifecycle mappings

[ http://jira.codehaus.org/browse/MNG-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4805. -- Resolution: Fixed Fix Version/s: 3.0-beta-4 Assignee: Benjamin Bentmann Done in [r99573

[jira] Updated: (MNG-4805) Update default plugin versions used for built-in lifecycle mappings

[ http://jira.codehaus.org/browse/MNG-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4805: --- Summary: Update default plugin versions used for built-in lifecycle mappings (was: Update default pl

[jira] Created: (MSITE-501) Properties overwritten by settings.xml are ignored when creating parent-links

Properties overwritten by settings.xml are ignored when creating parent-links - Key: MSITE-501 URL: http://jira.codehaus.org/browse/MSITE-501 Project: Maven 2.x Site Plugin

[jira] Commented: (MEAR-113) The default contextRoot should match the default bundleFileName

[ http://jira.codehaus.org/browse/MEAR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234876#action_234876 ] Jeroen Ruijgers commented on MEAR-113: -- This patch breakes today's behaviour when the buildname is

[jira] Commented: (MEAR-126) Add includeInApplicationXml property in ejbModule

[ http://jira.codehaus.org/browse/MEAR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234873#action_234873 ] Jeroen Ruijgers commented on MEAR-126: -- If you use an EJB as a client, you better use the ejb-clie

[jira] Commented: (SCM-574) GitCheckInCommand fails on empty changed files list

[ http://jira.codehaus.org/browse/SCM-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234865#action_234865 ] Mark Struberg commented on SCM-574: --- yes, this seems to be a good hack. > GitCheckInCommand fails on