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

Daniel Estermann edited comment on ARIES-1792 at 4/16/18 11:51 AM:
-------------------------------------------------------------------

The fix didn't work for me unfortunately. Here is the log: 
https://paste.fedoraproject.org/paste/ALB-AoWe0lc9SB1afiaRUw

Current stable version of the plugin with the same project takes the same 
amount of time, about 11 seconds: 
https://paste.fedoraproject.org/paste/Ou~7U8xGAV6oulNR7Y4smw


was (Author: soundcrac...@gmail.com):
The fix didn't work for me unfortunately. Here is the log: 
https://paste.fedoraproject.org/paste/ALB-AoWe0lc9SB1afiaRUw

The master version of the plugin takes about the same amount of time: 
https://paste.fedoraproject.org/paste/z0mMIpXLXMWqHFfet-mVRw

> 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)

Reply via email to