You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Henry Saputra (JIRA)" <ji...@apache.org> on 2011/06/29 11:29:29 UTC

[jira] [Commented] (GORA-35) Published POMs contain the wrong reference to the parent config

    [ https://issues.apache.org/jira/browse/GORA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057122#comment-13057122 ] 

Henry Saputra commented on GORA-35:
-----------------------------------

Looks like this is fixed in main trunk.

> Published POMs contain the wrong reference to the parent config
> ---------------------------------------------------------------
>
>                 Key: GORA-35
>                 URL: https://issues.apache.org/jira/browse/GORA-35
>             Project: Gora
>          Issue Type: Bug
>          Components: build process
>    Affects Versions: 0.1-incubating
>            Reporter: Julien Nioche
>            Priority: Critical
>             Fix For: 0.2-incubating
>
>
> The POM for core contains
>     <parent>
>         <groupId>org.apache.gora</groupId>
>         <artifactId>apache-gora</artifactId>
>         <version>0.1-incubating</version>
>     </parent>
> however the parent is defined as 
> <groupId>org.apache.gora</groupId>
> <artifactId>gora</artifactId>
> we can't fetch the jars with Ivy as a result. Could we fix that for the 0.1 artefacts?
>  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira