[jira] [Commented] (SUREFIRE-2218) Add support for fetching test classes from a jar

2023-12-01 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792014#comment-17792014 ] Sebb commented on SUREFIRE-2218: That would be fine as a name.   BTW, the documentation is a bit

[jira] [Created] (SUREFIRE-2218) Add support for fetching test classes from a jar

2023-11-30 Thread Sebb (Jira)
Sebb created SUREFIRE-2218: -- Summary: Add support for fetching test classes from a jar Key: SUREFIRE-2218 URL: https://issues.apache.org/jira/browse/SUREFIRE-2218 Project: Maven Surefire Issue

[jira] [Commented] (MCOMPILER-537) Inconsistent behaviour when compiler is forked

2023-06-06 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729685#comment-17729685 ] Sebb commented on MCOMPILER-537: AFAICT the compiler does produce these messages when run stand-alone;

[jira] [Created] (MCOMPILER-537) Inconsistent behaviour when compiler is forked

2023-06-06 Thread Sebb (Jira)
Sebb created MCOMPILER-537: -- Summary: Inconsistent behaviour when compiler is forked Key: MCOMPILER-537 URL: https://issues.apache.org/jira/browse/MCOMPILER-537 Project: Maven Compiler Plugin Issue

[jira] [Commented] (MCOMPILER-491) testCompile goal doesn't fail the build when encoding error occurs

2023-06-06 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729678#comment-17729678 ] Sebb commented on MCOMPILER-491: AFAICT, the compiler still generates the same class file provided

[jira] [Commented] (MCOMPILER-491) testCompile goal doesn't fail the build when encoding error occurs

2023-06-06 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729660#comment-17729660 ] Sebb commented on MCOMPILER-491: We found the same issue in Commons Compress:

[jira] [Commented] (MNG-5512) Deploy uses passwords that failed decryption; retries even if login fails

2022-01-11 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17473192#comment-17473192 ] Sebb commented on MNG-5512: --- It would be best if decryption failures were detected before trying to use a

[jira] [Commented] (MNG-5512) Deploy uses passwords that failed decryption; retries even if login fails

2022-01-10 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471877#comment-17471877 ] Sebb commented on MNG-5512: --- Note that there are two errors here: - not stopping when decryption fails - not

[jira] [Commented] (MNG-5512) Deploy uses passwords that failed decryption; retries even if login fails

2022-01-10 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MNG-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471852#comment-17471852 ] Sebb commented on MNG-5512: --- Are you not able to test it yourself? > Deploy uses passwords that failed

[jira] [Created] (MSCRIPTING-6) Download page link is broken

2021-04-22 Thread Sebb (Jira)
Sebb created MSCRIPTING-6: - Summary: Download page link is broken Key: MSCRIPTING-6 URL: https://issues.apache.org/jira/browse/MSCRIPTING-6 Project: Maven Scripting Issue Type: Bug

[jira] [Created] (MSHARED-984) Broken link to hash for maven-script-interpreter

2021-04-22 Thread Sebb (Jira)
Sebb created MSHARED-984: Summary: Broken link to hash for maven-script-interpreter Key: MSHARED-984 URL: https://issues.apache.org/jira/browse/MSHARED-984 Project: Maven Shared Components Issue

[jira] [Comment Edited] (SUREFIRE-1840) Why sudo docker?

2020-11-28 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239939#comment-17239939 ] Sebb edited comment on SUREFIRE-1840 at 11/28/20, 12:00 PM: I'm not saying

[jira] [Commented] (SUREFIRE-1840) Why sudo docker?

2020-11-28 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239939#comment-17239939 ] Sebb commented on SUREFIRE-1840: I'm not saying sudo should be removed, merely that the reason for it

[jira] [Commented] (SUREFIRE-1840) Why sudo docker?

2020-11-27 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239717#comment-17239717 ] Sebb commented on SUREFIRE-1840: Two comments: 1) I use Docker on macOS, and sudo is NOT needed for

[jira] [Created] (SUREFIRE-1840) Why sudo docker?

2020-09-12 Thread Sebb (Jira)
Sebb created SUREFIRE-1840: -- Summary: Why sudo docker? Key: SUREFIRE-1840 URL: https://issues.apache.org/jira/browse/SUREFIRE-1840 Project: Maven Surefire Issue Type: Bug Components:

[jira] [Commented] (MRELEASE-845) Improvements to processing strategy

2019-12-22 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MRELEASE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001914#comment-17001914 ] Sebb commented on MRELEASE-845: --- I don't see why this would be considered a breaking change. Even if it

[jira] [Moved] (MNGSITE-385) Code style should mention "else" style

2019-12-14 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MNGSITE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb moved COMDEV-336 to MNGSITE-385: - Component/s: (was: Website) Key: MNGSITE-385 (was: COMDEV-336)

[jira] [Commented] (MPIR-385) Emails in mailing list section of pom are improperly handled

2019-09-21 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MPIR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935007#comment-16935007 ] Sebb commented on MPIR-385: --- I see the patch fixes the code by adding a new method. However, this used to work

[jira] [Commented] (MPIR-380) Emails in developers section of pom are improperly handled

2019-09-17 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MPIR-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931749#comment-16931749 ] Sebb commented on MPIR-380: --- FTR: I've raised MPIR-385 for the bug > Emails in developers section of pom are

[jira] [Commented] (MPIR-380) Emails in developers section of pom are improperly handled

2019-09-17 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MPIR-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931572#comment-16931572 ] Sebb commented on MPIR-380: --- That is not the case according to the Maven POM doc:

[jira] [Updated] (MPIR-385) Emails in mailing list section of pom are improperly handled

2019-09-17 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MPIR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MPIR-385: -- Description: The generated file mailing-lists.html contains email names of the form: Subscribe instead of

[jira] [Updated] (MPIR-385) Emails in mailing list section of pom are improperly handled

2019-09-17 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MPIR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MPIR-385: -- Labels: regression (was: ) > Emails in mailing list section of pom are improperly handled >

[jira] [Created] (MPIR-385) Emails in mailing list section of pom are improperly handled

2019-09-17 Thread Sebb (Jira)
Sebb created MPIR-385: - Summary: Emails in mailing list section of pom are improperly handled Key: MPIR-385 URL: https://issues.apache.org/jira/browse/MPIR-385 Project: Maven Project Info Reports Plugin

[jira] [Commented] (MPIR-380) Emails in developers section of pom are improperly handled

2019-09-17 Thread Sebb (Jira)
[ https://issues.apache.org/jira/browse/MPIR-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931540#comment-16931540 ] Sebb commented on MPIR-380: --- Similar issue with mailing-lists.html; the mailto: prefix is omitted > Emails in

[jira] [Created] (MNGSITE-341) Download pages must use HTTPS for sigs, hashes, KEYS

2018-07-23 Thread Sebb (JIRA)
Sebb created MNGSITE-341: Summary: Download pages must use HTTPS for sigs, hashes, KEYS Key: MNGSITE-341 URL: https://issues.apache.org/jira/browse/MNGSITE-341 Project: Maven Project Web Site Issue

[jira] [Commented] (MSKINS-143) Allow setting anonymizeIP and forceSSL

2018-05-29 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MSKINS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494449#comment-16494449 ] Sebb commented on MSKINS-143: - I assume the Google Analytics code is optional? If it's not possible to

[jira] [Reopened] (MDOAP-49) Website still points to jira.codehaus.org

2017-05-01 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MDOAP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened MDOAP-49: --- That commit was 2 years ago, but the website has not yet been updated. Would it be possible to at least regenerate the

[jira] [Created] (MDOAP-49) Website still points to jira.codehaus.org

2017-04-30 Thread Sebb (JIRA)
Sebb created MDOAP-49: - Summary: Website still points to jira.codehaus.org Key: MDOAP-49 URL: https://issues.apache.org/jira/browse/MDOAP-49 Project: Maven DOAP Plugin Issue Type: Bug

[jira] [Created] (MSCMPUB-30) scm-publish:publish-scm changes files unnecessarily

2017-02-14 Thread Sebb (JIRA)
Sebb created MSCMPUB-30: --- Summary: scm-publish:publish-scm changes files unnecessarily Key: MSCMPUB-30 URL: https://issues.apache.org/jira/browse/MSCMPUB-30 Project: Maven SCM Publish Plugin Issue

[jira] [Created] (MSCMPUB-29) Website still points to jira.codehaus.org

2017-02-14 Thread Sebb (JIRA)
Sebb created MSCMPUB-29: --- Summary: Website still points to jira.codehaus.org Key: MSCMPUB-29 URL: https://issues.apache.org/jira/browse/MSCMPUB-29 Project: Maven SCM Publish Plugin Issue Type: Bug

[jira] [Comment Edited] (MNGSITE-261) .htaccess file forces http: for several redirects

2016-10-22 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MNGSITE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15597432#comment-15597432 ] Sebb edited comment on MNGSITE-261 at 10/22/16 8:26 AM: Thanks, that's better.

[jira] [Reopened] (MNGSITE-261) .htaccess file forces http: for several redirects

2016-10-22 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MNGSITE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened MNGSITE-261: -- Thanks, that's better. However, there are still some entries which may change from http: to https: RedirectMatch

[jira] [Created] (MJAR-224) Not possible to exclude classes from primary jar only

2016-05-19 Thread Sebb (JIRA)
Sebb created MJAR-224: - Summary: Not possible to exclude classes from primary jar only Key: MJAR-224 URL: https://issues.apache.org/jira/browse/MJAR-224 Project: Maven JAR Plugin Issue Type: Bug

[jira] [Commented] (MPOM-118) Enforce strong GPG signatures by default

2016-05-18 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289970#comment-15289970 ] Sebb commented on MPOM-118: --- Would it be worth adding a feature to the GPG plugin to print a large warning if a

[jira] [Issue Comment Deleted] (MPOM-118) Enforce strong GPG signatures by default

2016-05-18 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MPOM-118: -- Comment: was deleted (was: I don't see the point. Hashes are only really useful for checking that a download has

[jira] [Commented] (MPOM-118) Enforce strong GPG signatures by default

2016-05-18 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289955#comment-15289955 ] Sebb commented on MPOM-118: --- I don't see the point. Hashes are only really useful for checking that a download

[jira] [Commented] (MASFRES-6) Apache Parent POM 9 apache-release profile issues

2016-05-01 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MASFRES-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265978#comment-15265978 ] Sebb commented on MASFRES-6: And no-one thought to add redirects ... > Apache Parent POM 9 apache-release

[jira] [Created] (MNG-6012) Missing profile is only notified at the end of a run

2016-05-01 Thread Sebb (JIRA)
Sebb created MNG-6012: - Summary: Missing profile is only notified at the end of a run Key: MNG-6012 URL: https://issues.apache.org/jira/browse/MNG-6012 Project: Maven Issue Type: Bug

[jira] [Commented] (MASFRES-6) Apache Parent POM 9 apache-release profile issues

2016-05-01 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MASFRES-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265901#comment-15265901 ] Sebb commented on MASFRES-6: The Parent Pom 17 has: source-release So AFAICT it only includes a zip by

[jira] [Commented] (MASFRES-6) Apache Parent POM 9 apache-release profile issues

2016-05-01 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MASFRES-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265896#comment-15265896 ] Sebb commented on MASFRES-6:

[jira] [Reopened] (DOXIA-491) Where are the binary downloads for Doxia Tools?

2016-01-05 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/DOXIA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened DOXIA-491: bq. Either way the downloads page needs changes to make it clear that Doxia Tools is an umbrella and that its subparts

[jira] [Created] (MNGSITE-261) .htaccess file forces http: for several redirects

2015-10-12 Thread Sebb (JIRA)
Sebb created MNGSITE-261: Summary: .htaccess file forces http: for several redirects Key: MNGSITE-261 URL: https://issues.apache.org/jira/browse/MNGSITE-261 Project: Maven Project Web Site Issue

[jira] [Created] (MNGSITE-260) Download pages don't use customised versions

2015-10-12 Thread Sebb (JIRA)
Sebb created MNGSITE-260: Summary: Download pages don't use customised versions Key: MNGSITE-260 URL: https://issues.apache.org/jira/browse/MNGSITE-260 Project: Maven Project Web Site Issue Type:

[jira] [Reopened] (MANT-63) get phase uses snapshot repo for non-snapshot dependencies

2015-06-19 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MANT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened MANT-63: -- This is still an issue. The get task should be generated to use the SNAPSHOT repo iff the dependency is a SNAPSHOT

[jira] [Created] (MNG-5834) Don't add checksums on gpg signature files

2015-05-31 Thread Sebb (JIRA)
Sebb created MNG-5834: - Summary: Don't add checksums on gpg signature files Key: MNG-5834 URL: https://issues.apache.org/jira/browse/MNG-5834 Project: Maven Issue Type: Improvement Affects Versions:

[jira] [Updated] (MNGSITE-239) Download page does not cite Java requirement for 3.3.x versions

2015-05-31 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MNGSITE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MNGSITE-239: - Description: The download page does not mention the Java version requirement for running version 3.3.x in the

[jira] [Created] (MNGSITE-239) Download page does not cite Java requirement for 3.3.x versions

2015-05-31 Thread Sebb (JIRA)
Sebb created MNGSITE-239: Summary: Download page does not cite Java requirement for 3.3.x versions Key: MNGSITE-239 URL: https://issues.apache.org/jira/browse/MNGSITE-239 Project: Maven Project Web Site

[jira] [Resolved] (MNG-5834) Don't add checksums on gpg signature files

2015-05-31 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MNG-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved MNG-5834. --- Resolution: Invalid Sorry, raised in error Don't add checksums on gpg signature files

[jira] [Closed] (MNG-5834) Don't add checksums on gpg signature files

2015-05-31 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MNG-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed MNG-5834. - Invalid Don't add checksums on gpg signature files -- Key:

[jira] [Commented] (MNGSITE-183) Announce e-mail and project website must reference source download page

2015-05-28 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MNGSITE-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14563366#comment-14563366 ] Sebb commented on MNGSITE-183: -- Not sufficient, the component website must also link to the

[jira] [Commented] (MNGSITE-183) Announce e-mail and project website must reference source download page

2015-05-28 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MNGSITE-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14563995#comment-14563995 ] Sebb commented on MNGSITE-183: -- There were two places (announce message and website) listed

[jira] [Commented] (DOXIASITETOOLS-96) Flexible site descriptor inheritance

2015-05-04 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14527568#comment-14527568 ] Sebb commented on DOXIASITETOOLS-96: Not as far as I can tell. This issue is

[jira] [Commented] (MANT-66) Ambiguous date in generated header comment

2015-04-29 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MANT-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520562#comment-14520562 ] Sebb commented on MANT-66: -- That would be fine. Ambiguous date in generated header comment

[jira] [Commented] (MPOM-69) avoid Rat plugin warning

2015-02-15 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322051#comment-14322051 ] Sebb commented on MPOM-69: -- Furthermore, the patch to the Apache pom should be flagged as a

[jira] [Commented] (MPOM-69) avoid Rat plugin warning

2015-02-15 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322068#comment-14322068 ] Sebb commented on MPOM-69: -- The warning is nothing to do with RAT per se. It just so happens that

[jira] [Commented] (MPOM-69) avoid Rat plugin warning

2015-02-15 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322043#comment-14322043 ] Sebb commented on MPOM-69: -- The comment in the Apache Pom refers to RAT-158. However RAT is not the

[jira] [Commented] (MPOM-69) avoid Rat plugin warning

2015-02-15 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322260#comment-14322260 ] Sebb commented on MPOM-69: -- You are assuming that the Apache pom will be released before RAT, and

[jira] [Commented] (MPOM-69) avoid Rat plugin warning

2015-02-15 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322126#comment-14322126 ] Sebb commented on MPOM-69: -- The problem obviously only occurs when the Maven RAT plugin is used

[jira] [Commented] (MPOM-69) avoid Rat plugin warning

2015-02-15 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322216#comment-14322216 ] Sebb commented on MPOM-69: -- bq. it relates to the jars selected by Maven RAT plugin If this problem

[jira] [Commented] (MPOM-44) Compiler version settings cannot be overridden by defining maven.compiler.source/target

2013-06-30 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13696350#comment-13696350 ] Sebb commented on MPOM-44: -- The extended patch changes lots of other unrelated items as well. Also

[jira] [Created] (MPOM-46) Update Javadoc plugin for CVE-2013-1571, VU#225657 - MJAVADOC-370

2013-06-30 Thread Sebb (JIRA)
Sebb created MPOM-46: Summary: Update Javadoc plugin for CVE-2013-1571, VU#225657 - MJAVADOC-370 Key: MPOM-46 URL: https://issues.apache.org/jira/browse/MPOM-46 Project: Maven POMs Issue Type: Bug

[jira] [Created] (MPOM-44) Compiler version settings cannot be overridden by defining maven.compiler.source/target

2013-06-18 Thread Sebb (JIRA)
Sebb created MPOM-44: Summary: Compiler version settings cannot be overridden by defining maven.compiler.source/target Key: MPOM-44 URL: https://issues.apache.org/jira/browse/MPOM-44 Project: Maven POMs

[jira] [Updated] (MPOM-44) Compiler version settings cannot be overridden by defining maven.compiler.source/target

2013-06-18 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MPOM-44: - Attachment: MPOM-44.patch Compiler version settings cannot be overridden by defining maven.compiler.source/target

[jira] [Commented] (MPOM-32) Apache POM 10 forces all child projects to generate the project info reports

2013-01-05 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13545272#comment-13545272 ] Sebb commented on MPOM-32: -- Please remove the list of reports from the pom; it is unnecessary and

[jira] [Updated] (MPOM-32) Apache POM 10 forces all child projects to generate the project info reports

2013-01-05 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MPOM-32: - Affects Version/s: ASF-11 ASF-12 Apache POM 10 forces all child projects to generate the

[jira] [Created] (MPOM-32) Apache POM 10 forces all child projects to generate the project info reports

2011-09-10 Thread Sebb (JIRA)
Apache POM 10 forces all child projects to generate the project info reports Key: MPOM-32 URL: https://issues.apache.org/jira/browse/MPOM-32 Project: Maven POMs

[jira] [Created] (MPOM-28) apache jar resource bundle does not appear to be documented

2011-09-05 Thread Sebb (JIRA)
apache jar resource bundle does not appear to be documented --- Key: MPOM-28 URL: https://issues.apache.org/jira/browse/MPOM-28 Project: Maven POMs Issue Type: Bug

[jira] [Created] (MPOM-29) apache jar resource bundle bugs

2011-09-05 Thread Sebb (JIRA)
apache jar resource bundle bugs --- Key: MPOM-29 URL: https://issues.apache.org/jira/browse/MPOM-29 Project: Maven POMs Issue Type: Bug Components: asf Environment: version=1.4

[jira] [Updated] (MPOM-29) apache jar resource bundle bugs

2011-09-05 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MPOM-29: - Attachment: MPOM-29.patch Patch for apache-jar-resource-bundle and apache-jar-txt-resource-bundle apache jar resource

[jira] [Created] (MPOM-10) Apache Parent POM 9 apache-release profile issues

2011-05-18 Thread Sebb (JIRA)
Apache Parent POM 9 apache-release profile issues - Key: MPOM-10 URL: https://issues.apache.org/jira/browse/MPOM-10 Project: Maven POM Issue Type: Bug Reporter: Sebb The

[jira] [Commented] (MPOM-9) Apache Parent POM 9 does not allow override of useAgent in apache-release profile

2011-05-06 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13029852#comment-13029852 ] Sebb commented on MPOM-9: - When using GPG 1.x, the current settings cause Maven to hang unless the

[jira] [Updated] (MPOM-9) Apache Parent POM 9 does not allow override of useAgent in apache-release profile

2011-05-06 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MPOM-9: Priority: Critical (was: Major) Apache Parent POM 9 does not allow override of useAgent in apache-release profile

[jira] [Issue Comment Edited] (MPOM-9) Apache Parent POM 9 does not allow override of useAgent in apache-release profile

2011-05-06 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13029852#comment-13029852 ] Sebb edited comment on MPOM-9 at 5/6/11 10:58 AM: -- When using GPG 1.x, the

[jira] [Reopened] (MPOM-9) Apache Parent POM 9 does not allow override of useAgent in apache-release profile

2011-05-06 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened MPOM-9: - In retrospect, I think deleting the useAgent tag is better. Apache Parent POM 9 does not allow override of useAgent in

[jira] [Commented] (MPOM-9) Apache Parent POM 9 does not allow override of useAgent in apache-release profile

2011-05-06 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030168#comment-13030168 ] Sebb commented on MPOM-9: - Because the useAgent setting is installation dependent it does not make

[jira] [Updated] (MPOM-7) Apache Parent Pom should be properly documented

2011-04-26 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MPOM-7: Attachment: asf-pom.patch Patchj: - wrap long comment line - add details of url and issue tracker for this pom Apache Parent

[jira] [Created] (MPOM-9) Apache Parent POM 9 does not allow override of useAgent in apache-release profile

2011-04-25 Thread Sebb (JIRA)
Apache Parent POM 9 does not allow override of useAgent in apache-release profile --- Key: MPOM-9 URL: https://issues.apache.org/jira/browse/MPOM-9 Project: Maven POM

[jira] Reopened: (MPOM-7) Apache Parent Pom should be properly documented

2011-02-10 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened MPOM-7: - The POM still needs the dcoumentation. Apache Parent Pom should be properly documented

[jira] Commented: (MPOM-7) Apache Parent Pom should be properly documented

2011-02-05 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12991055#comment-12991055 ] Sebb commented on MPOM-7: - Thanks, that will make it much easier for users of the POM in future.

[jira] Created: (MPOM-7) CLONE - Apache Parent Pom should be properly documented

2011-02-04 Thread Sebb (JIRA)
CLONE - Apache Parent Pom should be properly documented --- Key: MPOM-7 URL: https://issues.apache.org/jira/browse/MPOM-7 Project: Maven POM Issue Type: Improvement Reporter:

[jira] Commented: (MPOM-7) CLONE - Apache Parent Pom should be properly documented

2011-02-04 Thread Sebb (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990880#comment-12990880 ] Sebb commented on MPOM-7: - [Unable to re-open the original issue so created a clone] The Pom itself