[
https://issues.apache.org/jira/browse/ARIES-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440760#comment-16440760
]
Xavier Roussel commented on ARIES-1792:
---------------------------------------
I modified the code to always include artifacts with the same group id and it
work perfectly like this on my project .
[DEBUG] Finding artifacts urls: 10ms
[DEBUG] Create class loader: 0ms
[DEBUG] Building class finder: 143ms
[DEBUG] Creating package scope class finder: 153ms
[DEBUG] Finding bean classes: 40ms
[DEBUG] Creating blueprint model: 94ms
The modification is on the same branch
[https://github.com/xroussel/aries/tree/ARIES-1792_exclude_2]
> 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)
