[
https://issues.apache.org/jira/browse/OODT-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Ramirez updated OODT-120:
------------------------------
Attachment: OODT-120.pramirez.20110202.patch.txt
The first attached patch (OODT-120.pramirez.20110202.patch.txt) gives a sample
of where I was thinking of going with this. I'd like to have an archetype for
each of the major components in OODT and possibly a multimodule archetype. The
patch helps someone get started with a new filemgr for their project fairly
fast.
To use apply the patch:
cd filemgr-archetype
mvn install
cd ..
mvn archetype:generate -DarchetypeCatalog=local
The last command filters out all the other maven installed archetypes and only
shows you the local ones. For OODT version use 0.2 or 0.1-incubating. Since the
artifacts are not currently pushed to Maven Central you will have to have
previously installed the OODT version.
> Archetypes for Components
> -------------------------
>
> Key: OODT-120
> URL: https://issues.apache.org/jira/browse/OODT-120
> Project: OODT
> Issue Type: New Feature
> Components: crawler, curator, file manager, push pull framework,
> resource manager, workflow manager
> Reporter: Paul Ramirez
> Assignee: Paul Ramirez
> Priority: Minor
> Fix For: 0.3
>
> Attachments: OODT-120.pramirez.20110202.patch.txt,
> OODT-120.pramirez.20110202.patch.txt
>
>
> Publish some archetypes to the repository for some quick get started on our
> components.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
