[
https://issues.apache.org/jira/browse/BIGTOP-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164463#comment-14164463
]
jay vyas commented on BIGTOP-1479:
----------------------------------
1) Do we need to *reference the subprojects as maven submodules* ( i assume yes
), and if so...
2) Im not sure that we can mix maven and gradle at that level - i.e. i dont
think you can have a project like this:
{noformat}
pom.xml
module1
build.gradle
module2
build.gradle
{noformat}
I'll dig more and thinkl about it. i know we are fast moving to *gradle*, so i
think if there is some removal of poms that can / should be done, now is the
time to do it, rather than add tooling to do a bunch of pom/gradle glue .
> 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)
