[jira] [Commented] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385666#comment-16385666
]
Hervé Boutemy commented on DOXIASITETOOLS-148:
--
a few weeks ago, I revived the sources of siteskinner-maven-plugin from old
Codehaus svn to GitHub, which is the only case I know of that uses this field:
see [http://www.mojohaus.org/siteskinner-maven-plugin/]
this field can be useful, just need to finish to put a clear semantic on every
date that is used in Doxia (and there are many which are not clear, like last
edit date vs creation date in the header)
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-345) Upgrade to Doxia 1.7
[ https://issues.apache.org/jira/browse/MPIR-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385411#comment-16385411 ] Sylwester Lachiewicz commented on MPIR-345: --- Can we try with .1.8? > Upgrade to Doxia 1.7 > > > Key: MPIR-345 > URL: https://issues.apache.org/jira/browse/MPIR-345 > Project: Maven Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.9 >Reporter: Michael Osipov >Priority: Major > Fix For: 2.10 > > Attachments: 1.7.log, MPIR-345.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MDEPLOY-231) Move checksum generation from install to deploy plugin
Karl Heinz Marbaise created MDEPLOY-231: --- Summary: Move checksum generation from install to deploy plugin Key: MDEPLOY-231 URL: https://issues.apache.org/jira/browse/MDEPLOY-231 Project: Maven Deploy Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Fix For: 3.0.0 It is need to consistently move the checksum generation into maven-deploy-plugin which means to change the maven-artifact-transfer component accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-693) Upgrade JUnit from 4.11 to 4.12
[ https://issues.apache.org/jira/browse/MSHARED-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385402#comment-16385402 ] Hudson commented on MSHARED-693: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » CODE-IMPROVEMENTS #2 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/CODE-IMPROVEMENTS/2/ > Upgrade JUnit from 4.11 to 4.12 > --- > > Key: MSHARED-693 > URL: https://issues.apache.org/jira/browse/MSHARED-693 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-artifact-transfer-1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-680) Add null check for DependencyResolver/DependencyCollector/ProjectDeployer Interfaces
[ https://issues.apache.org/jira/browse/MSHARED-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385401#comment-16385401 ] Hudson commented on MSHARED-680: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » CODE-IMPROVEMENTS #2 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/CODE-IMPROVEMENTS/2/ > Add null check for DependencyResolver/DependencyCollector/ProjectDeployer > Interfaces > > > Key: MSHARED-680 > URL: https://issues.apache.org/jira/browse/MSHARED-680 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > > * Null Check for DependencyCollector > * Null Check for ProjectDeployer > * Null Check for DependencyResolver -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-656) Make integration testing for different Maven versions possible
[
https://issues.apache.org/jira/browse/MSHARED-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385400#comment-16385400
]
Hudson commented on MSHARED-656:
Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-656
#24
See
https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-656/24/
> Make integration testing for different Maven versions possible
> --
>
> Key: MSHARED-656
> URL: https://issues.apache.org/jira/browse/MSHARED-656
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-1.0.0
>
>
> Creating a way to make integration testing of the different implementation
> possible during the building of the shared component. Currently it is only
> possible to make running the tests only for Maven 3.0.X based on the
> definition of the dependencies in particular:
> {code:xml}
>
> org.sonatype.aether
> aether-impl
> 1.7
> test
>
> {code}
> Based on the usage of tools like Takari plugin testing we need to lift up the
> build requirements to JDK 8 minimum.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1490) Change header of the Failsafe Report
[ https://issues.apache.org/jira/browse/SUREFIRE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385396#comment-16385396 ] Tibor Digana commented on SUREFIRE-1490: [~fedyafed] It looked to me you meant these titles http://maven.apache.org/surefire/surefire-integration-tests/project-reports.html but you meant http://maven.apache.org/surefire/surefire-integration-tests/failsafe-report.html I will try to implement polymorphic Resource bundle where each MOJO would have own implementation of abstract methods - keys. > Change header of the Failsafe Report > > > Key: SUREFIRE-1490 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1490 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Report Plugin >Affects Versions: 2.20.1 >Reporter: Ivan Fedotov >Assignee: Tibor Digana >Priority: Minor > > Hi! > I noted that the Failsafe Report's header is "Surefire Report", which is > quite confusing. > Can you fix this? > Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (SUREFIRE-1490) Change header of the Failsafe Report
[ https://issues.apache.org/jira/browse/SUREFIRE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reopened SUREFIRE-1490: > Change header of the Failsafe Report > > > Key: SUREFIRE-1490 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1490 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Report Plugin >Affects Versions: 2.20.1 >Reporter: Ivan Fedotov >Assignee: Tibor Digana >Priority: Minor > > Hi! > I noted that the Failsafe Report's header is "Surefire Report", which is > quite confusing. > Can you fix this? > Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-656) Make integration testing for different Maven versions possible
[
https://issues.apache.org/jira/browse/MSHARED-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MSHARED-656:
Description:
Creating a way to make integration testing of the different implementation
possible during the building of the shared component. Currently it is only
possible to make running the tests only for Maven 3.0.X based on the definition
of the dependencies in particular:
{code:xml}
org.sonatype.aether
aether-impl
1.7
test
{code}
Based on the usage of tools like Takari plugin testing we need to lift up the
build requirements to JDK 8 minimum.
was:
Creating a way to make integration testing of the different implementation
possible during the building of the shared component. Currently it is only
possible to make running the tests only for Maven 3.0.X based on the definition
of the dependencies in particular:
{code:xml}
org.sonatype.aether
aether-impl
1.7
test
{code}
Based on the usage of tools like Takari plugin testing we need to lift up the
build requirements to JDK 8 minimum.
The minimum runtime is Java 7.
> Make integration testing for different Maven versions possible
> --
>
> Key: MSHARED-656
> URL: https://issues.apache.org/jira/browse/MSHARED-656
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-1.0.0
>
>
> Creating a way to make integration testing of the different implementation
> possible during the building of the shared component. Currently it is only
> possible to make running the tests only for Maven 3.0.X based on the
> definition of the dependencies in particular:
> {code:xml}
>
> org.sonatype.aether
> aether-impl
> 1.7
> test
>
> {code}
> Based on the usage of tools like Takari plugin testing we need to lift up the
> build requirements to JDK 8 minimum.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSHARED-656) Make integration testing for different Maven versions possible
[
https://issues.apache.org/jira/browse/MSHARED-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MSHARED-656:
Description:
Creating a way to make integration testing of the different implementation
possible during the building of the shared component. Currently it is only
possible to make running the tests only for Maven 3.0.X based on the definition
of the dependencies in particular:
{code:xml}
org.sonatype.aether
aether-impl
1.7
test
{code}
Based on the usage of tools like Takari plugin testing we need to lift up the
build requirements to JDK 8 minimum.
The minimum runtime is Java 7.
was:
Creating a way to make integration testing of the different implementation
possible during the building of the shared component. Currently it is only
possible to make running the tests only for Maven 3.0.X based on the definition
of the dependencies in particular:
{code:xml}
org.sonatype.aether
aether-impl
1.7
test
{code}
Based on the usage of tools like Takari plugin testing we need to lift up the
build requirements to JDK 8 minimum.
> Make integration testing for different Maven versions possible
> --
>
> Key: MSHARED-656
> URL: https://issues.apache.org/jira/browse/MSHARED-656
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-1.0.0
>
>
> Creating a way to make integration testing of the different implementation
> possible during the building of the shared component. Currently it is only
> possible to make running the tests only for Maven 3.0.X based on the
> definition of the dependencies in particular:
> {code:xml}
>
> org.sonatype.aether
> aether-impl
> 1.7
> test
>
> {code}
> Based on the usage of tools like Takari plugin testing we need to lift up the
> build requirements to JDK 8 minimum.
> The minimum runtime is Java 7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSHARED-656) Make integration testing for different Maven versions possible
[
https://issues.apache.org/jira/browse/MSHARED-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MSHARED-656:
Description:
Creating a way to make integration testing of the different implementation
possible during the building of the shared component. Currently it is only
possible to make running the tests only for Maven 3.0.X based on the definition
of the dependencies in particular:
{code:xml}
org.sonatype.aether
aether-impl
1.7
test
{code}
Based on the usage of tools like Takari plugin testing we need to lift up the
build requirements to JDK 8 minimum.
was:
Creating a way to make integration testing of the different implementation
possible during the building of the shared component. Currently it is only
possible to make running the tests only for Maven 3.0.X based on the definition
of the dependencies in particular:
{code:xml}
org.sonatype.aether
aether-impl
1.7
test
{code}
> Make integration testing for different Maven versions possible
> --
>
> Key: MSHARED-656
> URL: https://issues.apache.org/jira/browse/MSHARED-656
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-1.0.0
>
>
> Creating a way to make integration testing of the different implementation
> possible during the building of the shared component. Currently it is only
> possible to make running the tests only for Maven 3.0.X based on the
> definition of the dependencies in particular:
> {code:xml}
>
> org.sonatype.aether
> aether-impl
> 1.7
> test
>
> {code}
> Based on the usage of tools like Takari plugin testing we need to lift up the
> build requirements to JDK 8 minimum.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MINSTALL-143) Move checksum generation from install to deploy plugin
[ https://issues.apache.org/jira/browse/MINSTALL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MINSTALL-143: - Issue Type: Improvement (was: Dependency upgrade) > Move checksum generation from install to deploy plugin > -- > > Key: MINSTALL-143 > URL: https://issues.apache.org/jira/browse/MINSTALL-143 > Project: Maven Install Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > We should move the checksum generation from maven-install-plugin to > maven-deploy-plugin cause the checksums will only be needed as a preparation > for the transfer to a remote repository but not for an installation into a > local repository. > This needed to be done within maven-artifact-transfer component first. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINSTALL-143) Move checksum generation from install to deploy plugin
[ https://issues.apache.org/jira/browse/MINSTALL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MINSTALL-143: - Description: We should move the checksum generation from maven-install-plugin to maven-deploy-plugin cause the checksums will only be needed as a preparation for the transfer to a remote repository but not for an installation into a local repository. This needed to be done within maven-artifact-transfer component first. > Move checksum generation from install to deploy plugin > -- > > Key: MINSTALL-143 > URL: https://issues.apache.org/jira/browse/MINSTALL-143 > Project: Maven Install Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > > We should move the checksum generation from maven-install-plugin to > maven-deploy-plugin cause the checksums will only be needed as a preparation > for the transfer to a remote repository but not for an installation into a > local repository. > This needed to be done within maven-artifact-transfer component first. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINSTALL-143) Move checksum generation from install to deploy plugin
[ https://issues.apache.org/jira/browse/MINSTALL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MINSTALL-143: - Summary: Move checksum generation from install to deploy plugin (was: Use maven-artifact-transfer with handling of Checksums) > Move checksum generation from install to deploy plugin > -- > > Key: MINSTALL-143 > URL: https://issues.apache.org/jira/browse/MINSTALL-143 > Project: Maven Install Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINSTALL-143) Use maven-artifact-transfer with handling of Checksums
Karl Heinz Marbaise created MINSTALL-143: Summary: Use maven-artifact-transfer with handling of Checksums Key: MINSTALL-143 URL: https://issues.apache.org/jira/browse/MINSTALL-143 Project: Maven Install Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385390#comment-16385390
]
Michael Osipov commented on DOXIASITETOOLS-148:
---
[~rfscholte], I really doubt that any of us will have the time for this.
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MSHARED-694) Upgrade JUnit 3.8.2 to 4.12
[ https://issues.apache.org/jira/browse/MSHARED-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-694. --- Resolution: Fixed Done in [7fbd6f83d24967c0305c033116d3e626ffe0db46|https://gitbox.apache.org/repos/asf?p=maven-verifier.git;a=commitdiff;h=7fbd6f83d24967c0305c033116d3e626ffe0db46] > Upgrade JUnit 3.8.2 to 4.12 > --- > > Key: MSHARED-694 > URL: https://issues.apache.org/jira/browse/MSHARED-694 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-verifier >Affects Versions: maven-verifier-3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-verifier-3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-694) Upgrade JUnit 3.8.2 to 4.12
[ https://issues.apache.org/jira/browse/MSHARED-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385386#comment-16385386 ] Hudson commented on MSHARED-694: Build succeeded in Jenkins: Maven TLP » maven-verifier » master #4 See https://builds.apache.org/job/maven-box/job/maven-verifier/job/master/4/ > Upgrade JUnit 3.8.2 to 4.12 > --- > > Key: MSHARED-694 > URL: https://issues.apache.org/jira/browse/MSHARED-694 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-verifier >Affects Versions: maven-verifier-3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-verifier-3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-694) Upgrade JUnit 3.8.2 to 4.12
Karl Heinz Marbaise created MSHARED-694: --- Summary: Upgrade JUnit 3.8.2 to 4.12 Key: MSHARED-694 URL: https://issues.apache.org/jira/browse/MSHARED-694 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-verifier Affects Versions: maven-verifier-3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-verifier-3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-690) Change package from org.apache.maven.it to org.apache.maven.shared.verifier
[
https://issues.apache.org/jira/browse/MSHARED-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHARED-690.
---
Resolution: Fixed
Done in
[eb124cbe2fba450f09df00172793eac7caab0b73|https://gitbox.apache.org/repos/asf?p=maven-verifier.git;a=commitdiff;h=eb124cbe2fba450f09df00172793eac7caab0b73]
> Change package from org.apache.maven.it to org.apache.maven.shared.verifier
> ---
>
> Key: MSHARED-690
> URL: https://issues.apache.org/jira/browse/MSHARED-690
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-verifier
>Affects Versions: maven-verifier-1.7
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: maven-verifier-1.7
>
>
> I think it makes sense to change the package name from
> {{org.apache.maven.it}} to {{org.apache.maven.shared.verifier}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-690) Change package from org.apache.maven.it to org.apache.maven.shared.verifier
[
https://issues.apache.org/jira/browse/MSHARED-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385369#comment-16385369
]
Hudson commented on MSHARED-690:
Build succeeded in Jenkins: Maven TLP » maven-verifier » master #3
See https://builds.apache.org/job/maven-box/job/maven-verifier/job/master/3/
> Change package from org.apache.maven.it to org.apache.maven.shared.verifier
> ---
>
> Key: MSHARED-690
> URL: https://issues.apache.org/jira/browse/MSHARED-690
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-verifier
>Affects Versions: maven-verifier-1.7
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: maven-verifier-1.7
>
>
> I think it makes sense to change the package name from
> {{org.apache.maven.it}} to {{org.apache.maven.shared.verifier}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSHARED-690) Change package from org.apache.maven.it to org.apache.maven.shared.verifier
[
https://issues.apache.org/jira/browse/MSHARED-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MSHARED-690:
Priority: Major (was: Critical)
> Change package from org.apache.maven.it to org.apache.maven.shared.verifier
> ---
>
> Key: MSHARED-690
> URL: https://issues.apache.org/jira/browse/MSHARED-690
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-verifier
>Affects Versions: maven-verifier-1.7
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: maven-verifier-1.7
>
>
> I think it makes sense to change the package name from
> {{org.apache.maven.it}} to {{org.apache.maven.shared.verifier}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSHARED-549) Remove hard code version for maven-shade-plugin
[ https://issues.apache.org/jira/browse/MSHARED-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-549: Description: We need to explicitly overwrite the version which is inherited from parent. > Remove hard code version for maven-shade-plugin > --- > > Key: MSHARED-549 > URL: https://issues.apache.org/jira/browse/MSHARED-549 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.9.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > > We need to explicitly overwrite the version which is inherited from parent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-549) Remove hard code version for maven-shade-plugin
[ https://issues.apache.org/jira/browse/MSHARED-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-549: Description: We need to explicitly overwrite the version which is inherited from parent. So we can't remove that at the moment. (was: We need to explicitly overwrite the version which is inherited from parent.) > Remove hard code version for maven-shade-plugin > --- > > Key: MSHARED-549 > URL: https://issues.apache.org/jira/browse/MSHARED-549 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.9.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > > We need to explicitly overwrite the version which is inherited from parent. > So we can't remove that at the moment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-549) Remove hard code version for maven-shade-plugin
[ https://issues.apache.org/jira/browse/MSHARED-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-549. --- Resolution: Won't Fix Currently this will not happen until we upgrade the parent version. > Remove hard code version for maven-shade-plugin > --- > > Key: MSHARED-549 > URL: https://issues.apache.org/jira/browse/MSHARED-549 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.9.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > > We need to explicitly overwrite the version which is inherited from parent. > So we can't remove that at the moment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-549) Remove hard code version for maven-shade-plugin
[ https://issues.apache.org/jira/browse/MSHARED-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-549: Fix Version/s: (was: maven-artifact-transfer-1.0.0) > Remove hard code version for maven-shade-plugin > --- > > Key: MSHARED-549 > URL: https://issues.apache.org/jira/browse/MSHARED-549 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.9.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > > We need to explicitly overwrite the version which is inherited from parent. > So we can't remove that at the moment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MWAR-401) Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.7.0
[ https://issues.apache.org/jira/browse/MWAR-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MWAR-401. Resolution: Fixed Done in [2a16d37e4c2d81fcc207647913df1f7e689974f2|https://gitbox.apache.org/repos/asf?p=maven-war-plugin.git;a=commitdiff;h=2a16d37e4c2d81fcc207647913df1f7e689974f2] > Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.7.0 > > > Key: MWAR-401 > URL: https://issues.apache.org/jira/browse/MWAR-401 > Project: Maven WAR Plugin > Issue Type: Task >Reporter: Christian Schulte >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MWAR-401) Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.7.0
[ https://issues.apache.org/jira/browse/MWAR-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385357#comment-16385357 ] Hudson commented on MWAR-401: - Build succeeded in Jenkins: Maven TLP » maven-war-plugin » master #8 See https://builds.apache.org/job/maven-box/job/maven-war-plugin/job/master/8/ > Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.7.0 > > > Key: MWAR-401 > URL: https://issues.apache.org/jira/browse/MWAR-401 > Project: Maven WAR Plugin > Issue Type: Task >Reporter: Christian Schulte >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MWAR-401) Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.7.0
[ https://issues.apache.org/jira/browse/MWAR-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MWAR-401: - Fix Version/s: (was: next-release) 3.3.0 > Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.7.0 > > > Key: MWAR-401 > URL: https://issues.apache.org/jira/browse/MWAR-401 > Project: Maven WAR Plugin > Issue Type: Task >Reporter: Christian Schulte >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MWAR-401) Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.7.0
[ https://issues.apache.org/jira/browse/MWAR-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MWAR-401: - Summary: Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.7.0 (was: Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.6.0) > Upgrade the WAR lifecycle to use the maven-compiler-plugin 3.7.0 > > > Key: MWAR-401 > URL: https://issues.apache.org/jira/browse/MWAR-401 > Project: Maven WAR Plugin > Issue Type: Task >Reporter: Christian Schulte >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: next-release > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MWAR-412) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MWAR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MWAR-412. Resolution: Fixed Done in [da97036d7fdd88d30e5f55865fdc0d5d12e7fcb4|https://gitbox.apache.org/repos/asf?p=maven-war-plugin.git;a=commitdiff;h=da97036d7fdd88d30e5f55865fdc0d5d12e7fcb4] > Upgrade parent to 31 > > > Key: MWAR-412 > URL: https://issues.apache.org/jira/browse/MWAR-412 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MWAR-412) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MWAR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385341#comment-16385341 ] Hudson commented on MWAR-412: - Build succeeded in Jenkins: Maven TLP » maven-war-plugin » master #7 See https://builds.apache.org/job/maven-box/job/maven-war-plugin/job/master/7/ > Upgrade parent to 31 > > > Key: MWAR-412 > URL: https://issues.apache.org/jira/browse/MWAR-412 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MWAR-412) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MWAR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385338#comment-16385338 ] Hudson commented on MWAR-412: - Build succeeded in Jenkins: Maven TLP » maven-war-plugin » MWAR-412 #2 See https://builds.apache.org/job/maven-box/job/maven-war-plugin/job/MWAR-412/2/ > Upgrade parent to 31 > > > Key: MWAR-412 > URL: https://issues.apache.org/jira/browse/MWAR-412 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385336#comment-16385336
]
Robert Scholte commented on DOXIASITETOOLS-148:
---
[~hboutemy] pointed me at reproducable sites (as a follow up of reproducable
builds). Based on that we need to review the whole concept, which implies
locking dates.
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DOXIA-568) Doxia Markdown extension > Support for some MarkDown extensions has been removed since 1.7
[ https://issues.apache.org/jira/browse/DOXIA-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385333#comment-16385333 ] Sylwester Lachiewicz commented on DOXIA-568: No, its hard to find changes between versions [wiki|https://github.com/vsch/flexmark-java/wiki/Extensions/_history?page=1] related to this features. > Doxia Markdown extension > Support for some MarkDown extensions has been > removed since 1.7 > -- > > Key: DOXIA-568 > URL: https://issues.apache.org/jira/browse/DOXIA-568 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Markdown >Affects Versions: 1.8 >Reporter: Matthieu Ghilain >Priority: Major > > Currently the markdown extensions which are allowed by the Doxia parser seems > to be fixed to a subset of what was allowed with Doxia 1.7 and old PegDown > library. > I would like to be able to use the anchor link extension which was available > with 1.7 as well as the syntax highlighting that was also available for > scripts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-680) Add null check for DependencyResolver/DependencyCollector/ProjectDeployer Interfaces
[ https://issues.apache.org/jira/browse/MSHARED-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385329#comment-16385329 ] Hudson commented on MSHARED-680: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-656 #21 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-656/21/ > Add null check for DependencyResolver/DependencyCollector/ProjectDeployer > Interfaces > > > Key: MSHARED-680 > URL: https://issues.apache.org/jira/browse/MSHARED-680 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > > * Null Check for DependencyCollector > * Null Check for ProjectDeployer > * Null Check for DependencyResolver -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-656) Make integration testing for different Maven versions possible
[
https://issues.apache.org/jira/browse/MSHARED-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385331#comment-16385331
]
Hudson commented on MSHARED-656:
Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-656
#21
See
https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-656/21/
> Make integration testing for different Maven versions possible
> --
>
> Key: MSHARED-656
> URL: https://issues.apache.org/jira/browse/MSHARED-656
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.9.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-1.0.0
>
>
> Creating a way to make integration testing of the different implementation
> possible during the building of the shared component. Currently it is only
> possible to make running the tests only for Maven 3.0.X based on the
> definition of the dependencies in particular:
> {code:xml}
>
> org.sonatype.aether
> aether-impl
> 1.7
> test
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-693) Upgrade JUnit from 4.11 to 4.12
[ https://issues.apache.org/jira/browse/MSHARED-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385330#comment-16385330 ] Hudson commented on MSHARED-693: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-656 #21 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-656/21/ > Upgrade JUnit from 4.11 to 4.12 > --- > > Key: MSHARED-693 > URL: https://issues.apache.org/jira/browse/MSHARED-693 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-artifact-transfer-1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-693) Upgrade JUnit from 4.11 to 4.12
[ https://issues.apache.org/jira/browse/MSHARED-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-693. --- Resolution: Fixed Done in [78de5f32c2f85ecd9ade2f17722a6cbc1beffb1d|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=78de5f32c2f85ecd9ade2f17722a6cbc1beffb1d] > Upgrade JUnit from 4.11 to 4.12 > --- > > Key: MSHARED-693 > URL: https://issues.apache.org/jira/browse/MSHARED-693 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-artifact-transfer-1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-133) Drop deprecated alias 'full'
[
https://issues.apache.org/jira/browse/MPH-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385320#comment-16385320
]
Michael Osipov commented on MPH-133:
Branch pushed.
> Drop deprecated alias 'full'
>
>
> Key: MPH-133
> URL: https://issues.apache.org/jira/browse/MPH-133
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Parameter has been replaced with {{detail}} ago. Time to remove the alias
> along with its handling.
> [~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-693) Upgrade JUnit from 4.11 to 4.12
[ https://issues.apache.org/jira/browse/MSHARED-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385322#comment-16385322 ] Hudson commented on MSHARED-693: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #8 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/8/ > Upgrade JUnit from 4.11 to 4.12 > --- > > Key: MSHARED-693 > URL: https://issues.apache.org/jira/browse/MSHARED-693 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-artifact-transfer-1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-134) Drop deprecated alias 'mojo'
[
https://issues.apache.org/jira/browse/MPH-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385318#comment-16385318
]
Michael Osipov commented on MPH-134:
Branch pushed.
> Drop deprecated alias 'mojo'
>
>
> Key: MPH-134
> URL: https://issues.apache.org/jira/browse/MPH-134
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Parameter has been replaced with {{goal}} ago. Time to remove the alias along
> with its handling.
> [~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DOXIASITETOOLS-148) Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385317#comment-16385317
]
Sylwester Lachiewicz commented on DOXIASITETOOLS-148:
-
plus 1 year ;)
> Remove SiteRenderingContext#publishDate (undo DOXIASITETOOLS-63)
>
>
> Key: DOXIASITETOOLS-148
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-148
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
>Affects Versions: 1.6
>Reporter: Michael Osipov
>Priority: Major
>
> The field {{publishDate}} has been introduced DOXIATESITETOOLS-63 but cannot
> be set anywhere. Either provide a sane setting option including proper
> documentation or drop it completely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-693) Upgrade JUnit from 4.11 to 4.12
[ https://issues.apache.org/jira/browse/MSHARED-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385314#comment-16385314 ] Hudson commented on MSHARED-693: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-693 #2 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-693/2/ > Upgrade JUnit from 4.11 to 4.12 > --- > > Key: MSHARED-693 > URL: https://issues.apache.org/jira/browse/MSHARED-693 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-artifact-transfer-1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-680) Add null check for DependencyResolver/DependencyCollector/ProjectDeployer Interfaces
[ https://issues.apache.org/jira/browse/MSHARED-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385313#comment-16385313 ] Hudson commented on MSHARED-680: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-693 #2 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-693/2/ > Add null check for DependencyResolver/DependencyCollector/ProjectDeployer > Interfaces > > > Key: MSHARED-680 > URL: https://issues.apache.org/jira/browse/MSHARED-680 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > > * Null Check for DependencyCollector > * Null Check for ProjectDeployer > * Null Check for DependencyResolver -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-680) Add null check for DependencyResolver/DependencyCollector/ProjectDeployer Interfaces
[ https://issues.apache.org/jira/browse/MSHARED-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-680. --- Resolution: Fixed Done in [ad73795401eb7f626503283b5f9ac9c8fc22b030|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=ad73795401eb7f626503283b5f9ac9c8fc22b030] > Add null check for DependencyResolver/DependencyCollector/ProjectDeployer > Interfaces > > > Key: MSHARED-680 > URL: https://issues.apache.org/jira/browse/MSHARED-680 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > > * Null Check for DependencyCollector > * Null Check for ProjectDeployer > * Null Check for DependencyResolver -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DOXIASITETOOLS-179) Report error line and column from Velocity runtime exception
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385308#comment-16385308
]
Michael Osipov commented on DOXIASITETOOLS-179:
---
I do see the error line:
{noformat}
[INFO] Rendering 1 Doxia document: 1 apt
[ERROR] Method charAt threw exception for reference $text in template
C:\Users\mosipov\Downloads\velocity-exception-site\src\site\apt\index.apt.vm at
[20,17]
[ERROR] Error parsing
C:\Users\mosipov\Downloads\velocity-exception-site\src\site\apt\index.apt.vm as
a velocity template, using as text.
[INFO] --
{noformat}
[~slachiewicz], thanks for the example!
> Report error line and column from Velocity runtime exception
>
>
> Key: DOXIASITETOOLS-179
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-179
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Reporter: Jan Krupička
>Priority: Major
> Labels: usability
> Attachments: velocity-exception-site.zip
>
>
> I have a site page {{index.apt.vm}} which is a Velocity template:
> {noformat}
> My best index page
> #set ($text = 'text')
> #set ($text = $text.charAt(-1))
> {noformat}
> When building maven site, this template fails (of course) with a runtime
> exception. Also the maven build fails (good) with the following output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project
> test-project: Error getting a parser for 'My/site/path/index.apt.vm'
> {noformat}
> This output is not much helpful and is a little misleading. Velocity throws
> an exception with parsing error line and column. It would be nice to see this
> in maven error message so it is easy to see where the problem is.
> I can see full stack trace with maven debug build (-X) but I would expect
> this type of error to be reported in normal build.
> Related class and method:
> {{org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)}}
> Velocity method that throws useful exception with error description
> (line/column)
> {{org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)}}
> Velocity exception to catch and use:
> {{org.apache.velocity.exception.ParseErrorException}}
> Full stacktrace from debug output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> org.apache.velocity.exception.MethodInvocationException: Invocation of method
> 'charAt' in class java.lang.String threw exception
> java.lang.StringIndexOutOfBoundsException: String index out of range:
> -1 at d:\projects\test\tmp\test\src\site\apt\index.apt.vm[line 3, column 23]
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:243)
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:187)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
> at
> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
> at org.apache.velocity.Template.merge(Template.java:356)
> at org.apache.velocity.Template.merge(Template.java:260)
> at
> org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
>
[jira] [Closed] (MEAR-209) Change and use a internal unique id instead of artifactId only
[
https://issues.apache.org/jira/browse/MEAR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MEAR-209.
Resolution: Fixed
Done in
[3638d07a0a0132c3f798769e493ba19c776de68c|https://gitbox.apache.org/repos/asf?p=maven-ear-plugin.git;a=commitdiff;h=3638d07a0a0132c3f798769e493ba19c776de68c]
> Change and use a internal unique id instead of artifactId only
> --
>
> Key: MEAR-209
> URL: https://issues.apache.org/jira/browse/MEAR-209
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.0.0
>
>
> EarMojo see line 344:
> {quote}
> // TODO: With the next major release the modules
> // should be identified by a unique id instead of the
> // the artifactId's only which means this
> // check can be removed.
> checkModuleUniqueness();
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MEAR-209) Change and use a internal unique id instead of artifactId only
[
https://issues.apache.org/jira/browse/MEAR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385303#comment-16385303
]
Hudson commented on MEAR-209:
-
Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » master #8
See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/master/8/
> Change and use a internal unique id instead of artifactId only
> --
>
> Key: MEAR-209
> URL: https://issues.apache.org/jira/browse/MEAR-209
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.0.0
>
>
> EarMojo see line 344:
> {quote}
> // TODO: With the next major release the modules
> // should be identified by a unique id instead of the
> // the artifactId's only which means this
> // check can be removed.
> checkModuleUniqueness();
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-680) Add null check for DependencyResolver/DependencyCollector/ProjectDeployer Interfaces
[ https://issues.apache.org/jira/browse/MSHARED-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385304#comment-16385304 ] Hudson commented on MSHARED-680: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #7 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/7/ > Add null check for DependencyResolver/DependencyCollector/ProjectDeployer > Interfaces > > > Key: MSHARED-680 > URL: https://issues.apache.org/jira/browse/MSHARED-680 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-1.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > > * Null Check for DependencyCollector > * Null Check for ProjectDeployer > * Null Check for DependencyResolver -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DOXIASITETOOLS-179) Report error line and column from Velocity runtime exception
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385305#comment-16385305
]
Sylwester Lachiewicz commented on DOXIASITETOOLS-179:
-
Looks like difference in logging between maven-site-plugin versions (IT in
[^velocity-exception-site.zip])
maven-site-plugin *3.4*
{code:java}
[INFO] --- maven-site-plugin:3.4:site (default-site) @ site-tool-test ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.9
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:2.9:index),
file "index.html" already exists for the English version.
[INFO] Rendering 1 Doxia document: 1 apt
[ERROR] Method charAt threw exception for reference $text in template
maven-doxia-sitetools\doxia-integration-tools\src\test\resources\unit\velocity-exception-site\src\site\apt\index.apt.vm
at [20,17]
[ERROR] Error parsing
maven-doxia-sitetools\doxia-integration-tools\src\test\resources\unit\velocity-exception-site\src\site\apt\index.apt.vm
as a velocity template, using as text.
[INFO]
[INFO] BUILD FAILURE
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
site-tool-test: Error getting a parser for
'maven-doxia-sitetools\doxia-integration-tools\src\test\resources\unit\velocity-exception-site\src\site\apt\index.apt.vm'
-> [Help 1]
{code}
maven-site-plugin *3.5*
{code:java}
[INFO] --- maven-site-plugin:3.5:site (default-site) @ site-tool-test ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.9
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.1
skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:2.9:index),
file "index.html" already exists for the English version.
[INFO] Rendering 1 Doxia document: 1 apt
[ERROR] Error parsing
maven-doxia-sitetools\doxia-integration-tools\src\test\resources\unit\velocity-exception-site\src\site\apt\index.apt.vm
as a velocity template, using as text.
[INFO]
[INFO] BUILD FAILURE
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.5:site (default-site) on project
site-tool-test: Error getting a parser for
'maven-doxia-sitetools\doxia-integration-tools\src\test\resources\unit\velocity-exception-site\src\site\apt\index.apt.vm'
-> [Help 1]
{code}
> Report error line and column from Velocity runtime exception
>
>
> Key: DOXIASITETOOLS-179
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-179
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Reporter: Jan Krupička
>Priority: Major
> Labels: usability
> Attachments: velocity-exception-site.zip
>
>
> I have a site page {{index.apt.vm}} which is a Velocity template:
> {noformat}
> My best index page
> #set ($text = 'text')
> #set ($text = $text.charAt(-1))
> {noformat}
> When building maven site, this template fails (of course) with a runtime
> exception. Also the maven build fails (good) with the following output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project
> test-project: Error getting a parser for 'My/site/path/index.apt.vm'
> {noformat}
> This output is not much helpful and is a little misleading. Velocity throws
> an exception with parsing error line and column. It would be nice to see this
> in maven error message so it is easy to see where the problem is.
> I can see full stack trace with maven debug build (-X) but I would expect
> this type of error to be reported in normal build.
> Related class and method:
> {{org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)}}
> Velocity method that throws useful exception with error description
> (line/column)
> {{org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)}}
> Velocity exception to catch and use:
> {{org.apache.velocity.exception.ParseErrorException}}
> Full stacktrace from debug output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> org.apache.velocity.exception.MethodInvocationException: Invocation of method
> 'charAt'
[jira] [Created] (MSHARED-693) Upgrade JUnit from 4.11 to 4.12
Karl Heinz Marbaise created MSHARED-693: --- Summary: Upgrade JUnit from 4.11 to 4.12 Key: MSHARED-693 URL: https://issues.apache.org/jira/browse/MSHARED-693 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-artifact-transfer Affects Versions: maven-artifact-transfer-1.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-artifact-transfer-1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DOXIASITETOOLS-179) Report error line and column from Velocity runtime exception
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated DOXIASITETOOLS-179:
Attachment: velocity-exception-site.zip
> Report error line and column from Velocity runtime exception
>
>
> Key: DOXIASITETOOLS-179
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-179
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Reporter: Jan Krupička
>Priority: Major
> Labels: usability
> Attachments: velocity-exception-site.zip
>
>
> I have a site page {{index.apt.vm}} which is a Velocity template:
> {noformat}
> My best index page
> #set ($text = 'text')
> #set ($text = $text.charAt(-1))
> {noformat}
> When building maven site, this template fails (of course) with a runtime
> exception. Also the maven build fails (good) with the following output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project
> test-project: Error getting a parser for 'My/site/path/index.apt.vm'
> {noformat}
> This output is not much helpful and is a little misleading. Velocity throws
> an exception with parsing error line and column. It would be nice to see this
> in maven error message so it is easy to see where the problem is.
> I can see full stack trace with maven debug build (-X) but I would expect
> this type of error to be reported in normal build.
> Related class and method:
> {{org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)}}
> Velocity method that throws useful exception with error description
> (line/column)
> {{org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)}}
> Velocity exception to catch and use:
> {{org.apache.velocity.exception.ParseErrorException}}
> Full stacktrace from debug output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> org.apache.velocity.exception.MethodInvocationException: Invocation of method
> 'charAt' in class java.lang.String threw exception
> java.lang.StringIndexOutOfBoundsException: String index out of range:
> -1 at d:\projects\test\tmp\test\src\site\apt\index.apt.vm[line 3, column 23]
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:243)
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:187)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
> at
> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
> at org.apache.velocity.Template.merge(Template.java:356)
> at org.apache.velocity.Template.merge(Template.java:260)
> at
> org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
>
[jira] [Commented] (MEAR-209) Change and use a internal unique id instead of artifactId only
[
https://issues.apache.org/jira/browse/MEAR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385298#comment-16385298
]
Hudson commented on MEAR-209:
-
Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » MEAR-209 #2
See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/MEAR-209/2/
> Change and use a internal unique id instead of artifactId only
> --
>
> Key: MEAR-209
> URL: https://issues.apache.org/jira/browse/MEAR-209
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.0.0
>
>
> EarMojo see line 344:
> {quote}
> // TODO: With the next major release the modules
> // should be identified by a unique id instead of the
> // the artifactId's only which means this
> // check can be removed.
> checkModuleUniqueness();
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MEAR-209) Change and use a internal unique id instead of artifactId only
[
https://issues.apache.org/jira/browse/MEAR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MEAR-209:
Assignee: Karl Heinz Marbaise
> Change and use a internal unique id instead of artifactId only
> --
>
> Key: MEAR-209
> URL: https://issues.apache.org/jira/browse/MEAR-209
> Project: Maven Ear Plugin
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.0.0
>
>
> EarMojo see line 344:
> {quote}
> // TODO: With the next major release the modules
> // should be identified by a unique id instead of the
> // the artifactId's only which means this
> // check can be removed.
> checkModuleUniqueness();
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MEAR-249) Maven EAR plugin - two libraries with a same ArtifactId
[ https://issues.apache.org/jira/browse/MEAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MEAR-249. Resolution: Incomplete Assignee: Karl Heinz Marbaise This has been fixed by MEAR-171 > Maven EAR plugin - two libraries with a same ArtifactId > --- > > Key: MEAR-249 > URL: https://issues.apache.org/jira/browse/MEAR-249 > Project: Maven Ear Plugin > Issue Type: Bug >Affects Versions: waiting-for-feedback >Reporter: Tomas Tulka >Assignee: Karl Heinz Marbaise >Priority: Major > > When an EAR module has two (or more) dependencies with a same artifactId, > Maven copy those into the /lib directory and one rewrites the other. In the > end there is only one library in the EAR. > This is not what I would expect, because it is correct to have such > dependencies. The plugin should deal with it or print a warning (it's a > tricky issue when it is about transitive dependencies). > > com.group1 > same-artifact > > > com.group2 > same-artifact > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (DOXIA-555) Footer overrides for FO/PDF outputs
[
https://issues.apache.org/jira/browse/DOXIA-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385285#comment-16385285
]
Hervé Boutemy edited comment on DOXIA-555 at 3/4/18 6:40 PM:
-
I'll take away compatibility questions (which are part of some renaming not
done currently...) and see the proposal:
1. o.a.m.doxia.siterenderer.RenderingContext definitely is part of
doxia-site-renderer, to render a Doxia document as part of a site: I don't see
where to put it in Doxia Core, and see its javadoc
http://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/apidocs/org/apache/maven/doxia/siterenderer/DocumentRenderer.html
2. o.a.m.doxia.docrenderer.DocumentRendererContext API is completely different
(see
http://maven.apache.org/doxia/doxia-sitetools/doxia-doc-renderer/apidocs/org/apache/maven/doxia/docrenderer/DocumentRendererContext.html)
and is about metadata for a "document" pdf that collects multiple Doxia
"documents". Here, we should find a clear term for the "document" equivalent to
a site. And I don't see where to put this API in Doxia Core, neither how it
relates to the first API
and finally, on your third point "pas to parsers ... to use for example to
print warning/errors while parsing", we could probably add new methods like
{{get/setSource}} to Parser
http://maven.apache.org/doxia/doxia/doxia-core/apidocs/org/apache/maven/doxia/parser/Parser.html
and implement it in AbstractParser
http://maven.apache.org/doxia/doxia/doxia-core/apidocs/org/apache/maven/doxia/parser/AbstractParser.html:
I imagine every Parser uses AbstractParser, then the addition in the interface
won't break compatibility
But this is IMHO a good idea to completely decouple from the previous ones =>
I'd propose a separate Jira issue
was (Author: hboutemy):
I'll take away compatibility questions (which are part of some renaming not
done currently...) and see the proposal:
1. o.a.m.doxia.siterenderer.RenderingContext definitely is part of
doxia-site-renderer, to render a Doxia document as part of a site: I don't see
where to put it in Doxia Core, and see its javadoc
http://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/apidocs/org/apache/maven/doxia/siterenderer/DocumentRenderer.html
2. o.a.m.doxia.docrenderer.DocumentRendererContext API is completely different
(see
http://maven.apache.org/doxia/doxia-sitetools/doxia-doc-renderer/apidocs/org/apache/maven/doxia/docrenderer/DocumentRendererContext.html)
and is about metadata for a "document" pdf that collects multiple Doxia
"documents". Here, we should find a clear term for the "document" equivalent to
a site. And I don't see where to put this API in Doxia Core, neither how it
relates to the first API
and finally, on your third point "pas to parsers ... to use for example to
print warning/errors while parsing", we could probably add a new method to
Parser
http://maven.apache.org/doxia/doxia/doxia-core/apidocs/org/apache/maven/doxia/parser/Parser.html
and implement it in AbstractParser
http://maven.apache.org/doxia/doxia/doxia-core/apidocs/org/apache/maven/doxia/parser/AbstractParser.html:
I imagine every Parser uses AbstractParser, then the addition in the interface
won't break compatibility
But this is IMHO a good idea to completely decouple from the previous ones =>
I'd propose a separate Jira issue
> Footer overrides for FO/PDF outputs
> ---
>
> Key: DOXIA-555
> URL: https://issues.apache.org/jira/browse/DOXIA-555
> Project: Maven Doxia
> Issue Type: New Feature
> Components: Module - FO
>Reporter: Alex O'Ree
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 2.0
>
> Attachments: DOXIA-555.patch
>
>
> Related https://issues.apache.org/jira/browse/MPDF-81
> I have a use case where I cannot have the copyright symbol on the bottom of
> generated PDF documents. Currently, it looks like the footer is hard coded
> and cannot be customized.
> http://svn.apache.org/viewvc/maven/doxia/doxia/tags/doxia-1.7/doxia-modules/doxia-module-fo/src/main/java/org/apache/maven/doxia/module/fo/FoAggregateSink.java?view=markup#l762
> ideally, this should be configurable either properties or better yet, the pdf
> descriptor document (maven-pdf-plugin). This would require a change in the
> schema used for the pdf descriptor
> http://maven.apache.org/xsd/document-1.0.1.xsd
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DOXIA-555) Footer overrides for FO/PDF outputs
[ https://issues.apache.org/jira/browse/DOXIA-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385285#comment-16385285 ] Hervé Boutemy commented on DOXIA-555: - I'll take away compatibility questions (which are part of some renaming not done currently...) and see the proposal: 1. o.a.m.doxia.siterenderer.RenderingContext definitely is part of doxia-site-renderer, to render a Doxia document as part of a site: I don't see where to put it in Doxia Core, and see its javadoc http://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/apidocs/org/apache/maven/doxia/siterenderer/DocumentRenderer.html 2. o.a.m.doxia.docrenderer.DocumentRendererContext API is completely different (see http://maven.apache.org/doxia/doxia-sitetools/doxia-doc-renderer/apidocs/org/apache/maven/doxia/docrenderer/DocumentRendererContext.html) and is about metadata for a "document" pdf that collects multiple Doxia "documents". Here, we should find a clear term for the "document" equivalent to a site. And I don't see where to put this API in Doxia Core, neither how it relates to the first API and finally, on your third point "pas to parsers ... to use for example to print warning/errors while parsing", we could probably add a new method to Parser http://maven.apache.org/doxia/doxia/doxia-core/apidocs/org/apache/maven/doxia/parser/Parser.html and implement it in AbstractParser http://maven.apache.org/doxia/doxia/doxia-core/apidocs/org/apache/maven/doxia/parser/AbstractParser.html: I imagine every Parser uses AbstractParser, then the addition in the interface won't break compatibility But this is IMHO a good idea to completely decouple from the previous ones => I'd propose a separate Jira issue > Footer overrides for FO/PDF outputs > --- > > Key: DOXIA-555 > URL: https://issues.apache.org/jira/browse/DOXIA-555 > Project: Maven Doxia > Issue Type: New Feature > Components: Module - FO >Reporter: Alex O'Ree >Assignee: Hervé Boutemy >Priority: Major > Fix For: 2.0 > > Attachments: DOXIA-555.patch > > > Related https://issues.apache.org/jira/browse/MPDF-81 > I have a use case where I cannot have the copyright symbol on the bottom of > generated PDF documents. Currently, it looks like the footer is hard coded > and cannot be customized. > http://svn.apache.org/viewvc/maven/doxia/doxia/tags/doxia-1.7/doxia-modules/doxia-module-fo/src/main/java/org/apache/maven/doxia/module/fo/FoAggregateSink.java?view=markup#l762 > ideally, this should be configurable either properties or better yet, the pdf > descriptor document (maven-pdf-plugin). This would require a change in the > schema used for the pdf descriptor > http://maven.apache.org/xsd/document-1.0.1.xsd -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DOXIA-568) Doxia Markdown extension > Support for some MarkDown extensions has been removed since 1.7
[ https://issues.apache.org/jira/browse/DOXIA-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385274#comment-16385274 ] Hervé Boutemy commented on DOXIA-568: - what do you expect from newer version? is there some change interesting to this issue? > Doxia Markdown extension > Support for some MarkDown extensions has been > removed since 1.7 > -- > > Key: DOXIA-568 > URL: https://issues.apache.org/jira/browse/DOXIA-568 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Markdown >Affects Versions: 1.8 >Reporter: Matthieu Ghilain >Priority: Major > > Currently the markdown extensions which are allowed by the Doxia parser seems > to be fixed to a subset of what was allowed with Doxia 1.7 and old PegDown > library. > I would like to be able to use the anchor link extension which was available > with 1.7 as well as the syntax highlighting that was also available for > scripts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-692) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MSHARED-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-692. --- Resolution: Fixed Done in [0e25582894aa832a295fbc800e74ec00337a25d0|https://gitbox.apache.org/repos/asf?p=maven-shared-io.git;a=commitdiff;h=0e25582894aa832a295fbc800e74ec00337a25d0] > Upgrade parent to 31 > > > Key: MSHARED-692 > URL: https://issues.apache.org/jira/browse/MSHARED-692 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-shared-io >Affects Versions: maven-shared-io-3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-shared-io-3.0.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-692) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MSHARED-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385237#comment-16385237 ] Hudson commented on MSHARED-692: Build succeeded in Jenkins: Maven TLP » maven-shared-io » master #2 See https://builds.apache.org/job/maven-box/job/maven-shared-io/job/master/2/ > Upgrade parent to 31 > > > Key: MSHARED-692 > URL: https://issues.apache.org/jira/browse/MSHARED-692 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-shared-io >Affects Versions: maven-shared-io-3.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-shared-io-3.0.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DOXIA-555) Footer overrides for FO/PDF outputs
[ https://issues.apache.org/jira/browse/DOXIA-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385231#comment-16385231 ] Sylwester Lachiewicz commented on DOXIA-555: We have: doxia-doc-renderer - org.apache.maven.doxia.docrenderer.DocumentRendererContext doxia-site-renderer - org.apache.maven.doxia.siterenderer.RenderingContext (with TODO rename to DocumentRenderingContext) from this 2 RenderingContext looks better candidate to move to doxia-core and pass to parsers. It would be also possible for other plugins/parsers to setup source filename or any other attributes to use for example to print warning/errors while parsing. > Footer overrides for FO/PDF outputs > --- > > Key: DOXIA-555 > URL: https://issues.apache.org/jira/browse/DOXIA-555 > Project: Maven Doxia > Issue Type: New Feature > Components: Module - FO >Reporter: Alex O'Ree >Assignee: Hervé Boutemy >Priority: Major > Fix For: 2.0 > > Attachments: DOXIA-555.patch > > > Related https://issues.apache.org/jira/browse/MPDF-81 > I have a use case where I cannot have the copyright symbol on the bottom of > generated PDF documents. Currently, it looks like the footer is hard coded > and cannot be customized. > http://svn.apache.org/viewvc/maven/doxia/doxia/tags/doxia-1.7/doxia-modules/doxia-module-fo/src/main/java/org/apache/maven/doxia/module/fo/FoAggregateSink.java?view=markup#l762 > ideally, this should be configurable either properties or better yet, the pdf > descriptor document (maven-pdf-plugin). This would require a change in the > schema used for the pdf descriptor > http://maven.apache.org/xsd/document-1.0.1.xsd -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-257) Upgrade JUnit to 4.12
[ https://issues.apache.org/jira/browse/MEAR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385230#comment-16385230 ] Hudson commented on MEAR-257: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » CODE-IMPROVEMENTS #2 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/CODE-IMPROVEMENTS/2/ > Upgrade JUnit to 4.12 > - > > Key: MEAR-257 > URL: https://issues.apache.org/jira/browse/MEAR-257 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-254) Support JavaEE version 8
[
https://issues.apache.org/jira/browse/MEAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385229#comment-16385229
]
Hudson commented on MEAR-254:
-
Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » CODE-IMPROVEMENTS #2
See
https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/CODE-IMPROVEMENTS/2/
> Support JavaEE version 8
>
>
> Key: MEAR-254
> URL: https://issues.apache.org/jira/browse/MEAR-254
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.10.1
>Reporter: Fred Bricon
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.0
>
>
> Java EE 8 EARs can not be built using the latest ear plugin, eg.
> {quote}
>
> maven-ear-plugin
> 2.10.1
>
> true
> 8
> lib
>
>
> {quote}
> yields :
> ??Failed to execute goal
> org.apache.maven.plugins:maven-ear-plugin:2.10.1:generate-application-xml
> (default-generate-application-xml) on project gsdf: Invalid version [8]??
> See
> http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html#8
> for the latest Java EE schema updates
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MSHARED-692) Upgrade parent to 31
Karl Heinz Marbaise created MSHARED-692: --- Summary: Upgrade parent to 31 Key: MSHARED-692 URL: https://issues.apache.org/jira/browse/MSHARED-692 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-shared-io Affects Versions: maven-shared-io-3.0.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-shared-io-3.0.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MEAR-257) Upgrade JUnit to 4.12
[ https://issues.apache.org/jira/browse/MEAR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MEAR-257. Resolution: Fixed Done in [a593c591a49f44be288dbea44b8f8950d9b45b0b|https://gitbox.apache.org/repos/asf?p=maven-ear-plugin.git;a=commitdiff;h=a593c591a49f44be288dbea44b8f8950d9b45b0b] > Upgrade JUnit to 4.12 > - > > Key: MEAR-257 > URL: https://issues.apache.org/jira/browse/MEAR-257 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MEAR-257) Upgrade JUnit to 4.12
[ https://issues.apache.org/jira/browse/MEAR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385217#comment-16385217 ] Hudson commented on MEAR-257: - Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » master #6 See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/master/6/ > Upgrade JUnit to 4.12 > - > > Key: MEAR-257 > URL: https://issues.apache.org/jira/browse/MEAR-257 > Project: Maven Ear Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-675) RAT check - Unknown license for MOVED_TO_GIT file
[
https://issues.apache.org/jira/browse/MSHARED-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MSHARED-675.
--
Resolution: Invalid
Assignee: Robert Scholte
> RAT check - Unknown license for MOVED_TO_GIT file
> -
>
> Key: MSHARED-675
> URL: https://issues.apache.org/jira/browse/MSHARED-675
> Project: Maven Shared Components
> Issue Type: Bug
>Reporter: Sylwester Lachiewicz
>Assignee: Robert Scholte
>Priority: Minor
>
> While moving from svn to git new file "MOVED_TO_GIT" was introduced but RAT
> plugin complains about unaproved license in this file
> {noformat}
> Found in checkstyle-plugin repository
> *
> Summary
> ---
> Generated at: 2018-01-12T00:26:21+01:00
> Notes: 8
> Binaries: 1
> Archives: 0
> Standards: 260
> Apache Licensed: 259
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 1 Unknown Licenses
> ***
> Unapproved licenses:
> MOVED_TO_GIT
> ***
> Archives:
> *
> Files with Apache License headers will be marked AL
> Binary files (which do not require AL headers) will be marked B
> Compressed archives will be marked A
> Notices, licenses etc will be marked N
> !? MOVED_TO_GIT
> ALpom.xml
> ALsrc/it/check-fail/invoker.properties
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MEAR-257) Upgrade JUnit to 4.12
Karl Heinz Marbaise created MEAR-257: Summary: Upgrade JUnit to 4.12 Key: MEAR-257 URL: https://issues.apache.org/jira/browse/MEAR-257 Project: Maven Ear Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-675) RAT check - Unknown license for MOVED_TO_GIT file
[
https://issues.apache.org/jira/browse/MSHARED-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385189#comment-16385189
]
Sylwester Lachiewicz commented on MSHARED-675:
--
Yes, you right - only svn, git repos has no issue with that.
Please close my issue.
> RAT check - Unknown license for MOVED_TO_GIT file
> -
>
> Key: MSHARED-675
> URL: https://issues.apache.org/jira/browse/MSHARED-675
> Project: Maven Shared Components
> Issue Type: Bug
>Reporter: Sylwester Lachiewicz
>Priority: Minor
>
> While moving from svn to git new file "MOVED_TO_GIT" was introduced but RAT
> plugin complains about unaproved license in this file
> {noformat}
> Found in checkstyle-plugin repository
> *
> Summary
> ---
> Generated at: 2018-01-12T00:26:21+01:00
> Notes: 8
> Binaries: 1
> Archives: 0
> Standards: 260
> Apache Licensed: 259
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 1 Unknown Licenses
> ***
> Unapproved licenses:
> MOVED_TO_GIT
> ***
> Archives:
> *
> Files with Apache License headers will be marked AL
> Binary files (which do not require AL headers) will be marked B
> Compressed archives will be marked A
> Notices, licenses etc will be marked N
> !? MOVED_TO_GIT
> ALpom.xml
> ALsrc/it/check-fail/invoker.properties
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1490) Change header of the Failsafe Report
[ https://issues.apache.org/jira/browse/SUREFIRE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385178#comment-16385178 ] Michael Osipov commented on SUREFIRE-1490: -- [~fedyafed], correctly analyzed. > Change header of the Failsafe Report > > > Key: SUREFIRE-1490 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1490 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Report Plugin >Affects Versions: 2.20.1 >Reporter: Ivan Fedotov >Assignee: Tibor Digana >Priority: Minor > > Hi! > I noted that the Failsafe Report's header is "Surefire Report", which is > quite confusing. > Can you fix this? > Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (SUREFIRE-1490) Change header of the Failsafe Report
[
https://issues.apache.org/jira/browse/SUREFIRE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385175#comment-16385175
]
Ivan Fedotov edited comment on SUREFIRE-1490 at 3/4/18 3:04 PM:
[~tibor17], customized title can override this, but I meant default values, as
[~michael-o] said.
By default, {{FailsafeReportMojo.getName}} uses {{"report.failsafe.name"}} from
bundle.
But by default {{SurefireReportGenerator.doGenerateReport}} uses
{{"report.surefire.header"}} no matter what report is executed.
May be {{FailsafeReportMojo.getTitle}} should return something like
{{"report.failsafe.header"}} from bundle by default?
was (Author: fedyafed):
[~tibor17], customized title can override this, but I meant default values, as
[~michael-o] said.
By default, FailsafeReportMojo.getName uses "report.failsafe.name" from bundle.
But by default SurefireReportGenerator.doGenerateReport uses
"report.surefire.header" no matter what report is executed.
May be FailsafeReportMojo.getTitle should return something like
"report.failsafe.header" from bundle by default?
> Change header of the Failsafe Report
>
>
> Key: SUREFIRE-1490
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1490
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Report Plugin
>Affects Versions: 2.20.1
>Reporter: Ivan Fedotov
>Assignee: Tibor Digana
>Priority: Minor
>
> Hi!
> I noted that the Failsafe Report's header is "Surefire Report", which is
> quite confusing.
> Can you fix this?
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1490) Change header of the Failsafe Report
[ https://issues.apache.org/jira/browse/SUREFIRE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385175#comment-16385175 ] Ivan Fedotov commented on SUREFIRE-1490: [~tibor17], customized title can override this, but I meant default values, as [~michael-o] said. By default, FailsafeReportMojo.getName uses "report.failsafe.name" from bundle. But by default SurefireReportGenerator.doGenerateReport uses "report.surefire.header" no matter what report is executed. May be FailsafeReportMojo.getTitle should return something like "report.failsafe.header" from bundle by default? > Change header of the Failsafe Report > > > Key: SUREFIRE-1490 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1490 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Report Plugin >Affects Versions: 2.20.1 >Reporter: Ivan Fedotov >Assignee: Tibor Digana >Priority: Minor > > Hi! > I noted that the Failsafe Report's header is "Surefire Report", which is > quite confusing. > Can you fix this? > Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DOXIA-568) Doxia Markdown extension > Support for some MarkDown extensions has been removed since 1.7
[ https://issues.apache.org/jira/browse/DOXIA-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385165#comment-16385165 ] Sylwester Lachiewicz commented on DOXIA-568: So we need to update flexmark-java to latest 0.32.4? > Doxia Markdown extension > Support for some MarkDown extensions has been > removed since 1.7 > -- > > Key: DOXIA-568 > URL: https://issues.apache.org/jira/browse/DOXIA-568 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Markdown >Affects Versions: 1.8 >Reporter: Matthieu Ghilain >Priority: Major > > Currently the markdown extensions which are allowed by the Doxia parser seems > to be fixed to a subset of what was allowed with Doxia 1.7 and old PegDown > library. > I would like to be able to use the anchor link extension which was available > with 1.7 as well as the syntax highlighting that was also available for > scripts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-134) Drop deprecated alias 'mojo'
[
https://issues.apache.org/jira/browse/MPH-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385164#comment-16385164
]
Karl Heinz Marbaise commented on MPH-134:
-
+1 clean it up...
> Drop deprecated alias 'mojo'
>
>
> Key: MPH-134
> URL: https://issues.apache.org/jira/browse/MPH-134
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Parameter has been replaced with {{goal}} ago. Time to remove the alias along
> with its handling.
> [~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MJLINK-12) There is not have parameter "compression" for jlink
[ https://issues.apache.org/jira/browse/MJLINK-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJLINK-12. - Resolution: Implemented Assignee: Karl Heinz Marbaise First thanks for your feedback but it would be great if you could make text copies instead of images apart from that this issue is already fixed in the current master (not yet released)...see MJLINK-5. > There is not have parameter "compression" for jlink > --- > > Key: MJLINK-12 > URL: https://issues.apache.org/jira/browse/MJLINK-12 > Project: Maven JLink Plugin > Issue Type: Bug >Affects Versions: 3.0.0-alpha-1 > Environment: Window 10 64bit > JDK 9.0.4 > Maven 3.5.2 >Reporter: Jarrod Quan >Assignee: Karl Heinz Marbaise >Priority: Major > Attachments: image-2018-03-04-22-09-44-046.png, > image-2018-03-04-22-10-57-127.png, image-2018-03-04-22-18-47-681.png, > image-2018-03-04-22-18-52-215.png, image-2018-03-04-22-21-07-848.png, > image-2018-03-04-22-22-32-856.png > > > !image-2018-03-04-22-10-57-127.png!!image-2018-03-04-22-18-52-215.png!!image-2018-03-04-22-21-07-848.png!!image-2018-03-04-22-09-44-046.png!!image-2018-03-04-22-22-32-856.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPH-134) Drop deprecated alias 'mojo'
Michael Osipov created MPH-134:
--
Summary: Drop deprecated alias 'mojo'
Key: MPH-134
URL: https://issues.apache.org/jira/browse/MPH-134
Project: Maven Help Plugin
Issue Type: Task
Components: describe
Affects Versions: 2.2
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.0.0
Parameter has been replaced with {{goal}} ago. Time to remove the alias along
with its handling.
[~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPH-132) Drop parameter 'medium'
[
https://issues.apache.org/jira/browse/MPH-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385161#comment-16385161
]
Hudson commented on MPH-132:
Build succeeded in Jenkins: Maven TLP » maven-help-plugin » MPH-132 #2
See https://builds.apache.org/job/maven-box/job/maven-help-plugin/job/MPH-132/2/
> Drop parameter 'medium'
> ---
>
> Key: MPH-132
> URL: https://issues.apache.org/jira/browse/MPH-132
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Based on MPH-31, this parameter adds no real value given that we have
> {{minimal}} and {{detail}}. Drop it to reduce complexity.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MJLINK-12) There is not have parameter "compression" for jlink
Jarrod Quan created MJLINK-12: - Summary: There is not have parameter "compression" for jlink Key: MJLINK-12 URL: https://issues.apache.org/jira/browse/MJLINK-12 Project: Maven JLink Plugin Issue Type: Bug Affects Versions: 3.0.0-alpha-1 Environment: Window 10 64bit JDK 9.0.4 Maven 3.5.2 Reporter: Jarrod Quan Attachments: image-2018-03-04-22-09-44-046.png, image-2018-03-04-22-10-57-127.png, image-2018-03-04-22-18-47-681.png, image-2018-03-04-22-18-52-215.png, image-2018-03-04-22-21-07-848.png, image-2018-03-04-22-22-32-856.png !image-2018-03-04-22-10-57-127.png!!image-2018-03-04-22-18-52-215.png!!image-2018-03-04-22-21-07-848.png!!image-2018-03-04-22-09-44-046.png!!image-2018-03-04-22-22-32-856.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPH-133) Drop deprecated alias 'full'
[
https://issues.apache.org/jira/browse/MPH-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPH-133:
---
Summary: Drop deprecated alias 'full' (was: Drop deprecated alias full)
> Drop deprecated alias 'full'
>
>
> Key: MPH-133
> URL: https://issues.apache.org/jira/browse/MPH-133
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Parameter has been replaced with {{detail}} ago. Time to remove the alias
> along with its handling.
> [~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPH-132) Drop parameter 'medium'
[
https://issues.apache.org/jira/browse/MPH-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPH-132:
---
Summary: Drop parameter 'medium' (was: Drop parameter medium)
> Drop parameter 'medium'
> ---
>
> Key: MPH-132
> URL: https://issues.apache.org/jira/browse/MPH-132
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Based on MPH-31, this parameter adds no real value given that we have
> {{minimal}} and {{detail}}. Drop it to reduce complexity.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-689) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MSHARED-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385154#comment-16385154 ] Hudson commented on MSHARED-689: Build failed in Jenkins: Maven TLP » maven-verifier » CODE_IMPROVEMENTS #2 See https://builds.apache.org/job/maven-box/job/maven-verifier/job/CODE_IMPROVEMENTS/2/ > Upgrade parent to 31 > > > Key: MSHARED-689 > URL: https://issues.apache.org/jira/browse/MSHARED-689 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-verifier >Affects Versions: maven-verifier-1.7 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-verifier-1.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-133) Drop deprecated alias full
[
https://issues.apache.org/jira/browse/MPH-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385152#comment-16385152
]
Karl Heinz Marbaise commented on MPH-133:
-
+1 for that. As already mentioned if someone really needs this we might
consider to re add it.
> Drop deprecated alias full
> --
>
> Key: MPH-133
> URL: https://issues.apache.org/jira/browse/MPH-133
> Project: Maven Help Plugin
> Issue Type: Task
> Components: describe
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> Parameter has been replaced with {{detail}} ago. Time to remove the alias
> along with its handling.
> [~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MEAR-254) Support JavaEE version 8
[
https://issues.apache.org/jira/browse/MEAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MEAR-254.
Resolution: Fixed
Done in
[962528d731773fd3fa83d2e0f739e0b49356e72c|https://gitbox.apache.org/repos/asf?p=maven-ear-plugin.git;a=commitdiff;h=962528d731773fd3fa83d2e0f739e0b49356e72c]
> Support JavaEE version 8
>
>
> Key: MEAR-254
> URL: https://issues.apache.org/jira/browse/MEAR-254
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.10.1
>Reporter: Fred Bricon
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.0
>
>
> Java EE 8 EARs can not be built using the latest ear plugin, eg.
> {quote}
>
> maven-ear-plugin
> 2.10.1
>
> true
> 8
> lib
>
>
> {quote}
> yields :
> ??Failed to execute goal
> org.apache.maven.plugins:maven-ear-plugin:2.10.1:generate-application-xml
> (default-generate-application-xml) on project gsdf: Invalid version [8]??
> See
> http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html#8
> for the latest Java EE schema updates
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MPH-133) Drop deprecated alias full
Michael Osipov created MPH-133:
--
Summary: Drop deprecated alias full
Key: MPH-133
URL: https://issues.apache.org/jira/browse/MPH-133
Project: Maven Help Plugin
Issue Type: Task
Components: describe
Affects Versions: 2.2
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.0.0
Parameter has been replaced with {{detail}} ago. Time to remove the alias along
with its handling.
[~khmarbaise], [~gboue], any objections?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPH-31) medium mode should include plugin descriptions
[ https://issues.apache.org/jira/browse/MPH-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPH-31. - Resolution: Won't Fix Fix Version/s: (was: Backlog) No one did ever take action and since the parameter has no real effect, it will be dropped in 3.0.0. > medium mode should include plugin descriptions > -- > > Key: MPH-31 > URL: https://issues.apache.org/jira/browse/MPH-31 > Project: Maven Help Plugin > Issue Type: Bug > Components: describe >Reporter: Dan Fabulich >Priority: Major > > Run "mvn help:describe -Dplugin=compiler -Dmojo=compile". You'll get this: > [INFO] Mojo: 'compiler:compile' > === > Goal: 'compile' > Description: > Compiles application sources > === > Try again with "mvn help:describe -Dplugin=compiler -Dmojo=compile -Dmedium". > You'll get the exact same information. Try again with "-Dfull". You'll get > a highly verbose description of every parameter, including their type, > required, readonly, and description. > -Dmedium should include an "in-between" amount of information. I might > suggest that it include all parameters by name and the description, but not > type/required/readonly. (Perhaps omit readonly parameters from -Dmedium > view?) We might also consider using only the first sentence of the > description, just like Javadoc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPH-90) help:effective-pom does not show project properties injected into plugin parameters
[
https://issues.apache.org/jira/browse/MPH-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPH-90.
-
Resolution: Feedback Received
Closing this. Obviously, I have wrong expectations. This goal outputs what has
been set explicitly.
> help:effective-pom does not show project properties injected into plugin
> parameters
> ---
>
> Key: MPH-90
> URL: https://issues.apache.org/jira/browse/MPH-90
> Project: Maven Help Plugin
> Issue Type: New Feature
> Components: effective-pom
>Affects Versions: 2.1.1
> Environment: Maven 2.2.1 and Maven 3.0.3
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Minor
> Attachments: compiler-debug.png, effective-pom.log, pom.xml,
> target-option.png
>
>
> When I define something like this in my POM:
> {code:xml}
>
> 1.6
> 1.6
>
> {code}
> the compiler plugin picks this up but this settings is not reflected in the
> {{Model}} and not written out as part of the effective POM.
> Either this is fixed within the system or the docs of this plugin need to
> mention this clearly.
> This is related to MJAVADOC-310 and MPIR-263.
> I a workaround for now by passing those properties to the plugin but this
> does not solve this problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MEAR-254) Support JavaEE version 8
[
https://issues.apache.org/jira/browse/MEAR-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385135#comment-16385135
]
Hudson commented on MEAR-254:
-
Build succeeded in Jenkins: Maven TLP » maven-ear-plugin » master #5
See https://builds.apache.org/job/maven-box/job/maven-ear-plugin/job/master/5/
> Support JavaEE version 8
>
>
> Key: MEAR-254
> URL: https://issues.apache.org/jira/browse/MEAR-254
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.10.1
>Reporter: Fred Bricon
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.0
>
>
> Java EE 8 EARs can not be built using the latest ear plugin, eg.
> {quote}
>
> maven-ear-plugin
> 2.10.1
>
> true
> 8
> lib
>
>
> {quote}
> yields :
> ??Failed to execute goal
> org.apache.maven.plugins:maven-ear-plugin:2.10.1:generate-application-xml
> (default-generate-application-xml) on project gsdf: Invalid version [8]??
> See
> http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html#8
> for the latest Java EE schema updates
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1490) Change header of the Failsafe Report
[
https://issues.apache.org/jira/browse/SUREFIRE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385130#comment-16385130
]
Michael Osipov commented on SUREFIRE-1490:
--
[~tibor17], are you sure that this is the case? The {{SurefireReportGenerator}}
is used by {{AbstractSurefireReportMojo}} which is ther super class of the
Failsafe Report. I think this is really an issue, it is not about
customization, but simply wrong default values.
> Change header of the Failsafe Report
>
>
> Key: SUREFIRE-1490
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1490
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Report Plugin
>Affects Versions: 2.20.1
>Reporter: Ivan Fedotov
>Assignee: Tibor Digana
>Priority: Minor
>
> Hi!
> I noted that the Failsafe Report's header is "Surefire Report", which is
> quite confusing.
> Can you fix this?
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MSHARED-676) Providing https links to verify dist KEYS
[
https://issues.apache.org/jira/browse/MSHARED-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHARED-676.
---
Resolution: Fixed
Done in
[d4dfd1368a651b092d21cfc84da947e25fda579e|https://gitbox.apache.org/repos/asf?p=maven-dependency-tree.git;a=commitdiff;h=d4dfd1368a651b092d21cfc84da947e25fda579e]
> Providing https links to verify dist KEYS
> -
>
> Key: MSHARED-676
> URL: https://issues.apache.org/jira/browse/MSHARED-676
> Project: Maven Shared Components
> Issue Type: Bug
>Reporter: Sylwester Lachiewicz
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Links in download.html page for each component should point to https:// site
> ie. [https://maven.apache.org/shared/maven-dependency-tree/download.cgi]
> has links to
> [http://www.apache.org/dist/maven/KEYS|http://www.apache.org/dev/release-signing#verifying-signature]
> [http://www.apache.org/dev/release-signing#verifying-signature]
> [http://www.apache.org/dist/maven/shared/maven-dependency-tree-3.0.1-source-release.zip.md5]
>
> Search in sources for:
> {noformat}
> href="http://{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-676) Providing https links to verify dist KEYS
[
https://issues.apache.org/jira/browse/MSHARED-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385126#comment-16385126
]
Hudson commented on MSHARED-676:
Build succeeded in Jenkins: Maven TLP » maven-dependency-tree » master #4
See
https://builds.apache.org/job/maven-box/job/maven-dependency-tree/job/master/4/
> Providing https links to verify dist KEYS
> -
>
> Key: MSHARED-676
> URL: https://issues.apache.org/jira/browse/MSHARED-676
> Project: Maven Shared Components
> Issue Type: Bug
>Reporter: Sylwester Lachiewicz
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Links in download.html page for each component should point to https:// site
> ie. [https://maven.apache.org/shared/maven-dependency-tree/download.cgi]
> has links to
> [http://www.apache.org/dist/maven/KEYS|http://www.apache.org/dev/release-signing#verifying-signature]
> [http://www.apache.org/dev/release-signing#verifying-signature]
> [http://www.apache.org/dist/maven/shared/maven-dependency-tree-3.0.1-source-release.zip.md5]
>
> Search in sources for:
> {noformat}
> href="http://{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-676) Providing https links to verify dist KEYS
[
https://issues.apache.org/jira/browse/MSHARED-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385125#comment-16385125
]
Hudson commented on MSHARED-676:
Build succeeded in Jenkins: Maven TLP » maven-dependency-tree » MSHARED-676 #2
See
https://builds.apache.org/job/maven-box/job/maven-dependency-tree/job/MSHARED-676/2/
> Providing https links to verify dist KEYS
> -
>
> Key: MSHARED-676
> URL: https://issues.apache.org/jira/browse/MSHARED-676
> Project: Maven Shared Components
> Issue Type: Bug
>Reporter: Sylwester Lachiewicz
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Links in download.html page for each component should point to https:// site
> ie. [https://maven.apache.org/shared/maven-dependency-tree/download.cgi]
> has links to
> [http://www.apache.org/dist/maven/KEYS|http://www.apache.org/dev/release-signing#verifying-signature]
> [http://www.apache.org/dev/release-signing#verifying-signature]
> [http://www.apache.org/dist/maven/shared/maven-dependency-tree-3.0.1-source-release.zip.md5]
>
> Search in sources for:
> {noformat}
> href="http://{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-691) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MSHARED-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385124#comment-16385124 ] Hudson commented on MSHARED-691: Build succeeded in Jenkins: Maven TLP » maven-dependency-tree » MSHARED-676 #2 See https://builds.apache.org/job/maven-box/job/maven-dependency-tree/job/MSHARED-676/2/ > Upgrade parent to 31 > > > Key: MSHARED-691 > URL: https://issues.apache.org/jira/browse/MSHARED-691 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-tree >Affects Versions: maven-dependency-tree-3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-dependency-tree-3.0.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-691) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MSHARED-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-691. --- Resolution: Fixed Done in [967c3ac168095f60c7434c700b5d550b2a749cac|https://gitbox.apache.org/repos/asf?p=maven-dependency-tree.git;a=commitdiff;h=967c3ac168095f60c7434c700b5d550b2a749cac] > Upgrade parent to 31 > > > Key: MSHARED-691 > URL: https://issues.apache.org/jira/browse/MSHARED-691 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-tree >Affects Versions: maven-dependency-tree-3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-dependency-tree-3.0.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-691) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MSHARED-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385122#comment-16385122 ] Hudson commented on MSHARED-691: Build succeeded in Jenkins: Maven TLP » maven-dependency-tree » master #3 See https://builds.apache.org/job/maven-box/job/maven-dependency-tree/job/master/3/ > Upgrade parent to 31 > > > Key: MSHARED-691 > URL: https://issues.apache.org/jira/browse/MSHARED-691 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-dependency-tree >Affects Versions: maven-dependency-tree-3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-dependency-tree-3.0.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-691) Upgrade parent to 31
Karl Heinz Marbaise created MSHARED-691: --- Summary: Upgrade parent to 31 Key: MSHARED-691 URL: https://issues.apache.org/jira/browse/MSHARED-691 Project: Maven Shared Components Issue Type: Improvement Components: maven-dependency-tree Affects Versions: maven-dependency-tree-3.0.2 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-dependency-tree-3.0.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MSHARED-676) Providing https links to verify dist KEYS
[
https://issues.apache.org/jira/browse/MSHARED-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MSHARED-676:
---
Assignee: Karl Heinz Marbaise
> Providing https links to verify dist KEYS
> -
>
> Key: MSHARED-676
> URL: https://issues.apache.org/jira/browse/MSHARED-676
> Project: Maven Shared Components
> Issue Type: Bug
>Reporter: Sylwester Lachiewicz
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Links in download.html page for each component should point to https:// site
> ie. [https://maven.apache.org/shared/maven-dependency-tree/download.cgi]
> has links to
> [http://www.apache.org/dist/maven/KEYS|http://www.apache.org/dev/release-signing#verifying-signature]
> [http://www.apache.org/dev/release-signing#verifying-signature]
> [http://www.apache.org/dist/maven/shared/maven-dependency-tree-3.0.1-source-release.zip.md5]
>
> Search in sources for:
> {noformat}
> href="http://{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MSHARED-689) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MSHARED-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-689. --- Resolution: Fixed Done in [ef65dc192f4a011216f060e7bd576d79b220618b|https://gitbox.apache.org/repos/asf?p=maven-verifier.git;a=commitdiff;h=ef65dc192f4a011216f060e7bd576d79b220618b] > Upgrade parent to 31 > > > Key: MSHARED-689 > URL: https://issues.apache.org/jira/browse/MSHARED-689 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-verifier >Affects Versions: maven-verifier-1.7 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-verifier-1.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-689) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MSHARED-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385108#comment-16385108 ] Hudson commented on MSHARED-689: Build succeeded in Jenkins: Maven TLP » maven-verifier » master #2 See https://builds.apache.org/job/maven-box/job/maven-verifier/job/master/2/ > Upgrade parent to 31 > > > Key: MSHARED-689 > URL: https://issues.apache.org/jira/browse/MSHARED-689 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-verifier >Affects Versions: maven-verifier-1.7 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-verifier-1.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1490) Change header of the Failsafe Report
[
https://issues.apache.org/jira/browse/SUREFIRE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385106#comment-16385106
]
Tibor Digana commented on SUREFIRE-1490:
[~fedyafed]
The surefire tests have Surefire Report. The failsafe have opposite. I did not
see one for both in my practice. The ttile can be customized in version
{{2.21.0}}. I supposed you wanted customization and mark this issue as an
duplicate.
> Change header of the Failsafe Report
>
>
> Key: SUREFIRE-1490
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1490
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Report Plugin
>Affects Versions: 2.20.1
>Reporter: Ivan Fedotov
>Assignee: Tibor Digana
>Priority: Minor
>
> Hi!
> I noted that the Failsafe Report's header is "Surefire Report", which is
> quite confusing.
> Can you fix this?
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
