[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[ https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820840#comment-13820840 ] ASF subversion and git services commented on LUCENE-5217: - Commit 1541357 from [~steve_rowe] in branch 'dev/branches/branch_4x' [ https://svn.apache.org/r1541357 ] Backport LUCENE-5217 and LUCENE-5322 to branch_4x > disable transitive dependencies in maven config > --- > > Key: LUCENE-5217 > URL: https://issues.apache.org/jira/browse/LUCENE-5217 > Project: Lucene - Core > Issue Type: Bug >Reporter: Robert Muir >Assignee: Steve Rowe > Fix For: 4.6, 5.0 > > Attachments: LUCENE-5217.patch, LUCENE-5217.patch, LUCENE-5217.patch, > LUCENE-5217.patch > > > Our ivy configuration does this: each dependency is specified and so we know > what will happen. Unfortunately the maven setup is not configured the same > way. > Instead the maven setup is configured to download the internet: and it > excludes certain things specifically. > This is really hard to configure and maintain: we added a > 'validate-maven-dependencies' that tries to fail on any extra jars, but all > it really does is run a license check after maven "runs". It wouldnt find > unnecessary dependencies being dragged in if something else in lucene was > using them and thus they had a license file. > Since maven supports wildcard exclusions: MNG-3832, we can disable this > transitive shit completely. > We should do this, so its configuration is the exact parallel of ivy. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[ https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820832#comment-13820832 ] ASF subversion and git services commented on LUCENE-5217: - Commit 1541355 from [~steve_rowe] in branch 'dev/trunk' [ https://svn.apache.org/r1541355 ] Move LUCENE-5217 and LUCENE-5322 entries to the 4.7 section > disable transitive dependencies in maven config > --- > > Key: LUCENE-5217 > URL: https://issues.apache.org/jira/browse/LUCENE-5217 > Project: Lucene - Core > Issue Type: Bug >Reporter: Robert Muir >Assignee: Steve Rowe > Fix For: 4.6, 5.0 > > Attachments: LUCENE-5217.patch, LUCENE-5217.patch, LUCENE-5217.patch, > LUCENE-5217.patch > > > Our ivy configuration does this: each dependency is specified and so we know > what will happen. Unfortunately the maven setup is not configured the same > way. > Instead the maven setup is configured to download the internet: and it > excludes certain things specifically. > This is really hard to configure and maintain: we added a > 'validate-maven-dependencies' that tries to fail on any extra jars, but all > it really does is run a license check after maven "runs". It wouldnt find > unnecessary dependencies being dragged in if something else in lucene was > using them and thus they had a license file. > Since maven supports wildcard exclusions: MNG-3832, we can disable this > transitive shit completely. > We should do this, so its configuration is the exact parallel of ivy. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[ https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810334#comment-13810334 ] ASF subversion and git services commented on LUCENE-5217: - Commit 1537530 from [~steve_rowe] in branch 'dev/trunk' [ https://svn.apache.org/r1537530 ] LUCENE-5217: changes entry > disable transitive dependencies in maven config > --- > > Key: LUCENE-5217 > URL: https://issues.apache.org/jira/browse/LUCENE-5217 > Project: Lucene - Core > Issue Type: Bug >Reporter: Robert Muir >Assignee: Steve Rowe > Fix For: 4.6, 5.0 > > Attachments: LUCENE-5217.patch, LUCENE-5217.patch, LUCENE-5217.patch, > LUCENE-5217.patch > > > Our ivy configuration does this: each dependency is specified and so we know > what will happen. Unfortunately the maven setup is not configured the same > way. > Instead the maven setup is configured to download the internet: and it > excludes certain things specifically. > This is really hard to configure and maintain: we added a > 'validate-maven-dependencies' that tries to fail on any extra jars, but all > it really does is run a license check after maven "runs". It wouldnt find > unnecessary dependencies being dragged in if something else in lucene was > using them and thus they had a license file. > Since maven supports wildcard exclusions: MNG-3832, we can disable this > transitive shit completely. > We should do this, so its configuration is the exact parallel of ivy. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[
https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810335#comment-13810335
]
Steve Rowe commented on LUCENE-5217:
{{validate-maven-dependencies}} and {{nightly-smoke}} both passed. Committed
to trunk. I'll wait a few days before committing to branch_4x.
> disable transitive dependencies in maven config
> ---
>
> Key: LUCENE-5217
> URL: https://issues.apache.org/jira/browse/LUCENE-5217
> Project: Lucene - Core
> Issue Type: Bug
>Reporter: Robert Muir
>Assignee: Steve Rowe
> Fix For: 4.6, 5.0
>
> Attachments: LUCENE-5217.patch, LUCENE-5217.patch, LUCENE-5217.patch,
> LUCENE-5217.patch
>
>
> Our ivy configuration does this: each dependency is specified and so we know
> what will happen. Unfortunately the maven setup is not configured the same
> way.
> Instead the maven setup is configured to download the internet: and it
> excludes certain things specifically.
> This is really hard to configure and maintain: we added a
> 'validate-maven-dependencies' that tries to fail on any extra jars, but all
> it really does is run a license check after maven "runs". It wouldnt find
> unnecessary dependencies being dragged in if something else in lucene was
> using them and thus they had a license file.
> Since maven supports wildcard exclusions: MNG-3832, we can disable this
> transitive shit completely.
> We should do this, so its configuration is the exact parallel of ivy.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[ https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810330#comment-13810330 ] ASF subversion and git services commented on LUCENE-5217: - Commit 1537528 from [~steve_rowe] in branch 'dev/trunk' [ https://svn.apache.org/r1537528 ] LUCENE-5217: Maven config: get dependencies from Ant+Ivy; disable transitive dependency resolution for all depended-on artifacts by putting an exclusion for each transitive dependency in the section of the grandparent POM > disable transitive dependencies in maven config > --- > > Key: LUCENE-5217 > URL: https://issues.apache.org/jira/browse/LUCENE-5217 > Project: Lucene - Core > Issue Type: Bug >Reporter: Robert Muir >Assignee: Steve Rowe > Attachments: LUCENE-5217.patch, LUCENE-5217.patch, LUCENE-5217.patch, > LUCENE-5217.patch > > > Our ivy configuration does this: each dependency is specified and so we know > what will happen. Unfortunately the maven setup is not configured the same > way. > Instead the maven setup is configured to download the internet: and it > excludes certain things specifically. > This is really hard to configure and maintain: we added a > 'validate-maven-dependencies' that tries to fail on any extra jars, but all > it really does is run a license check after maven "runs". It wouldnt find > unnecessary dependencies being dragged in if something else in lucene was > using them and thus they had a license file. > Since maven supports wildcard exclusions: MNG-3832, we can disable this > transitive shit completely. > We should do this, so its configuration is the exact parallel of ivy. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[
https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771155#comment-13771155
]
Steve Rowe commented on LUCENE-5217:
I tried
[{{}}|http://ant.apache.org/ivy/history/trunk/use/makepom.html] on
the solrj module - I had hoped that it would take the {{}} directives in our {{ivy.xml}} files and populate the
appropriate exclusions in the output POM, but it doesn't :( - here's the
zookeeper dependency from its output:
{noformat}
org.apache.zookeeper
zookeeper
3.4.5
true
{noformat}
> disable transitive dependencies in maven config
> ---
>
> Key: LUCENE-5217
> URL: https://issues.apache.org/jira/browse/LUCENE-5217
> Project: Lucene - Core
> Issue Type: Bug
>Reporter: Robert Muir
>
> Our ivy configuration does this: each dependency is specified and so we know
> what will happen. Unfortunately the maven setup is not configured the same
> way.
> Instead the maven setup is configured to download the internet: and it
> excludes certain things specifically.
> This is really hard to configure and maintain: we added a
> 'validate-maven-dependencies' that tries to fail on any extra jars, but all
> it really does is run a license check after maven "runs". It wouldnt find
> unnecessary dependencies being dragged in if something else in lucene was
> using them and thus they had a license file.
> Since maven supports wildcard exclusions: MNG-3832, we can disable this
> transitive shit completely.
> We should do this, so its configuration is the exact parallel of ivy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[ https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771128#comment-13771128 ] Robert Muir commented on LUCENE-5217: - more/faster/simpler ways to test that the maven config == ivy config would help. But my original concern is actually that i greatly prefer a "whitelist" like ivy, where you just say transitive=false and declare exactly what you want, and we know from the ivy.xml exactly what is being downloaded just by looking at it. With maven it seems it wants you to make a "blacklist" of what you dont want, and you don't have any idea what is really being downloaded by looking at the configuration. > disable transitive dependencies in maven config > --- > > Key: LUCENE-5217 > URL: https://issues.apache.org/jira/browse/LUCENE-5217 > Project: Lucene - Core > Issue Type: Bug >Reporter: Robert Muir > > Our ivy configuration does this: each dependency is specified and so we know > what will happen. Unfortunately the maven setup is not configured the same > way. > Instead the maven setup is configured to download the internet: and it > excludes certain things specifically. > This is really hard to configure and maintain: we added a > 'validate-maven-dependencies' that tries to fail on any extra jars, but all > it really does is run a license check after maven "runs". It wouldnt find > unnecessary dependencies being dragged in if something else in lucene was > using them and thus they had a license file. > Since maven supports wildcard exclusions: MNG-3832, we can disable this > transitive shit completely. > We should do this, so its configuration is the exact parallel of ivy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[ https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771123#comment-13771123 ] David Smiley commented on LUCENE-5217: -- I have a proposal that may address the fundamental concern -- and the concern is that modifications to our maven pom's could bring inadvertent/unintentional transitive dependencies. What if we check-in to source control the output of "mvn dependency:tree" -- at least the essential part of the output. Then, as part of the nightly Continuous-Integration build, an ant task vets that the checked-in dependency tree matches the current output. Cool? > disable transitive dependencies in maven config > --- > > Key: LUCENE-5217 > URL: https://issues.apache.org/jira/browse/LUCENE-5217 > Project: Lucene - Core > Issue Type: Bug >Reporter: Robert Muir > > Our ivy configuration does this: each dependency is specified and so we know > what will happen. Unfortunately the maven setup is not configured the same > way. > Instead the maven setup is configured to download the internet: and it > excludes certain things specifically. > This is really hard to configure and maintain: we added a > 'validate-maven-dependencies' that tries to fail on any extra jars, but all > it really does is run a license check after maven "runs". It wouldnt find > unnecessary dependencies being dragged in if something else in lucene was > using them and thus they had a license file. > Since maven supports wildcard exclusions: MNG-3832, we can disable this > transitive shit completely. > We should do this, so its configuration is the exact parallel of ivy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[
https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771062#comment-13771062
]
Steve Rowe commented on LUCENE-5217:
I can't get the wildcard-exclusion-disables-transitive-dependendencies thing to
work - I tried with Maven 3.0.3, 3.0.5 and 3.1.0 (on OS X 10.8.4), all behave
the same.
I tested a single Solr module and looked at a single dependency's transitive
dependency: solrj module, zookeeper dependency, and zookeeper's transitive
dependency netty.
Here's the zookeeper dependency config from solrj's POM:
{noformat}
org.apache.zookeeper
zookeeper
javax.jms
jms
com.sun.jmx
jmxri
com.sun.jdmk
jmxtools
log4j
log4j
org.jboss.netty
netty
org.slf4j
slf4j-log4j12
jline
jline
{noformat}
Without making any changes, here's the output from running {{mvn -X -DskipTests
install}} under {{maven-build/solr/solrj/src/java/}}:
{noformat}
[INFO] --- maven-remote-resources-plugin:1.4:process (default) @ solr-solrj ---
[...]
[DEBUG] org.apache.solr:solr-solrj:jar:5.0-SNAPSHOT (selected for null)
[DEBUG] org.apache.zookeeper:zookeeper:jar:3.4.5:compile (selected for
compile)
[DEBUG] org.slf4j:slf4j-api:jar:1.6.1:compile (applying version: 1.6.6)
[DEBUG] org.slf4j:slf4j-api:jar:1.6.6:compile (selected for compile)
[DEBUG] commons-io:commons-io:jar:2.1:compile (selected for compile)
[DEBUG] org.noggit:noggit:jar:0.5:compile (selected for compile)
[DEBUG] org.apache.httpcomponents:httpclient:jar:4.2.3:compile (selected for
compile)
[DEBUG] org.apache.httpcomponents:httpcore:jar:4.2.2:compile (selected for
compile)
[DEBUG] commons-logging:commons-logging:jar:1.1.1:compile (selected for
compile)
[DEBUG] commons-codec:commons-codec:jar:1.6:compile (applying version: 1.7)
[DEBUG] commons-codec:commons-codec:jar:1.7:compile (selected for compile)
[DEBUG] org.apache.httpcomponents:httpmime:jar:4.2.3:compile (selected for
compile)
[DEBUG] org.codehaus.woodstox:wstx-asl:jar:3.2.7:runtime (selected for
runtime)
[DEBUG] stax:stax-api:jar:1.0.1:runtime (selected for runtime)
[DEBUG] org.slf4j:jcl-over-slf4j:jar:1.6.6:compile (selected for compile)
[DEBUG] org.slf4j:jul-to-slf4j:jar:1.6.6:compile (selected for compile)
[DEBUG] org.slf4j:slf4j-api:jar:1.6.6:compile (selected for compile)
[DEBUG] org.slf4j:slf4j-log4j12:jar:1.6.6:compile (selected for compile)
[DEBUG] log4j:log4j:jar:1.2.17:compile (applying version: 1.2.16)
[DEBUG] log4j:log4j:jar:1.2.16:compile (selected for compile)
[DEBUG] log4j:log4j:jar:1.2.16:compile (selected for compile)
[DEBUG] junit:junit:jar:4.10:test (selected for test)
{noformat}
You can see above that zookeeper's only transitive dependency is slf4j-api.
I get the same output (and behavior) when I remove netty from my local Maven
repository:
{noformat}
rm -rf ~/.m2/repository/org/jboss/netty
{noformat}
Even when netty isn't in my local repository, Maven doesn't try to download it.
However, when I change the solrj POM to use the wildcard exclusions:
{noformat}
org.apache.zookeeper
zookeeper
*
*
{noformat}
I get the following output from running {{mvn -X -DskipTests install}} under
{{maven-build/solr/solrj/src/java/}}:
{noformat}
[INFO] --- maven-remote-resources-plugin:1.4:process (default) @ solr-solrj ---
[...]
[DEBUG] org.apache.solr:solr-solrj:jar:5.0-SNAPSHOT (selected for null)
[DEBUG] org.apache.zookeeper:zookeeper:jar:3.4.5:compile (selected for
compile)
[DEBUG] org.slf4j:slf4j-api:jar:1.6.1:compile (applying version: 1.6.6)
[DEBUG] org.slf4j:slf4j-api:jar:1.6.6:compile (selected for compile)
[DEBUG] org.slf4j:slf4j-log4j12:jar:1.6.1:compile (applying version: 1.6.6)
[DEBUG] org.slf4j:slf4j-log4j12:jar:1.6.6:compile (selected for compile)
[DEBUG] log4j:log4j:jar:1.2.17:compile (applying version: 1.2.16)
[DEBUG] log4j:log4j:jar:1.2.16:compile (selected for compile)
[DEBUG] log4j:log4j:jar:1.2.15:compile (applying version: 1.2.16)
[DEBUG] log4j:log4j:jar:1.2.16:compile (selected for compile)
[DEBUG] jline:jline:jar:0.9.94:compile (applying version: 0.9.1)
[DEBUG] jline:jline:jar:0.9.1:compile (selected for compile)
[DEBUG] Using connector WagonRepositoryConnector with priority 0.0 for
http://maven.restlet.org
Downloading:
http://maven.restlet.org/org/jboss/netty/netty/3.2.2.Final/netty-3.2.2.Final.pom
[DEBUG] Writing tracking file
/Users/sarowe/.m2/repository/org/jboss/netty/netty/3.2.2.Final/netty-3.2.2.Final.pom.lastUpdated
[DEBUG] Using connector WagonRepositoryConnector with priority 0.0 for
http://repo.maven.apache.org/maven2
Downloading:
http://repo.maven.apache.org/maven2/org/jboss/netty/netty/3.2.2.Final/netty-3.2.2.Final.pom
Download
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[ https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768152#comment-13768152 ] Robert Muir commented on LUCENE-5217: - I wont comment on "viral change" :) But I think this is a totally fair thing to do for 5.0, since its a new major release. > disable transitive dependencies in maven config > --- > > Key: LUCENE-5217 > URL: https://issues.apache.org/jira/browse/LUCENE-5217 > Project: Lucene - Core > Issue Type: Bug >Reporter: Robert Muir > > Our ivy configuration does this: each dependency is specified and so we know > what will happen. Unfortunately the maven setup is not configured the same > way. > Instead the maven setup is configured to download the internet: and it > excludes certain things specifically. > This is really hard to configure and maintain: we added a > 'validate-maven-dependencies' that tries to fail on any extra jars, but all > it really does is run a license check after maven "runs". It wouldnt find > unnecessary dependencies being dragged in if something else in lucene was > using them and thus they had a license file. > Since maven supports wildcard exclusions: MNG-3832, we can disable this > transitive shit completely. > We should do this, so its configuration is the exact parallel of ivy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[ https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768115#comment-13768115 ] Steve Rowe commented on LUCENE-5217: bq. This is really hard to configure and maintain I agree. bq. maven supports wildcard exclusions: MNG-3832 I did not know that. bq. I think it just means we have to require a minimum of maven 3 instead of also supporting 2. Since this has been out for 3 years (in fact older than the ant 1.8.2 that we require), I don't see this as a significant imposition on anyone? +1, though this will be a viral change, unlike the Ant upgrade: for Ant, we only forced Lucene/Solr source users to upgrade, but for Maven, everybody who depends on binary Lucene/Solr artifacts will have to upgrade their own projects to Maven 3 - I think. I'll do some testing to confirm. > disable transitive dependencies in maven config > --- > > Key: LUCENE-5217 > URL: https://issues.apache.org/jira/browse/LUCENE-5217 > Project: Lucene - Core > Issue Type: Bug >Reporter: Robert Muir > > Our ivy configuration does this: each dependency is specified and so we know > what will happen. Unfortunately the maven setup is not configured the same > way. > Instead the maven setup is configured to download the internet: and it > excludes certain things specifically. > This is really hard to configure and maintain: we added a > 'validate-maven-dependencies' that tries to fail on any extra jars, but all > it really does is run a license check after maven "runs". It wouldnt find > unnecessary dependencies being dragged in if something else in lucene was > using them and thus they had a license file. > Since maven supports wildcard exclusions: MNG-3832, we can disable this > transitive shit completely. > We should do this, so its configuration is the exact parallel of ivy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-5217) disable transitive dependencies in maven config
[ https://issues.apache.org/jira/browse/LUCENE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767950#comment-13767950 ] Robert Muir commented on LUCENE-5217: - This is also described here: http://www.smartjava.org/content/maven-and-wildcard-exclusions I think it just means we have to require a minimum of maven 3 instead of also supporting 2. Since this has been out for 3 years (in fact older than the ant 1.8.2 that we require), I don't see this as a significant imposition on anyone? > disable transitive dependencies in maven config > --- > > Key: LUCENE-5217 > URL: https://issues.apache.org/jira/browse/LUCENE-5217 > Project: Lucene - Core > Issue Type: Bug >Reporter: Robert Muir > > Our ivy configuration does this: each dependency is specified and so we know > what will happen. Unfortunately the maven setup is not configured the same > way. > Instead the maven setup is configured to download the internet: and it > excludes certain things specifically. > This is really hard to configure and maintain: we added a > 'validate-maven-dependencies' that tries to fail on any extra jars, but all > it really does is run a license check after maven "runs". It wouldnt find > unnecessary dependencies being dragged in if something else in lucene was > using them and thus they had a license file. > Since maven supports wildcard exclusions: MNG-3832, we can disable this > transitive shit completely. > We should do this, so its configuration is the exact parallel of ivy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
