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] [Commented] (GIRAPH-346) Top Level POM
Date Thu, 27 Sep 2012 00:29:08 GMT

    [ https://issues.apache.org/jira/browse/GIRAPH-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464321#comment-13464321
] 

Nitay Joffe commented on GIRAPH-346:
------------------------------------

You're right that if you changed something in giraph-main you would have to do an install
first to make formats compile correctly. I was actually wondering if other multi-module maven
projects have a quick way around this (using the raw source everywhere instead of compiling
against jars at all), but it seems like this is actually the standard practice?

Also we should get our CI building SNAPSHOT jars on every commit. Has this been discussed
or should I open up an issue?
                
> 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