[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-778?pag...
]
Sanne Grinovero commented on HSEARCH-778:
-----------------------------------------
I tend to agree in the sense that if there is no strong reasons we should keep the
groupid, BUT there are two rather good reasons:
# HSEARCH-677 will definitely impact the dependency declarations of existing projects
# we should be consistent with the other project, which already moved away from the
_org.hibernate_ group space
I think we should do it ASAP, as until we're in Alpha stages it's unlikely that
anybody is using it, other than the hardcore people reading our mailing lists and blog
posts on a daily basis.
It is getting more critical now as I don't think we will be able to finish HSEARCH-677
before the beta1 milestone.
Move Hibernate Search to new groupId / artifactId
-------------------------------------------------
Key: HSEARCH-778
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-778
Project: Hibernate Search
Issue Type: Task
Reporter: Emmanuel Bernard
Fix For: 4.0.0.Beta1
There has been discussions to move to org.hibernate.search
and possibly split Hibernate Search into more packages which would lead to some
renaming.
http://www.mail-archive.com/hibernate-dev@lists.jboss.org/msg06095.html
Possible modules:
* hibernate-search (aggregator)
* hibernate-search-core
* hibernate-search-analyzers
* hibernate-search-infinispan
* hibernate-search-orm (really hibernate-search-hibernate-core but that's mouthful :)
)
(alternative names has been proposed and nothing is settled, see thread for more info)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira