commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-392) OSGI import requires ant.taskdef and javax.mail
Date Fri, 14 Aug 2009 19:10:14 GMT


Oliver Heger commented on CONFIGURATION-392:

Ant is used by {{EnvironmentConfiguration}} to access environment variables on Java versions
before 1.5. The mail API is used by unit tests for {{DataConfiguration}}, therefore it is
declared with test scope in the pom.

The OSGi directives are created by the maven build. The configuration for this is inherited
from the commons-parent pom. I wonder why packages that have been included with scope=test
are added to the imports header. I guess, it is possible to override the configuration of
the maven bundle plug-in, but what would be the best strategy for handling optional dependencies?

Hopefully one of our OSGi experts can comment on this?

> OSGI import requires ant.taskdef and javax.mail
> -----------------------------------------------
>                 Key: CONFIGURATION-392
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.6
>         Environment: OSGI
>            Reporter: Martin Heitz
>   Original Estimate: 0.75h
>  Remaining Estimate: 0.75h
> In the Manifest the OSGI Import-Package states, that commons configuration depends on and on javax.mail: 
> Import-Package: javax.mail.internet,javax.naming,javax.servlet,javax.s
>  ql,javax.xml.parsers,javax.xml.transform,javax.xml.transform.dom,java
>  s.codec.binary,org.apache.commons.collections,org.apache.commons.coll
>  ections.iterators,,org.apache.commo
>  ns.collections.set,org.apache.commons.configuration;version="1.6",org
>  .apache.commons.configuration.beanutils;version="1.6",org.apache.comm
>  ons.configuration.event;version="1.6",org.apache.commons.configuratio
>  n.interpol;version="1.6",org.apache.commons.configuration.plist;versi
>  on="1.6",org.apache.commons.configuration.reloading;version="1.6",org
>  .apache.commons.configuration.tree;version="1.6",org.apache.commons.c
>  onfiguration.tree.xpath;version="1.6",org.apache.commons.configuratio
>  n.web;version="1.6",org.apache.commons.digester,org.apache.commons.di
>  gester.substitution,org.apache.commons.digester.xmlrules,org.apache.c
>  ommons.jxpath,org.apache.commons.jxpath.ri,org.apache.commons.jxpath.
>  ri.compiler,org.apache.commons.jxpath.ri.model,org.apache.commons.lan
>  g,org.apache.commons.lang.exception,org.apache.commons.lang.text,org.
>  apache.commons.logging,org.apache.commons.logging.impl,org.apache.too
>  ls.ant.taskdefs,org.w3c.dom,org.xml.sax,org.xml.sax.helpers
> As result of this, when developing RCP application and using commons configuration as
OSGI bundle, the built client needs the ant bundle (and a bundle providing javax.mail) in
the execution runtime!
> The worst thing is, that it looks like that ant is not even used within commons configuration
itself - except for a javadoc comment which actually does not need an import (EnvironmentConfiguration).
> javax.mail cannot be found at all in the sources.
> In addition to that, also the imports to jxpath, SAX and javax.naming should be optional
as those are only needed for specific configurations.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message