<div dir="ltr"><div><div><div><div><div><div>I think it is fine to have it in hibernate "branding"<br></div>you could go for something like org.hibernate.wildfly:lucene-modules.<br><br></div>This doesn't really belong in org.wildfly:lucence-modules.<br></div>if anything it could be part of wildfly-extras and as such in org.wildfly.extras.<br></div><br></div>But given that hibernate is well established project, no reason not to have it under its umbrella.<br><br>--<br></div>tomaz<br><div><div><div><div><div><br><div><br></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 6, 2017 at 4:40 PM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@hibernate.org" target="_blank">sanne@hibernate.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
I'm going to assume that there's no interest in giving these modules a<br>
"WildFly branding" and/or home, so I'll use the proposed<br>
org.hibernate.lucene-modules group id, and keep them on the Hibernate<br>
github organization.<br>
<br>
Last chance to propose alternatives this week ;)<br>
<br>
Thanks for any feedback!<br>
<span class="HOEnZb"><font color="#888888"><br>
Sanne<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 17 February 2017 at 12:00, Sanne Grinovero <<a href="mailto:sanne@hibernate.org">sanne@hibernate.org</a>> wrote:<br>
> # Context<br>
><br>
> historically the Hibernate Search project released modules for<br>
> WildFly, so that people could use the latest version of it w/o having<br>
> to wait for WildFly to upgrade it and release.<br>
><br>
> This zip we distribute would also include updated modules for Apache Lucene.<br>
><br>
> We have now separated the Lucene modules into their own repository, so<br>
> that other projects (e.g. Infinispan) can use the same modules.<br>
><br>
> In case you want to have a look, the POC is hosted at:<br>
> - <a href="https://github.com/hibernate/lucene-modules" rel="noreferrer" target="_blank">https://github.com/hibernate/<wbr>lucene-modules</a><br>
><br>
> We planned to deploy this zip file as a Maven artifact under<br>
> coordinates "org.hibernate.lucene-modules:<wbr>lucene-modules:lucene-modules"<wbr>.<br>
><br>
> # I have three questions:<br>
><br>
> ## Would it be useful to make this a "Feature Pack" ?<br>
><br>
> Ideally we would like future versions of WildFly to use the same<br>
> structure (and same content) of these modules, when it will come to<br>
> upgrade the Lucene version within WildFly.<br>
><br>
> That's because we will have already tested these in (at least) the<br>
> Hibernate and Infinispan projects, while replicating the same<br>
> structure within the WildFly build would not guarantee the same<br>
> output, and would not be covered by the same amount and quality of<br>
> integration tests.<br>
><br>
> ## Would you prefer this to be hosted as <a href="http://github.com/wildfly" rel="noreferrer" target="_blank">github.com/wildfly</a> ?<br>
><br>
> We'd be happy to transfer ownership and still maintain it: having this<br>
> under "Hibernate" probably sends the wrong message.<br>
> It contains no Hibernate code and we'd like to encourage other people<br>
> possibly using Lucene on WildFly to use the same modules, again for<br>
> consistency reasons.<br>
><br>
> ## Should we use a WildFly flavoured organization id?<br>
><br>
> For the same reasons as in the previous question, yet I ask this<br>
> separately as I guess we could still keep it on github/hibernate if<br>
> you prefer, yet distribute it as "org.wildfly:lucene-modules" or<br>
> something else you might want to suggest.<br>
><br>
> Thanks,<br>
> Sanne<br>
______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>