[
https://issues.apache.org/jira/browse/PROVISIONR-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686835#comment-13686835
]
Ioannis Canellos commented on PROVISIONR-12:
--------------------------------------------
Yeah I'd be surprised if we had issues with upgrading groovy (unless there was
a deprecated language feature or something).
About the live test issue, a workaround would be to add in the container
configuration relative paths pointing to the tarball as maven repos (we could
append them in org.ops4j.pax.url). I think that this would work.
> Upgrade to Karaf 2.3.1
> ----------------------
>
> Key: PROVISIONR-12
> URL: https://issues.apache.org/jira/browse/PROVISIONR-12
> Project: Provisionr
> Issue Type: Dependency upgrade
> Components: Core, Karaf
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Attachments: PROVISIONR-12.patch, PROVISIONR-12.patch
>
>
> We are now using Karaf 2.2.10. Should we should skip this upgrade and go
> directly for 3.0.0 (as soon as it has a GA release)?
> Unfortunately it's not trivial to make this change due to Activiti
> requirements.
> Related GitHub issue:
> https://github.com/axemblr/axemblr-provisionr/issues/117
--
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
