Of course it does not offer any additional functionality, but when
deployed as archetype
into the maven repo it allows to "bootstrap" a Search enabled maven
project using the
maven archetype plugin
(
http://maven.apache.org/plugins/maven-archetype-plugin).
I agree in current setup the quickstart project gets a little into the
way, but that is mainly
because it uses a obsolete format/setup.
Did you have ever problems with the quickstart module in Validator? That's
how it would like like
in Search as well.
--Hardy
On Fri, 12 Feb 2010 11:31:50 -0300, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
Is the quickstart archetype really needed?
On my side, I always exclude it as it goes in my way.
On 12 févr. 2010, at 15:25, Hardy Ferentschik wrote:
> Hi,
>
> For HSEARCH-459 I would like to move Search to a multi-module setup
> (similar to Validator).
> This way the archetype sources will actually always get compiled and are
> less likely to get outdated.
>
> I think we talked before about potential benefits of having a
> multi-module
> build for Search. Any objections
> if I go ahead with this?
>
> --Hardy
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev