[
https://issues.apache.org/activemq/browse/CAMEL-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63099#action_63099
]
Claus Ibsen commented on CAMEL-3316:
------------------------------------
Seems a bit odd?
When there is such a major change I usually do as follows
{code}
mvn clean install -Dtest=false
{code}
from the root of the Camel project. Why can't Maven 3.0 work likewise without
all the relative hints?
> maven3 requires relativepaths to find parents
> ---------------------------------------------
>
> Key: CAMEL-3316
> URL: https://issues.apache.org/activemq/browse/CAMEL-3316
> Project: Apache Camel
> Issue Type: Bug
> Reporter: Daniel Kulp
> Attachments: maven3.patch
>
>
> When the version changed from 2.5.0-SNAP to 2.6.0-SNAP, the parent was not in
> the local repo and maven3 complains it cannot find it. Adding relative
> paths to everything fixes it. patch will be supplied.
> BTW: having a "build system" component in JIRA for these types of things
> would probably be a good idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
