Fix logic bug in start level change handling where the active start level
was not getting initialized properly, thus causing it to improperly re-process
bundles on the boundaries of the start level change range. (FELIX-3411)


git-svn-id: http://svn.apache.org/repos/asf/felix/trunk/framework@1443503 13f79535-47bb-0310-9956-ffa450edef68
Catch and ignore IAEs due to harmless check-then-act situation. (FELIX-3939)


git-svn-id: http://svn.apache.org/repos/asf/felix/trunk/framework@1451284 13f79535-47bb-0310-9956-ffa450edef68
Be more flexible and allow misbehaving threads to continue to issue class load
requests on class loaders from disposed of bundle wirings. Also attempt to
give a reasonable exception when a new class load request is made on a class
loader from a disposed bundle wiring. (FELIX-3907)


git-svn-id: http://svn.apache.org/repos/asf/felix/trunk/framework@1452999 13f79535-47bb-0310-9956-ffa450edef68
[FELIX-3957] Error events can be thrown when refreshing fragment bundles

git-svn-id: http://svn.apache.org/repos/asf/felix/trunk/framework@1453949 13f79535-47bb-0310-9956-ffa450edef68
Use the default java security policy if no security provider is present and don't check for allpermission if an extension bundle is installed and there is no security manager present. (FELIX-3961,FELIX-3950)

git-svn-id: http://svn.apache.org/repos/asf/felix/trunk/framework@1454470 13f79535-47bb-0310-9956-ffa450edef68
Update changelog for release

git-svn-id: http://svn.apache.org/repos/asf/felix/trunk/framework@1454546 13f79535-47bb-0310-9956-ffa450edef68
[maven-release-plugin] prepare release org.apache.felix.framework-4.2.1

git-svn-id: http://svn.apache.org/repos/asf/felix/trunk/framework@1454553 13f79535-47bb-0310-9956-ffa450edef68
[maven-release-plugin] prepare for next development iteration

git-svn-id: http://svn.apache.org/repos/asf/felix/trunk/framework@1454555 13f79535-47bb-0310-9956-ffa450edef68