[jira] [Updated] (MSKINS-102) Make Fluido-generated pages pass W3 HTML5 Validation Service
[ https://issues.apache.org/jira/browse/MSKINS-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSKINS-102: Labels: up-for-grabs (was: ) > Make Fluido-generated pages pass W3 HTML5 Validation Service > > > Key: MSKINS-102 > URL: https://issues.apache.org/jira/browse/MSKINS-102 > Project: Maven Skins > Issue Type: Task > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov >Priority: Major > Labels: up-for-grabs > > No generated HTML page passes [W3 Validation > Service|http://validator.w3.org/check?uri=http%3A%2F%2Fmaven.apache.org%2Fskins%2Fmaven-fluido-skin%2F=%28detect+automatically%29=Inline=0=W3C_Validator%2F1.3+http%3A%2F%2Fvalidator.w3.org%2Fservices], > multiple errors are logged. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSKINS-104) Remove obsolete meta tags
[ https://issues.apache.org/jira/browse/MSKINS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSKINS-104: Labels: up-for-grabs (was: ) > Remove obsolete meta tags > - > > Key: MSKINS-104 > URL: https://issues.apache.org/jira/browse/MSKINS-104 > Project: Maven Skins > Issue Type: Sub-task > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov >Priority: Major > Labels: up-for-grabs > > Issued error: > bq. Using the meta element to specify the document-wide default language is > obsolete. Consider specifying the language on the root element instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSKINS-107) Add "generator" meta tag in HTML head
[
https://issues.apache.org/jira/browse/MSKINS-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MSKINS-107:
Labels: up-for-grabs (was: )
> Add "generator" meta tag in HTML head
> -
>
> Key: MSKINS-107
> URL: https://issues.apache.org/jira/browse/MSKINS-107
> Project: Maven Skins
> Issue Type: Task
> Components: Default Skin, Fluido Skin
>Reporter: Michael Osipov
>Priority: Major
> Labels: up-for-grabs
>
> It shall be the same as the comment before the {{}} tag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MSKINS-145) Google+ Shutdown - remove code from skins
[ https://issues.apache.org/jira/browse/MSKINS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MSKINS-145: --- Assignee: Sylwester Lachiewicz > Google+ Shutdown - remove code from skins > - > > Key: MSKINS-145 > URL: https://issues.apache.org/jira/browse/MSKINS-145 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Labels: up-for-grabs > Time Spent: 20m > Remaining Estimate: 0h > > Due to Google shutdown of all APIs related to Google+ we should remove our > code generation logic to display GooglePlus buttons. > https://developers.google.com/+/integrations-shutdown -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSKINS-145) Google+ Shutdown - remove code from skins
[ https://issues.apache.org/jira/browse/MSKINS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSKINS-145. --- Resolution: Fixed > Google+ Shutdown - remove code from skins > - > > Key: MSKINS-145 > URL: https://issues.apache.org/jira/browse/MSKINS-145 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Labels: up-for-grabs > Fix For: fluido-1.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Due to Google shutdown of all APIs related to Google+ we should remove our > code generation logic to display GooglePlus buttons. > https://developers.google.com/+/integrations-shutdown -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSKINS-145) Google+ Shutdown - remove code from skins
[ https://issues.apache.org/jira/browse/MSKINS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSKINS-145: Fix Version/s: fluido-1.8 > Google+ Shutdown - remove code from skins > - > > Key: MSKINS-145 > URL: https://issues.apache.org/jira/browse/MSKINS-145 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Labels: up-for-grabs > Fix For: fluido-1.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Due to Google shutdown of all APIs related to Google+ we should remove our > code generation logic to display GooglePlus buttons. > https://developers.google.com/+/integrations-shutdown -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSKINS-137) Enable "Hamburger menu" with top-nav only
[ https://issues.apache.org/jira/browse/MSKINS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSKINS-137. --- Resolution: Fixed > Enable "Hamburger menu" with top-nav only > - > > Key: MSKINS-137 > URL: https://issues.apache.org/jira/browse/MSKINS-137 > Project: Maven Skins > Issue Type: Improvement >Reporter: Josh Elser >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: fluido-1.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Revitalizing this old PR https://github.com/apache/maven-skins/pull/4 > Still an issue for us down in HBase. Changes seem to apply and have worked in > local testing on the HBase site. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSKINS-137) Enable "Hamburger menu" with top-nav only
[ https://issues.apache.org/jira/browse/MSKINS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MSKINS-137: Fix Version/s: fluido-1.8 > Enable "Hamburger menu" with top-nav only > - > > Key: MSKINS-137 > URL: https://issues.apache.org/jira/browse/MSKINS-137 > Project: Maven Skins > Issue Type: Improvement >Reporter: Josh Elser >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: fluido-1.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Revitalizing this old PR https://github.com/apache/maven-skins/pull/4 > Still an issue for us down in HBase. Changes seem to apply and have worked in > local testing on the HBase site. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-fluido-skin] slachiewicz edited a comment on issue #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab…
slachiewicz edited a comment on issue #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab… URL: https://github.com/apache/maven-fluido-skin/pull/6#issuecomment-489388936 Thx @joshelser for effort to use that code and testing on HBase site. Merged in ec4b18a33ed4212761c05aa077a54797f25d0652 Hope we can release new fluido version soon :) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-fluido-skin] slachiewicz commented on issue #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab…
slachiewicz commented on issue #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab… URL: https://github.com/apache/maven-fluido-skin/pull/6#issuecomment-489388936 Thx @joshelser for effort to use that code and testing on HBase site. Hope we can release new fluido version soon :) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-fluido-skin] asfgit closed pull request #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena…
asfgit closed pull request #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena… URL: https://github.com/apache/maven-fluido-skin/pull/1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MSKINS-145) Google+ Shutdown - remove code from skins
[ https://issues.apache.org/jira/browse/MSKINS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833210#comment-16833210 ] Hudson commented on MSKINS-145: --- Build succeeded in Jenkins: Maven TLP » maven-fluido-skin » master #7 See https://builds.apache.org/job/maven-box/job/maven-fluido-skin/job/master/7/ > Google+ Shutdown - remove code from skins > - > > Key: MSKINS-145 > URL: https://issues.apache.org/jira/browse/MSKINS-145 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Reporter: Sylwester Lachiewicz >Priority: Minor > Labels: up-for-grabs > Time Spent: 20m > Remaining Estimate: 0h > > Due to Google shutdown of all APIs related to Google+ we should remove our > code generation logic to display GooglePlus buttons. > https://developers.google.com/+/integrations-shutdown -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-fluido-skin] slachiewicz commented on issue #7: MSKINS-145 remove googlePlus code from skins
slachiewicz commented on issue #7: MSKINS-145 remove googlePlus code from skins URL: https://github.com/apache/maven-fluido-skin/pull/7#issuecomment-489388489 Great! Thank You, code merged. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-fluido-skin] asfgit closed pull request #7: MSKINS-145 remove googlePlus code from skins
asfgit closed pull request #7: MSKINS-145 remove googlePlus code from skins URL: https://github.com/apache/maven-fluido-skin/pull/7 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-fluido-skin] barclay-reg commented on issue #7: MSKINS-145 remove googlePlus code from skins
barclay-reg commented on issue #7: MSKINS-145 remove googlePlus code from skins URL: https://github.com/apache/maven-fluido-skin/pull/7#issuecomment-489367975 @slachiewicz done - didn't realised, that the ITs folder names reference a (requirement) issue This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MPOM-220) Update ASF logo to the latest version
Sylwester Lachiewicz created MPOM-220: - Summary: Update ASF logo to the latest version Key: MPOM-220 URL: https://issues.apache.org/jira/browse/MPOM-220 Project: Maven POMs Issue Type: Improvement Reporter: Sylwester Lachiewicz Assignee: Sylwester Lachiewicz Based on ASF press kit - update link to existing logo https://www.apache.org/images/asf_logo_wide.gif to new https://www.apache.org/images/asf_logo_wide_2016.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [maven-compiler-plugin] khmarbaise commented on issue #17: Miscellaneous code cleanups
khmarbaise commented on issue #17: Miscellaneous code cleanups URL: https://github.com/apache/maven-compiler-plugin/pull/17#issuecomment-489367244 Please create some of them... This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-compiler-plugin] rhowe-gds commented on issue #17: Miscellaneous code cleanups
rhowe-gds commented on issue #17: Miscellaneous code cleanups URL: https://github.com/apache/maven-compiler-plugin/pull/17#issuecomment-489366272 If you want a Jira ticket for these changes let me know and I'll make one and rewrite the commits This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MJAVADOC-562) Ability to pass --release to Javadoc tool
[
https://issues.apache.org/jira/browse/MJAVADOC-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833142#comment-16833142
]
Kevin Risden commented on MJAVADOC-562:
---
You can see the diff on github if that helps. -
[https://github.com/apache/maven-javadoc-plugin/commit/fc6fdcdfb53ff18821d37f45fe4de0564a0fffd0]
> Ability to pass --release to Javadoc tool
> -
>
> Key: MJAVADOC-562
> URL: https://issues.apache.org/jira/browse/MJAVADOC-562
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Components: jar, javadoc
>Affects Versions: 3.0.1
>Reporter: Gili
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.1.0
>
>
> Users of the {{maven-compiler-plugin}} are able to build in one compiler
> version while targeting an older version. We need the same ability for this
> plugin.
> Justification: https://bugs.openjdk.java.net/browse/JDK-8212233
> Workaround: Build the project using the same JDK version as the project is
> targetting.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-593) Module not found
[
https://issues.apache.org/jira/browse/MJAVADOC-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833133#comment-16833133
]
Robert Scholte commented on MJAVADOC-593:
-
Looks like a duplicate of MJAVADOC-576
> Module not found
>
>
> Key: MJAVADOC-593
> URL: https://issues.apache.org/jira/browse/MJAVADOC-593
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.1.0
> Environment: Apache Netbeans 10
> OpenJDK 11
> OpenJFX 11
>Reporter: Cédric Servais
>Priority: Major
>
> Hello,
> I'm using the maven-javadoc-plugin version 3.1 to generate the javadoc for my
> Java 11 project. I currently have an issue "module not found" provided by the
> plugin:
> {code:java}
> // espace réservé du code
> Loading source file
> D:\Jangos\JaNGOSExtractor\src\main\java\module-info.java...
> [parsing started
> SimpleFileObject[D:\Jangos\JaNGOSExtractor\src\main\java\module-info.java]]
> [parsing completed 13ms]
> [loading
> C:\Users\Cedri\.m2\repository\com\github\warkdev\Utils\1.0\Utils-1.0.jar(/module-info.class)]
> [loading /modules/java.base/module-info.class]
> [loading
> C:\Users\Cedri\.m2\repository\org\openjfx\javafx-controls\11.0.2\javafx-controls-11.0.2-win.jar(/module-info.class)]
> [loading
> C:\Users\Cedri\.m2\repository\org\openjfx\javafx-graphics\11.0.2\javafx-graphics-11.0.2-win.jar(/module-info.class)]
> [loading
> C:\Users\Cedri\.m2\repository\org\openjfx\javafx-base\11.0.2\javafx-base-11.0.2-win.jar(/module-info.class)]
> [loading /modules/java.desktop/module-info.class]
> [loading /modules/java.xml/module-info.class]
> [loading /modules/java.datatransfer/module-info.class]
> [loading /modules/java.prefs/module-info.class]
> [loading /modules/jdk.unsupported/module-info.class]
> [loading
> C:\Users\Cedri\.m2\repository\com\github\warkdev\jmpq3\java9-module-dd4a82f438-1\jmpq3-java9-module-dd4a82f438-1.jar(/module-info.class)]
> [loading
> C:\Users\Cedri\.m2\repository\org\openjfx\javafx-swing\11.0.2\javafx-swing-11.0.2-win.jar(/module-info.class)]
> [loading /modules/jdk.unsupported.desktop/module-info.class]
> [done in 604 ms]
> 1 error
> Error while creating javadoc report:
> Exit code: 1 - error: module not found: eu.jangos.extractor
> Command line was: "C:\Program Files (x86)\Java\jdk-11.0.2\bin\javadoc.exe"
> @options @packages @argfile{code}
> I had a look to several possible solutions but I couldn't find any workaround
> for this. The project I'm using is the following:
> [https://github.com/Warkdev/JaNGOSExtractor]
> Could you please let me know if I'm doing something wrong ?
> Ps: I tested with the plugin version 3.0.1 but it seems that it doesn't
> support my 3rd party library compiled for Java 11. (Error Unsupported Class
> Version 55)
>
> Thanks in advance,
> Warkdev
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-593) Module not found
[
https://issues.apache.org/jira/browse/MJAVADOC-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833131#comment-16833131
]
Robert Scholte commented on MJAVADOC-593:
-
[~Nibsi] The empty directory is created to be able to patch modules, so this is
intended behavior.
[~Warkdev] Your project contains named and automatic modules, which means some
patching needs to be done. In your case with {{mvn package javadoc:javadoc}}
it'll work.
> Module not found
>
>
> Key: MJAVADOC-593
> URL: https://issues.apache.org/jira/browse/MJAVADOC-593
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.1.0
> Environment: Apache Netbeans 10
> OpenJDK 11
> OpenJFX 11
>Reporter: Cédric Servais
>Priority: Major
>
> Hello,
> I'm using the maven-javadoc-plugin version 3.1 to generate the javadoc for my
> Java 11 project. I currently have an issue "module not found" provided by the
> plugin:
> {code:java}
> // espace réservé du code
> Loading source file
> D:\Jangos\JaNGOSExtractor\src\main\java\module-info.java...
> [parsing started
> SimpleFileObject[D:\Jangos\JaNGOSExtractor\src\main\java\module-info.java]]
> [parsing completed 13ms]
> [loading
> C:\Users\Cedri\.m2\repository\com\github\warkdev\Utils\1.0\Utils-1.0.jar(/module-info.class)]
> [loading /modules/java.base/module-info.class]
> [loading
> C:\Users\Cedri\.m2\repository\org\openjfx\javafx-controls\11.0.2\javafx-controls-11.0.2-win.jar(/module-info.class)]
> [loading
> C:\Users\Cedri\.m2\repository\org\openjfx\javafx-graphics\11.0.2\javafx-graphics-11.0.2-win.jar(/module-info.class)]
> [loading
> C:\Users\Cedri\.m2\repository\org\openjfx\javafx-base\11.0.2\javafx-base-11.0.2-win.jar(/module-info.class)]
> [loading /modules/java.desktop/module-info.class]
> [loading /modules/java.xml/module-info.class]
> [loading /modules/java.datatransfer/module-info.class]
> [loading /modules/java.prefs/module-info.class]
> [loading /modules/jdk.unsupported/module-info.class]
> [loading
> C:\Users\Cedri\.m2\repository\com\github\warkdev\jmpq3\java9-module-dd4a82f438-1\jmpq3-java9-module-dd4a82f438-1.jar(/module-info.class)]
> [loading
> C:\Users\Cedri\.m2\repository\org\openjfx\javafx-swing\11.0.2\javafx-swing-11.0.2-win.jar(/module-info.class)]
> [loading /modules/jdk.unsupported.desktop/module-info.class]
> [done in 604 ms]
> 1 error
> Error while creating javadoc report:
> Exit code: 1 - error: module not found: eu.jangos.extractor
> Command line was: "C:\Program Files (x86)\Java\jdk-11.0.2\bin\javadoc.exe"
> @options @packages @argfile{code}
> I had a look to several possible solutions but I couldn't find any workaround
> for this. The project I'm using is the following:
> [https://github.com/Warkdev/JaNGOSExtractor]
> Could you please let me know if I'm doing something wrong ?
> Ps: I tested with the plugin version 3.0.1 but it seems that it doesn't
> support my 3rd party library compiled for Java 11. (Error Unsupported Class
> Version 55)
>
> Thanks in advance,
> Warkdev
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-562) Ability to pass --release to Javadoc tool
[
https://issues.apache.org/jira/browse/MJAVADOC-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833106#comment-16833106
]
Michael Osipov commented on MJAVADOC-562:
-
Me neither, Gary.
> Ability to pass --release to Javadoc tool
> -
>
> Key: MJAVADOC-562
> URL: https://issues.apache.org/jira/browse/MJAVADOC-562
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Components: jar, javadoc
>Affects Versions: 3.0.1
>Reporter: Gili
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.1.0
>
>
> Users of the {{maven-compiler-plugin}} are able to build in one compiler
> version while targeting an older version. We need the same ability for this
> plugin.
> Justification: https://bugs.openjdk.java.net/browse/JDK-8212233
> Workaround: Build the project using the same JDK version as the project is
> targetting.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJAVADOC-562) Ability to pass --release to Javadoc tool
[
https://issues.apache.org/jira/browse/MJAVADOC-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833097#comment-16833097
]
Gary Gregory commented on MJAVADOC-562:
---
Sad that I can't view the diff due to lack of karma:
https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=blobdiff;f=src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java;h=3446c7321b787e34289e3fbdb20d3bdd7bb076af;hp=e6cea0728c3963606b75db0ed4c4730cce825ead;hb=fc6fdcdfb53ff18821d37f45fe4de0564a0fffd0;hpb=babbc70561bcc25e256d23cd204c6a7e67c130bd
> Ability to pass --release to Javadoc tool
> -
>
> Key: MJAVADOC-562
> URL: https://issues.apache.org/jira/browse/MJAVADOC-562
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Components: jar, javadoc
>Affects Versions: 3.0.1
>Reporter: Gili
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.1.0
>
>
> Users of the {{maven-compiler-plugin}} are able to build in one compiler
> version while targeting an older version. We need the same ability for this
> plugin.
> Justification: https://bugs.openjdk.java.net/browse/JDK-8212233
> Workaround: Build the project using the same JDK version as the project is
> targetting.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6650) Java11 Regression Bug: Transitive dependencies not resolved
[
https://issues.apache.org/jira/browse/MNG-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833087#comment-16833087
]
Robert Scholte commented on MNG-6650:
-
Issue confirmed, but I don't think it is Java 11 related, it doesn't make sense
and I see it for Java 9 as well.
So I think it is a bug rather than regression related to profiles and boms in
general.
> Java11 Regression Bug: Transitive dependencies not resolved
> ---
>
> Key: MNG-6650
> URL: https://issues.apache.org/jira/browse/MNG-6650
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.6.0
> Environment: Works with Java 1.8
> Fails with Java 11
> Reproduced on Mac and Windows as well as in travis-ci (linux).
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: MNG-6650.tgz
>
>
> I have found a strange situation where maven seems to be unable to resolve
> transitive dependencies for a particular dependency but only in Java11+
> The failing build can be found here with all the analysis:
> [https://github.com/devonfw/devon4j/pull/82]
> As you can read there with all the details the error is related to a profile
> with
>
> [9,)
>
> That should fire on Java11 and seems to do but as a result all dependencies
> are eliminated in this case what seems like a strange maven bug.
> The Code to reproduce the issue locally can also be cloned from here:
> [https://github.com/hohwille/devon4j/tree/feature/16-java-11]
> (be sure to checkout this "feature/16-java-11" branch)
> After building you can even reduce and reproduce the error from
> {{templates/server/target/test-classes/projects/basic/project/basic}}
> Just "cd" there and run "mvn clean install" with Java1.8 and with Java11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6650) Java11 Regression Bug: Transitive dependencies not resolved
[
https://issues.apache.org/jira/browse/MNG-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833072#comment-16833072
]
Jörg Hohwiller commented on MNG-6650:
-
[^MNG-6650.tgz]
This archive contains a small POM and a very simple single Java class.
The Java class compiles with maven 3.6.0 in build with Java 1.8 but failes with
Java 11.
Can you please extract the archive and confirm that you can reproduce this
effect?
> Java11 Regression Bug: Transitive dependencies not resolved
> ---
>
> Key: MNG-6650
> URL: https://issues.apache.org/jira/browse/MNG-6650
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.6.0
> Environment: Works with Java 1.8
> Fails with Java 11
> Reproduced on Mac and Windows as well as in travis-ci (linux).
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: MNG-6650.tgz
>
>
> I have found a strange situation where maven seems to be unable to resolve
> transitive dependencies for a particular dependency but only in Java11+
> The failing build can be found here with all the analysis:
> [https://github.com/devonfw/devon4j/pull/82]
> As you can read there with all the details the error is related to a profile
> with
>
> [9,)
>
> That should fire on Java11 and seems to do but as a result all dependencies
> are eliminated in this case what seems like a strange maven bug.
> The Code to reproduce the issue locally can also be cloned from here:
> [https://github.com/hohwille/devon4j/tree/feature/16-java-11]
> (be sure to checkout this "feature/16-java-11" branch)
> After building you can even reduce and reproduce the error from
> {{templates/server/target/test-classes/projects/basic/project/basic}}
> Just "cd" there and run "mvn clean install" with Java1.8 and with Java11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MNG-6650) Java11 Regression Bug: Transitive dependencies not resolved
[
https://issues.apache.org/jira/browse/MNG-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833072#comment-16833072
]
Jörg Hohwiller edited comment on MNG-6650 at 5/4/19 2:45 PM:
-
[^MNG-6650.tgz]
This archive contains a small POM and a very simple single Java class.
The Java class compiles with maven 3.6.0 in build with Java 1.8 but fails with
Java 11.
Can you please extract the archive and confirm that you can reproduce this
effect?
was (Author: hohwille):
[^MNG-6650.tgz]
This archive contains a small POM and a very simple single Java class.
The Java class compiles with maven 3.6.0 in build with Java 1.8 but failes with
Java 11.
Can you please extract the archive and confirm that you can reproduce this
effect?
> Java11 Regression Bug: Transitive dependencies not resolved
> ---
>
> Key: MNG-6650
> URL: https://issues.apache.org/jira/browse/MNG-6650
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.6.0
> Environment: Works with Java 1.8
> Fails with Java 11
> Reproduced on Mac and Windows as well as in travis-ci (linux).
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: MNG-6650.tgz
>
>
> I have found a strange situation where maven seems to be unable to resolve
> transitive dependencies for a particular dependency but only in Java11+
> The failing build can be found here with all the analysis:
> [https://github.com/devonfw/devon4j/pull/82]
> As you can read there with all the details the error is related to a profile
> with
>
> [9,)
>
> That should fire on Java11 and seems to do but as a result all dependencies
> are eliminated in this case what seems like a strange maven bug.
> The Code to reproduce the issue locally can also be cloned from here:
> [https://github.com/hohwille/devon4j/tree/feature/16-java-11]
> (be sure to checkout this "feature/16-java-11" branch)
> After building you can even reduce and reproduce the error from
> {{templates/server/target/test-classes/projects/basic/project/basic}}
> Just "cd" there and run "mvn clean install" with Java1.8 and with Java11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6650) Java11 Regression Bug: Transitive dependencies not resolved
[
https://issues.apache.org/jira/browse/MNG-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Hohwiller updated MNG-6650:
Attachment: MNG-6650.tgz
> Java11 Regression Bug: Transitive dependencies not resolved
> ---
>
> Key: MNG-6650
> URL: https://issues.apache.org/jira/browse/MNG-6650
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.6.0
> Environment: Works with Java 1.8
> Fails with Java 11
> Reproduced on Mac and Windows as well as in travis-ci (linux).
>Reporter: Jörg Hohwiller
>Priority: Major
> Attachments: MNG-6650.tgz
>
>
> I have found a strange situation where maven seems to be unable to resolve
> transitive dependencies for a particular dependency but only in Java11+
> The failing build can be found here with all the analysis:
> [https://github.com/devonfw/devon4j/pull/82]
> As you can read there with all the details the error is related to a profile
> with
>
> [9,)
>
> That should fire on Java11 and seems to do but as a result all dependencies
> are eliminated in this case what seems like a strange maven bug.
> The Code to reproduce the issue locally can also be cloned from here:
> [https://github.com/hohwille/devon4j/tree/feature/16-java-11]
> (be sure to checkout this "feature/16-java-11" branch)
> After building you can even reduce and reproduce the error from
> {{templates/server/target/test-classes/projects/basic/project/basic}}
> Just "cd" there and run "mvn clean install" with Java1.8 and with Java11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] [maven-compiler-plugin] rhowe opened a new pull request #17: Miscellaneous code cleanups
rhowe opened a new pull request #17: Miscellaneous code cleanups URL: https://github.com/apache/maven-compiler-plugin/pull/17 These were the result of running the IntelliJ linter and picking the juiciest looking changes. Hopefully there's nothing too contentious here - see individual commits for details. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (DOXIA-592) Upgrade Markdown parser - flexmark-java to 0.42.8
Sylwester Lachiewicz created DOXIA-592: -- Summary: Upgrade Markdown parser - flexmark-java to 0.42.8 Key: DOXIA-592 URL: https://issues.apache.org/jira/browse/DOXIA-592 Project: Maven Doxia Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Upgrade parser library flexmark-java to latest version supported on Java 7 Changelog: https://github.com/vsch/flexmark-java/blob/master/VERSION.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DOXIA-576) Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient)
[ https://issues.apache.org/jira/browse/DOXIA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-576: --- Fix Version/s: 1.9 > Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient) > --- > > Key: DOXIA-576 > URL: https://issues.apache.org/jira/browse/DOXIA-576 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 1.9 > > > The following vulnerabilities are fixed with an upgrade: > [CVE-2011-1498|https://nvd.nist.gov/vuln/detail/CVE-2011-1498] > Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with > an authenticating proxy server, sends the Proxy-Authorization header to the > origin server, which allows remote web servers to obtain sensitive > information by logging this header. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30644] > [CVE-2012-6153|https://nvd.nist.gov/vuln/detail/CVE-2012-6153] > http/conn/ssl/AbstractVerifier.java in Apache Commons HttpClient before > 4.2.3 does not properly verify that the server hostname matches a domain name > in the subject's Common Name (CN) or subjectAltName field of the X.509 > certificate, which allows man-in-the-middle attackers to spoof SSL servers > via a certificate with a subject that specifies a common name in a field that > is not the CN field. NOTE: this issue exists because of an incomplete fix for > CVE-2012-5783. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30645] > [CVE-2014-3577|https://nvd.nist.gov/vuln/detail/CVE-2014-3577] > Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with > an authenticating proxy server, sends the Proxy-Authorization header to the > origin server, which allows remote web servers to obtain sensitive > information by logging this header. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30646] > [CVE-2015-5262|https://nvd.nist.gov/vuln/detail/CVE-2015-5262] > http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents > HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting > during an SSL handshake, which allows remote attackers to cause a denial of > service (HTTPS call hang) via unspecified vectors. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30647] > HTTPCLIENT-1803 > Affected versions of the package are vulnerable to Directory Traversal, > which may allow access to sensitive files and data on the server. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-31517] > Discovered with [Snyk.io|https://snyk.io/] scan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DOXIA-576) Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient)
[ https://issues.apache.org/jira/browse/DOXIA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-576: --- Description: The following vulnerabilities are fixed with an upgrade: [CVE-2011-1498|https://nvd.nist.gov/vuln/detail/CVE-2011-1498] Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with an authenticating proxy server, sends the Proxy-Authorization header to the origin server, which allows remote web servers to obtain sensitive information by logging this header. [Snyk.io details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30644] [CVE-2012-6153|https://nvd.nist.gov/vuln/detail/CVE-2012-6153] http/conn/ssl/AbstractVerifier.java in Apache Commons HttpClient before 4.2.3 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field. NOTE: this issue exists because of an incomplete fix for CVE-2012-5783. [Snyk.io details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30645] [CVE-2014-3577|https://nvd.nist.gov/vuln/detail/CVE-2014-3577] Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with an authenticating proxy server, sends the Proxy-Authorization header to the origin server, which allows remote web servers to obtain sensitive information by logging this header. [Snyk.io details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30646] [CVE-2015-5262|https://nvd.nist.gov/vuln/detail/CVE-2015-5262] http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting during an SSL handshake, which allows remote attackers to cause a denial of service (HTTPS call hang) via unspecified vectors. [Snyk.io details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30647] HTTPCLIENT-1803 Affected versions of the package are vulnerable to Directory Traversal, which may allow access to sensitive files and data on the server. [Snyk.io details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-31517] Discovered with [Snyk.io|https://snyk.io/] scan. was:Upgrade dependency version to address security improvements > Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient) > --- > > Key: DOXIA-576 > URL: https://issues.apache.org/jira/browse/DOXIA-576 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > > The following vulnerabilities are fixed with an upgrade: > [CVE-2011-1498|https://nvd.nist.gov/vuln/detail/CVE-2011-1498] > Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with > an authenticating proxy server, sends the Proxy-Authorization header to the > origin server, which allows remote web servers to obtain sensitive > information by logging this header. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30644] > [CVE-2012-6153|https://nvd.nist.gov/vuln/detail/CVE-2012-6153] > http/conn/ssl/AbstractVerifier.java in Apache Commons HttpClient before > 4.2.3 does not properly verify that the server hostname matches a domain name > in the subject's Common Name (CN) or subjectAltName field of the X.509 > certificate, which allows man-in-the-middle attackers to spoof SSL servers > via a certificate with a subject that specifies a common name in a field that > is not the CN field. NOTE: this issue exists because of an incomplete fix for > CVE-2012-5783. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30645] > [CVE-2014-3577|https://nvd.nist.gov/vuln/detail/CVE-2014-3577] > Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with > an authenticating proxy server, sends the Proxy-Authorization header to the > origin server, which allows remote web servers to obtain sensitive > information by logging this header. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30646] > [CVE-2015-5262|https://nvd.nist.gov/vuln/detail/CVE-2015-5262] > http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents > HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting > during an SSL handshake, which allows remote attackers to cause a denial of > service (HTTPS call hang) via unspecified vectors. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30647] > HTTPCLIENT-1803 > Affected versions of the package are vulnerable to Directory Traversal, > which may allow access to sensitive files and data on the server.
[jira] [Assigned] (DOXIA-576) Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient)
[ https://issues.apache.org/jira/browse/DOXIA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned DOXIA-576: -- Assignee: Sylwester Lachiewicz > Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient) > --- > > Key: DOXIA-576 > URL: https://issues.apache.org/jira/browse/DOXIA-576 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 1.9 > > > The following vulnerabilities are fixed with an upgrade: > [CVE-2011-1498|https://nvd.nist.gov/vuln/detail/CVE-2011-1498] > Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with > an authenticating proxy server, sends the Proxy-Authorization header to the > origin server, which allows remote web servers to obtain sensitive > information by logging this header. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30644] > [CVE-2012-6153|https://nvd.nist.gov/vuln/detail/CVE-2012-6153] > http/conn/ssl/AbstractVerifier.java in Apache Commons HttpClient before > 4.2.3 does not properly verify that the server hostname matches a domain name > in the subject's Common Name (CN) or subjectAltName field of the X.509 > certificate, which allows man-in-the-middle attackers to spoof SSL servers > via a certificate with a subject that specifies a common name in a field that > is not the CN field. NOTE: this issue exists because of an incomplete fix for > CVE-2012-5783. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30645] > [CVE-2014-3577|https://nvd.nist.gov/vuln/detail/CVE-2014-3577] > Apache HttpClient 4.x before 4.1.1 in Apache HttpComponents, when used with > an authenticating proxy server, sends the Proxy-Authorization header to the > origin server, which allows remote web servers to obtain sensitive > information by logging this header. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30646] > [CVE-2015-5262|https://nvd.nist.gov/vuln/detail/CVE-2015-5262] > http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents > HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting > during an SSL handshake, which allows remote attackers to cause a denial of > service (HTTPS call hang) via unspecified vectors. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30647] > HTTPCLIENT-1803 > Affected versions of the package are vulnerable to Directory Traversal, > which may allow access to sensitive files and data on the server. [Snyk.io > details|https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-31517] > Discovered with [Snyk.io|https://snyk.io/] scan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
