[jira] [Resolved] (DAFFODIL-1679) create sbt plugins for our tools, for daffodil schema compiling, for running daffodil parse/unparse, etc.

["Mike Beckerle (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Beckerle resolved DAFFODIL-1679.
-------------------------------------
    Resolution: Won't Do

Wish list sort of a thing.

> create sbt plugins for our tools, for daffodil schema compiling, for running daffodil parse/unparse, etc.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1679
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1679
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Infrastructure
>            Reporter: Mike Beckerle
>            Priority: Minor
>
> Yes, we're going to need to be sbt-plugin experts.
> This tool should be merged with the sbt eclipse plugin, though the constraints on such a thing are totally unclear to me, whereas this tool is specifically for projects with sub-projects and lib_managed.
> There are a few things we do at major releases like LineCounter that also should be that sort of sbt-based tool. Updating copyright banners is another thing we do. 
> C
> The daffodil schema compilation process should be something one can do from sbt.
> Processing data using daffodil to parse or unparse should be something one can do from sbt. (E.g., so that the work flow of things like the VMF spec-scraper can be automated with sbt.  E.g., compile the spec scraper schema. Use it to parse the specs and generate the VMF schema. Then compile the VMF schema and package as a jar.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)