aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Przybysz (JIRA)" <>
Subject [jira] [Commented] (ARIES-1792) blueprint-maven-plugin slows down compilation
Date Fri, 13 Apr 2018 16:58:00 GMT


Dominik Przybysz commented on ARIES-1792:

[~xroussel] I have added an optimization on my github fork []

Can you use run it with your project?

I have also added there some debug logs to measure which part of plugin execution is the
longest. Can you provide also the logs?

I would like to know how your modules are connected. Your 20+ bundles are all bundles with
implementation and the maven dependencies are between impls? If so, then I would suggest,
that you can create some bundles with only api/spi and depend on them in your bundles. It
works great in our project at work - we haven't spotted any significant slow downs caused
by BMP.

> blueprint-maven-plugin slows down compilation
> ---------------------------------------------
>                 Key: ARIES-1792
>                 URL:
>             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

View raw message