[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-620) Archetype does not deploy on JBoss Nexus repository due to missing pom fields

Hardy Ferentschik (JIRA) noreply at atlassian.com
Mon Nov 8 04:16:13 EST 2010


    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39056#action_39056 ] 

Hardy Ferentschik commented on HSEARCH-620:
-------------------------------------------

Talked to Paul. He is willing to temporarily disable POM validation during deployment, but in the long run we need a better solution. The problem is that the POM which gets deployed in the repository (the archetype pom) is actually generated by _archetype:create-from-project_. The pom in _hibernate-search-archetype_ contains actually most of the required information, but this is the pom which becomes bundled in the archetype. 
I am not sure whether there is a way to use _archetype:create-from-project_ and also influence what goes into the generated pom. There are a couple of related archetype issues:
* http://jira.codehaus.org/browse/ARCHETYPE-302
* http://jira.codehaus.org/browse/ARCHETYPE-347 

> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list