Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Component

Last Release

First OSGi release

Notes / Comments

attributes

2.2

 

No m2 build

beanutils

1.8.0-BETA

 

 

betwixt

0.8

 

 

chain

1.1

 

 

cli

1.1

 

 

codec

1.3

 

 

collections

3.2

 

 

configuration

1.5

 

 

daemon

1.0.1

 

 

dbcp

1.2.2

 

 

dbutils

1.1

 

 

digester

1.8

 

 

discovery

0.4

 

 

el

1.0

 

 

email

1.1

 

 

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4c5b83a14fd8050e-1da14199-427943d3-93d7a5fe-9b0a9841e3b8423417e63ade"><ac:plain-text-body><![CDATA[

fileupload

1.2

1.2.1 m2,manual,pending

[http://felix.markmail.org/message/tgm45au3rpmpmfnf javax.portlet]

]]></ac:plain-text-body></ac:structured-macro>

io

1.3.2

1.4 m2,manual,pending

 

jci

1.0

 

 

jelly

1.0

 

No m2 build

jexl

1.1

 

 

jxpath

1.2

 

 

lang

2.3

 

 

launcher

1.1

 

 

logging

1.1.1

 

OSGi is N/A; See Below

math

1.1

 

 

modeler

2.0.1

 

 

net

1.4.1

 

 

pool

1.3

1.4 (m1, manual)

 

primitives

1.0

 

 

proxy

No yet released

 

 

scxml

0.7

 

 

transaction

1.2

 

 

validator

1.3.1

 

 

vfs

1.0

 

 

Commons Logging

Wiki Markup
The things that commons-logging does with classloaders in order to try and work in various servlet engine configurations are not compatible with the classloaders that OSGi environments set up. Therefore adding OSGi attributes to commons-logging is not useful, as commons-logging is not usable in an OSGi environment.
niallp: Can't be? But what if it is, logging is used by many so I would be surprised if its not
 See \[http://commons.markmail.org/message/kdnjlbokvuiigcew this thread\].