[
https://issues.apache.org/jira/browse/DAFFODIL-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444504#comment-17444504
]
Dave Thompson commented on DAFFODIL-1927:
-----------------------------------------
Verified the specified commit (commit a7b745314de5348728b1d4a61c8b86251d52e1db)
is included in the latest pull from the daffodil repository.
Verified changes identified in commit comment were implemented with a question
about a test that Mike is to check out.
Verified all affected daffodil subproject sbt test suites execute successfully,
including the modified and added tests.
Verified the nightly test schemas compile and save successfully.
Verified the nightly test suite executes successfully.
Working on creating an external layering transformer for verification. This
should not hold up v3.2.0 release.
> Ability to add new layering transformers in Jars external to Daffodil
> ---------------------------------------------------------------------
>
> Key: DAFFODIL-1927
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1927
> Project: Daffodil
> Issue Type: New Feature
> Components: Back End
> Affects Versions: 2.2.0
> Reporter: Mike Beckerle
> Assignee: Mike Beckerle
> Priority: Critical
> Fix For: 3.2.0
>
>
> Pluggable layering transforms, rather than registering them in a singleton
> object.
> We might want to use the java Services API for this kindof thing. Would
> prevent users from having to call the register function--just need to put a
> special file in the META-INF directory in the jar file.
> See the file LayerTransformer.scala.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
