giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitay Joffe (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GIRAPH-346) Top Level POM
Date Wed, 26 Sep 2012 04:38:09 GMT
Nitay Joffe created GIRAPH-346:
----------------------------------

             Summary: Top Level POM
                 Key: GIRAPH-346
                 URL: https://issues.apache.org/jira/browse/GIRAPH-346
             Project: Giraph
          Issue Type: Improvement
            Reporter: Nitay Joffe
            Priority: Minor


Most Maven projects that have multiple modules (as we do with main / formats) have a top level
pom.xml. This allows you avoid redundancy and also to build everything from top level all
at once. I'm using a lot of the formats stuff, especially playing with hive / hcatalog and
it's a pain having to constantly compile everything twice.

So I propose we move all the main code under a subdir, say giraph/ or main/. Then add a pom.xml
that both the giraph/ and the formats/ subdirs can point to.

Note we will still build completely separate jars. If people want to just build giraph-main
without formats they can do so directly from the subdirectory.

Let me know if you guys +1 the idea and I'll whip it up.

--
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

Mime
View raw message