[jira] (MCHANGES-308) Support filters when using REST API / JQL

[ https://jira.codehaus.org/browse/MCHANGES-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333246#comment-333246 ] Markku Saarela commented on MCHANGES-308: - I think this must be bug not wish, because now

[jira] (MCHANGES-319) JIRA report should support taking JQL as configuration

[ https://jira.codehaus.org/browse/MCHANGES-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333245#comment-333245 ] Markku Saarela commented on MCHANGES-319: - Is this duplicate of MCHANGES-308

[jira] (MCHANGES-290) Provide GitHub support for generate announcement report

Markku Saarela created MCHANGES-290: --- Summary: Provide GitHub support for generate announcement report Key: MCHANGES-290 URL: https://jira.codehaus.org/browse/MCHANGES-290 Project: Maven 2.x Changes

[jira] Commented: (MRELEASE-128) SCM properties being replaced during release:perform

[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239921#action_239921 ] Markku Saarela commented on MRELEASE-128: - Also Maven 2.2.1 with 2.1 version doesn't work c

[jira] Commented: (MRELEASE-128) SCM properties being replaced during release:perform

[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239920#action_239920 ] Markku Saarela commented on MRELEASE-128: - I confirms previous comment. With Maven 3.0 and

[jira] Updated: (MJAR-61) Manifest classpath ignores the "real" JAR filenames specified in

[ http://jira.codehaus.org/browse/MJAR-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markku Saarela updated MJAR-61: --- Attachment: MJAR-61.zip Install common-jar first and then multi-module project.I also created MSHARED-147 iss

[jira] Created: (MSHARED-147) Maven Archiver does not obey project.build.finalName in Class-Path entry

Maven Archiver does not obey project.build.finalName in Class-Path entry Key: MSHARED-147 URL: http://jira.codehaus.org/browse/MSHARED-147 Project: Maven Shared Components

[jira] Commented: (MECLIPSE-363) eclipse:to-maven crashes if any plugin JAR lacks a Bundle-SymbolicName field in its manifest

[ http://jira.codehaus.org/browse/MECLIPSE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216684#action_216684 ] Markku Saarela commented on MECLIPSE-363: - TestNG plugin version 5.9.0.2 has minimal manife

[jira] Reopened: (MPH-74) effective-pom goal pluginManagement plugin configuration inheritance to child pom profile plugin failed.

[ http://jira.codehaus.org/browse/MPH-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markku Saarela reopened MPH-74: --- I have explained what confused me with this plugin configuration inheritance. What has changed when Maven 3.0-alph

[jira] Commented: (MPH-74) effective-pom goal pluginManagement plugin configuration inheritance to child pom profile plugin failed.

[ http://jira.codehaus.org/browse/MPH-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215928#action_215928 ] Markku Saarela commented on MPH-74: --- This produces different output in profiles element depending is pl

[jira] Updated: (MPH-74) effective-pom goal pluginManagement plugin configuration inheritance to child pom profile plugin failed.

[ http://jira.codehaus.org/browse/MPH-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markku Saarela updated MPH-74: -- Attachment: MNG-2174-2.zip new project with 2 modules to produce different output. > effective-pom goal pluginMa

[jira] Created: (MPH-74) effective-pom goal pluginManagement plugin configuration inheritance to child pom profile plugin failed.

effective-pom goal pluginManagement plugin configuration inheritance to child pom profile plugin failed. Key: MPH-74 URL: http://jira.codehaus.org/browse/MPH-

[jira] Commented: (MEAR-118) Invalid application.xml generated

[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204265#action_204265 ] Markku Saarela commented on MEAR-118: - This bug blocks my usage of this version of plugin, because

[jira] Commented: (MSOURCES-44) If project doesn't contain sources (contains only test sources) source:jar will fail

[ http://jira.codehaus.org/browse/MSOURCES-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176377#action_176377 ] Markku Saarela commented on MSOURCES-44: Source plugin must obey maven archiver which defa

[jira] Commented: (MRELEASE-280) AIOBE on release:perform

[ http://jira.codehaus.org/browse/MRELEASE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108431 ] Markku Saarela commented on MRELEASE-280: - I get same exception. I have project that has dependency to an other pro

[jira] Commented: (MNG-2708) Required parameters of self written Mojo configured in execution part of POM are ignored and causing error

[ http://jira.codehaus.org/browse/MNG-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95646 ] Markku Saarela commented on MNG-2708: - This is very bad bug because I must make my own versions of plugins witch I need to

[jira] Commented: (MRELEASE-129) Release fails on EAR project with EJB module reference

[ http://jira.codehaus.org/browse/MRELEASE-129?page=comments#action_73465 ] Markku Saarela commented on MRELEASE-129: - Same effect is for ejb-client type dependencies. > Release fails on EAR project with EJB module reference > ---