oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OODT-837) Remove Non-Essential Components from OODT
Date Sun, 16 Jul 2017 16:16:00 GMT

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

Chris A. Mattmann resolved OODT-837.
    Resolution: Fixed

LMC-053601:oodt mattmann$ git push -u origin master
Counting objects: 9, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 947 bytes | 0 bytes/s, done.
Total 9 (delta 6), reused 0 (delta 0)
remote: oodt git commit: remove Catalog component: OODT-837.
remote: oodt git commit: Record change for OODT-836, OODT-837.
remote: oodt git commit: Record change for OODT-836, OODT-837.
To https://git-wip-us.apache.org/repos/asf/oodt.git
   a82ee5d..ad29238  master -> master
Branch master set up to track remote branch master from origin.
LMC-053601:oodt mattmann$ 

> Remove Non-Essential Components from OODT
> -----------------------------------------
>                 Key: OODT-837
>                 URL: https://issues.apache.org/jira/browse/OODT-837
>             Project: OODT
>          Issue Type: Bug
>          Components: build proces
>            Reporter: Michael Starch
>            Assignee: Chris A. Mattmann
>             Fix For: 1.1
> The OODT code base has many different components that are non-essential to OODT.  These
components often make it more difficult for new users to get up and running. In addition,
errors in these components can reflect poorly on the project itself.  These items ARE valuable
contributions, but are better-suited to be optional additions to the base oodt rather than
part of the basic build.
> These items should be pulled out into optional supporting projects that are not permanently
included in the base checkout.
> Although the complete list of non-essentials need to be identified, the following are
proposed. Note: radix is used as the "official build".  Also note: The OODT community must
come to a consensus on this list.
>     - agility -- Python OODT, official build is Java
>     - app -- A swing based GUI for OODT, official build uses OPS-UI
>     - balance -- PHP web interfaces, offical build uses OPS-UI
>     - catalog -- Is catalog ever used anymore?
>     - docker -- All non-radix builds confuse the "recommended" build process
>     - grid -- Is Grid used anymore?
>     - opendapps - Not included in radix
>     - profile -- What is this?
>     - protocol -- Supports Pushpull, which is out.
>     - pushpull -- not included in radix.
>     - sso -- security module, is it used by OODT?
>     - streaming -- Additional code to support streaming.  Spark separates streaming,
so should we.
>     - vagrant -- All non-radix builds confuse the "recommended" build process
>     - xmlps -- Sits on Grid, is it used?
>     - xmlquery -- Believed to be unused (solr fills this functionality) 

This message was sent by Atlassian JIRA

View raw message