I've only briefly touched *QueryImplementation classes, but this seems to map binaries to sources.
I need a way to map sources to separate JAR outputs (assuming a standard NetBeans Java Project with Existing Sources). Or is SourceForBinaryQueryImplementation a bijection? --emi On Mon, Jul 10, 2017 at 2:53 PM, Jaroslav Tulach <[email protected]> wrote: > On the API level you may only need to write a single module and register > implementation of this class > > http://bits.netbeans.org/dev/javadoc/org-netbeans-api-java-classpath/org/ > netbeans/spi/java/queries/SourceForBinaryQueryImplementation.html > > to properly answer these queries > > http://bits.netbeans.org/dev/javadoc/org-netbeans-api-java-classpath/org/ > netbeans/api/java/queries/SourceForBinaryQuery.html > > into Lookup via > > http://bits.netbeans.org/dev/javadoc/org-openide-util-lookup/org/openide/util/ > lookup/ServiceProvider.html > > > -jt > > > > On pátek 7. července 2017 13:27:42 CEST Emilian Bold wrote: >> Hello, >> >> It seems Eclipse supports this but I'm not able to find our UI for this. >> >> I'm looking at the JMeter codebase and they have multiple subfolders >> (src/components, src/core) which would each generate a separate JAR. >> >> I'm able to create a Java Project with Existing Sources but it will >> always create a single output JAR. >> >> Is this something we should try to support? >> >> Or is manual Mavenization the only way? >> >> --emi > >
