[jira] [Created] (MWAR-365) Upgrade plexus-archiver from 3.0.1 to 3.0.3
Karl Heinz Marbaise created MWAR-365: Summary: Upgrade plexus-archiver from 3.0.1 to 3.0.3 Key: MWAR-365 URL: https://issues.apache.org/jira/browse/MWAR-365 Project: Maven WAR Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Priority: Critical Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MWAR-365) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MWAR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MWAR-365. Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1727825|http://svn.apache.org/r1727825] > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MWAR-365 > URL: https://issues.apache.org/jira/browse/MWAR-365 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MJAR-205) Compatibility with JDK9 requires an update of plexus-archiver
[ https://issues.apache.org/jira/browse/MJAR-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJAR-205. Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1727826|http://svn.apache.org/r1727826] > Compatibility with JDK9 requires an update of plexus-archiver > - > > Key: MJAR-205 > URL: https://issues.apache.org/jira/browse/MJAR-205 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Sanne Grinovero >Assignee: Karl Heinz Marbaise > Labels: java9 > Fix For: 3.0.0 > > > The Maven Jar plugin will fail when running on Java 9 since preview build 95 > (since inclusion of project Verona) because of a small issue in the used > version of plexus-archiver. > See also: > - https://github.com/codehaus-plexus/plexus-archiver/issues/13 > The trivial fix was merged: > - https://github.com/codehaus-plexus/plexus-archiver/pull/12 > This is to track the need for an update to a `plexus-archiver` version > including the above patches. Would love to see a Maven release including > this too, so that we can use our project's existing testsuites to test for > Java9 compatibility ASAP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MASSEMBLY-797) Upgrade plexus-archiver from 3.0.1 to 3.0.3
Karl Heinz Marbaise created MASSEMBLY-797: - Summary: Upgrade plexus-archiver from 3.0.1 to 3.0.3 Key: MASSEMBLY-797 URL: https://issues.apache.org/jira/browse/MASSEMBLY-797 Project: Maven Assembly Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Priority: Critical Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MASSEMBLY-797) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MASSEMBLY-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MASSEMBLY-797. - Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1727828|http://svn.apache.org/r1727828] > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MASSEMBLY-797 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-797 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MACR-28) Upgrade plexus-archiver from 3.0.1 to 3.0.3
Karl Heinz Marbaise created MACR-28: --- Summary: Upgrade plexus-archiver from 3.0.1 to 3.0.3 Key: MACR-28 URL: https://issues.apache.org/jira/browse/MACR-28 Project: Maven ACR Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Critical Fix For: 3.0.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MACR-28) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MACR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MACR-28. --- Resolution: Fixed Fixed in [r1727829|http://svn.apache.org/r1727829] > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MACR-28 > URL: https://issues.apache.org/jira/browse/MACR-28 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MEAR-225) Upgrade plexus-archiver from 3.0.1 to 3.0.3
Karl Heinz Marbaise created MEAR-225: Summary: Upgrade plexus-archiver from 3.0.1 to 3.0.3 Key: MEAR-225 URL: https://issues.apache.org/jira/browse/MEAR-225 Project: Maven Ear Plugin Issue Type: Improvement Affects Versions: 2.10.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Critical Fix For: 2.10.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MEAR-225) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MEAR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MEAR-225. Resolution: Fixed Fixed in [r1727830|http://svn.apache.org/r1727830] > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MEAR-225 > URL: https://issues.apache.org/jira/browse/MEAR-225 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 2.10.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 2.10.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MDEP-517) Upgrade plexus-archiver from 2.9 to 3.0.3
Karl Heinz Marbaise created MDEP-517: Summary: Upgrade plexus-archiver from 2.9 to 3.0.3 Key: MDEP-517 URL: https://issues.apache.org/jira/browse/MDEP-517 Project: Maven Dependency Plugin Issue Type: Improvement Affects Versions: 3.0 Reporter: Karl Heinz Marbaise Priority: Critical Fix For: 3.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MDEP-517) Upgrade plexus-archiver from 2.9 to 3.0.3
[ https://issues.apache.org/jira/browse/MDEP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEP-517. Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1727833|http://svn.apache.org/r1727833] > Upgrade plexus-archiver from 2.9 to 3.0.3 > - > > Key: MDEP-517 > URL: https://issues.apache.org/jira/browse/MDEP-517 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MJAR-205) Compatibility with JDK9 requires an update of plexus-archiver
[ https://issues.apache.org/jira/browse/MJAR-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125367#comment-15125367 ] Hudson commented on MJAR-205: - FAILURE: Integrated in maven-plugins #5046 (See [https://builds.apache.org/job/maven-plugins/5046/]) [MJAR-205] Compatibility with JDK9 requires an update of plexus-archiver (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1727826]) * maven-jar-plugin/pom.xml > Compatibility with JDK9 requires an update of plexus-archiver > - > > Key: MJAR-205 > URL: https://issues.apache.org/jira/browse/MJAR-205 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Sanne Grinovero >Assignee: Karl Heinz Marbaise > Labels: java9 > Fix For: 3.0.0 > > > The Maven Jar plugin will fail when running on Java 9 since preview build 95 > (since inclusion of project Verona) because of a small issue in the used > version of plexus-archiver. > See also: > - https://github.com/codehaus-plexus/plexus-archiver/issues/13 > The trivial fix was merged: > - https://github.com/codehaus-plexus/plexus-archiver/pull/12 > This is to track the need for an update to a `plexus-archiver` version > including the above patches. Would love to see a Maven release including > this too, so that we can use our project's existing testsuites to test for > Java9 compatibility ASAP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MWAR-365) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MWAR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125368#comment-15125368 ] Hudson commented on MWAR-365: - FAILURE: Integrated in maven-plugins #5046 (See [https://builds.apache.org/job/maven-plugins/5046/]) [MWAR-365] Upgrade plexus-archiver from 3.0.1 to 3.0.3 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1727825]) * maven-war-plugin/pom.xml > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MWAR-365 > URL: https://issues.apache.org/jira/browse/MWAR-365 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MASSEMBLY-797) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MASSEMBLY-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125369#comment-15125369 ] Hudson commented on MASSEMBLY-797: -- FAILURE: Integrated in maven-plugins #5046 (See [https://builds.apache.org/job/maven-plugins/5046/]) [MASSEMBLY-797] Upgrade plexus-archiver from 3.0.1 to 3.0.3 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1727828]) * maven-assembly-plugin/pom.xml > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MASSEMBLY-797 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-797 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MEJB-95) Upgrade plexus-archiver from 3.0.1 to 3.0.3
Karl Heinz Marbaise created MEJB-95: --- Summary: Upgrade plexus-archiver from 3.0.1 to 3.0.3 Key: MEJB-95 URL: https://issues.apache.org/jira/browse/MEJB-95 Project: Maven EJB Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Priority: Critical Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MEJB-95) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MEJB-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MEJB-95. --- Resolution: Fixed Assignee: Karl Heinz Marbaise Fixed in [r1727834|http://svn.apache.org/r1727834] > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MEJB-95 > URL: https://issues.apache.org/jira/browse/MEJB-95 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MRAR-50) Upgrade plexus-archiver from 3.0.1 to 3.0.3
Karl Heinz Marbaise created MRAR-50: --- Summary: Upgrade plexus-archiver from 3.0.1 to 3.0.3 Key: MRAR-50 URL: https://issues.apache.org/jira/browse/MRAR-50 Project: Maven Rar Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Critical Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRAR-50) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MRAR-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MRAR-50. --- Resolution: Fixed Fixed in [r1727835|http://svn.apache.org/r1727835] > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MRAR-50 > URL: https://issues.apache.org/jira/browse/MRAR-50 > Project: Maven Rar Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSOURCES-93) Upgrade plexus-archiver from 3.0.1 to 3.0.3
Karl Heinz Marbaise created MSOURCES-93: --- Summary: Upgrade plexus-archiver from 3.0.1 to 3.0.3 Key: MSOURCES-93 URL: https://issues.apache.org/jira/browse/MSOURCES-93 Project: Maven Source Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Critical Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MSOURCES-93) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MSOURCES-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSOURCES-93. --- Resolution: Fixed Fixed in [r1727836|http://svn.apache.org/r1727836] > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MSOURCES-93 > URL: https://issues.apache.org/jira/browse/MSOURCES-93 > Project: Maven Source Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MEAR-225) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MEAR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125377#comment-15125377 ] Hudson commented on MEAR-225: - FAILURE: Integrated in maven-plugins #5047 (See [https://builds.apache.org/job/maven-plugins/5047/]) [MEAR-225] Upgrade plexus-archiver from 3.0.1 to 3.0.3 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1727830]) * maven-ear-plugin/pom.xml > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MEAR-225 > URL: https://issues.apache.org/jira/browse/MEAR-225 > Project: Maven Ear Plugin > Issue Type: Improvement >Affects Versions: 2.10.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 2.10.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MACR-28) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MACR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125375#comment-15125375 ] Hudson commented on MACR-28: FAILURE: Integrated in maven-plugins #5047 (See [https://builds.apache.org/job/maven-plugins/5047/]) [MACR-28] Upgrade plexus-archiver from 3.0.1 to 3.0.3 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1727829]) * maven-acr-plugin/pom.xml > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MACR-28 > URL: https://issues.apache.org/jira/browse/MACR-28 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MDEP-517) Upgrade plexus-archiver from 2.9 to 3.0.3
[ https://issues.apache.org/jira/browse/MDEP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125376#comment-15125376 ] Hudson commented on MDEP-517: - FAILURE: Integrated in maven-plugins #5047 (See [https://builds.apache.org/job/maven-plugins/5047/]) [MDEP-517] Upgrade plexus-archiver from 2.9 to 3.0.3 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1727833]) * maven-dependency-plugin/pom.xml > Upgrade plexus-archiver from 2.9 to 3.0.3 > - > > Key: MDEP-517 > URL: https://issues.apache.org/jira/browse/MDEP-517 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MEJB-95) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MEJB-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125378#comment-15125378 ] Hudson commented on MEJB-95: FAILURE: Integrated in maven-plugins #5048 (See [https://builds.apache.org/job/maven-plugins/5048/]) [MEJB-95] Upgrade plexus-archiver from 3.0.1 to 3.0.3 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1727834]) * maven-ejb-plugin/pom.xml > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MEJB-95 > URL: https://issues.apache.org/jira/browse/MEJB-95 > Project: Maven EJB Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRAR-50) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MRAR-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125379#comment-15125379 ] Hudson commented on MRAR-50: FAILURE: Integrated in maven-plugins #5048 (See [https://builds.apache.org/job/maven-plugins/5048/]) [MRAR-50] Upgrade plexus-archiver from 3.0.1 to 3.0.3 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1727835]) * maven-rar-plugin/pom.xml > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MRAR-50 > URL: https://issues.apache.org/jira/browse/MRAR-50 > Project: Maven Rar Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSOURCES-93) Upgrade plexus-archiver from 3.0.1 to 3.0.3
[ https://issues.apache.org/jira/browse/MSOURCES-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125380#comment-15125380 ] Hudson commented on MSOURCES-93: FAILURE: Integrated in maven-plugins #5048 (See [https://builds.apache.org/job/maven-plugins/5048/]) [MSOURCES-93] Upgrade plexus-archiver from 3.0.1 to 3.0.3 (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1727836]) * maven-source-plugin/pom.xml > Upgrade plexus-archiver from 3.0.1 to 3.0.3 > --- > > Key: MSOURCES-93 > URL: https://issues.apache.org/jira/browse/MSOURCES-93 > Project: Maven Source Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHARED-494) Impossible to generate a reproducible build due to timestamp in pom.properties
Emanuele Tagliaferri created MSHARED-494:
Summary: Impossible to generate a reproducible build due to
timestamp in pom.properties
Key: MSHARED-494
URL: https://issues.apache.org/jira/browse/MSHARED-494
Project: Maven Shared Components
Issue Type: Bug
Components: maven-archiver
Affects Versions: maven-archiver-3.0.0
Reporter: Emanuele Tagliaferri
Priority: Minor
Try to making a pom for do a reproducible build, meaning by reproducible build
the ability to produce the exact same artifact (same checksum) starting from
the same code, a two different times, i had some trouble with the files
generated in: /META-INF/maven/${groupId}/${artifactId}/ in the specific the
/META-INF/maven/${groupId}/${artifactId}/pom.properties contains the timestamp.
digging in the code in the class:
http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
line 86
is used the java.util.Properties#store which write the timestamp in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSHARED-494) Impossible to generate a reproducible build due to timestamp in pom.properties
[
https://issues.apache.org/jira/browse/MSHARED-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emanuele Tagliaferri updated MSHARED-494:
-
Description:
Try to making a pom for do a reproducible build, meaning by reproducible build
the ability to produce the exact same artifact (same checksum) starting from
the same code, a two different times, i had some trouble with the files
generated in: /META-INF/maven/\${groupId}/\${artifactId}/ in the specific the
/META-INF/maven/\${groupId}/\${artifactId}/pom.properties contains the
timestamp.
digging in the code in the class:
http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
line 86
is used the java.util.Properties#store which write the timestamp in any case.
was:
Try to making a pom for do a reproducible build, meaning by reproducible build
the ability to produce the exact same artifact (same checksum) starting from
the same code, a two different times, i had some trouble with the files
generated in: /META-INF/maven/${groupId}/${artifactId}/ in the specific the
/META-INF/maven/${groupId}/${artifactId}/pom.properties contains the timestamp.
digging in the code in the class:
http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
line 86
is used the java.util.Properties#store which write the timestamp in any case.
> Impossible to generate a reproducible build due to timestamp in pom.properties
> --
>
> Key: MSHARED-494
> URL: https://issues.apache.org/jira/browse/MSHARED-494
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.0.0
>Reporter: Emanuele Tagliaferri
>Priority: Minor
>
> Try to making a pom for do a reproducible build, meaning by reproducible
> build the ability to produce the exact same artifact (same checksum) starting
> from the same code, a two different times, i had some trouble with the files
> generated in: /META-INF/maven/\${groupId}/\${artifactId}/ in the specific the
> /META-INF/maven/\${groupId}/\${artifactId}/pom.properties contains the
> timestamp.
> digging in the code in the class:
> http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
> line 86
> is used the java.util.Properties#store which write the timestamp in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSHARED-494) Impossible to generate a reproducible build due to timestamp in pom.properties
[
https://issues.apache.org/jira/browse/MSHARED-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emanuele Tagliaferri updated MSHARED-494:
-
Description:
Try to making a pom for do a reproducible build, meaning by reproducible build
the ability to produce the exact same artifact (same checksum) starting from
the same code, a two different times, i had some trouble with the files
generated in: /META-INF/maven/${groupId}/${artifactId}/
in the specific the /META-INF/maven/${groupId} / ${artifactId} /pom.properties
contains the timestamp.
digging in the code in the class:
http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
line 86
is used the java.util.Properties#store which write the timestamp in any case.
was:
Try to making a pom for do a reproducible build, meaning by reproducible build
the ability to produce the exact same artifact (same checksum) starting from
the same code, a two different times, i had some trouble with the files
generated in: /META-INF/maven/${groupId}/${artifactId}/
in the specific the /META-INF/maven/${groupId}/${artifactId}/pom.properties
contains the timestamp.
digging in the code in the class:
http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
line 86
is used the java.util.Properties#store which write the timestamp in any case.
> Impossible to generate a reproducible build due to timestamp in pom.properties
> --
>
> Key: MSHARED-494
> URL: https://issues.apache.org/jira/browse/MSHARED-494
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.0.0
>Reporter: Emanuele Tagliaferri
>Priority: Minor
>
> Try to making a pom for do a reproducible build, meaning by reproducible
> build the ability to produce the exact same artifact (same checksum) starting
> from the same code, a two different times, i had some trouble with the files
> generated in: /META-INF/maven/${groupId}/${artifactId}/
> in the specific the /META-INF/maven/${groupId} / ${artifactId}
> /pom.properties contains the timestamp.
> digging in the code in the class:
> http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
> line 86
> is used the java.util.Properties#store which write the timestamp in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSHARED-494) Impossible to generate a reproducible build due to timestamp in pom.properties
[
https://issues.apache.org/jira/browse/MSHARED-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emanuele Tagliaferri updated MSHARED-494:
-
Description:
Try to making a pom for do a reproducible build, meaning by reproducible build
the ability to produce the exact same artifact (same checksum) starting from
the same code, a two different times, i had some trouble with the files
generated in: /META-INF/maven/${groupId}/${artifactId}/
in the specific the /META-INF/maven/${groupId}/${artifactId}/pom.properties
contains the timestamp.
digging in the code in the class:
http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
line 86
is used the java.util.Properties#store which write the timestamp in any case.
was:
Try to making a pom for do a reproducible build, meaning by reproducible build
the ability to produce the exact same artifact (same checksum) starting from
the same code, a two different times, i had some trouble with the files
generated in: /META-INF/maven/\${groupId}/\${artifactId}/ in the specific the
/META-INF/maven/\${groupId}/\${artifactId}/pom.properties contains the
timestamp.
digging in the code in the class:
http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
line 86
is used the java.util.Properties#store which write the timestamp in any case.
> Impossible to generate a reproducible build due to timestamp in pom.properties
> --
>
> Key: MSHARED-494
> URL: https://issues.apache.org/jira/browse/MSHARED-494
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.0.0
>Reporter: Emanuele Tagliaferri
>Priority: Minor
>
> Try to making a pom for do a reproducible build, meaning by reproducible
> build the ability to produce the exact same artifact (same checksum) starting
> from the same code, a two different times, i had some trouble with the files
> generated in: /META-INF/maven/${groupId}/${artifactId}/
> in the specific the /META-INF/maven/${groupId}/${artifactId}/pom.properties
> contains the timestamp.
> digging in the code in the class:
> http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
> line 86
> is used the java.util.Properties#store which write the timestamp in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSHARED-494) Impossible to generate a reproducible build due to timestamp in pom.properties
[
https://issues.apache.org/jira/browse/MSHARED-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emanuele Tagliaferri updated MSHARED-494:
-
Description:
Try to making a pom for do a reproducible build, meaning by reproducible build
the ability to produce the exact same artifact (same checksum) starting from
the same code, a two different times, i had some trouble with the files
generated in: /META-INF/maven/groupId/artifactId/
in the specific the /META-INF/maven/groupId/artifactId/pom.properties contains
the timestamp.
digging in the code in the class:
http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
line 86
is used the java.util.Properties#store which write the timestamp in any case.
was:
Try to making a pom for do a reproducible build, meaning by reproducible build
the ability to produce the exact same artifact (same checksum) starting from
the same code, a two different times, i had some trouble with the files
generated in: /META-INF/maven/${groupId}/${artifactId}/
in the specific the /META-INF/maven/${groupId} / ${artifactId} /pom.properties
contains the timestamp.
digging in the code in the class:
http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
line 86
is used the java.util.Properties#store which write the timestamp in any case.
> Impossible to generate a reproducible build due to timestamp in pom.properties
> --
>
> Key: MSHARED-494
> URL: https://issues.apache.org/jira/browse/MSHARED-494
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.0.0
>Reporter: Emanuele Tagliaferri
>Priority: Minor
>
> Try to making a pom for do a reproducible build, meaning by reproducible
> build the ability to produce the exact same artifact (same checksum) starting
> from the same code, a two different times, i had some trouble with the files
> generated in: /META-INF/maven/groupId/artifactId/
> in the specific the /META-INF/maven/groupId/artifactId/pom.properties
> contains the timestamp.
> digging in the code in the class:
> http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
> line 86
> is used the java.util.Properties#store which write the timestamp in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5227) The 'optional' flag of a dependency should be manageable.
[
https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125411#comment-15125411
]
Christian Schulte commented on MNG-5227:
Let me know if I there is anything I can do to help. Does it mean you are
planning to change the Aether package names? We had 'org.sonatype.aether' and
'org.eclipse.aether' maybe it's time someone registers a 'aether.codes',
'aether.software' or whatever domain name and we use that for the package name
once and for all? Maybe even rename the whole thing?
> The 'optional' flag of a dependency should be manageable.
> -
>
> Key: MNG-5227
> URL: https://issues.apache.org/jira/browse/MNG-5227
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.3
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.4.0
>
>
> {code}
>
>
>
> groupId
> artifactId
> version
> false
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5227) The 'optional' flag of a dependency should be manageable.
[
https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125437#comment-15125437
]
Jason van Zyl commented on MNG-5227:
No, I definitely do not want to rename the packages. It caused so much
disruption that I really don't think it's worth it. Once it's entirely
internalized it won't really matter so I don't see much point in causing a lot
of grief. I'm working with the Eclipse Foundation on the termination of Aether
and I don't think anyone is going to mind if we leave the package names as they
are. I really don't see it as value-adding work to flip a bunch of package
names and make adapters for everything. Should have a release out in a day or
two.
> The 'optional' flag of a dependency should be manageable.
> -
>
> Key: MNG-5227
> URL: https://issues.apache.org/jira/browse/MNG-5227
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.3
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.4.0
>
>
> {code}
>
>
>
> groupId
> artifactId
> version
> false
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSHARED-494) Impossible to generate a reproducible build due to timestamp in pom.properties
[
https://issues.apache.org/jira/browse/MSHARED-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125496#comment-15125496
]
Michael Osipov commented on MSHARED-494:
This method does not write the timestamp. Oracle's implementation of
{{store()}} does write the stupid {{new Date().toString()}}.
> Impossible to generate a reproducible build due to timestamp in pom.properties
> --
>
> Key: MSHARED-494
> URL: https://issues.apache.org/jira/browse/MSHARED-494
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.0.0
>Reporter: Emanuele Tagliaferri
>Priority: Minor
>
> Try to making a pom for do a reproducible build, meaning by reproducible
> build the ability to produce the exact same artifact (same checksum) starting
> from the same code, a two different times, i had some trouble with the files
> generated in: /META-INF/maven/groupId/artifactId/
> in the specific the /META-INF/maven/groupId/artifactId/pom.properties
> contains the timestamp.
> digging in the code in the class:
> http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
> line 86
> is used the java.util.Properties#store which write the timestamp in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MSHARED-494) Impossible to generate a reproducible build due to timestamp in pom.properties
[
https://issues.apache.org/jira/browse/MSHARED-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125496#comment-15125496
]
Michael Osipov edited comment on MSHARED-494 at 1/31/16 8:49 PM:
-
This method does not write the timestamp. Oracle's implementation of
[{{store()}}|http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u40-b25/java/util/Properties.java#Properties.store0%28java.io.BufferedWriter%2Cjava.lang.String%2Cboolean%29]
does write the stupid {{new Date().toString()}}.
was (Author: michael-o):
This method does not write the timestamp. Oracle's implementation of
{{store()}} does write the stupid {{new Date().toString()}}.
> Impossible to generate a reproducible build due to timestamp in pom.properties
> --
>
> Key: MSHARED-494
> URL: https://issues.apache.org/jira/browse/MSHARED-494
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.0.0
>Reporter: Emanuele Tagliaferri
>Priority: Minor
>
> Try to making a pom for do a reproducible build, meaning by reproducible
> build the ability to produce the exact same artifact (same checksum) starting
> from the same code, a two different times, i had some trouble with the files
> generated in: /META-INF/maven/groupId/artifactId/
> in the specific the /META-INF/maven/groupId/artifactId/pom.properties
> contains the timestamp.
> digging in the code in the class:
> http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
> line 86
> is used the java.util.Properties#store which write the timestamp in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MSHARED-494) Impossible to generate a reproducible build due to timestamp in pom.properties
[
https://issues.apache.org/jira/browse/MSHARED-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125496#comment-15125496
]
Michael Osipov edited comment on MSHARED-494 at 1/31/16 8:53 PM:
-
This method does not write the timestamp. Oracle's implementation of
[{{store()}}|http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u40-b25/java/util/Properties.java#Properties.store0%28java.io.BufferedWriter%2Cjava.lang.String%2Cboolean%29]
does write the stupid {{new Date().toString()}}. If you provide a proper
implementation of an
[{{FilterOutputStream}}|https://docs.oracle.com/javase/7/docs/api/java/io/FilterOutputStream.html]
wich drops this line, I will add it to the code.
was (Author: michael-o):
This method does not write the timestamp. Oracle's implementation of
[{{store()}}|http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u40-b25/java/util/Properties.java#Properties.store0%28java.io.BufferedWriter%2Cjava.lang.String%2Cboolean%29]
does write the stupid {{new Date().toString()}}.
> Impossible to generate a reproducible build due to timestamp in pom.properties
> --
>
> Key: MSHARED-494
> URL: https://issues.apache.org/jira/browse/MSHARED-494
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.0.0
>Reporter: Emanuele Tagliaferri
>Priority: Minor
>
> Try to making a pom for do a reproducible build, meaning by reproducible
> build the ability to produce the exact same artifact (same checksum) starting
> from the same code, a two different times, i had some trouble with the files
> generated in: /META-INF/maven/groupId/artifactId/
> in the specific the /META-INF/maven/groupId/artifactId/pom.properties
> contains the timestamp.
> digging in the code in the class:
> http://svn.apache.org/viewvc/maven/shared/tags/maven-archiver-3.0.0/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java?revision=1708674&view=markup
> line 86
> is used the java.util.Properties#store which write the timestamp in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MSHARED-448) testRecreation failure with OpenJDK 8 on Linux
[
https://issues.apache.org/jira/browse/MSHARED-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MSHARED-448:
--
Assignee: Michael Osipov
> testRecreation failure with OpenJDK 8 on Linux
> --
>
> Key: MSHARED-448
> URL: https://issues.apache.org/jira/browse/MSHARED-448
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: maven-archiver-3.0.0
> Environment: OpenJDK 1.8.0_60 (Linux, amd64)
> Maven 3.3.3
>Reporter: Mikolaj Izdebski
>Assignee: Michael Osipov
>
> testRecreation test of maven-archiver 3.0.0 fails with OpenJDK on Linux
> {code}
> testRecreation(org.apache.maven.archiver.MavenArchiverTest) Time elapsed:
> 0.026 sec <<< FAILURE!
> junit.framework.AssertionFailedError: expected:<144525731> but
> was:<144525725>
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.failNotEquals(Assert.java:287)
> at junit.framework.Assert.assertEquals(Assert.java:67)
> at junit.framework.Assert.assertEquals(Assert.java:134)
> at junit.framework.Assert.assertEquals(Assert.java:140)
> at
> org.apache.maven.archiver.MavenArchiverTest.testRecreation(MavenArchiverTest.java:248)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSHARED-362) Support removing default manifest entries with maven-archiver plugin
[ https://issues.apache.org/jira/browse/MSHARED-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125512#comment-15125512 ] Michael Osipov commented on MSHARED-362: Here is a similar request to the matter. > Support removing default manifest entries with maven-archiver plugin > > > Key: MSHARED-362 > URL: https://issues.apache.org/jira/browse/MSHARED-362 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Affects Versions: maven-archiver-2.4.2, maven-archiver-2.5 >Reporter: Richard Neish >Priority: Minor > > As described in the StackOverflow question at > http://stackoverflow.com/q/25098307/274350 maven-archiver should allow the > user to remove the default manifest entries, such as "Built-By:" > Currently it is possible to set an empty value for these default entries, but > not to remove them from the manifest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MSHARED-362) Support removing default manifest entries with maven-archiver plugin
[ https://issues.apache.org/jira/browse/MSHARED-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-362: --- Comment: was deleted (was: Here is a similar request to the matter.) > Support removing default manifest entries with maven-archiver plugin > > > Key: MSHARED-362 > URL: https://issues.apache.org/jira/browse/MSHARED-362 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-archiver >Affects Versions: maven-archiver-2.4.2, maven-archiver-2.5 >Reporter: Richard Neish >Priority: Minor > > As described in the StackOverflow question at > http://stackoverflow.com/q/25098307/274350 maven-archiver should allow the > user to remove the default manifest entries, such as "Built-By:" > Currently it is possible to set an empty value for these default entries, but > not to remove them from the manifest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1224) Improve Code Quality After Sonar Report
Tibor Digana created SUREFIRE-1224: -- Summary: Improve Code Quality After Sonar Report Key: SUREFIRE-1224 URL: https://issues.apache.org/jira/browse/SUREFIRE-1224 Project: Maven Surefire Issue Type: Improvement Affects Versions: 2.19.1 Reporter: Tibor Digana Assignee: Tibor Digana Priority: Minor Fix For: 2.19.2 https://analysis.apache.org/dashboard/index?id=org.apache.maven.surefire:surefire&did=2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1224) Improve Code Quality After Sonar Report
[ https://issues.apache.org/jira/browse/SUREFIRE-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1224. -- Resolution: Fixed commit eaf25fa03c44d2a813d3bdaa27e08a76ad1f87b2 > Improve Code Quality After Sonar Report > --- > > Key: SUREFIRE-1224 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1224 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.19.1 >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.19.2 > > > https://analysis.apache.org/dashboard/index?id=org.apache.maven.surefire:surefire&did=2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5227) The 'optional' flag of a dependency should be manageable.
[
https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125568#comment-15125568
]
Christian Schulte commented on MNG-5227:
I would not mind signing a CLA with Eclipse if that helps. No experience with
any processes there, though.
> The 'optional' flag of a dependency should be manageable.
> -
>
> Key: MNG-5227
> URL: https://issues.apache.org/jira/browse/MNG-5227
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.3
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.4.0
>
>
> {code}
>
>
>
> groupId
> artifactId
> version
> false
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1224) Improve Code Quality After Sonar Report
[ https://issues.apache.org/jira/browse/SUREFIRE-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125574#comment-15125574 ] Hudson commented on SUREFIRE-1224: -- SUCCESS: Integrated in maven-surefire #1580 (See [https://builds.apache.org/job/maven-surefire/1580/]) [SUREFIRE-1224] Improve Code Quality After Sonar Report (tibor17: rev eaf25fa03c44d2a813d3bdaa27e08a76ad1f87b2) * surefire-providers/common-junit48/src/main/java/org/apache/maven/surefire/common/junit48/RequestedTest.java * surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNGMapConfigurator.java * surefire-booter/src/main/java/org/apache/maven/surefire/booter/Classpath.java * maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactory.java * maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireHelper.java * surefire-booter/src/main/java/org/apache/maven/surefire/booter/TypeEncodedValue.java * surefire-providers/common-junit48/src/main/java/org/apache/maven/surefire/common/junit48/GroupMatcherCategoryFilter.java * surefire-booter/src/main/java/org/apache/maven/surefire/booter/IsolatedClassLoader.java * surefire-providers/surefire-junit47/src/main/java/org/apache/maven/surefire/junitcore/pc/ParallelComputerBuilder.java * surefire-api/src/main/java/org/apache/maven/surefire/testset/ResolvedTest.java * surefire-providers/surefire-junit3/src/main/java/org/apache/maven/surefire/junit/PojoTestSet.java * surefire-api/src/main/java/org/apache/maven/surefire/testset/TestListResolver.java * surefire-booter/src/main/java/org/apache/maven/surefire/booter/PropertiesWrapper.java * surefire-providers/surefire-junit47/src/test/java/org/apache/maven/surefire/junitcore/pc/ParallelComputerBuilderTest.java * surefire-api/src/test/java/org/apache/maven/surefire/testset/ResolvedTestTest.java * surefire-report-parser/src/main/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParser.java > Improve Code Quality After Sonar Report > --- > > Key: SUREFIRE-1224 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1224 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.19.1 >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.19.2 > > > https://analysis.apache.org/dashboard/index?id=org.apache.maven.surefire:surefire&did=2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5227) The 'optional' flag of a dependency should be manageable.
[
https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125575#comment-15125575
]
Jason van Zyl commented on MNG-5227:
It's a little more complicated at Eclipse because your employer has to sign the
corporate CLA. This usually takes a while, and honestly we're transitioning
this back to Apache so I'll have something for you in Maven Central in a day or
two.
> The 'optional' flag of a dependency should be manageable.
> -
>
> Key: MNG-5227
> URL: https://issues.apache.org/jira/browse/MNG-5227
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.3
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.4.0
>
>
> {code}
>
>
>
> groupId
> artifactId
> version
> false
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
