[jira] [Resolved] (MJLINK-29) Upgrade maven-compiler-plugin to version 3.8.0 in IT's

[ https://issues.apache.org/jira/browse/MJLINK-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Stein resolved MJLINK-29. --- Resolution: Done Merged https://github.com/apache/maven-jlink-plugin/pull/5 > Upgrade maven-c

[jira] [Closed] (MJLINK-29) Upgrade maven-compiler-plugin to version 3.8.0 in IT's

[ https://issues.apache.org/jira/browse/MJLINK-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Stein closed MJLINK-29. - > Upgrade maven-compiler-plugin to version 3.8.0 in IT's > ---

[jira] [Commented] (MJLINK-29) Upgrade maven-compiler-plugin to version 3.8.0 in IT's

[ https://issues.apache.org/jira/browse/MJLINK-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773438#comment-16773438 ] Hudson commented on MJLINK-29: -- Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin »

[GitHub] sormuras commented on issue #5: [MJLINK-29] Upgrade maven-compiler-plugin to version 3.8.0 in ITs.

sormuras commented on issue #5: [MJLINK-29] Upgrade maven-compiler-plugin to version 3.8.0 in ITs. URL: https://github.com/apache/maven-jlink-plugin/pull/5#issuecomment-465774593 Thanks @andretadeu! This is an automated messa

[GitHub] sormuras merged pull request #5: [MJLINK-29] Upgrade maven-compiler-plugin to version 3.8.0 in ITs.

sormuras merged pull request #5: [MJLINK-29] Upgrade maven-compiler-plugin to version 3.8.0 in ITs. URL: https://github.com/apache/maven-jlink-plugin/pull/5 This is an automated message from the Apache Git Service. To respon

[jira] [Commented] (MASSEMBLY-905) The springboot project is packaged and cannot be accessed over HTTPS, only over HTTP

[ https://issues.apache.org/jira/browse/MASSEMBLY-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773322#comment-16773322 ] Michael Osipov commented on MASSEMBLY-905: -- The Assembly plugin does not down

[jira] [Commented] (MPOM-216) Update java minimum version to 7

[ https://issues.apache.org/jira/browse/MPOM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773334#comment-16773334 ] Hudson commented on MPOM-216: - Build succeeded in Jenkins: Maven TLP » maven-parent » master #1

[jira] [Closed] (MPOM-216) Update java minimum version to 7

[ https://issues.apache.org/jira/browse/MPOM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MPOM-216. --- Resolution: Fixed Assignee: Robert Scholte Fix Version/s: MAVEN-34 Fixed in [5b8015fd5

[GitHub] rfscholte merged pull request #6: [MPOM-216] Update java minimum version to 7

rfscholte merged pull request #6: [MPOM-216] Update java minimum version to 7 URL: https://github.com/apache/maven-parent/pull/6 This is an automated message from the Apache Git Service. To respond to the message, please log

[jira] [Commented] (MSHARED-685) DirectoryScanner#checkSymlinkBehaviour() does not use assert*

[ https://issues.apache.org/jira/browse/MSHARED-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773323#comment-16773323 ] Robert Scholte commented on MSHARED-685: The title and description are not clear

[jira] [Updated] (MNG-6596) maven should not make assumptions on the location of the parent pom

[ https://issues.apache.org/jira/browse/MNG-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6596: Fix Version/s: waiting-for-feedback > maven should not make assumptions on the location of the parent

[jira] [Updated] (MASSEMBLY-905) The springboot project is packaged and cannot be accessed over HTTPS, only over HTTP

[ https://issues.apache.org/jira/browse/MASSEMBLY-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MASSEMBLY-905: - Fix Version/s: waiting-for-feedback > The springboot project is packaged and cannot be

[jira] [Commented] (MNG-6596) maven should not make assumptions on the location of the parent pom

[ https://issues.apache.org/jira/browse/MNG-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773311#comment-16773311 ] Michael Osipov commented on MNG-6596: - I don't understand this request. If the parent P

[jira] [Commented] (SCM-921) maven-scm-provider-jgit not handling relative paths on Windows Server

[ https://issues.apache.org/jira/browse/SCM-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773296#comment-16773296 ] Michael Osipov commented on SCM-921: Can you write a test which shows that uppercase let

[GitHub] oehme closed pull request #12: Improve "Older projects with module-info" chapter

oehme closed pull request #12: Improve "Older projects with module-info" chapter URL: https://github.com/apache/maven-compiler-plugin/pull/12 This is an automated message from the Apache Git Service. To respond to the message

[GitHub] oehme commented on issue #12: Improve "Older projects with module-info" chapter

oehme commented on issue #12: Improve "Older projects with module-info" chapter URL: https://github.com/apache/maven-compiler-plugin/pull/12#issuecomment-465688817 I've tried this out on the slf4j project, because they had this exact setup. I flipped it around as suggested here and it comp

[GitHub] rfscholte commented on issue #12: Improve "Older projects with module-info" chapter

rfscholte commented on issue #12: Improve "Older projects with module-info" chapter URL: https://github.com/apache/maven-compiler-plugin/pull/12#issuecomment-465674923 AFAIK the current setup is the only way to ensure that content of the classfiles and its modueldescriptor are reliable, i

[jira] [Created] (MNG-6596) maven should not make assumptions on the location of the parent pom

Pieter van den Hombergh created MNG-6596: Summary: maven should not make assumptions on the location of the parent pom Key: MNG-6596 URL: https://issues.apache.org/jira/browse/MNG-6596 Project

[GitHub] sormuras commented on issue #12: Improve "Older projects with module-info" chapter

sormuras commented on issue #12: Improve "Older projects with module-info" chapter URL: https://github.com/apache/maven-compiler-plugin/pull/12#issuecomment-465511229 Thanks for the PR, @oehme Do you have an integration test (or demo project) that uses this "split" compile strateg

[GitHub] oehme opened a new pull request #12: Improve "Older projects with module-info" chapter

oehme opened a new pull request #12: Improve "Older projects with module-info" chapter URL: https://github.com/apache/maven-compiler-plugin/pull/12 The previous suggestion lead to all source code being compiled twice, once with Java 9 and once with Java 6. This is unnecessarily slow. Th

[jira] [Updated] (MASSEMBLY-905) The springboot project is packaged and cannot be accessed over HTTPS, only over HTTP

[ https://issues.apache.org/jira/browse/MASSEMBLY-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zgx updated MASSEMBLY-905: -- Description: 1: one of my simple springboot projects, running in an IDE such as eclipse, is accessible over