[
https://issues.apache.org/jira/browse/ARIES-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449616#comment-16449616
]
Xavier Roussel commented on ARIES-1792:
---------------------------------------
I understand the ClassLoader needs to access the classes but the ClassFinder
doesn't needs to scan all the artifacts for annotation, that's why you can (
and need ) to add all the artifacts to the ClassLoader but only filtered
artifacts to the ClassFinder.
It doesn't make sense to add the artifact to the include pattern because
following this logic all the artifacts linked to my module are required by my
module so I will have to add all of them to the includepattern and the filers
will be useless ...
More if I add the artifact(s) to the includepattern it will be scanned by the
ClassFinder for annotations, which is exactly what consume time during
compilation.
Try out my branch, you will see that everything works fine like that.
> 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)
