[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-620?pag...
]
G Fernandes commented on HSEARCH-620:
-------------------------------------
[
ARCHETYPE-302|http://jira.codehaus.org/browse/ARCHETYPE-302] is not an issue anymore,
right? Right now it's possible to create and install/deploy an artifact on-the-fly
with the latest [proposed
changes|https://github.com/hibernate/hibernate-search/pull/1] in
the HSEARCH build.
Regarding [
ARCHETYPE-347|http://jira.codehaus.org/browse/ARCHETYPE-347], I've just
posted a patch to solve it. Tested locally with maven 3.0, Nexus Pro 1.8 and hibernate
search trunk, doing a release and successfully promoting the archetypes in the staging
repo.
Archetype does not deploy on JBoss Nexus repository due to missing
pom fields
-----------------------------------------------------------------------------
Key: HSEARCH-620
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-620
Project: Hibernate Search
Issue Type: Bug
Components: build
Affects Versions: 3.3.0.Beta3
Reporter: Hardy Ferentschik
Assignee: Hardy Ferentschik
Fix For: 3.3.0
Attachments: archetype-deploy-error.png
The quickstart archetype does not deploy on the Nexus server, because the test pom is
missing several project information fields. For the purpose of the archetype this is not a
problem, but it seems that Nexus is configured to verify certain pom fields. Using the
current configuration I was not able to close the staging repository (see screenshot).
As a solution we can add dummy fields for the required nodes. We should also talk to Paul
- do this rules always makes sense?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira