[jira] [Commented] (MINDEXER-108) Lift restriction on leading wildcard queries
[
https://issues.apache.org/jira/browse/MINDEXER-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265041#comment-16265041
]
Andreas Sewe commented on MINDEXER-108:
---
> What versions of lucene accepts * as prefix? Current master uses Lucene 5.x
> and it does not accept it...
I am using Lucene 5.4.4 (haven’t changed that from the current master). After
uncommenting the above {{ParseException}}-throwing in {{indexer-core}} code, it
happily runs queries like {{(#g:*.maven)}}, which I build like this
{noformat}
queryCreator.constructQuery(MAVEN.GROUP_ID, new
SearchTypedStringSearchExpression("*.maven", SearchType.EXACT))
{noformat}
and run using {{indexer.searchIterator(...)}}.
That being said, the Maven Indexer still logs the following:
{noformat}
[DEBUG] Executing unbounded search, and fitting topHitCounts to 12537, an OOMEx
might follow. To avoid OOM use narrower queries or limit your expectancy with
request.setCount() method where appropriate. See MINDEXER-14 for details.
{noformat}
AFAICT, the {{IteratorSearchResponse}} contains all results, so that warning
seems inappropriate; MINDEXER-14 has been marked as fixed, after all.)
> Lift restriction on leading wildcard queries
>
>
> Key: MINDEXER-108
> URL: https://issues.apache.org/jira/browse/MINDEXER-108
> Project: Maven Indexer
> Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Andreas Sewe
> Fix For: 6.0
>
>
> The {{DefaultQueryCreator}} prevents queries with leading wildcard:
> {noformat}
> if ( query.startsWith( "*" ) || query.startsWith( "?" ) )
> {
> throw new ParseException( "Query cannot start with '*' or '?'!" );
> }
> {noformat}
> While this was necessary in older versions of Lucene, the version used now
> happily executes such queries. The restriction can thus be lifted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINDEXER-108) Lift restriction on leading wildcard queries
[
https://issues.apache.org/jira/browse/MINDEXER-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265074#comment-16265074
]
ASF GitHub Bot commented on MINDEXER-108:
-
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-indexer/pull/22
MINDEXER-108: Lift the wildcard prefix restriction
MINDEXER-108: lift the prefix restriction
Historically Lucene needed this, but latest versions
can cope with it. This is still OOM prone, so use with care,
but the possibility is here.
Note: PR build on https://github.com/apache/maven-indexer/pull/21 (hence,
keep in mind while review).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cstamas/maven-indexer mindexer-108
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-indexer/pull/22.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 #22
commit ad07405c06b422cb529d3badaa1b6b376699c9c1
Author: Tamas Cservenak
Date: 2017-11-23T11:01:56Z
Prepare for next major release (6.x)
Changes:
- update parent pom
- update dependencies (but remain Java7!)
- update sisu (drop sonatype guice, use vanilla guice)
- update to maven-resolver (from aether)
No source changes happened.
commit fc801678e2e46513e4dda8973bcb06ef4f105b69
Author: Tamas Cservenak
Date: 2017-11-23T15:05:51Z
switch to archetype-catalog dep
As we really just provide helper class to implement
org.apache.maven.archetype.source.ArchetypeDataSource
commit 0d8b480a9a0434b386a0c494d44fb59e0c23618f
Author: Tamas Cservenak
Date: 2017-11-24T09:30:20Z
MINDEXER-108: lift the prefix restriction
Historically Lucene needed this, but latest versions
can cope with it. This is still OOM prone, so use with care,
but the possibility is here.
> Lift restriction on leading wildcard queries
>
>
> Key: MINDEXER-108
> URL: https://issues.apache.org/jira/browse/MINDEXER-108
> Project: Maven Indexer
> Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Andreas Sewe
> Fix For: 6.0
>
>
> The {{DefaultQueryCreator}} prevents queries with leading wildcard:
> {noformat}
> if ( query.startsWith( "*" ) || query.startsWith( "?" ) )
> {
> throw new ParseException( "Query cannot start with '*' or '?'!" );
> }
> {noformat}
> While this was necessary in older versions of Lucene, the version used now
> happily executes such queries. The restriction can thus be lifted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (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:all-tabpanel
]
Cservenak, Tamas closed MINDEXER-106.
-
Resolution: Fixed
Release 6.x makes maven-indexer compatible with maven 3.1+. With it, now same
problem will stand for 3.0- line of maven, but they can still use older
releases.
> 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
> Fix For: 6.0
>
>
> 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-108) Lift restriction on leading wildcard queries
[
https://issues.apache.org/jira/browse/MINDEXER-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cservenak, Tamas reassigned MINDEXER-108:
-
Assignee: Cservenak, Tamas
> Lift restriction on leading wildcard queries
>
>
> Key: MINDEXER-108
> URL: https://issues.apache.org/jira/browse/MINDEXER-108
> Project: Maven Indexer
> Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Andreas Sewe
>Assignee: Cservenak, Tamas
> Fix For: 6.0
>
>
> The {{DefaultQueryCreator}} prevents queries with leading wildcard:
> {noformat}
> if ( query.startsWith( "*" ) || query.startsWith( "?" ) )
> {
> throw new ParseException( "Query cannot start with '*' or '?'!" );
> }
> {noformat}
> While this was necessary in older versions of Lucene, the version used now
> happily executes such queries. The restriction can thus be lifted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MINDEXER-87) Remove legacy marked code
[ https://issues.apache.org/jira/browse/MINDEXER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cservenak, Tamas updated MINDEXER-87: - Fix Version/s: (was: 6.0) > Remove legacy marked code > - > > Key: MINDEXER-87 > URL: https://issues.apache.org/jira/browse/MINDEXER-87 > Project: Maven Indexer > Issue Type: Bug >Reporter: Cservenak, Tamas > > Remove legacy code and also some of the unneded cruft (yes, we do plan to > break API a bit). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MINDEXER-83) Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new ones) so that it is possible to add artifact files one by one
[ https://issues.apache.org/jira/browse/MINDEXER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cservenak, Tamas reassigned MINDEXER-83: Assignee: Cservenak, Tamas > Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new > ones) so that it is possible to add artifact files one by one > -- > > Key: MINDEXER-83 > URL: https://issues.apache.org/jira/browse/MINDEXER-83 > Project: Maven Indexer > Issue Type: Task >Reporter: Martin Todorov >Assignee: Cservenak, Tamas > Fix For: 6.0 > > > The currently existing method only accepts a list of files. This assumes you > already have a list of the files. However, this is inconvenient for use if > you have the artifact files coming one by one (for example when deploying an > artifact over over HTTP). > This method should be re-worked and it would be great if some new methods > could be introduced for when adding files which belong to a particular > artifact. > It would also be great if there could be methods that accept (File file, > Artifact artifact, ..) when adding and updating an artifact to the index. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINDEXER-87) Remove legacy marked code
[
https://issues.apache.org/jira/browse/MINDEXER-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265131#comment-16265131
]
Cservenak, Tamas commented on MINDEXER-87:
--
Moving out of 6.x release, as according to ML feedback, folks are using
(locally built) master, and this change may introduce incompatible changes (as
new API, the {{Indexer}} does not fully cover {{NexusIndexer}}, so moving post
6.0
> Remove legacy marked code
> -
>
> Key: MINDEXER-87
> URL: https://issues.apache.org/jira/browse/MINDEXER-87
> Project: Maven Indexer
> Issue Type: Bug
>Reporter: Cservenak, Tamas
>
> Remove legacy code and also some of the unneded cruft (yes, we do plan to
> break API a bit).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINDEXER-83) Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new ones) so that it is possible to add artifact files one by one
[ https://issues.apache.org/jira/browse/MINDEXER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265135#comment-16265135 ] Cservenak, Tamas commented on MINDEXER-83: -- "Sneaked" into PR https://github.com/apache/maven-indexer/pull/21 > Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new > ones) so that it is possible to add artifact files one by one > -- > > Key: MINDEXER-83 > URL: https://issues.apache.org/jira/browse/MINDEXER-83 > Project: Maven Indexer > Issue Type: Task >Reporter: Martin Todorov >Assignee: Cservenak, Tamas > Fix For: 6.0 > > > The currently existing method only accepts a list of files. This assumes you > already have a list of the files. However, this is inconvenient for use if > you have the artifact files coming one by one (for example when deploying an > artifact over over HTTP). > This method should be re-worked and it would be great if some new methods > could be introduced for when adding files which belong to a particular > artifact. > It would also be great if there could be methods that accept (File file, > Artifact artifact, ..) when adding and updating an artifact to the index. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINDEXER-81) Make ArtifactInfo extensible
[ https://issues.apache.org/jira/browse/MINDEXER-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265136#comment-16265136 ] Cservenak, Tamas commented on MINDEXER-81: -- Completely agreed and the comment above is in agreement with foreseen change. Still, am moving this change out of 6.0 release, as it would introduce breaking change (ArtifactInfo would need to be rewritten), will be done post 6.0 > Make ArtifactInfo extensible > > > Key: MINDEXER-81 > URL: https://issues.apache.org/jira/browse/MINDEXER-81 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Cservenak, Tamas > > Make ArtifactInfo extensible, a followup of MINDEXER-32 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MINDEXER-81) Make ArtifactInfo extensible
[ https://issues.apache.org/jira/browse/MINDEXER-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cservenak, Tamas updated MINDEXER-81: - Fix Version/s: (was: 6.0) > Make ArtifactInfo extensible > > > Key: MINDEXER-81 > URL: https://issues.apache.org/jira/browse/MINDEXER-81 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Cservenak, Tamas > > Make ArtifactInfo extensible, a followup of MINDEXER-32 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINDEXER-24) Publish indexer site
[ https://issues.apache.org/jira/browse/MINDEXER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265139#comment-16265139 ] Cservenak, Tamas commented on MINDEXER-24: -- Do we need anything more with this issue? Or should I move it out of 6.0 fix version to continue with release? > Publish indexer site > > > Key: MINDEXER-24 > URL: https://issues.apache.org/jira/browse/MINDEXER-24 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Cservenak, Tamas > Fix For: 6.0 > > > Publish indexer site > http://maven.apache.org/maven-indexer -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MINDEXER-88) Clean up the plugin versions and possibly upgrade the plugins to their latest versions
[
https://issues.apache.org/jira/browse/MINDEXER-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cservenak, Tamas reassigned MINDEXER-88:
Assignee: Cservenak, Tamas
> Clean up the plugin versions and possibly upgrade the plugins to their latest
> versions
> --
>
> Key: MINDEXER-88
> URL: https://issues.apache.org/jira/browse/MINDEXER-88
> Project: Maven Indexer
> Issue Type: Task
>Reporter: Martin Todorov
>Assignee: Cservenak, Tamas
> Fix For: 6.0
>
>
> When building with Maven 3.2.1, the following warning can be seen:
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-core:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-cli:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-examples:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:maven-indexer:pom:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 499, column
> 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> {code}
> Essentially, these versions should be set and furthermore, the plugin
> versions should be updated to their latest versions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (MINDEXER-88) Clean up the plugin versions and possibly upgrade the plugins to their latest versions
[
https://issues.apache.org/jira/browse/MINDEXER-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cservenak, Tamas reopened MINDEXER-88:
--
> Clean up the plugin versions and possibly upgrade the plugins to their latest
> versions
> --
>
> Key: MINDEXER-88
> URL: https://issues.apache.org/jira/browse/MINDEXER-88
> Project: Maven Indexer
> Issue Type: Task
>Reporter: Martin Todorov
>Assignee: Cservenak, Tamas
> Fix For: 6.0
>
>
> When building with Maven 3.2.1, the following warning can be seen:
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-core:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-cli:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-examples:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:maven-indexer:pom:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 499, column
> 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> {code}
> Essentially, these versions should be set and furthermore, the plugin
> versions should be updated to their latest versions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MENFORCER-287) Exclusion of dependencies in a deeper level are ignored
Tomas Tulka created MENFORCER-287: - Summary: Exclusion of dependencies in a deeper level are ignored Key: MENFORCER-287 URL: https://issues.apache.org/jira/browse/MENFORCER-287 Project: Maven Enforcer Plugin Issue Type: Bug Affects Versions: 3.0.0-M1 Environment: Apache Maven 3.3.9, jdk1.8.0_111, OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" Reporter: Tomas Tulka Attachments: pom.xml Dependency Convergence returns an error even when the conflicting version is excluded (in a deeper level): com.fasterxml.jackson.core jackson-core 2.6.3 com.vi cloudwatch-log4j-appender 1.3 commons-logging commons-logging com.fasterxml.jackson.core jackson-core com.fasterxml.jackson.core jackson-databind Result: Dependency convergence error for com.fasterxml.jackson.core:jackson-core:2.6.3 paths to dependency are: +-com.mycompany:MavenDependencyConvergenceEval:1.0-SNAPSHOT +-com.fasterxml.jackson.core:jackson-core:2.6.3 and +-com.mycompany:MavenDependencyConvergenceEval:1.0-SNAPSHOT +-com.vi:cloudwatch-log4j-appender:1.3 +-com.amazonaws:aws-java-sdk-logs:1.11.5 +-com.amazonaws:aws-java-sdk-core:1.11.5 +-com.fasterxml.jackson.core:jackson-databind:2.6.6 +-com.fasterxml.jackson.core:jackson-core:2.6.6 and +-com.mycompany:MavenDependencyConvergenceEval:1.0-SNAPSHOT +-com.vi:cloudwatch-log4j-appender:1.3 +-com.amazonaws:aws-java-sdk-logs:1.11.5 +-com.amazonaws:aws-java-sdk-core:1.11.5 +-com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:2.6.6 +-com.fasterxml.jackson.core:jackson-core:2.6.6 There is actually only one version of dependency com.fasterxml.jackson.core:jackson-core: [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ MavenDependencyConvergenceEval --- [INFO] com.mycompany:MavenDependencyConvergenceEval:pom:1.0-SNAPSHOT [INFO] +- com.fasterxml.jackson.core:jackson-core:jar:2.6.3:compile [INFO] \- com.vi:cloudwatch-log4j-appender:jar:1.3:compile [INFO]+- org.apache.logging.log4j:log4j-core:jar:2.5:compile [INFO]| \- org.apache.logging.log4j:log4j-api:jar:2.5:compile [INFO]\- com.amazonaws:aws-java-sdk-logs:jar:1.11.5:compile [INFO] \- com.amazonaws:aws-java-sdk-core:jar:1.11.5:compile [INFO] +- org.apache.httpcomponents:httpclient:jar:4.5.2:compile [INFO] | +- org.apache.httpcomponents:httpcore:jar:4.4.4:compile [INFO] | \- commons-codec:commons-codec:jar:1.9:compile [INFO] +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.6:compile [INFO] | \- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.0:compile [INFO] +- com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:2.6.6:compile [INFO] \- joda-time:joda-time:jar:2.8.1:compile -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MINDEXER-88) Clean up the plugin versions and possibly upgrade the plugins to their latest versions
[
https://issues.apache.org/jira/browse/MINDEXER-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cservenak, Tamas closed MINDEXER-88.
Resolution: Fixed
> Clean up the plugin versions and possibly upgrade the plugins to their latest
> versions
> --
>
> Key: MINDEXER-88
> URL: https://issues.apache.org/jira/browse/MINDEXER-88
> Project: Maven Indexer
> Issue Type: Task
>Reporter: Martin Todorov
>Assignee: Cservenak, Tamas
> Fix For: 6.0
>
>
> When building with Maven 3.2.1, the following warning can be seen:
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-core:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-cli:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-examples:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:maven-indexer:pom:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 499, column
> 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> {code}
> Essentially, these versions should be set and furthermore, the plugin
> versions should be updated to their latest versions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINDEXER-88) Clean up the plugin versions and possibly upgrade the plugins to their latest versions
[
https://issues.apache.org/jira/browse/MINDEXER-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265215#comment-16265215
]
Cservenak, Tamas commented on MINDEXER-88:
--
https://github.com/apache/maven-indexer/commit/ad07405c06b422cb529d3badaa1b6b376699c9c1
https://github.com/apache/maven-indexer/commit/fc801678e2e46513e4dda8973bcb06ef4f105b69
> Clean up the plugin versions and possibly upgrade the plugins to their latest
> versions
> --
>
> Key: MINDEXER-88
> URL: https://issues.apache.org/jira/browse/MINDEXER-88
> Project: Maven Indexer
> Issue Type: Task
>Reporter: Martin Todorov
>Assignee: Cservenak, Tamas
> Fix For: 6.0
>
>
> When building with Maven 3.2.1, the following warning can be seen:
> {code}
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-core:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-cli:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:indexer-examples:jar:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @
> org.apache.maven.indexer:maven-indexer:6.0-SNAPSHOT,
> /root/.jenkins/jobs/maven-indexer/workspace/pom.xml, line 499, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.maven.indexer:maven-indexer:pom:6.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. @ line 499, column
> 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> {code}
> Essentially, these versions should be set and furthermore, the plugin
> versions should be updated to their latest versions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINDEXER-108) Lift restriction on leading wildcard queries
[
https://issues.apache.org/jira/browse/MINDEXER-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265220#comment-16265220
]
ASF GitHub Bot commented on MINDEXER-108:
-
Github user asfgit closed the pull request at:
https://github.com/apache/maven-indexer/pull/22
> Lift restriction on leading wildcard queries
>
>
> Key: MINDEXER-108
> URL: https://issues.apache.org/jira/browse/MINDEXER-108
> Project: Maven Indexer
> Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Andreas Sewe
>Assignee: Cservenak, Tamas
> Fix For: 6.0
>
>
> The {{DefaultQueryCreator}} prevents queries with leading wildcard:
> {noformat}
> if ( query.startsWith( "*" ) || query.startsWith( "?" ) )
> {
> throw new ParseException( "Query cannot start with '*' or '?'!" );
> }
> {noformat}
> While this was necessary in older versions of Lucene, the version used now
> happily executes such queries. The restriction can thus be lifted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINDEXER-83) Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new ones) so that it is possible to add artifact files one by one
[ https://issues.apache.org/jira/browse/MINDEXER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265223#comment-16265223 ] ASF GitHub Bot commented on MINDEXER-83: Github user cstamas closed the pull request at: https://github.com/apache/maven-indexer/pull/21 > Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new > ones) so that it is possible to add artifact files one by one > -- > > Key: MINDEXER-83 > URL: https://issues.apache.org/jira/browse/MINDEXER-83 > Project: Maven Indexer > Issue Type: Task >Reporter: Martin Todorov >Assignee: Cservenak, Tamas > Fix For: 6.0 > > > The currently existing method only accepts a list of files. This assumes you > already have a list of the files. However, this is inconvenient for use if > you have the artifact files coming one by one (for example when deploying an > artifact over over HTTP). > This method should be re-worked and it would be great if some new methods > could be introduced for when adding files which belong to a particular > artifact. > It would also be great if there could be methods that accept (File file, > Artifact artifact, ..) when adding and updating an artifact to the index. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MINDEXER-108) Lift restriction on leading wildcard queries
[
https://issues.apache.org/jira/browse/MINDEXER-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cservenak, Tamas closed MINDEXER-108.
-
Resolution: Fixed
> Lift restriction on leading wildcard queries
>
>
> Key: MINDEXER-108
> URL: https://issues.apache.org/jira/browse/MINDEXER-108
> Project: Maven Indexer
> Issue Type: Improvement
>Affects Versions: 6.0
>Reporter: Andreas Sewe
>Assignee: Cservenak, Tamas
> Fix For: 6.0
>
>
> The {{DefaultQueryCreator}} prevents queries with leading wildcard:
> {noformat}
> if ( query.startsWith( "*" ) || query.startsWith( "?" ) )
> {
> throw new ParseException( "Query cannot start with '*' or '?'!" );
> }
> {noformat}
> While this was necessary in older versions of Lucene, the version used now
> happily executes such queries. The restriction can thus be lifted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (MINDEXER-83) Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new ones) so that it is possible to add artifact files one by one
[ https://issues.apache.org/jira/browse/MINDEXER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cservenak, Tamas closed MINDEXER-83. Resolution: Fixed > Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new > ones) so that it is possible to add artifact files one by one > -- > > Key: MINDEXER-83 > URL: https://issues.apache.org/jira/browse/MINDEXER-83 > Project: Maven Indexer > Issue Type: Task >Reporter: Martin Todorov >Assignee: Cservenak, Tamas > Fix For: 6.0 > > > The currently existing method only accepts a list of files. This assumes you > already have a list of the files. However, this is inconvenient for use if > you have the artifact files coming one by one (for example when deploying an > artifact over over HTTP). > This method should be re-worked and it would be great if some new methods > could be introduced for when adding files which belong to a particular > artifact. > It would also be great if there could be methods that accept (File file, > Artifact artifact, ..) when adding and updating an artifact to the index. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINDEXER-83) Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new ones) so that it is possible to add artifact files one by one
[ https://issues.apache.org/jira/browse/MINDEXER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265224#comment-16265224 ] Cservenak, Tamas commented on MINDEXER-83: -- Merged as https://github.com/apache/maven-indexer/commit/339eec6052a74fea91a99da2e33cbbd6a95aee3f > Refactor the Indexer.addArtifactsToIndex(...) method (possibly introduce new > ones) so that it is possible to add artifact files one by one > -- > > Key: MINDEXER-83 > URL: https://issues.apache.org/jira/browse/MINDEXER-83 > Project: Maven Indexer > Issue Type: Task >Reporter: Martin Todorov >Assignee: Cservenak, Tamas > Fix For: 6.0 > > > The currently existing method only accepts a list of files. This assumes you > already have a list of the files. However, this is inconvenient for use if > you have the artifact files coming one by one (for example when deploying an > artifact over over HTTP). > This method should be re-worked and it would be great if some new methods > could be introduced for when adding files which belong to a particular > artifact. > It would also be great if there could be methods that accept (File file, > Artifact artifact, ..) when adding and updating an artifact to the index. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MJLINK-6) Allow set the jmods path
[ https://issues.apache.org/jira/browse/MJLINK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265374#comment-16265374 ] Karl Heinz Marbaise commented on MJLINK-6: -- You are right, but you can't build on OS X for runtime on Windows or on Linux for runtime on Windows...cause the resulting runtime image is currently limited to the platform you build on... > Allow set the jmods path > > > Key: MJLINK-6 > URL: https://issues.apache.org/jira/browse/MJLINK-6 > Project: Maven JLink Plugin > Issue Type: Improvement >Affects Versions: 3.0.0-alpha-2 >Reporter: Roberto Araujo >Priority: Minor > > The current version of the plugin hard-coded the `jmods` folder (based on > `jlink` binary location). But, for instance, if I want to build a runtime > image for Linux running the build in a OSX the runtime image will not be > compatible. > I suggest to allow users define the JDK `jmods` folder, and if nothing is > set, use the one based on the JAVA_HOME/Toolchain configuration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MJLINK-6) Allow set the jmods path
[ https://issues.apache.org/jira/browse/MJLINK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265399#comment-16265399 ] Roberto Araujo commented on MJLINK-6: - But I can build a runtime image for Linux on OS X (At least for a docker containers). E.g., If I use the `--module-path` option the `jmod` folder from the Linux distribution (available at http://jdk.java.net/9/) the assembled runtime image will work on Docker container (tested with debian:sid). But if I use the `jmod` folder from my JAVA_HOME (i'm on OS X) the assembled runtime image will not work in the container (the binaries are not compatible). > Allow set the jmods path > > > Key: MJLINK-6 > URL: https://issues.apache.org/jira/browse/MJLINK-6 > Project: Maven JLink Plugin > Issue Type: Improvement >Affects Versions: 3.0.0-alpha-2 >Reporter: Roberto Araujo >Priority: Minor > > The current version of the plugin hard-coded the `jmods` folder (based on > `jlink` binary location). But, for instance, if I want to build a runtime > image for Linux running the build in a OSX the runtime image will not be > compatible. > I suggest to allow users define the JDK `jmods` folder, and if nothing is > set, use the one based on the JAVA_HOME/Toolchain configuration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MNG-6312) Update Maven Wagon dependency
Sylwester Lachiewicz created MNG-6312: - Summary: Update Maven Wagon dependency Key: MNG-6312 URL: https://issues.apache.org/jira/browse/MNG-6312 Project: Maven Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Based on OWASP report - update Maven Wagon from 2.12 to 3.0.0 to fix known vulnerability in shaded jsoup wagon-http-2.12-shaded.jar\META-INF/maven/org.jsoup/jsoup/pom.xml (cpe:/a:jsoup:jsoup:1.7.2, org.jsoup:jsoup:1.7.2) : CVE-2015-6748 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCM-739) Release Plugin: Use "git --depth 1" When Checking Out
[
https://issues.apache.org/jira/browse/SCM-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265483#comment-16265483
]
ASF GitHub Bot commented on SCM-739:
Github user arteam commented on the issue:
https://github.com/apache/maven-scm/pull/56
I like the proposal, but I am a a little bit confused. Does the new
parameter should be added to the `executeCheckOutCommand` method (like
`recursive`) and be implemented by the all `AbstractCheckOutCommand`
implementations or should it be a field in `GitCheckOutCommand`?
> Release Plugin: Use "git --depth 1" When Checking Out
> -
>
> Key: SCM-739
> URL: https://issues.apache.org/jira/browse/SCM-739
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
>Affects Versions: 1.8.1
>Reporter: Ernst de Haan
>
> *Executive summary: Please use {{--depth 1}} when checking out from a git
> repository.*
> Currently when doing {{mvn release:prepare release:perform}}, the git
> checkout step takes a significant amount of time.
> During the git checkout it appears to not only check out the correct version
> of the code, but also _all_ history, as would be done with a regular:
> {code:none}git clone URL{code}
> However, git supports checking out only the latest version of the code base,
> using this command: {code:none}git clone --depth 1 URL{code}
> For the purpose of the Maven Release Plugin, that should be sufficient, as
> far as I can see.
> Changing the plugin to use {{--depth 1}} will:
> - _significantly_ improve performance on larger repositories and/or with a
> lot of history
> - and reduce I/O on repositories with a lot of history.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MNG-6313) Update dependences and default plugins to latest version
Sylwester Lachiewicz created MNG-6313: - Summary: Update dependences and default plugins to latest version Key: MNG-6313 URL: https://issues.apache.org/jira/browse/MNG-6313 Project: Maven Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Priority: Minor Still on Java 7 default-bindings.xml maven-install-plugin 2.4 -> 2.5.2 (2014) maven-deploy-plugin 2.7 -> 2.8.2 (2014) *maven-resources-plugin* 2.6 -> 3.0.2 (2016) maven-compiler-plugin 3.1 -> 3.7 (?) (2017) maven-surefire-plugin 2.12.4 -> 2.20.1 (?) (2017) *maven-jar-plugin* 2.4 -> 3.0.2 (2017) *maven-war-plugin* 2.2 -> 3.2 (2017) Update parent-pom 27 -> 30 to aligh with other maven projects maven-shared-utils to 3.1 -> 3.2 commons-lang 3.5 -> 3.6 guice 4.0 -> 4.1 (?) commons-io -> 2.6 logback-classic 1.2.1 -> 1.2.3 Plugins - internal use (maybe some update to parent-pom) maven-release-plugin 2.5.3 maven-surefire-plugin 2.20.1 (more colors) ;-) maven-bundle-plugin 2.5.4 maven-site-plugin 3.6 apache-rat-plugin 0.12 findbugs-maven-plugin 3.0.5 maven-assembly-plugin 3.0 -> 3.1 maven-jxr-plugin 2.5 maven-jar-plugin 3.0.2 maven-compiler-plugin 3.7 animal-sniffer-maven-plugin 1.15 -> 1.16 Will be good to know which plugins must be migrated to 3.x line i.e. add link to maven webpage for dev to [Wiki|https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6306) Replace use of Guava in maven-resolver-provider with a lighter weight alternative
[ https://issues.apache.org/jira/browse/MNG-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265496#comment-16265496 ] ASF GitHub Bot commented on MNG-6306: - GitHub user slachiewicz opened a pull request: https://github.com/apache/maven/pull/138 MNG-6306 remove Guava usage from maven-resolver-provider You can merge this pull request into a Git repository by running: $ git pull https://github.com/slachiewicz/maven feature/MNG-6306 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven/pull/138.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 #138 commit d2c7a34af7be5b1ff5c9d0b824bd2b1a4435aea0 Author: Sylwester Lachiewicz Date: 2017-11-24T19:38:10Z MNG-6306 remove Guava usage from maven-resolver-provider > Replace use of Guava in maven-resolver-provider with a lighter weight > alternative > - > > Key: MNG-6306 > URL: https://issues.apache.org/jira/browse/MNG-6306 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.5.2 >Reporter: Andy Wilkinson > > Spring Boot's CLI currently embeds Aether and uses Maven's Aether Provider > 3.2.1. We'd [like to switch to Maven Resolver and Maven Resolver > Provider|https://github.com/spring-projects/spring-boot/issues/7627] but the > use of Guava adds 2.4MB to a < 10MB binary. We'd like to avoid that 25% > increase if we can. > Given that Aether and Maven Resolver are intended to be embedded, would it be > possible to remove the use of Guava from Maven Resolver Provider? Its use > appears to have been added in [this > commit|https://github.com/apache/maven/commit/61c374042560b2dc21c294886615931a888df597#diff-b275596b2058bcd469e4c45288cef7b4]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (MNG-6306) Replace use of Guava in maven-resolver-provider with a lighter weight alternative
[ https://issues.apache.org/jira/browse/MNG-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNG-6306: --- Assignee: Michael Osipov > Replace use of Guava in maven-resolver-provider with a lighter weight > alternative > - > > Key: MNG-6306 > URL: https://issues.apache.org/jira/browse/MNG-6306 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.5.2 >Reporter: Andy Wilkinson >Assignee: Michael Osipov > > Spring Boot's CLI currently embeds Aether and uses Maven's Aether Provider > 3.2.1. We'd [like to switch to Maven Resolver and Maven Resolver > Provider|https://github.com/spring-projects/spring-boot/issues/7627] but the > use of Guava adds 2.4MB to a < 10MB binary. We'd like to avoid that 25% > increase if we can. > Given that Aether and Maven Resolver are intended to be embedded, would it be > possible to remove the use of Guava from Maven Resolver Provider? Its use > appears to have been added in [this > commit|https://github.com/apache/maven/commit/61c374042560b2dc21c294886615931a888df597#diff-b275596b2058bcd469e4c45288cef7b4]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6306) Replace use of Guava in maven-resolver-provider with a lighter weight alternative
[ https://issues.apache.org/jira/browse/MNG-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265540#comment-16265540 ] Michael Osipov commented on MNG-6306: - [~rfscholte], I'll pull as-is because the change is minimal. I don't think that a consent is necessary here. > Replace use of Guava in maven-resolver-provider with a lighter weight > alternative > - > > Key: MNG-6306 > URL: https://issues.apache.org/jira/browse/MNG-6306 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.5.2 >Reporter: Andy Wilkinson >Assignee: Michael Osipov > > Spring Boot's CLI currently embeds Aether and uses Maven's Aether Provider > 3.2.1. We'd [like to switch to Maven Resolver and Maven Resolver > Provider|https://github.com/spring-projects/spring-boot/issues/7627] but the > use of Guava adds 2.4MB to a < 10MB binary. We'd like to avoid that 25% > increase if we can. > Given that Aether and Maven Resolver are intended to be embedded, would it be > possible to remove the use of Guava from Maven Resolver Provider? Its use > appears to have been added in [this > commit|https://github.com/apache/maven/commit/61c374042560b2dc21c294886615931a888df597#diff-b275596b2058bcd469e4c45288cef7b4]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MNG-6306) Replace use of Guava in maven-resolver-provider with a lighter weight alternative
[ https://issues.apache.org/jira/browse/MNG-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6306: Fix Version/s: 3.5.3 > Replace use of Guava in maven-resolver-provider with a lighter weight > alternative > - > > Key: MNG-6306 > URL: https://issues.apache.org/jira/browse/MNG-6306 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.5.2 >Reporter: Andy Wilkinson >Assignee: Michael Osipov > Fix For: 3.5.3 > > > Spring Boot's CLI currently embeds Aether and uses Maven's Aether Provider > 3.2.1. We'd [like to switch to Maven Resolver and Maven Resolver > Provider|https://github.com/spring-projects/spring-boot/issues/7627] but the > use of Guava adds 2.4MB to a < 10MB binary. We'd like to avoid that 25% > increase if we can. > Given that Aether and Maven Resolver are intended to be embedded, would it be > possible to remove the use of Guava from Maven Resolver Provider? Its use > appears to have been added in [this > commit|https://github.com/apache/maven/commit/61c374042560b2dc21c294886615931a888df597#diff-b275596b2058bcd469e4c45288cef7b4]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6306) Replace use of Guava in maven-resolver-provider with a lighter weight alternative
[ https://issues.apache.org/jira/browse/MNG-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265548#comment-16265548 ] ASF GitHub Bot commented on MNG-6306: - Github user asfgit closed the pull request at: https://github.com/apache/maven/pull/138 > Replace use of Guava in maven-resolver-provider with a lighter weight > alternative > - > > Key: MNG-6306 > URL: https://issues.apache.org/jira/browse/MNG-6306 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.5.2 >Reporter: Andy Wilkinson >Assignee: Michael Osipov > Fix For: 3.5.3 > > > Spring Boot's CLI currently embeds Aether and uses Maven's Aether Provider > 3.2.1. We'd [like to switch to Maven Resolver and Maven Resolver > Provider|https://github.com/spring-projects/spring-boot/issues/7627] but the > use of Guava adds 2.4MB to a < 10MB binary. We'd like to avoid that 25% > increase if we can. > Given that Aether and Maven Resolver are intended to be embedded, would it be > possible to remove the use of Guava from Maven Resolver Provider? Its use > appears to have been added in [this > commit|https://github.com/apache/maven/commit/61c374042560b2dc21c294886615931a888df597#diff-b275596b2058bcd469e4c45288cef7b4]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MNG-6306) Replace use of Guava in maven-resolver-provider with a lighter weight alternative
[ https://issues.apache.org/jira/browse/MNG-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6306. --- Resolution: Fixed Fixed with [866582d296ed80f36f33e5293cd07647185e0e43|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=866582d296ed80f36f33e5293cd07647185e0e43]. > Replace use of Guava in maven-resolver-provider with a lighter weight > alternative > - > > Key: MNG-6306 > URL: https://issues.apache.org/jira/browse/MNG-6306 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.5.2 >Reporter: Andy Wilkinson >Assignee: Michael Osipov > Fix For: 3.5.3 > > > Spring Boot's CLI currently embeds Aether and uses Maven's Aether Provider > 3.2.1. We'd [like to switch to Maven Resolver and Maven Resolver > Provider|https://github.com/spring-projects/spring-boot/issues/7627] but the > use of Guava adds 2.4MB to a < 10MB binary. We'd like to avoid that 25% > increase if we can. > Given that Aether and Maven Resolver are intended to be embedded, would it be > possible to remove the use of Guava from Maven Resolver Provider? Its use > appears to have been added in [this > commit|https://github.com/apache/maven/commit/61c374042560b2dc21c294886615931a888df597#diff-b275596b2058bcd469e4c45288cef7b4]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6306) Replace use of Guava in maven-resolver-provider with a lighter weight alternative
[ https://issues.apache.org/jira/browse/MNG-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265551#comment-16265551 ] Hudson commented on MNG-6306: - SUCCESS: Integrated in Jenkins build maven-3.x #1678 (See [https://builds.apache.org/job/maven-3.x/1678/]) [MNG-6306] Replace use of Guava in maven-resolver-provider with a (michaelo: [http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=866582d296ed80f36f33e5293cd07647185e0e43]) * (edit) maven-resolver-provider/pom.xml * (edit) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultModelResolver.java > Replace use of Guava in maven-resolver-provider with a lighter weight > alternative > - > > Key: MNG-6306 > URL: https://issues.apache.org/jira/browse/MNG-6306 > Project: Maven > Issue Type: Improvement >Affects Versions: 3.5.2 >Reporter: Andy Wilkinson >Assignee: Michael Osipov > Fix For: 3.5.3 > > > Spring Boot's CLI currently embeds Aether and uses Maven's Aether Provider > 3.2.1. We'd [like to switch to Maven Resolver and Maven Resolver > Provider|https://github.com/spring-projects/spring-boot/issues/7627] but the > use of Guava adds 2.4MB to a < 10MB binary. We'd like to avoid that 25% > increase if we can. > Given that Aether and Maven Resolver are intended to be embedded, would it be > possible to remove the use of Guava from Maven Resolver Provider? Its use > appears to have been added in [this > commit|https://github.com/apache/maven/commit/61c374042560b2dc21c294886615931a888df597#diff-b275596b2058bcd469e4c45288cef7b4]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
