[jira] (SCM-483) Update SCM Perforce Provider to use P4Java

[ https://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348771#comment-348771 ] Dan Tran edited comment on SCM-483 at 6/26/14 1:54 AM: --- maven scm provider for P

[jira] (SCM-483) Update SCM Perforce Provider to use P4Java

[ https://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-483. Resolution: Won't Fix Assignee: Dan Tran maven scm provider for Perforce using p4java is not at workshop.perforce.com

[jira] (MSHADE-174) Unable to shade Java 8 jarfiles with static interface methods using minimizeJar

[ https://jira.codehaus.org/browse/MSHADE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spencer Alderman updated MSHADE-174: Summary: Unable to shade Java 8 jarfiles with static interface methods using minimizeJar (was:

[jira] (MSHADE-174) Unable to shade Java 8 jarfiles with static interface methods

[ https://jira.codehaus.org/browse/MSHADE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spencer Alderman updated MSHADE-174: Description: Maven shade does not appear to work with shading in Java 8 jarfiles that include s

[jira] (MSHADE-174) Unable to shade Java 8 jarfiles with static interface methods

[ https://jira.codehaus.org/browse/MSHADE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spencer Alderman updated MSHADE-174: Description: Maven shade does not appear to work with shading in Java 8 jarfiles that include s

[jira] (MSHADE-174) Unable to shade Java 8 jarfiles with static interface methods

Spencer Alderman created MSHADE-174: --- Summary: Unable to shade Java 8 jarfiles with static interface methods Key: MSHADE-174 URL: https://jira.codehaus.org/browse/MSHADE-174 Project: Maven Shade Plu

[jira] (SCM-756) TCK should invoke EditCommand for provider like Perforce before any change

[ https://jira.codehaus.org/browse/SCM-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-756: - Summary: TCK should invoke EditCommand for provider like Perforce before any change (was: TCK should invoke EditCommand

[jira] (SCM-754) Require Tag/Branch Command to return the entire source tree is impractical

[ https://jira.codehaus.org/browse/SCM-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-754: - Component/s: (was: maven-scm-api) maven-scm-tck > Require Tag/Branch Command to return the entire so

[jira] (SCM-756) TCK should invoke EditCommand for required edit mode provider like Perforce

[ https://jira.codehaus.org/browse/SCM-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-756: - Component/s: (was: maven-scm-api) maven-scm-tck > TCK should invoke EditCommand for required edit mo

[jira] (SCM-755) Inject SecDispatcher into TCK base test case

[ https://jira.codehaus.org/browse/SCM-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-755: - Component/s: (was: maven-scm-api) maven-scm-tck > Inject SecDispatcher into TCK base test case > ---

[jira] (SCM-761) Allow downstream TCK to define its own tag

[ https://jira.codehaus.org/browse/SCM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-761: - Component/s: (was: maven-scm-api) maven-scm-tck > Allow downstream TCK to define its own tag > -

[jira] (MNG-3397) [RFC] change the POM to use attributes

[ https://jira.codehaus.org/browse/MNG-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348768#comment-348768 ] Sergei Ivanov commented on MNG-3397: I support the idea of a compact colon-separated dependency i

[jira] (MWAR-311) Filtering of resources broken in version 2.4

[ https://jira.codehaus.org/browse/MWAR-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348763#comment-348763 ] Evan Brodie commented on MWAR-311: -- I'm not sure, I just wanted to confirm. Thank you. > Filtering

[jira] (MNG-5654) Move pluginManagement out of build area

[ https://jira.codehaus.org/browse/MNG-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348762#comment-348762 ] Robert Scholte commented on MNG-5654: - IMO {{plugins}} relates to {{pluginManagement}} the same a

[jira] (MWAR-311) Filtering of resources broken in version 2.4

[ https://jira.codehaus.org/browse/MWAR-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348761#comment-348761 ] Karl-Heinz Marbaise commented on MWAR-311: -- It will be available with version 2.5. How shoul

[jira] (SCM-761) Allow downstream TCK to define its own tag

[ https://jira.codehaus.org/browse/SCM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SCM-761: - fixed at http://git-wip-us.apache.org/repos/asf/maven-scm/commit/692b76a9 > Allow downstream TCK to define its own tag > --

[jira] (SCM-761) Allow downstream TCK to define its own tag

[ https://jira.codehaus.org/browse/SCM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-761. Resolution: Fixed Fix Version/s: 1.10 Assignee: Dan Tran fixed at http://git-wip-us.apache.org/repos/asf/ma

[jira] (SCM-761) Allow downstream TCK to define its own tag

Dan Tran created SCM-761: Summary: Allow downstream TCK to define its own tag Key: SCM-761 URL: https://jira.codehaus.org/browse/SCM-761 Project: Maven SCM Issue Type: Task Components: mave

[jira] (MNG-5653) [RFC] POM using attributes for plugin definitions

[ https://jira.codehaus.org/browse/MNG-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MNG-5653: - Fix Version/s: Issues to be reviewed for 4.x > [RFC] POM using attributes for plugin definitions

[jira] (MNG-5654) Move pluginManagement out of build area

Karl-Heinz Marbaise created MNG-5654: Summary: Move pluginManagement out of build area Key: MNG-5654 URL: https://jira.codehaus.org/browse/MNG-5654 Project: Maven Issue Type: Improvement

[jira] (MNG-5653) [RFC] POM using attributes for plugin definitions

Karl-Heinz Marbaise created MNG-5653: Summary: [RFC] POM using attributes for plugin definitions Key: MNG-5653 URL: https://jira.codehaus.org/browse/MNG-5653 Project: Maven Issue Type: Im

[jira] (MNG-3397) [RFC] change the POM to use attributes

[ https://jira.codehaus.org/browse/MNG-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348748#comment-348748 ] Karl-Heinz Marbaise commented on MNG-3397: -- So an exclusions could look like this: {code:xml

[jira] (MWAR-311) Filtering of resources broken in version 2.4

[ https://jira.codehaus.org/browse/MWAR-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348747#comment-348747 ] Evan Brodie commented on MWAR-311: -- So does this mean that it won't be available in the Maven reposi

[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root

[ https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348740#comment-348740 ] Martin Ellis commented on MRELEASE-875: --- In case it helps anyone, I am currently working ar

[jira] (MEAR-183) Extra 'temp' directory created in wrong place

[ https://jira.codehaus.org/browse/MEAR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348737#comment-348737 ] Stéphane Nicoll commented on MEAR-183: -- @Karl, the regular build directory I guess. > Extra 'te

[jira] (MCOMPILER-194) Strange effects with springs @Configurable (AspectJ) and new compiler plugin version 3.0

[ https://jira.codehaus.org/browse/MCOMPILER-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348733#comment-348733 ] Alexander Kriegisch edited comment on MCOMPILER-194 at 6/25/14 4:53 AM: --

[jira] (MCOMPILER-194) Strange effects with springs @Configurable (AspectJ) and new compiler plugin version 3.0

[ https://jira.codehaus.org/browse/MCOMPILER-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kriegisch updated MCOMPILER-194: -- Attachment: SO_AJ_MavenSoftExceptions.zip Sample AspectJ + Maven project showing

[jira] (MCOMPILER-209) Incremental compilation doesn't work unless useIncrementalCompilation is set to 'false'

[ https://jira.codehaus.org/browse/MCOMPILER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kriegisch updated MCOMPILER-209: -- Attachment: SO_AJ_MavenSoftExceptions.zip Sample AspectJ + Mavcen project showing

[jira] (MCOMPILER-209) Incremental compilation doesn't work unless useIncrementalCompilation is set to 'false'

[ https://jira.codehaus.org/browse/MCOMPILER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348732#comment-348732 ] Alexander Kriegisch edited comment on MCOMPILER-209 at 6/25/14 4:49 AM: --

[jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement

[ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-760. Resolution: Fixed fixed at http://git-wip-us.apache.org/repos/asf/maven-scm/commit/2b647833 > remove maven-scm-plugin's R

[jira] (SCM-757) bootstrap/checkout/export goals now requires -Dproject.basedir=. set at command line

[ https://jira.codehaus.org/browse/SCM-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-757. Resolution: Fixed fixed at https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=commit;h=82b8f4bd > bootstrap/checko