Hey Chris, Thanks for your response!
> Check out the Maven archetype effort called OODT RADIX that you've seen up > on the Wiki and in other places. It lives inside of cas-mvn-plugins > archetypes folder: > > http://svn.apache.org/repos/asf/oodt/trunk/mvn/archetypes/ Yup - this is exactly where I am planning to put it. > You may want to put this archetype in there. I know that Paul and Cameron > did some work on a met extractor type as part of the OPSUI so it would be > great to integrate. Oh, interesting - I didn't know that. I'll have to touch base with them and see if some code etc can be leveraged or if this can be integrated somehow into their work. Thanks for the heads up. > However, for your idea of archetypes for everything, that.sounds.awesome. > Goal for ApacheCon NA 2013? Fast Feather talk showing all of our progress? > YES! :) Sounds like a goal to me! I really have a good feeling about archetypes - I think they can significantly lower the learning curve for new developers, so I'm happy to help in this effort. Best, Rishi On Dec 5, 2012, at 9:41 PM, Mattmann, Chris A (388J) wrote: > Hey Rishi, > > Check out the Maven archetype effort called OODT RADIX that you've seen up > on the Wiki and in other places. It lives inside of cas-mvn-plugins > archetypes folder: > > http://svn.apache.org/repos/asf/oodt/trunk/mvn/archetypes/ > > > You may want to put this archetype in there. I know that Paul and Cameron > did some work on a met extractor type as part of the OPSUI so it would be > great to integrate. Even though it is currently cas-mvn-plugins, it's so > close to cas-mvn, I would question the rename -- probably good enough as > it is. > > However, for your idea of archetypes for everything, that.sounds.awesome. > Goal for ApacheCon NA 2013? Fast Feather talk showing all of our progress? > YES! :) > > Cheers, > Chris > > On 12/5/12 3:54 PM, "Verma, Rishi (388J)" <[email protected]> wrote: > >> Hi All - >> >> Small point here, but the issue below is currently tagged under the >> 'cas-mvn-plugins' component; however, the proposed work is more of maven >> archetype related work. >> >> I'd like to propose we rename the component 'cas-mvn-plugins' to be >> 'cas-mvn' so that it can include code for cas-related maven archetypes. >> >> Any thoughts? >> >> Rishi >> >> On Dec 5, 2012, at 3:46 PM, Rishi Verma (JIRA) wrote: >> >>> Rishi Verma created OODT-539: >>> -------------------------------- >>> >>> Summary: 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: 0.5 >>> >>> >>> 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 is automatically generated by JIRA. >>> If you think it was sent incorrectly, please contact your JIRA >>> administrators >>> For more information on JIRA, see: >>> http://www.atlassian.com/software/jira >> >
