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

Christian Tzolov commented on SPARK-5428:
-----------------------------------------

[~pwendell] it is a bit confusing that the conversation is split across JIRA 
and github and I am not sure which one is up to date :)
As mentioned in the description at the moment you can not build a DEB package 
for the  examples module as it appears after the assembly module in the modules 
list. 
I can guess that any module declared after the assembly module and which is not 
an implicitly referred by a module listed before the assembly can't be used for 
packaging. 

So it will be a safe bet to keep the assembly last to ensure that all other 
projects artifacts are build. 

> Declare the 'assembly' module at the bottom of the <modules> element in the 
> parent POM
> --------------------------------------------------------------------------------------
>
>                 Key: SPARK-5428
>                 URL: https://issues.apache.org/jira/browse/SPARK-5428
>             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:
> http://maven.apache.org/guides/mini/guide-multiple-modules.html
> 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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to