[
https://issues.apache.org/jira/browse/BIGTOP-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175282#comment-14175282
]
Konstantin Boudnik commented on BIGTOP-1479:
--------------------------------------------
As for your question [~jayunit100]
.bq Do we need to reference the subprojects as maven submodules ( i assume yes
), and if so...
As a bit of history: back in a day [~rvs] tried to avoid having subprojects as
modules, because we stepped on a circular dependency at some point (all
submodules are tracing back to the top-level parent project). Perhaps it was
caused by our rudimentary knowledge of Maven back then. Or may be Maven has
improved and now it isn't an issue. Perhaps, it makes sense to give it another
try and see if the issue is still there.
I think [~gkesavan] makes sense and expressing project structure in Gradle
would improve the situation. I might give it a try unless someone else has
cycles to spend.
> top level Maven/Gradle build needs to be able to deploy everything
> ------------------------------------------------------------------
>
> Key: BIGTOP-1479
> URL: https://issues.apache.org/jira/browse/BIGTOP-1479
> Project: Bigtop
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.9.0
> Reporter: Roman Shaposhnik
> Fix For: 0.9.0
>
>
> Currently, if you run Maven from the top level quite a few artifacts (such as
> iTest, test artifacts, bigpetstore,... etc.) are not being built/deployed. We
> need to fix this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
