spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Commented] (SPARK-5428) Declare the 'assembly' module at the bottom of the <modules> element in the parent POM
Date Wed, 28 Jan 2015 11:01:34 GMT


Sean Owen commented on SPARK-5428:

Of course, I suppose this depends on the idea that you want to build examples into the assembly.
I don't think that's what happens today and they are not built into the Spark assembly on
purpose. I don't think this affects the Spark build, and shouldn't; I suggested it didn't
matter in case it helped someone else do something different with the build artifacts.

> Declare the 'assembly' module at the bottom of the <modules> element in the parent
> --------------------------------------------------------------------------------------
>                 Key: SPARK-5428
>                 URL:
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build, Deploy
>            Reporter: Christian Tzolov
>            Priority: Trivial
>              Labels: assembly, maven, pom
> For multiple-modules projects, Maven follows those execution order rules:
> If no explicit dependencies are declared Maven will follow the order declared in the
<modules> element.  
> Because the 'assembly' module is responsible to aggregate build artifacts from other
modules/project it make sense to be run last in the execution chain. 
> At the moment the 'assembly' stays before modules like 'examples' which makes it impossible
to generate DEP package that contains the examples jar. 
> IMHO the 'assembly' needs to be kept at the bottom of the <modules> list.   

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message