[
https://issues.apache.org/jira/browse/DAFFODIL-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649519#comment-17649519
]
Mike Beckerle commented on DAFFODIL-2683:
-----------------------------------------
Things I have learned the hard way in trying to do this re-packaging.
IntelliJ IDEA is NOT your friend. It goes catatonic for 1/2 hour before
responding to some of these "drag and drop" repackaging moves. Then, it wants
to fixup the imports and since there are a lot of errors, most of the imports
are deleted, requiring them to be recreated, painfully, file by file, symbol by
symbol.
This whole process needs to be scripted, and debugged using primitive tools
(not IntelliJ IDEA, or anything else that tries to be smart about imports when
opening/saving files)
I am giving up and abandoning my fork branches that were attempts to start this
process.
I now believe the right thing to do is the absolute minimum change - determine
exactly and only the symbols in packages that span modules (i.e., will span
jars)
Determine all the symbols in those referenced from other modules.
> 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: Clean Ups, General, Infrastructure
> 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)
