[ https://issues.apache.org/jira/browse/ARIES-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439799#comment-16439799 ]
Dominik Przybysz commented on ARIES-1792: ----------------------------------------- [~xroussel] [~soundcrac...@gmail.com] I've found a project with huge amount of dependencies and have started testing the plugin against it. I've added the excludeArtifacts option to the plugin configuration. {code:java} <excludeArtifacts> <excludeArtifact>.*(cats|cxf|jackson|jackrabbit|guava|spring|paranamer|commons|activemq|stax|geronimo|validation-api|jaxb|jetty).*</excludeArtifact> </excludeArtifacts>{code} The exclude patterns are tested against an artifact name, e. g.: {code:java} org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.0.2:provided{code} The code is available on another branch here: https://github.com/alien11689/aries/tree/ARIES-1792_exclude Can you check it? > 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)