You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Daniel Estermann (JIRA)" <ji...@apache.org> on 2018/04/13 13:40:00 UTC

[jira] [Commented] (ARIES-1792) blueprint-maven-plugin slows down compilation

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

Daniel Estermann commented on ARIES-1792:
-----------------------------------------

Please see the linked issue opened by me. In my projects this plugin not only consumes the compile time (I even didn't mention it), it also makes my builds fail.

> blueprint-maven-plugin slows down compilation
> ---------------------------------------------
>
>                 Key: ARIES-1792
>                 URL: https://issues.apache.org/jira/browse/ARIES-1792
>             Project: Aries
>          Issue Type: Improvement
>    Affects Versions: blueprint-maven-plugin-1.9.0
>            Reporter: Xavier Roussel
>            Priority: Major
>
> We have a maven project with 20+ modules all using BMP to generate blueprint file.
> During compilation, BMP is executed on each module and represents more than 70% of the project's compilation time.
> We specify a scanPath for each module as a parameter to BMP but it seems that it scan the module and also all the dependencies so because the modules are linked together, the whole project is scanned again and again for each module.
> It could be useful to add an option to exclude dependencies so that BMP only scan the current module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)