You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2022/10/18 12:18:00 UTC
[jira] [Updated] (DAFFODIL-2683) Don't split packages across jars - OGSI packaging requirements
[ https://issues.apache.org/jira/browse/DAFFODIL-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Lawrence updated DAFFODIL-2683:
-------------------------------------
Fix Version/s: (was: 3.4.0)
> Don't split packages across jars - OGSI packaging requirements
> --------------------------------------------------------------
>
> Key: DAFFODIL-2683
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2683
> Project: Daffodil
> Issue Type: Bug
> Components: General
> Affects Versions: 3.3.0
> Reporter: Mike Beckerle
> Priority: Major
>
> A user wants to use daffodil inside Apache Karaf, which uses OGSi containers.
> Converting a jar to an OGSi container is feasible; however, there is an underlying assumption that a package is not split across such containers.
> As of daffodil 3.3.0, the package structure is not organized this way. The packages are orthogonal to the modules.
> For example org.apache.daffodil.processors is split across 6 modules:
> * daffodil-io
> * daffodil-lib
> * daffodil-macro-lib (which shouldn't create a jar, but still it mentions the package)
> * daffodil-runtime1
> * daffodil-runtime1-unparser
> * daffodil-tdml-lib (only in test code, which shouldn't impact the jar)
> The requirement is for each package to end up in exactly and only one Jar.
> This ticket possibly interacts with other refactoring tickets that are open such as DAFFODIL-2536.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)