[jira] [Assigned] (YETUS-54) Add Yetus parent POM and top-level POM

["Sean Busbey (JIRA)" <ji...@apache.org>]

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

Sean Busbey reassigned YETUS-54:
--------------------------------

    Assignee: Sean Busbey

> Add Yetus parent POM and top-level POM
> --------------------------------------
>
>                 Key: YETUS-54
>                 URL: https://issues.apache.org/jira/browse/YETUS-54
>             Project: Yetus
>          Issue Type: Task
>          Components: Audience Annotations, build
>    Affects Versions: 0.1.0
>            Reporter: Andrew Bayer
>            Assignee: Sean Busbey
>         Attachments: YETUS-54.1.patch
>
>
> So at least for as long as we're using Maven, I'd strongly advise that we not have audience-annotations inherit from hadoop-common's parent POM and instead inherit from a Yetus parent POM. I'd also advise that we follow the same kind of split that Hadoop has, with a yetus-parent POM in a subdirectory, separate from a top-level POM in the root directory. Parent POMs are great for defining things to inherit (versions, dependencies, properties, SCM info, etc) but are crap for aggregation once you try to do things like site generation, javadoc, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)