This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 271423 - no match for org.apache.lucene:lucene-core:3.6.2 found
Summary: no match for org.apache.lucene:lucene-core:3.6.2 found
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: NB JUnit (show other bugs)
Version: 8.2
Hardware: PC Linux
: P3 normal (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-02 16:16 UTC by Jesse Glick
Modified: 2017-09-02 16:42 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2017-09-02 16:16:19 UTC 
Follows up #225522. Steps to reproduce shown there.

The problem is that `libs.lucene` bundles `lucene-core-3.5.0` which `maven.indexer` bundles `lucene-core-3.6.2`. There is nothing wrong with that in NetBeans since they will be in isolated class loaders. But an `nbm-application` can contain only one in its test classpath. Whichever you pick, `NbModuleSuite.S.rewrite` will complain about not being able to find the other one.

Probably it should gracefully fall back to loading whichever variant was in the test classpath, after issuing a warning (particularly if that variant is older than the version declared in `Maven-Class-Path`).
Comment 1 Jesse Glick 2017-09-02 16:16:41 UTC 
bug #225522 that is
Comment 2 Jesse Glick 2017-09-02 16:42:03 UTC 
Workaround: .enableClasspathModules(false).clusters(".*")