[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-620?pag...
]
Hardy Ferentschik commented on HSEARCH-620:
-------------------------------------------
As a workaround one can go through the normal 'mvn release:prepare; mvn
release:perform' cycle and then when closing the staging repository remove the
archetype project. Of course this means it does not get deployed, but that's no change
from the current situation.
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