sbang/jsr330activator issues and pull requests

#15 - Bump commons-fileupload from 1.3.3 to 1.5 in /jsr330activator.gogoshell/provision

Pull Request - State: open - Opened by dependabot[bot] over 1 year ago
Labels: dependencies

#14 - Bump logback-classic from 1.0.4 to 1.2.0 in /jsr330activator.tests

Pull Request - State: closed - Opened by dependabot[bot] about 3 years ago
Labels: dependencies

#13 - Bump logback-core from 1.0.4 to 1.2.0 in /jsr330activator.tests

Pull Request - State: closed - Opened by dependabot[bot] about 3 years ago
Labels: dependencies

#12 - Bump commons-io from 2.4 to 2.7 in /jsr330activator.gogoshell/provision

Pull Request - State: closed - Opened by dependabot[bot] about 3 years ago
Labels: dependencies

#12 - Bump commons-io from 2.4 to 2.7 in /jsr330activator.gogoshell/provision

Pull Request - State: closed - Opened by dependabot[bot] about 3 years ago
Labels: dependencies

#11 - Bump commons-fileupload from 1.3.1 to 1.3.3 in /jsr330activator.gogoshell/provision

Pull Request - State: closed - Opened by dependabot[bot] over 3 years ago
Labels: dependencies

#11 - Bump commons-fileupload from 1.3.1 to 1.3.3 in /jsr330activator.gogoshell/provision

Pull Request - State: closed - Opened by dependabot[bot] over 3 years ago
Labels: dependencies

#10 - Bump junit from 4.12 to 4.13.1

Pull Request - State: closed - Opened by dependabot[bot] over 3 years ago
Labels: dependencies

#10 - Bump junit from 4.12 to 4.13.1

Pull Request - State: closed - Opened by dependabot[bot] over 3 years ago
Labels: dependencies

#10 - Bump junit from 4.12 to 4.13.1

Pull Request - State: closed - Opened by dependabot[bot] over 3 years ago
Labels: dependencies

#9 - jsr330activator only supports a single provider for each type

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment
Labels: bug

#9 - jsr330activator only supports a single provider for each type

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment
Labels: bug

#9 - jsr330activator only supports a single provider for each type

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment
Labels: bug

#9 - jsr330activator only supports a single provider for each type

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment
Labels: bug

#8 - Activator fails with NoClassDefFoundError on declared exception from a different bundle

Issue - State: open - Opened by steinarb about 7 years ago
Labels: bug

#8 - Activator fails with NoClassDefFoundError on declared exception from a different bundle

Issue - State: open - Opened by steinarb about 7 years ago
Labels: bug

#8 - Activator fails with NoClassDefFoundError on declared exception from a different bundle

Issue - State: open - Opened by steinarb about 7 years ago
Labels: bug

#8 - Activator fails with NoClassDefFoundError on declared exception from a different bundle

Issue - State: open - Opened by steinarb about 7 years ago
Labels: bug

#7 - Providers implementing multiple interfaces aren't recognized unless the Provider<T> is the first interface

Issue - State: open - Opened by sbang about 7 years ago - 1 comment
Labels: bug

#7 - Providers implementing multiple interfaces aren't recognized unless the Provider<T> is the first interface

Issue - State: open - Opened by sbang about 7 years ago - 1 comment
Labels: bug

#7 - Providers implementing multiple interfaces aren't recognized unless the Provider<T> is the first interface

Issue - State: open - Opened by sbang about 7 years ago - 1 comment
Labels: bug

#7 - Providers implementing multiple interfaces aren't recognized unless the Provider<T> is the first interface

Issue - State: open - Opened by sbang about 7 years ago - 1 comment
Labels: bug

#7 - Providers implementing multiple interfaces aren't recognized unless the Provider<T> is the first interface

Issue - State: open - Opened by sbang about 7 years ago - 1 comment
Labels: bug

#7 - Providers implementing multiple interfaces aren't recognized unless the Provider<T> is the first interface

Issue - State: open - Opened by sbang about 7 years ago - 1 comment
Labels: bug

#6 - There should be some way of putting properties on provided services

Issue - State: closed - Opened by steinarb about 7 years ago
Labels: enhancement

#6 - There should be some way of putting properties on provided services

Issue - State: closed - Opened by steinarb about 7 years ago
Labels: enhancement

#6 - There should be some way of putting properties on provided services

Issue - State: closed - Opened by steinarb about 7 years ago
Labels: enhancement

#6 - There should be some way of putting properties on provided services

Issue - State: closed - Opened by steinarb about 7 years ago
Labels: enhancement

#5 - The Jsr330Activator should log errors when logging is available

Issue - State: open - Opened by steinarb about 7 years ago
Labels: enhancement

#5 - The Jsr330Activator should log errors when logging is available

Issue - State: open - Opened by steinarb about 7 years ago
Labels: enhancement

#5 - The Jsr330Activator should log errors when logging is available

Issue - State: open - Opened by steinarb about 7 years ago
Labels: enhancement

#5 - The Jsr330Activator should log errors when logging is available

Issue - State: open - Opened by steinarb about 7 years ago
Labels: enhancement

#5 - The Jsr330Activator should log errors when logging is available

Issue - State: open - Opened by steinarb about 7 years ago
Labels: enhancement

#4 - Some way of handling multiple instances of the same service, and not require all of them to activate the Provider<>

Issue - State: closed - Opened by sbang about 7 years ago - 3 comments
Labels: enhancement

#4 - Some way of handling multiple instances of the same service, and not require all of them to activate the Provider<>

Issue - State: closed - Opened by sbang about 7 years ago - 3 comments
Labels: enhancement

#4 - Some way of handling multiple instances of the same service, and not require all of them to activate the Provider<>

Issue - State: closed - Opened by sbang about 7 years ago - 3 comments
Labels: enhancement

#4 - Some way of handling multiple instances of the same service, and not require all of them to activate the Provider<>

Issue - State: closed - Opened by sbang about 7 years ago - 3 comments
Labels: enhancement

#3 - There should be some way of accessing the bundlecontext from the activated code

Issue - State: open - Opened by sbang about 7 years ago
Labels: enhancement

#3 - There should be some way of accessing the bundlecontext from the activated code

Issue - State: open - Opened by sbang about 7 years ago
Labels: enhancement

#3 - There should be some way of accessing the bundlecontext from the activated code

Issue - State: open - Opened by sbang about 7 years ago
Labels: enhancement

#3 - There should be some way of accessing the bundlecontext from the activated code

Issue - State: open - Opened by sbang about 7 years ago
Labels: enhancement

#3 - There should be some way of accessing the bundlecontext from the activated code

Issue - State: open - Opened by sbang about 7 years ago
Labels: enhancement

#3 - There should be some way of accessing the bundlecontext from the activated code

Issue - State: open - Opened by sbang about 7 years ago
Labels: enhancement

#3 - There should be some way of accessing the bundlecontext from the activated code

Issue - State: open - Opened by sbang about 7 years ago
Labels: enhancement

#2 - Need a way to get notified on activator shutdown (for pax-web unregistration)

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment

#2 - Need a way to get notified on activator shutdown (for pax-web unregistration)

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment

#2 - Need a way to get notified on activator shutdown (for pax-web unregistration)

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment

#2 - Need a way to get notified on activator shutdown (for pax-web unregistration)

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment

#2 - Need a way to get notified on activator shutdown (for pax-web unregistration)

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment

#2 - Need a way to get notified on activator shutdown (for pax-web unregistration)

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment

#2 - Need a way to get notified on activator shutdown (for pax-web unregistration)

Issue - State: closed - Opened by steinarb about 7 years ago - 1 comment