You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Phillips (JIRA)" <ji...@apache.org> on 2013/08/17 23:22:47 UTC
[jira] [Assigned] (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:all-tabpanel ]
Andrew Phillips reassigned JCLOUDS-225:
---------------------------------------
Assignee: Andrew Phillips
> 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
> Assignee: 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