You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Ioannis Canellos (JIRA)" <ji...@apache.org> on 2013/08/05 11:20:48 UTC
[jira] [Commented] (JCLOUDS-225) Karaf integration tests assume
that features are installed in local Maven repo
[ https://issues.apache.org/jira/browse/JCLOUDS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729333#comment-13729333 ]
Ioannis Canellos commented on JCLOUDS-225:
------------------------------------------
I created a pull request, that shows how we can configure the tests, to reuse to build generated repository feature/target/features-repo/ instead of the local maven repository.
https://github.com/jclouds/jclouds-karaf/pull/25
Personally, I don't like the approach that I took in the PR and prefer to just change the preparation goals (it just complicates configuration vs to the zero impact "clean install").
I just created the PR so that we can all have a better view of the problem and what its possible solution means.
[~abayer] We have the issue issue in whirr, what do u think?
> Karaf integration tests assume that features are installed in local Maven repo
> ------------------------------------------------------------------------------
>
> Key: JCLOUDS-225
> URL: https://issues.apache.org/jira/browse/JCLOUDS-225
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-karaf
> Affects Versions: 1.7.0, 1.6.2
> Reporter: Andrew Phillips
> Fix For: 1.6.3
>
>
> As per [~iocanel]'s comment in JCLOUDS-51, the Karaf integration tests expect features to be tested to be installed in the local Maven repo.
> This means that Karaf cannot be released using the current jclouds release commands [1], since the integrations tests fail during the release:prepare command as the features have only just been compiled, and not installed.
> One possibility could be to try -DpreparationGoals="clean install" (instead of "clean verify") during the release process. The other, as suggested by Ioannis, would be to "refactor the itests so that they look under features module target dir".
> [1] https://wiki.apache.org/jclouds/Releasing%20jclouds
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira