felix log seems to silently ignore exceptions so no logging print them out as warnings
…s workaround there is now check for OSGi compatibility
Cargo 1.4.0 brought check for availability of J2EE servlet port (CARGO-365). Hacking around it by passing reserved telnet port as substitute.
bugs of latestrelease) - upgraded cargo to forthcoming 1.2.4 version (currently staging) since snapshots have already dissappeared from repo
symbolic name or version -fixed booter so that when errors outside test runs occurs, they will get printed out as well
- Switched from using RUNTIME configuratio to STANDALONE - Booter now capable of detecting when execution wanders off to other threads and prohibits Apache GoGo from printing out this information to whatever System.out was present during it's activation (FELIX-3607)
- upgraded to cargo 1.2.2 - switched to osgi version that supports generics while still maintaining backwards compatibility with framework version 4.2 - short circuited LogReaderService to cargo/maven logging so that there is no need to configure logging any more than using adapters to standard osgi logging and use maven either in normal (info) or debug mode.
removed deployment of container deployables from configuration phase (deployer-deploy does that already)
reformatted codebase renamed test case attached proxy as standalone artifact
file location exists