But it is a single module. Yes, it has two artifacts, one of them is example code.
We can discuss if it needs to be resolved or not (I personally don't think it's critical). But the current situation is a bug - the examples javadocs existed and now they're missing. That's what I want to fix now. I'll open an issue and post a patch. Separating into a facet-examples module has the same problems as putting it under demo. Maybe we can put it under facet/src/java, but that's not great either... I suggest that we fix the current bug, and discuss more on LUCENE-3998. Shai On Nov 24, 2012 7:22 PM, "Robert Muir" <[email protected]> wrote: > > > On Sat, Nov 24, 2012 at 9:18 AM, Shai Erera <[email protected]> wrote: > >> bq. I don't think we should do this. >> >> Why? What's the harm? It's a fairly simple fix to the build.xml and it's >> not like all other modules have example code under demo, such that the >> facet one stands out. >> >> > It makes the build system, packaging, and release verification more > complicated if a single module has multiple artifacts. > > I think we should just keep it clean and let a single module be a single > module. >
