[
https://issues.apache.org/jira/browse/BIGTOP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097638#comment-13097638
]
Roman Shaposhnik commented on BIGTOP-51:
----------------------------------------
After some pondering, here's my take on this: +1 on org.apache.bigtop.itest ->
org.apache.bigtop.itest.execution part
As for org.apache.bigtop.itest -> org.apache.bigtop.itest.artifacts at this
point I really thing we should just rename it
to org.apache.bigtop.test[s].
Does it make sense?
> Layout of Bigtop repository can be optimized
> --------------------------------------------
>
> Key: BIGTOP-51
> URL: https://issues.apache.org/jira/browse/BIGTOP-51
> Project: Bigtop
> Issue Type: Bug
> Reporter: Roman Shaposhnik
> Assignee: Andrew Bayer
> Fix For: 0.2.0
>
> Attachments: BIGTOP-51-mk2.diff.txt, reorg.txt
>
>
> he current repo layout is not very self-explanatory. I like
> self-explanatory repo layouts. =) Hence, I'm proposing the following:
> - The current src/pkg contents will go to a new bigtop-packages/src
> directory.
> - The current src/repos directory will move to bigtop-repos - specifically
> to bigtop-repos/apt, since the only file we've got is Debian-specific
> currently.
> - The current top-level POM and src/site directory will move to bigtop-site.
> - test/src/itest-common will move to bigtop-test-framework
> - The code in test/src/integration will get folded in with what's currently
> in test/src/smokes, moved from (module)/src/test to (module)/src/main (since
> these are artifacts containing tests to be run later, not tests to be run at
> build time), and then all moved to bigtop-tests/test-artifacts.
> - test/src/suites will move to bigtop-tests/test-execution
> - docs can either stay as is or be renamed bigtop-docs for consistency.
> http://mail-archives.apache.org/mod_mbox/incubator-bigtop-dev/201108.mbox/%3CCAPbPdOYMquy4gRn7a=LJ+8gzvFRqz2xrxr2sDPG9x9BFvin=g...@mail.gmail.com%3E
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
