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

Chris A. Mattmann resolved OODT-539.
------------------------------------
    Resolution: Won't Fix

a great idea, but no one has done this since end of 2012 - not going to get 
done, unfortunately

> New maven archetype for generating a template MetExtractor project
> ------------------------------------------------------------------
>
>                 Key: OODT-539
>                 URL: https://issues.apache.org/jira/browse/OODT-539
>             Project: OODT
>          Issue Type: New Feature
>          Components: cas-mvn-plugins
>    Affects Versions: 0.4
>            Reporter: Rishi Verma
>            Assignee: Rishi Verma
>            Priority: Minor
>             Fix For: 1.1
>
>
> Create a new maven archetype for allowing developers to quickly generate 
> MetExtractor projects on their own.
> The rationale for creating this archetype is to make it simpler and quicker 
> to write new met extractors. Writing new met extractors is pretty easy, but 
> establishing the correct maven directory structure, pom file(s), and build 
> cycle can be tricky. I myself often just replicate the directory structure 
> and pom files from other projects instead of creating/writing new met 
> extractor projects from scratch. This can however lead to human errors and 
> also unwanted code and config. Having an archetype which generates a 
> preferred met extractor-specific maven directory structure, pom files, and 
> template met extractor code would make the job of creating new custom met 
> extractors more consistent and automatic.
> The proposed capability is the following:
> 1. New archetype to generate a full maven project for writing custom met 
> extractor(s)
> 2. Pre-populate generated project with template MetExtractor(s) which work 
> out-of-the box and make it obvious WHERE developer should add their custom 
> extraction code
> 3. Ensure generated project pom allows a build of met extractor project out 
> of the box
> To start out, I would recommend we include an extended CmdLineMetExtractor 
> class which works out-of-the box. We can include more custom met extractors 
> and template code later.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to