[jira] [Created] (MPOM-179) update sonar url to https://builds.apache.org/analysis/
Hervé Boutemy created MPOM-179: -- Summary: update sonar url to https://builds.apache.org/analysis/ Key: MPOM-179 URL: https://issues.apache.org/jira/browse/MPOM-179 Project: Maven POMs Issue Type: Task Components: maven Affects Versions: MAVEN-30 Reporter: Hervé Boutemy Fix For: MAVEN-31 current value: [https://analysis.apache.org/] has changed to [https://builds.apache.org/analysis/]: see [https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis] -- 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&focusedCommentId=16342728#comment-16342728 ] Hudson commented on MSHARED-656: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-656 #10 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-656/10/ > 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-678) Add null check for ProjectInstaller Interface
[ https://issues.apache.org/jira/browse/MSHARED-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342727#comment-16342727 ] Hudson commented on MSHARED-678: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-656 #10 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-656/10/ > Add null check for ProjectInstaller Interface > - > > Key: MSHARED-678 > URL: https://issues.apache.org/jira/browse/MSHARED-678 > 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: Minor > Fix For: maven-artifact-transfer-1.0.0 > > > Currently the interface {{ProjectInstaller}} defines the following method: > {code:java} > void install( ProjectBuildingRequest projectBuildingRequest, > ProjectInstallerRequest projectInstallerRequest ) > throws IOException, ArtifactInstallerException, NoFileAssignedException; > {code} > where we should check the parameter against {{null}} which should not be > allowed to be given as parameter. The result should be an > {{IllegalArgumentException}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-677) Add null checks for ArtifactResolver interface.
[ https://issues.apache.org/jira/browse/MSHARED-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342726#comment-16342726 ] Hudson commented on MSHARED-677: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-656 #10 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-656/10/ > Add null checks for ArtifactResolver interface. > --- > > Key: MSHARED-677 > URL: https://issues.apache.org/jira/browse/MSHARED-677 > 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: Minor > Fix For: maven-artifact-transfer-1.0.0 > > > The interface {{ArtifactResolver}} contains two methods > {code:java} > ArtifactResult resolveArtifact( ProjectBuildingRequest buildingRequest, > Artifact mavenArtifact ) > {code} > and > {code:java} > ArtifactResult resolveArtifact( ProjectBuildingRequest buildingRequest, > ArtifactCoordinate coordinate ) > {code} > which should check the incoming parameters against {{null}} and produce an > {{IllegalArgumentException}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-678) Add null check for ProjectInstaller Interface
[ https://issues.apache.org/jira/browse/MSHARED-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-678. --- Resolution: Fixed Done in [4e3ac40f6f9448ae6df1e5bf549c9fab8bea2c2a|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=4e3ac40f6f9448ae6df1e5bf549c9fab8bea2c2a] > Add null check for ProjectInstaller Interface > - > > Key: MSHARED-678 > URL: https://issues.apache.org/jira/browse/MSHARED-678 > 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: Minor > Fix For: maven-artifact-transfer-1.0.0 > > > Currently the interface {{ProjectInstaller}} defines the following method: > {code:java} > void install( ProjectBuildingRequest projectBuildingRequest, > ProjectInstallerRequest projectInstallerRequest ) > throws IOException, ArtifactInstallerException, NoFileAssignedException; > {code} > where we should check the parameter against {{null}} which should not be > allowed to be given as parameter. The result should be an > {{IllegalArgumentException}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-678) Add null check for ProjectInstaller Interface
[ https://issues.apache.org/jira/browse/MSHARED-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342718#comment-16342718 ] Hudson commented on MSHARED-678: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #4 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/4/ > Add null check for ProjectInstaller Interface > - > > Key: MSHARED-678 > URL: https://issues.apache.org/jira/browse/MSHARED-678 > 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: Minor > Fix For: maven-artifact-transfer-1.0.0 > > > Currently the interface {{ProjectInstaller}} defines the following method: > {code:java} > void install( ProjectBuildingRequest projectBuildingRequest, > ProjectInstallerRequest projectInstallerRequest ) > throws IOException, ArtifactInstallerException, NoFileAssignedException; > {code} > where we should check the parameter against {{null}} which should not be > allowed to be given as parameter. The result should be an > {{IllegalArgumentException}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-678) Add null check for ProjectInstaller Interface
Karl Heinz Marbaise created MSHARED-678: --- Summary: Add null check for ProjectInstaller Interface Key: MSHARED-678 URL: https://issues.apache.org/jira/browse/MSHARED-678 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 Fix For: maven-artifact-transfer-1.0.0 Currently the interface {{ProjectInstaller}} defines the following method: {code:java} void install( ProjectBuildingRequest projectBuildingRequest, ProjectInstallerRequest projectInstallerRequest ) throws IOException, ArtifactInstallerException, NoFileAssignedException; {code} where we should check the parameter against {{null}} which should not be allowed to be given as parameter. The result should be an {{IllegalArgumentException}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-655) ArtifactInstaller check for integrity of parameters null, empty collection, being a directory
[ https://issues.apache.org/jira/browse/MSHARED-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-655. --- Resolution: Fixed Assignee: Karl Heinz Marbaise Done in * https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=0d689e8a324b9b6c9f45d8e474cb4c5c573ee0f7 * https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=588b19dfd6f9985a7ce0a9ab27cf53304c6e4fb5 * https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=3cf02b285ab334b7ed86bda94fe005b0813cf144 * https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=cfc1b72fc846cbcc956f3be97f7842aa315f001a > ArtifactInstaller check for integrity of parameters null, empty collection, > being a directory > - > > Key: MSHARED-655 > URL: https://issues.apache.org/jira/browse/MSHARED-655 > 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: Minor > Fix For: maven-artifact-transfer-1.0.0 > > > Currently the interface {{ArtifactInstaller}} contains the two methods: > {code:java} > public interface ArtifactInstaller > { > void install( ProjectBuildingRequest request, Collection > mavenArtifacts ); > void install( ProjectBuildingRequest request, File localRepository, > Collection mavenArtifacts ); > } > {code} > We should make sure that {{ProjectBuildRequest}} can't be null. Furthermore > the {{mavenArtifacts}} should also being checked for {{null}}. We need to > think if an {{empty}} collection is allowed or not? (I think it should not > being allowed?) > Apart from that the {{localRepository}} should be checked for {{null}} and it > should be checked for being a directory if it is not {{null}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-667) plexus-utils 3.0.24 to 3.1.0
[ https://issues.apache.org/jira/browse/MSHARED-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-667. --- Resolution: Fixed Done in [69d7d319d065d8509462415a9afb6075d607169b|https://gitbox.apache.org/repos/asf?p=maven-filtering.git;a=commitdiff;h=69d7d319d065d8509462415a9afb6075d607169b] > plexus-utils 3.0.24 to 3.1.0 > > > Key: MSHARED-667 > URL: https://issues.apache.org/jira/browse/MSHARED-667 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-filtering >Affects Versions: maven-filtering-3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-filtering-3.1.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-669) Upgrade plexus-interpolation to 1.24
[ https://issues.apache.org/jira/browse/MSHARED-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-669. --- Resolution: Fixed Done in [7fbfe874d75fca07051fc6c7c03d1e9a40bb3394|https://gitbox.apache.org/repos/asf?p=maven-archiver.git;a=commitdiff;h=7fbfe874d75fca07051fc6c7c03d1e9a40bb3394] > Upgrade plexus-interpolation to 1.24 > > > Key: MSHARED-669 > URL: https://issues.apache.org/jira/browse/MSHARED-669 > Project: Maven Shared Components > Issue Type: Dependency upgrade >Affects Versions: maven-archiver-3.2.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-archiver-3.2.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-677) Add null checks for ArtifactResolver interface.
[ https://issues.apache.org/jira/browse/MSHARED-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-677. --- Resolution: Fixed Done in [3a7b4276e9240ab706edc19291c6dbfc7eb1b9fc|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=3a7b4276e9240ab706edc19291c6dbfc7eb1b9fc] > Add null checks for ArtifactResolver interface. > --- > > Key: MSHARED-677 > URL: https://issues.apache.org/jira/browse/MSHARED-677 > 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: Minor > Fix For: maven-artifact-transfer-1.0.0 > > > The interface {{ArtifactResolver}} contains two methods > {code:java} > ArtifactResult resolveArtifact( ProjectBuildingRequest buildingRequest, > Artifact mavenArtifact ) > {code} > and > {code:java} > ArtifactResult resolveArtifact( ProjectBuildingRequest buildingRequest, > ArtifactCoordinate coordinate ) > {code} > which should check the incoming parameters against {{null}} and produce an > {{IllegalArgumentException}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-677) Add null checks for ArtifactResolver interface.
[ https://issues.apache.org/jira/browse/MSHARED-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342689#comment-16342689 ] Hudson commented on MSHARED-677: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #3 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/3/ > Add null checks for ArtifactResolver interface. > --- > > Key: MSHARED-677 > URL: https://issues.apache.org/jira/browse/MSHARED-677 > 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: Minor > Fix For: maven-artifact-transfer-1.0.0 > > > The interface {{ArtifactResolver}} contains two methods > {code:java} > ArtifactResult resolveArtifact( ProjectBuildingRequest buildingRequest, > Artifact mavenArtifact ) > {code} > and > {code:java} > ArtifactResult resolveArtifact( ProjectBuildingRequest buildingRequest, > ArtifactCoordinate coordinate ) > {code} > which should check the incoming parameters against {{null}} and produce an > {{IllegalArgumentException}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-677) Add null checks for ArtifactResolver interface.
Karl Heinz Marbaise created MSHARED-677: --- Summary: Add null checks for ArtifactResolver interface. Key: MSHARED-677 URL: https://issues.apache.org/jira/browse/MSHARED-677 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 Fix For: maven-artifact-transfer-1.0.0 The interface {{ArtifactResolver}} contains two methods {code:java} ArtifactResult resolveArtifact( ProjectBuildingRequest buildingRequest, Artifact mavenArtifact ) {code} and {code:java} ArtifactResult resolveArtifact( ProjectBuildingRequest buildingRequest, ArtifactCoordinate coordinate ) {code} which should check the incoming parameters against {{null}} and produce an {{IllegalArgumentException}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPOM-178) Upgrade maven-compiler-plugin to 3.7.0
[ https://issues.apache.org/jira/browse/MPOM-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342657#comment-16342657 ] Hudson commented on MPOM-178: - Build succeeded in Jenkins: Maven TLP » maven-parent » master #54 See https://builds.apache.org/job/maven-box/job/maven-parent/job/master/54/ > Upgrade maven-compiler-plugin to 3.7.0 > -- > > Key: MPOM-178 > URL: https://issues.apache.org/jira/browse/MPOM-178 > Project: Maven POMs > Issue Type: Task > Components: maven >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPOM-178) Upgrade maven-compiler-plugin to 3.7.0
[ https://issues.apache.org/jira/browse/MPOM-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MPOM-178. --- Resolution: Fixed Fixed in [4d84954bff9fb56e5d1604e91f06b92208a51961|https://gitbox.apache.org/repos/asf?p=maven-parent.git;a=commit;h=4d84954bff9fb56e5d1604e91f06b92208a51961] > Upgrade maven-compiler-plugin to 3.7.0 > -- > > Key: MPOM-178 > URL: https://issues.apache.org/jira/browse/MPOM-178 > Project: Maven POMs > Issue Type: Task > Components: maven >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPOM-178) Upgrade maven-compiler-plugin to 3.7.0
Robert Scholte created MPOM-178: --- Summary: Upgrade maven-compiler-plugin to 3.7.0 Key: MPOM-178 URL: https://issues.apache.org/jira/browse/MPOM-178 Project: Maven POMs Issue Type: Task Components: maven Reporter: Robert Scholte Assignee: Robert Scholte Fix For: MAVEN-31 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPOM-177) propose Pony mail as default Apache mailing lists viewer (mod_mbox as alternate)
[ https://issues.apache.org/jira/browse/MPOM-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-177. -- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=maven-parent.git&a=commit&h=4b6f64db9ad3d09c09e32a89b4e947aafc2245a1 > propose Pony mail as default Apache mailing lists viewer (mod_mbox as > alternate) > > > Key: MPOM-177 > URL: https://issues.apache.org/jira/browse/MPOM-177 > Project: Maven POMs > Issue Type: Task > Components: maven >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: MAVEN-31 > > > Pony Mail is so much more user-friendly: > [https://lists.apache.org/list.html?us...@maven.apache.org] > than mod_mbox: https://mail-archives.apache.org/mod_mbox/maven-users -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPOM-177) propose Pony mail as default Apache mailing lists viewer (mod_mbox as alternate)
[ https://issues.apache.org/jira/browse/MPOM-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342542#comment-16342542 ] Hudson commented on MPOM-177: - Build succeeded in Jenkins: Maven TLP » maven-parent » master #53 See https://builds.apache.org/job/maven-box/job/maven-parent/job/master/53/ > propose Pony mail as default Apache mailing lists viewer (mod_mbox as > alternate) > > > Key: MPOM-177 > URL: https://issues.apache.org/jira/browse/MPOM-177 > Project: Maven POMs > Issue Type: Task > Components: maven >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy >Priority: Major > Fix For: MAVEN-31 > > > Pony Mail is so much more user-friendly: > [https://lists.apache.org/list.html?us...@maven.apache.org] > than mod_mbox: https://mail-archives.apache.org/mod_mbox/maven-users -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MPOM-177) propose Pony mail as default Apache mailing lists viewer (mod_mbox as alternate)
Hervé Boutemy created MPOM-177: -- Summary: propose Pony mail as default Apache mailing lists viewer (mod_mbox as alternate) Key: MPOM-177 URL: https://issues.apache.org/jira/browse/MPOM-177 Project: Maven POMs Issue Type: Task Components: maven Affects Versions: MAVEN-30 Reporter: Hervé Boutemy Assignee: Hervé Boutemy Fix For: MAVEN-31 Pony Mail is so much more user-friendly: [https://lists.apache.org/list.html?us...@maven.apache.org] than mod_mbox: https://mail-archives.apache.org/mod_mbox/maven-users -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (WAGON-494) wagon-ssh: infinite prompts when EOF on stdin
[ https://issues.apache.org/jira/browse/WAGON-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Basin updated WAGON-494: - Description: When running maven with stdin redirected to /dev/null or nul and connecting to unknown host, it repeats the host key prompt infininitely: {code:java} d:\ftpjob\ftpjob>mvnDebug org.codehaus.mojo:wagon-maven-plugin::sshexec@execute-test-commands https://github.com/sonatype/plexus-interactivity/blob/e63b88bfd5789a4d2ac07e3f9b3b15308b2416e8/plexus-interactivity-api/src/main/java/org/codehaus/plexus/components/interactivity/DefaultPrompter.java#L147] I don't know why they wrote it like this. Maybe they should've thrown a runtime exception instead of looping. Anyway, I can't find their Jira so maybe you can direct this to the right place. Or, as a workaround, always pass a default return value ("no" in case of the host key prompt). full pom: {code:java} http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 foo infloop 0.1-SNAPSHOT mojohaus-snapshots https://oss.sonatype.org/content/repositories/snapshots false true apache-snapshots https://repository.apache.org/content/repositories/snapshots false true maven-compiler-plugin 1.7 1.7 org.codehaus.mojo wagon-maven-plugin execute-test-commands sshexec bad-server-id scp://localhost pwd org.codehaus.mojo wagon-maven-plugin 1.1-SNAPSHOT org.apache.maven.wagon wagon-ssh 3.0.1-SNAPSHOT {code} was: When running maven with closed stdin and connecting to unknown host, it repeats the host key prompt infininitely: {code:java} d:\ftpjob\ftpjob>mvnDebug org.codehaus.mojo:wagon-maven-plugin::sshexec@execute-test-commands https://github.com/sonatype/plexus-interactivity/blob/e63b88bfd5789a4d2ac07e3f9b3b15308b2416e8/plexus-interactivity-api/src/main/java/org/codehaus/plexus/components/interactivity/DefaultPrompter.java#L147] I don't know why they wrote it like this. Maybe they should've thrown a runtime exception instead of looping. Anyway, I can't find their Jira so maybe you can direct this to the right place. Or, as a workaround, always pass a default return value ("no" in case of the host key prompt). full pom: {code:java} http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 foo infloop 0.1-SNAPSHOT mojohaus-snapshots https://oss.sonatype.org/content/repositories/snapshots false true apache-snapshots https://repository.apache.org/content/repositories/snapshots false true maven-compiler-plugin 1.7 1.7 org.codehaus.mojo wagon-maven-plugin execute-test-commands sshexec bad-server-id scp://localhost pwd
[jira] [Updated] (WAGON-494) wagon-ssh: infinite prompts when EOF on stdin
[ https://issues.apache.org/jira/browse/WAGON-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Basin updated WAGON-494: - Summary: wagon-ssh: infinite prompts when EOF on stdin (was: wagon-ssh: infinite prompts when stdin closed) > wagon-ssh: infinite prompts when EOF on stdin > - > > Key: WAGON-494 > URL: https://issues.apache.org/jira/browse/WAGON-494 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-ssh > Environment: windows7 >Reporter: Ilya Basin >Priority: Major > > When running maven with closed stdin and connecting to unknown host, it > repeats the host key prompt infininitely: > {code:java} > d:\ftpjob\ftpjob>mvnDebug > org.codehaus.mojo:wagon-maven-plugin::sshexec@execute-test-commands Listening for transport dt_socket at address: 8000 > [INFO] Scanning for projects... > [INFO] > [INFO] > > [INFO] Building ftpjob 1.0.0-SNAPSHOT > [INFO] > > [INFO] > [INFO] --- wagon-maven-plugin:1.1-SNAPSHOT:sshexec (execute-test-commands) @ > ftpjob --- > The authenticity of host 'localhost' can't be established. > RSA key fingerprint is b2:83:4c:3f:39:de:55:0f:22:0b:d4:65:f3:b6:c8:8a. > Are you sure you want to continue connecting? (yes/no): > The authenticity of host 'localhost' can't be established. > RSA key fingerprint is b2:83:4c:3f:39:de:55:0f:22:0b:d4:65:f3:b6:c8:8a. > Are you sure you want to continue connecting? (yes/no): > ..{code} > This infinite loop is the reaction to EOF in the plexus prompter: > [https://github.com/sonatype/plexus-interactivity/blob/e63b88bfd5789a4d2ac07e3f9b3b15308b2416e8/plexus-interactivity-api/src/main/java/org/codehaus/plexus/components/interactivity/DefaultPrompter.java#L147] > I don't know why they wrote it like this. Maybe they should've thrown a > runtime exception instead of looping. > Anyway, I can't find their Jira so maybe you can direct this to the right > place. > Or, as a workaround, always pass a default return value ("no" in case of the > host key prompt). > > full pom: > {code:java} > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > foo > infloop > 0.1-SNAPSHOT > > > mojohaus-snapshots > https://oss.sonatype.org/content/repositories/snapshots > > false > > > true > > > > apache-snapshots > > https://repository.apache.org/content/repositories/snapshots > > false > > > true > > > > > > > > maven-compiler-plugin > > 1.7 > 1.7 > > > > org.codehaus.mojo > wagon-maven-plugin > > > execute-test-commands > > sshexec > > > bad-server-id > scp://localhost > > pwd > > > > > > > > > > org.codehaus.mojo > wagon-maven-plugin > 1.1-SNAPSHOT > > > org.apache.maven.wagon > wagon-ssh > 3.0.1-SNAPSHOT > > > > > > > > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSITE-709) relativizeDecorationLinks=false seems to be ignored
[ https://issues.apache.org/jira/browse/MSITE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342520#comment-16342520 ] Hervé Boutemy commented on MSITE-709: - can you provide a sample test showing what you get and what you expect, please? I can't change any algorithm without tests, since experience showed in the past that some good ideas for some users are bad ideas for others: it's hard to find what works for every situation > relativizeDecorationLinks=false seems to be ignored > --- > > Key: MSITE-709 > URL: https://issues.apache.org/jira/browse/MSITE-709 > Project: Maven Site Plugin > Issue Type: Bug > Components: relative links >Affects Versions: 3.3 >Reporter: Archimedes Trajano >Priority: Major > Attachments: MSITE-709.diff > > > I am trying to prevent the site plugin from using the "incorrectly > implemented" pathutils and use the links I have put in myself. However, > setting relativizeDecorationLinks=false seems to have no effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MCOMPILER-321) Problematic Java 9 modules are silently ignored
[ https://issues.apache.org/jira/browse/MCOMPILER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342297#comment-16342297 ] Marcel Kolsteren edited comment on MCOMPILER-321 at 1/28/18 10:41 AM: -- Thanks for the quick response! True, the error that the Java compiler gives is correct, but I'd expect that the maven-compiler-plugin itself reports a more detailed error (and maybe even stops so that the Java compiler is not called at all). Regarding the problem with the java modules: that might be solved by using the method {{ModuleFinder#ofSystem}}. was (Author: mkolsteren): Thanks for the quick response! True, the error that the Java compiler gives is correct, but I'd expect that the maven-compiler-plugin itself reports the error (and maybe even stops so that the Java compiler is not called at all). Regarding the problem with the java modules: that might be solved by using the method {{ModuleFinder#ofSystem}}. > Problematic Java 9 modules are silently ignored > --- > > Key: MCOMPILER-321 > URL: https://issues.apache.org/jira/browse/MCOMPILER-321 > Project: Maven Compiler Plugin > Issue Type: Bug >Reporter: Marcel Kolsteren >Priority: Major > Attachments: maven-compiler-plugin-bug.zip > > > Before the compilation starts, the compiler plugin prepares the module path > and the class path. Unfortunately, this process is very lenient. If the > plugin cannot find a module that is specified in the module-info file, it > doesn't report this problem, and it just carries on. In the end, the compiler > will give a "module not found", giving no clue about the root cause. > As an example, I attached a simple maven project with a module info file that > refers to an automatic module named {{jython-standalone}}. The dependencies > contain a jar file {{jython-standalone-2.7.0.jar}}. That jar file contains no > module information, and it would normally be resolvable as an automatic > module. However, when building the project, the Java compiler fails with this > error: > {{module not found: jython.standalone}} > The root cause of the error is that the jar file contains a class at top > level, which is illegal for a module. So, the error message "module not > found" is misleading. > I think this is a bug, because the maven-compiler-plugin fails to perform its > task of building a correct module path, but doesn't tell, and just carries > on. Instead, it should stop, and give an informative error message. > Relevant source code: > * [https://github.com/apache/maven-compiler-plugin], class {{CompilerMojo}} > * [https://github.com/codehaus-plexus/plexus-languages], class > {{LocationManager}} and {{MainClassModuleNameExtractor}} > * > [https://docs.oracle.com/javase/9/docs/api/java/lang/module/ModuleFinder.html] > The {{MainClassModuleNameExtractor}} uses the {{ModuleFinder}} class of the > JDK to find modules. I think that these two error situations should lead to > an error and a clear description of possible causes: > * {{ModuleFinder#findAll}} returns an empty set. > * {{ModuleFinder#findAll}} results in a {{FindException}}. When this happens > is well documented in the {{ModuleFinder#of}} method. This exception is > currently swallowed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SUREFIRE-1445) Properties from configuration POM are not passed to Provider on JDK 9
[ https://issues-test.apache.org/jira/browse/SUREFIRE-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1445. -- Resolution: Fixed [https://github.com/apache/maven-surefire/commit/302094ef2a7103d1a72b798443995a7d2b3b6702] > Properties from configuration POM are not passed to Provider on JDK 9 > - > > Key: SUREFIRE-1445 > URL: https://issues-test.apache.org/jira/browse/SUREFIRE-1445 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: 2.19.1, 2.20, 2.20.1 > Environment: JDK 9 >Reporter: Marc Philipp >Assignee: Tibor Digana >Priority: Blocker > Fix For: 2.21.0.Jigsaw > > > Given the POM below, the {{JUnitPlatformProvider}} can read {{"excludeTags"}} > = {{"slow"}} from {{ProviderParameters.getProviderProperties()}} when it runs > on JDK 8 but not on JDK 9. > The reason is that the constructor of {{SurefireProperties}} relies on an > implementation detail of the class it extends, namely that {{putAll()}} will > call {{put()}} for each entry. However, while {{Properties}} does that on JDK > 8, it doesn't on JDK 9. > Here's a link to the line in {{SurefireProperties}}: > https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireProperties.java#L62 > {code:xml} > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd";> > 4.0.0 > junit5 > tagging > 1.0-SNAPSHOT > > > > maven-surefire-plugin > 2.19.1 > > > slow > > > > > org.junit.platform > > junit-platform-surefire-provider > 1.0.2 > > > org.junit.jupiter > junit-jupiter-engine > 5.0.2 > > > > > > > > org.junit.jupiter > junit-jupiter-api > 5.0.2 > test > > > > {code} -- This message was sent by Atlassian JIRA (v7.6.0#76001)
[jira] [Updated] (SUREFIRE-1445) Properties from configuration POM are not passed to Provider on JDK 9
[ https://issues-test.apache.org/jira/browse/SUREFIRE-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1445: --- Fix Version/s: 2.21.0.Jigsaw > Properties from configuration POM are not passed to Provider on JDK 9 > - > > Key: SUREFIRE-1445 > URL: https://issues-test.apache.org/jira/browse/SUREFIRE-1445 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: 2.19.1, 2.20, 2.20.1 > Environment: JDK 9 >Reporter: Marc Philipp >Assignee: Tibor Digana >Priority: Blocker > Fix For: 2.21.0.Jigsaw > > > Given the POM below, the {{JUnitPlatformProvider}} can read {{"excludeTags"}} > = {{"slow"}} from {{ProviderParameters.getProviderProperties()}} when it runs > on JDK 8 but not on JDK 9. > The reason is that the constructor of {{SurefireProperties}} relies on an > implementation detail of the class it extends, namely that {{putAll()}} will > call {{put()}} for each entry. However, while {{Properties}} does that on JDK > 8, it doesn't on JDK 9. > Here's a link to the line in {{SurefireProperties}}: > https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireProperties.java#L62 > {code:xml} > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/xsd/maven-4.0.0.xsd";> > 4.0.0 > junit5 > tagging > 1.0-SNAPSHOT > > > > maven-surefire-plugin > 2.19.1 > > > slow > > > > > org.junit.platform > > junit-platform-surefire-provider > 1.0.2 > > > org.junit.jupiter > junit-jupiter-engine > 5.0.2 > > > > > > > > org.junit.jupiter > junit-jupiter-api > 5.0.2 > test > > > > {code} -- This message was sent by Atlassian JIRA (v7.6.0#76001)