[jira] [Commented] (MINDEXER-105) README.md points to wrong issue tracker (Codehaus)
[
https://issues.apache.org/jira/browse/MINDEXER-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241693#comment-16241693
]
ASF GitHub Bot commented on MINDEXER-105:
-
Github user ebarboni commented on the issue:
https://github.com/apache/maven-indexer/pull/20
hi, if you edit the PR title to contains MINDEXER-105 it will connect the
githb to to the related jira issue.
> README.md points to wrong issue tracker (Codehaus)
> --
>
> Key: MINDEXER-105
> URL: https://issues.apache.org/jira/browse/MINDEXER-105
> Project: Maven Indexer
> Issue Type: Bug
>Reporter: Andreas Sewe
>Priority: Trivial
>
> The current {{README.md}}, as rendered at
> https://github.com/apache/maven-indexer/, points to the non-existent Codehaus
> JIRA. This should be updated to point here instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (MNG-6303) .mvn/jvm.config should allow to resolve environment variables
[
https://issues.apache.org/jira/browse/MNG-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240516#comment-16240516
]
Konrad Windszus edited comment on MNG-6303 at 11/7/17 9:31 AM:
---
A potential fix could be to replace
https://github.com/apache/maven/blob/master/apache-maven/src/bin/mvn#L170 by
{code}
cat "$1" | echo | tr -s '\n' ' '
{code}
That would allow basically every bourne shell feature to be used within at
least the {{.mvn/jvm.config}}. Of course an according fix need to be
implemented for Windows.
was (Author: kwin):
A potential fix could be to replace
https://github.com/apache/maven/blob/master/apache-maven/src/bin/mvn#L170 by
{code}
cat "$1" | echo | tr -s '\n' ' '
{code}
That would allow basically every bourne shell feature to be used within at
least the {{.mvn/jvm.config}}.
> .mvn/jvm.config should allow to resolve environment variables
> -
>
> Key: MNG-6303
> URL: https://issues.apache.org/jira/browse/MNG-6303
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 3.5.0
>Reporter: Konrad Windszus
>
> With the mechanism of having project-specific maven options being specified
> in {{.mvn/maven.config}} and {{.mvn/jvm.config}} (MNG-6267) it is often handy
> to share those settings among multiple developers (i.e. via maintaining it
> via the SCM). Unfortunately the mechanism does not support resolving
> environment variables, which makes it hard to deal with user-specific
> directories or settings. Please support resolving environment variables
> through a special pattern like {{$ENV_NAME}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINDEXER-106) ClassNotFoundException (org.sonatype.aether.version.InvalidVersionSpecificationException) under recent Maven versions
[
https://issues.apache.org/jira/browse/MINDEXER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241769#comment-16241769
]
Eric Barboni commented on MINDEXER-106:
---
Hi, is it an hadoc plugin you have issue with?
I have issue with this plugin yet.
https://github.com/mojohaus/nb-repository-plugin
If I use index-core 6.0 SNAPSHOT it works but break with the previous maven
3.0.5.
> ClassNotFoundException
> (org.sonatype.aether.version.InvalidVersionSpecificationException) under
> recent Maven versions
> -
>
> Key: MINDEXER-106
> URL: https://issues.apache.org/jira/browse/MINDEXER-106
> Project: Maven Indexer
> Issue Type: Bug
>Affects Versions: 5.1.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
>Reporter: Andreas Sewe
>
> It is impossible to use the latest released {{indexer-core}} (version 5.1.1)
> in a mojo executing under a recent version of Maven (3.5.0):
> {noformat}
> Caused by: java.lang.NoClassDefFoundError:
> org/sonatype/aether/version/InvalidVersionSpecificationException
> at
> org.apache.maven.index.context.IndexUtils.constructArtifactInfo(IndexUtils.java:111)
> at
> org.apache.maven.index.context.IndexUtils.updateDocument(IndexUtils.java:135)
> at
> org.apache.maven.index.updater.IndexDataReader.readIndex(IndexDataReader.java:92)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexData(DefaultIndexUpdater.java:509)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:197)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:76)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:642)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:862)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:157)
> ...
> Caused by: java.lang.ClassNotFoundException:
> org.sonatype.aether.version.InvalidVersionSpecificationException
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINDEXER-105) README.md points to wrong issue tracker (Codehaus)
[
https://issues.apache.org/jira/browse/MINDEXER-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241776#comment-16241776
]
ASF GitHub Bot commented on MINDEXER-105:
-
Github user sewe commented on the issue:
https://github.com/apache/maven-indexer/pull/20
> hi, if you edit the PR title to contains MINDEXER-105 it will connect the
githb to to the related jira issue.
@ebarboni Done.
> README.md points to wrong issue tracker (Codehaus)
> --
>
> Key: MINDEXER-105
> URL: https://issues.apache.org/jira/browse/MINDEXER-105
> Project: Maven Indexer
> Issue Type: Bug
>Reporter: Andreas Sewe
>Priority: Trivial
>
> The current {{README.md}}, as rendered at
> https://github.com/apache/maven-indexer/, points to the non-existent Codehaus
> JIRA. This should be updated to point here instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (MINDEXER-106) ClassNotFoundException (org.sonatype.aether.version.InvalidVersionSpecificationException) under recent Maven versions
[
https://issues.apache.org/jira/browse/MINDEXER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241769#comment-16241769
]
Eric Barboni edited comment on MINDEXER-106 at 11/7/17 10:13 AM:
-
Hi, is it an ad hoc plugin you have issue with?
I have issue with this plugin yet:
https://github.com/mojohaus/nb-repository-plugin
If I use index-core 6.0 SNAPSHOT it works but break with the previous maven
3.0.5.
was (Author: skygo):
Hi, is it an hadoc plugin you have issue with?
I have issue with this plugin yet.
https://github.com/mojohaus/nb-repository-plugin
If I use index-core 6.0 SNAPSHOT it works but break with the previous maven
3.0.5.
> ClassNotFoundException
> (org.sonatype.aether.version.InvalidVersionSpecificationException) under
> recent Maven versions
> -
>
> Key: MINDEXER-106
> URL: https://issues.apache.org/jira/browse/MINDEXER-106
> Project: Maven Indexer
> Issue Type: Bug
>Affects Versions: 5.1.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
>Reporter: Andreas Sewe
>
> It is impossible to use the latest released {{indexer-core}} (version 5.1.1)
> in a mojo executing under a recent version of Maven (3.5.0):
> {noformat}
> Caused by: java.lang.NoClassDefFoundError:
> org/sonatype/aether/version/InvalidVersionSpecificationException
> at
> org.apache.maven.index.context.IndexUtils.constructArtifactInfo(IndexUtils.java:111)
> at
> org.apache.maven.index.context.IndexUtils.updateDocument(IndexUtils.java:135)
> at
> org.apache.maven.index.updater.IndexDataReader.readIndex(IndexDataReader.java:92)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexData(DefaultIndexUpdater.java:509)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:197)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:76)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:642)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:862)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:157)
> ...
> Caused by: java.lang.ClassNotFoundException:
> org.sonatype.aether.version.InvalidVersionSpecificationException
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (MINDEXER-105) README.md points to wrong issue tracker (Codehaus)
[
https://issues.apache.org/jira/browse/MINDEXER-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) reassigned MINDEXER-105:
---
Assignee: Olivier Lamy (*$^¨%`£)
> README.md points to wrong issue tracker (Codehaus)
> --
>
> Key: MINDEXER-105
> URL: https://issues.apache.org/jira/browse/MINDEXER-105
> Project: Maven Indexer
> Issue Type: Bug
>Reporter: Andreas Sewe
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Trivial
> Fix For: 6.0
>
>
> The current {{README.md}}, as rendered at
> https://github.com/apache/maven-indexer/, points to the non-existent Codehaus
> JIRA. This should be updated to point here instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (MINDEXER-105) README.md points to wrong issue tracker (Codehaus)
[
https://issues.apache.org/jira/browse/MINDEXER-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) closed MINDEXER-105.
---
Resolution: Fixed
Fix Version/s: 6.0
> README.md points to wrong issue tracker (Codehaus)
> --
>
> Key: MINDEXER-105
> URL: https://issues.apache.org/jira/browse/MINDEXER-105
> Project: Maven Indexer
> Issue Type: Bug
>Reporter: Andreas Sewe
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Trivial
> Fix For: 6.0
>
>
> The current {{README.md}}, as rendered at
> https://github.com/apache/maven-indexer/, points to the non-existent Codehaus
> JIRA. This should be updated to point here instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MCOMPILER-315) "Older projects with module-info" documentation does not work
Keir created MCOMPILER-315: -- Summary: "Older projects with module-info" documentation does not work Key: MCOMPILER-315 URL: https://issues.apache.org/jira/browse/MCOMPILER-315 Project: Maven Compiler Plugin Issue Type: Bug Affects Versions: 3.7.0 Reporter: Keir Attachments: pom.xml I copied and pasted the 2nd snipped from https://maven.apache.org/plugins/maven-compiler-plugin/examples/module-info.html , amending it to refer to Java 8 rather than 6, however the jar produced by mvn package is still only consumable by Java 9 as all classes appear to have been compiled to its version. Is there something else I need to do to get this to work? If so, the documentation could be clearer. Or have I misunderstood something? I have attached the pom in question. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MCOMPILER-315) "Older projects with module-info" documentation does not work
[ https://issues.apache.org/jira/browse/MCOMPILER-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241836#comment-16241836 ] Keir commented on MCOMPILER-315: Would be also good to know if the executions mentioned (default-compile, base-compile) has special semantics? A quick google suggests default-compile does have special meaning however it doesn't seem to be referred to anywhere in official docs. > "Older projects with module-info" documentation does not work > - > > Key: MCOMPILER-315 > URL: https://issues.apache.org/jira/browse/MCOMPILER-315 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.7.0 >Reporter: Keir > Attachments: pom.xml > > > I copied and pasted the 2nd snipped from > https://maven.apache.org/plugins/maven-compiler-plugin/examples/module-info.html > , amending it to refer to Java 8 rather than 6, however the jar produced by > mvn package is still only consumable by Java 9 as all classes appear to have > been compiled to its version. Is there something else I need to do to get > this to work? If so, the documentation could be clearer. Or have I > misunderstood something? I have attached the pom in question. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WAGON-452) Missing exception handling when maven.wagon.http.ssl.ignore.validity.dates flag is set to 'true'
[ https://issues.apache.org/jira/browse/WAGON-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241936#comment-16241936 ] ASF GitHub Bot commented on WAGON-452: -- GitHub user DonnyDepp opened a pull request: https://github.com/apache/maven-wagon/pull/36 [WAGON-452] RelaxedTrustStrategy handle multiple certificates Ignoring ssl validity of dates is working, but in my case the server returns 3 (expired) certificates. With that RelaxedTrustStrategy always returned false. You can merge this pull request into a Git repository by running: $ git pull https://github.com/DonnyDepp/maven-wagon master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-wagon/pull/36.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #36 commit f825a855c58575808d215a37357ba90d38ff18ac Author: Andre Doeblitz Date: 2017-11-07T12:37:43Z [WAGON-452] RelaxedTrustStrategy handle multiple certificates Ignoring ssl validity of dates is working, but in my case the server returns 3 (expired) certificates. With that RelaxedTrustStrategy always returned false. > Missing exception handling when maven.wagon.http.ssl.ignore.validity.dates > flag is set to 'true' > > > Key: WAGON-452 > URL: https://issues.apache.org/jira/browse/WAGON-452 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http >Affects Versions: 2.10 >Reporter: Vítor Teixeira > Labels: easyfix, maven, security > Original Estimate: 24h > Remaining Estimate: 24h > > On org.apache.maven.wagon.providers.http.RelaxedTrustStrategy exception > handling is missing. > With maven.wagon.http.ssl.ignore.validity.dates=true the following exception > is thrown: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: timestamp check failed: > NotAfter: Tue Dec 29 23:59:59 GMT 2015 -> [Help 1] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WAGON-452) Missing exception handling when maven.wagon.http.ssl.ignore.validity.dates flag is set to 'true'
[ https://issues.apache.org/jira/browse/WAGON-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241986#comment-16241986 ] André Döblitz commented on WAGON-452: - Hello, sadly my company was late to renew their ssl certificates, so i had to use -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.ignore.validity.dates=true. More sadly this did not work in the latest maven release. maven.wagon.http.ssl.ignore.validity.dates builds up on maven.wagon.http.ssl.insecure. If insecure is true, then RelaxedTrustStrategy is created as TrustStrategy and validity.dates gets evaluated. RelaxedTrustStrategy checkmethod checks exactly one certificate and catches expiry-exception and throws it further if validity.dates is false. If validity.dates is true, the certificate check returns true. Later, depending on the TrustStrategy, RelaxedTrustStrategy checkmethod gets evaluated. If it returns true, no further checks are done. (So if validity.dates should be ignored, it returns true with an expired certificate.) But if it returns false, then sun.security.validator continues with further checks. sun.security.validator should not throw any ExpiryException when both flags are set true. In my case the Artifactory server had 3 certificates, so RelaxedTrustStrategy checkmethod always returned false, because "if ( certificates != null && certificates == 1 )" I changed it to check all given certificates. This works, any Exception will be handled in a proper way. But I dont know why the author intentionally limited the method to exactly 1 certificate. > Missing exception handling when maven.wagon.http.ssl.ignore.validity.dates > flag is set to 'true' > > > Key: WAGON-452 > URL: https://issues.apache.org/jira/browse/WAGON-452 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http >Affects Versions: 2.10 >Reporter: Vítor Teixeira > Labels: easyfix, maven, security > Original Estimate: 24h > Remaining Estimate: 24h > > On org.apache.maven.wagon.providers.http.RelaxedTrustStrategy exception > handling is missing. > With maven.wagon.http.ssl.ignore.validity.dates=true the following exception > is thrown: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: timestamp check failed: > NotAfter: Tue Dec 29 23:59:59 GMT 2015 -> [Help 1] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (WAGON-452) Missing exception handling when maven.wagon.http.ssl.ignore.validity.dates flag is set to 'true'
[ https://issues.apache.org/jira/browse/WAGON-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241986#comment-16241986 ] André Döblitz edited comment on WAGON-452 at 11/7/17 1:25 PM: -- Hello, sadly my company was late to renew their ssl certificates, so i had to use -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.ignore.validity.dates=true. More sadly this did not work in the latest maven release. maven.wagon.http.ssl.ignore.validity.dates builds up on maven.wagon.http.ssl.insecure. If insecure is true, then RelaxedTrustStrategy is created as TrustStrategy and validity.dates gets evaluated. RelaxedTrustStrategy checkmethod checks exactly one certificate and catches expiry-exception and throws it further if validity.dates is false. If validity.dates is true, the certificate check returns true. Later, depending on the TrustStrategy, RelaxedTrustStrategy checkmethod gets evaluated. If it returns true, no further checks are done. (So if validity.dates should be ignored, it returns true on an expired certificate.) But if it returns false, then sun.security.validator continues with further checks. sun.security.validator should not throw any ExpiryException when both flags are set true. In my case the Artifactory server had 3 certificates, so RelaxedTrustStrategy checkmethod always returned false, because "if ( certificates != null && certificates == 1 )" I changed it to check all given certificates. This works, any Exception will be handled in a proper way. But I dont know why the author intentionally limited the method to exactly 1 certificate. was (Author: donnydepp): Hello, sadly my company was late to renew their ssl certificates, so i had to use -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.ignore.validity.dates=true. More sadly this did not work in the latest maven release. maven.wagon.http.ssl.ignore.validity.dates builds up on maven.wagon.http.ssl.insecure. If insecure is true, then RelaxedTrustStrategy is created as TrustStrategy and validity.dates gets evaluated. RelaxedTrustStrategy checkmethod checks exactly one certificate and catches expiry-exception and throws it further if validity.dates is false. If validity.dates is true, the certificate check returns true. Later, depending on the TrustStrategy, RelaxedTrustStrategy checkmethod gets evaluated. If it returns true, no further checks are done. (So if validity.dates should be ignored, it returns true with an expired certificate.) But if it returns false, then sun.security.validator continues with further checks. sun.security.validator should not throw any ExpiryException when both flags are set true. In my case the Artifactory server had 3 certificates, so RelaxedTrustStrategy checkmethod always returned false, because "if ( certificates != null && certificates == 1 )" I changed it to check all given certificates. This works, any Exception will be handled in a proper way. But I dont know why the author intentionally limited the method to exactly 1 certificate. > Missing exception handling when maven.wagon.http.ssl.ignore.validity.dates > flag is set to 'true' > > > Key: WAGON-452 > URL: https://issues.apache.org/jira/browse/WAGON-452 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http >Affects Versions: 2.10 >Reporter: Vítor Teixeira > Labels: easyfix, maven, security > Original Estimate: 24h > Remaining Estimate: 24h > > On org.apache.maven.wagon.providers.http.RelaxedTrustStrategy exception > handling is missing. > With maven.wagon.http.ssl.ignore.validity.dates=true the following exception > is thrown: > sun.security.validator.ValidatorException: PKIX path validation failed: > java.security.cert.CertPathValidatorException: timestamp check failed: > NotAfter: Tue Dec 29 23:59:59 GMT 2015 -> [Help 1] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINDEXER-106) ClassNotFoundException (org.sonatype.aether.version.InvalidVersionSpecificationException) under recent Maven versions
[
https://issues.apache.org/jira/browse/MINDEXER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242042#comment-16242042
]
Andreas Sewe commented on MINDEXER-106:
---
{quote}
Hi, is it an ad hoc plugin you have issue with?
{quote}
It’s an internal plug-in, so I can’t (for now) release it to reproduce.
{quote}
I have issue with this plugin yet:
https://github.com/mojohaus/nb-repository-plugin
If I use index-core 6.0 SNAPSHOT it works but break with the previous maven
3.0.5.
{quote}
[~skygo], not sure I understand which combinations of Maven and the
{{nb-repository-plugin}} work and which do not. Can you please elaborate
(ideally with a {{mvn}} command-line), so that the {{maven-indexer}}
maintainers can reproduce this issue? Thank you.
> ClassNotFoundException
> (org.sonatype.aether.version.InvalidVersionSpecificationException) under
> recent Maven versions
> -
>
> Key: MINDEXER-106
> URL: https://issues.apache.org/jira/browse/MINDEXER-106
> Project: Maven Indexer
> Issue Type: Bug
>Affects Versions: 5.1.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
>Reporter: Andreas Sewe
>
> It is impossible to use the latest released {{indexer-core}} (version 5.1.1)
> in a mojo executing under a recent version of Maven (3.5.0):
> {noformat}
> Caused by: java.lang.NoClassDefFoundError:
> org/sonatype/aether/version/InvalidVersionSpecificationException
> at
> org.apache.maven.index.context.IndexUtils.constructArtifactInfo(IndexUtils.java:111)
> at
> org.apache.maven.index.context.IndexUtils.updateDocument(IndexUtils.java:135)
> at
> org.apache.maven.index.updater.IndexDataReader.readIndex(IndexDataReader.java:92)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexData(DefaultIndexUpdater.java:509)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:197)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:76)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:642)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:862)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:157)
> ...
> Caused by: java.lang.ClassNotFoundException:
> org.sonatype.aether.version.InvalidVersionSpecificationException
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1405) Allow provider to override default runOrder & RunOrderCalculator from surefire-api
[
https://issues.apache.org/jira/browse/SUREFIRE-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242208#comment-16242208
]
ASF GitHub Bot commented on SUREFIRE-1405:
--
GitHub user dipak-pawar opened a pull request:
https://github.com/apache/maven-surefire/pull/169
[SUREFIRE-1405] Allows user to extend RunOrder & RunOrderCalculator
* All supported runOrder options are hardCoded in RunOrder -
https://github.com/apache/maven-surefire/blob/master/surefire-api/src/main/java/org/apache/maven/surefire/util/RunOrder.java#L109
* With this implementation user can implement his own runOrder & it's
respective RunOrderCalculator.
Fixes: https://issues.apache.org/jira/browse/SUREFIRE-1405
**Implementation Details**
**How to create new RunOrder?**
To create new `runOrder` user has to implement `RunOrder` interface.
```java
public class YourRunOrder implements RunOrder
{
@Override
public String getName()
{
return "runOrderName";
}
@Override
public List> orderTestClasses( Collection>
scannedClasses,
RunOrderParameters
runOrderParameters, int threadCount )
{
// Add logic to order test classes for this runOrder.
return testClasses;
}
}
```
**How to define custom RunOrderCalculator?**
Implement `RunOrderCalculator` interface with logic you want to order test
classes.
e.g.
```java
public class YourRunOrderCalculator implements RunOrderCalculator {
private final RunOrderParameters runOrderParameters;
private final int threadCount;
private final RunOrder[] runOrder;
public YourRunOrderCalculator(RunOrderParameters runOrderParameters,
int threadCount) {
this.runOrder = runOrderParameters.getRunOrders();
this.runOrderParameters = runOrderParameters;
this.threadCount = threadCount;
}
// Add your logic to order test classes.
@Override
public TestsToRun orderTestClasses(TestsToRun scannedClasses) {
List> testClasses = new ArrayList>( 512 );
for ( Class scannedClass : scannedClasses )
{
testClasses.add( scannedClass );
}
final Collection> classes =
runOrder[0].orderTestClasses(testClasses, runOrderParameters, threadCount);
return new TestsToRun(new LinkedHashSet<>(classes));
}
}
```
**How to tell surefire to use custom `RunOrder` & `RunOrderCalculator`?**
We have `RunOrderProvider` spi to overwrite default runOrders &
`RunOrderCalculator` provided by surefire.
You need to registrar impl of RunOrderProvider in the file named
`META-INF/services/org.apache.maven.plugin.surefire.runorder.spi.RunOrderProvider`
in main resources.
File should contain fully qualified name of RunOrderProvider impl.
e.g.
`com.surefire.YourRunOrderProviderImpl`
Implementation of YourRunOrderProviderImpl is as follows:
```java
public class YourRunOrderProviderImpl implements RunOrderProvider
{
@Override
public Collection getRunOrders()
{
// here you can give all default runorders provided by surefire along
with custom runorder created above.
return Arrays.asList( ALPHABETICAL, FILESYSTEM, HOURLY,
RANDOM, REVERSE_ALPHABETICAL, BALANCED, FAILEDFIRST, new
YourRunOrder() );
}
@Override
public Integer priority()
{
return 1;
}
@Override
public RunOrderCalculator createRunOrderCalculator( RunOrderParameters
runOrderParameters, int threadCount )
{
return new YourRunOrderCalculator( runOrderParameters, threadCount
);
}
@Override
public Collection defaultRunOrder()
{
return Collections.singletonList( FILESYSTEM );
}
}
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dipak-pawar/maven-surefire
surefire_improvement
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-surefire/pull/169.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #169
commit 6735b1ef750c3bcd613d5998a313e5007dc37349
Author: Dipak Pawar
Date: 2017-08-23T15:33:08Z
[SUREFIRE-1405] Allows user to extend RunOrder & RunOrderCalculator
> Allow provider to override default runOrder & RunOrderCalculator from
> surefire-api
>
[GitHub] joshelser opened a new pull request #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena?
joshelser opened a new 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 ?bled and sidebar-navigation disabled Original work done in https://github.com/apache/maven-skins/pull/4/commits/f559695b03826158eb302e60b40d4924f28a8bf4 by Misty. This is an automated message from the Apache Git Service. To respond to the message, please log on 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] joshelser commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena?
joshelser commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena? URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-342601761 Old (unsubmitted) PR was apache/maven-skins#4 for those interested in the lineage. This is an automated message from the Apache Git Service. To respond to the message, please log on 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] (MSKINS-137) Enable "Hamburger menu" with top-nav only
Josh Elser created MSKINS-137: - Summary: 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 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 (v6.4.14#64029)
[jira] [Commented] (MSKINS-137) Enable "Hamburger menu" with top-nav only
[ https://issues.apache.org/jira/browse/MSKINS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242757#comment-16242757 ] ASF GitHub Bot commented on MSKINS-137: --- joshelser opened a new 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 …bled and sidebar-navigation disabled Original work done in https://github.com/apache/maven-skins/pull/4/commits/f559695b03826158eb302e60b40d4924f28a8bf4 by Misty. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > 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 > > 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 (v6.4.14#64029)
[jira] [Commented] (MSKINS-137) Enable "Hamburger menu" with top-nav only
[ https://issues.apache.org/jira/browse/MSKINS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242760#comment-16242760 ] ASF GitHub Bot commented on MSKINS-137: --- joshelser commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena… URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-342601761 Old (unsubmitted) PR was apache/maven-skins#4 for those interested in the lineage. This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > 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 > > 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 (v6.4.14#64029)
[jira] [Created] (MSITE-800) site:deploy
Ernst Reissner created MSITE-800: Summary: site:deploy Key: MSITE-800 URL: https://issues.apache.org/jira/browse/MSITE-800 Project: Maven Site Plugin Issue Type: Bug Environment: any Reporter: Ernst Reissner Lack in documentation: for goal site:deploy one needs in distributionManagement of the pom somenthing like fileSite file:///home/ernst/Software/RepositoryTarget/Site instead of fileRepository file:///home/ernst/Software/RepositoryTarget This shall be documented on teh site. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] hboutemy commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena?
hboutemy commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena? URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-342725018 Hi Josh, Thank you for your help: I'm very interested to merge. But I don't understand what this change does: can you describe a little bit the issue (what a "hamburger menu" is)? Is there one existing IT that show clearly the issue (then the fix)? Sidenote: this is a generic topic with Skins, ie understanding html/css changes. Any generic idea on how to describe an issue and a fix, between "designer oriented" people (who are html/css experts) and "java dev" oriented people (like Maven developpers, like me, who is not proficient at all with modern html/css, who need to judge before merging...) This is an automated message from the Apache Git Service. To respond to the message, please log on 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] hboutemy commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena?
hboutemy commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena? URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-342725018 Hi Josh, Thank you for your help: I'm very interested to merge. But I don't understand what this change does: can you describe a little bit the issue (what a "hamburger menu" is)? Is there one existing IT that show clearly the issue (then the fix)? Sidenote: this is a generic topic with Skins, ie understanding html/css changes. Any generic idea on how to describe an issue and a fix, between "designer oriented" people (who are html/css experts) and "java dev" oriented people (like Maven developpers, like me, who is not proficient at all with modern html/css, who need to judge before merging...) At least, I'm happy that Git migration already has given one great result: more effective discussion on PRs Regards, Herv? This is an automated message from the Apache Git Service. To respond to the message, please log on 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] hboutemy commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena?
hboutemy commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena? URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-342725018 Hi Josh, Thank you for your help: I'm very interested to merge. But I don't understand what this change does: can you describe a little bit the issue (what a "hamburger menu" is)? Is there one existing IT that show clearly the issue (then the fix)? Sidenote: this is a generic topic with Skins, ie understanding html/css changes. Any generic idea on how to describe an issue and a fix, between "designer oriented" people (who are html/css experts) and "java dev" oriented people (like Maven developpers, like me, who is not proficient at all with modern html/css, who need to judge before merging...) At least, I'm happy that Git migration already has given one great result: more effective discussion on PRs (I could easily merge the PR locally and run the ITs, but did not find where to look for improved "hamburger menus"... :) ) Regards, Herv? This is an automated message from the Apache Git Service. To respond to the message, please log on 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-137) Enable "Hamburger menu" with top-nav only
[ https://issues.apache.org/jira/browse/MSKINS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243449#comment-16243449 ] ASF GitHub Bot commented on MSKINS-137: --- hboutemy commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena… URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-342725018 Hi Josh, Thank you for your help: I'm very interested to merge. But I don't understand what this change does: can you describe a little bit the issue (what a "hamburger menu" is)? Is there one existing IT that show clearly the issue (then the fix)? Sidenote: this is a generic topic with Skins, ie understanding html/css changes. Any generic idea on how to describe an issue and a fix, between "designer oriented" people (who are html/css experts) and "java dev" oriented people (like Maven developpers, like me, who is not proficient at all with modern html/css, who need to judge before merging...) This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > 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 > > 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 (v6.4.14#64029)
[jira] [Commented] (MSKINS-137) Enable "Hamburger menu" with top-nav only
[ https://issues.apache.org/jira/browse/MSKINS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243452#comment-16243452 ] ASF GitHub Bot commented on MSKINS-137: --- hboutemy commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena… URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-342725018 Hi Josh, Thank you for your help: I'm very interested to merge. But I don't understand what this change does: can you describe a little bit the issue (what a "hamburger menu" is)? Is there one existing IT that show clearly the issue (then the fix)? Sidenote: this is a generic topic with Skins, ie understanding html/css changes. Any generic idea on how to describe an issue and a fix, between "designer oriented" people (who are html/css experts) and "java dev" oriented people (like Maven developpers, like me, who is not proficient at all with modern html/css, who need to judge before merging...) At least, I'm happy that Git migration already has given one great result: more effective discussion on PRs (I could easily merge the PR locally and run the ITs, but did not find where to look for improved "hamburger menus"... :) ) Regards, Hervé This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > 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 > > 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 (v6.4.14#64029)
[jira] [Commented] (MSKINS-137) Enable "Hamburger menu" with top-nav only
[ https://issues.apache.org/jira/browse/MSKINS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243451#comment-16243451 ] ASF GitHub Bot commented on MSKINS-137: --- hboutemy commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena… URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-342725018 Hi Josh, Thank you for your help: I'm very interested to merge. But I don't understand what this change does: can you describe a little bit the issue (what a "hamburger menu" is)? Is there one existing IT that show clearly the issue (then the fix)? Sidenote: this is a generic topic with Skins, ie understanding html/css changes. Any generic idea on how to describe an issue and a fix, between "designer oriented" people (who are html/css experts) and "java dev" oriented people (like Maven developpers, like me, who is not proficient at all with modern html/css, who need to judge before merging...) At least, I'm happy that Git migration already has given one great result: more effective discussion on PRs Regards, Hervé This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > 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 > > 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 (v6.4.14#64029)
[jira] [Updated] (MSITE-800) site:deploy
[
https://issues.apache.org/jira/browse/MSITE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MSITE-800:
Description:
Lack in documentation:
for goal {{site:deploy}} one needs in distributionManagement of the pom
something like
{code:xml}
fileSite
file:///home/ernst/Software/RepositoryTarget/Site
{code}
instead of
{code:xml}
fileRepository
file:///home/ernst/Software/RepositoryTarget
{code}
This shall be documented on the site.
was:
Lack in documentation:
for goal site:deploy one needs in distributionManagement of the pom somenthing
like
fileSite
file:///home/ernst/Software/RepositoryTarget/Site
instead of
fileRepository
file:///home/ernst/Software/RepositoryTarget
This shall be documented on teh site.
> site:deploy
> ---
>
> Key: MSITE-800
> URL: https://issues.apache.org/jira/browse/MSITE-800
> Project: Maven Site Plugin
> Issue Type: Bug
> Environment: any
>Reporter: Ernst Reissner
>
> Lack in documentation:
> for goal {{site:deploy}} one needs in distributionManagement of the pom
> something like
> {code:xml}
> fileSite
> file:///home/ernst/Software/RepositoryTarget/Site
> {code}
> instead of
> {code:xml}
> fileRepository
> file:///home/ernst/Software/RepositoryTarget
> {code}
> This shall be documented on the site.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MSITE-800) site:deploy
[
https://issues.apache.org/jira/browse/MSITE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243456#comment-16243456
]
Hervé Boutemy commented on MSITE-800:
-
thanks for your feedback
any pointer on where you're looking at, please?
and any idea on how to add the info you find missing?
> site:deploy
> ---
>
> Key: MSITE-800
> URL: https://issues.apache.org/jira/browse/MSITE-800
> Project: Maven Site Plugin
> Issue Type: Bug
> Environment: any
>Reporter: Ernst Reissner
>
> Lack in documentation:
> for goal {{site:deploy}} one needs in distributionManagement of the pom
> something like
> {code:xml}
> fileSite
> file:///home/ernst/Software/RepositoryTarget/Site
> {code}
> instead of
> {code:xml}
> fileRepository
> file:///home/ernst/Software/RepositoryTarget
> {code}
> This shall be documented on the site.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-6303) .mvn/jvm.config should allow to resolve environment variables
[
https://issues.apache.org/jira/browse/MNG-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243458#comment-16243458
]
Hervé Boutemy commented on MNG-6303:
are you able to provide a sample project that would show the difference with
the fix, so we can change it into an IT, please?
> .mvn/jvm.config should allow to resolve environment variables
> -
>
> Key: MNG-6303
> URL: https://issues.apache.org/jira/browse/MNG-6303
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 3.5.0
>Reporter: Konrad Windszus
>
> With the mechanism of having project-specific maven options being specified
> in {{.mvn/maven.config}} and {{.mvn/jvm.config}} (MNG-6267) it is often handy
> to share those settings among multiple developers (i.e. via maintaining it
> via the SCM). Unfortunately the mechanism does not support resolving
> environment variables, which makes it hard to deal with user-specific
> directories or settings. Please support resolving environment variables
> through a special pattern like {{$ENV_NAME}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
