shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Saputra (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SHIRO-236) Adding <relativePath> to the <parent> element to avoid Maven 3.0.x issue where parent is not in local repo yet.
Date Sun, 16 Jan 2011 20:44:00 GMT

     [ https://issues.apache.org/jira/browse/SHIRO-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Henry Saputra updated SHIRO-236:
--------------------------------

    Attachment: update_relativepath_pom.txt

Proposed patch.

> Adding <relativePath> to the <parent> element to avoid Maven 3.0.x issue
where parent is not in local repo yet.
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: SHIRO-236
>                 URL: https://issues.apache.org/jira/browse/SHIRO-236
>             Project: Shiro
>          Issue Type: Improvement
>            Reporter: Henry Saputra
>            Priority: Minor
>         Attachments: update_relativepath_pom.txt
>
>
> Add <relativePath> to the <parent> declaration in the pom.xml files to workaround
issue with Maven 3.0.x where the parent is not in the local repo (eg when you built from scratch
in developer machine) you will get error "Non-resolvable parent POM: Could not find artifact
" like this:
> The project org.apache.shiro:shiro-spring:1.2.0-SNAPSHOT (/Users/hsaputra/shiro/trunk/support/spring/pom.xml)
has 1 error
> [ERROR]     Non-resolvable parent POM: Could not find artifact org.apache.shiro:shiro-root:pom:1.2.0-SNAPSHOT
and 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help 2]
> Adding relative path element to the parent element seems to fix this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message