[
https://issues.apache.org/jira/browse/FELIX-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved FELIX-2115.
------------------------------------
Resolution: Fixed
Fix Version/s: bundlerepository-1.6.0
Assignee: Guillaume Nodet
Committing to https://svn.apache.org/repos/asf/felix/trunk ...
M
bundlerepository/src/main/java/org/apache/felix/bundlerepository/ResolverImpl.java
M
bundlerepository/src/test/java/org/apache/felix/bundlerepository/ResolverImplTest.java
A
org.osgi.service.obr/src/main/java/org/osgi/service/obr/InterrupteResolutionException.java
M
org.osgi.service.obr/src/main/java/org/osgi/service/obr/Resolver.java
Committed r912549
I've added an exception instead of throwing a RuntimeException so that users
can handle that one correctly.
> The api offers no way to have a timeout or cancel the resolution if it takes
> too long
> -------------------------------------------------------------------------------------
>
> Key: FELIX-2115
> URL: https://issues.apache.org/jira/browse/FELIX-2115
> Project: Felix
> Issue Type: Improvement
> Components: Bundle Repository (OBR)
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: bundlerepository-1.6.0
>
>
> One way would be either to add some methods to the Resolver such as:
> boolean resolve(long timeout)
> void cancel();
> I'd be much happier if we could use a Future instead.
> Future<Boolean> resolve();
> This would make it easier for the user because he doesn't have to start a
> thread on its own.
> However this breaks compatibility.
> We could therefore use something like:
> Future<Boolean> startResolve();
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
