Xavier Roussel commented on ARIES-1792:

I also tried the optimization and the problem is still here, the plugin still 
needs more than 10 sec ( same as before ) for one module. Here are the logs for 
one module, it's the same most of the others:

[DEBUG] Creating package scope class finder: 12286ms
[DEBUG] Finding bean classes: 30ms
[DEBUG] Creating blueprint model: 68ms
[DEBUG] Writing blueprint: 52ms

I added a few more debug and It seems that all the time is consumed by the 
fonction which scan the classes when the classloader is created ( readClassDef 
in org.apache.xbean.finder.AbstractFinder ). Which is normal I think because it 
reference all the project dependency, even camel,osgi,jetty,spring etc ...

[DEBUG] Adding urls ( ClassFinder constructor ) : 2304ms
[DEBUG] ReadClassDef ( ClassFinder constructor ) : 10131ms
[DEBUG] Creating PackageScopeClassFinder: 12438ms
[DEBUG] Finding bean classes: 37ms
[DEBUG] Creating blueprint model: 72ms
[DEBUG] Writing blueprint: 85ms

> 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

Reply via email to