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

Tuomas Kiviaho commented on MASSEMBLY-870:
------------------------------------------

I tried to upgrade from 2.6 to 3.1.1 and the problem still remains. Local 
repository is still not utilized and the build takes way too long.

> Regression: Repository downloads all dependencies remotely into _tmp folders
> ----------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-870
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-870
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 3.1.0
>            Reporter: Tuomas Kiviaho
>            Priority: Major
>
> Repository {{_tmp}} folders under {{achive-tmp}} are filled with dependency 
> artifacts (.jar files and all) from pom which are not met by the filtering. I 
> noticed this when shifting from 2.6 to 3.1.0 and it is quite critical because 
> these dependencies do not come from local repo, but instead they are always 
> downloaded remotely. 
> I do have {{dependency:copy}} also before this plugin which doesn't do this 
> so I bet it has something to do with how the Aether is setup in 
> {{DefaultRepositoryAssembler}}. By removing the {{<repositories>}} section 
> the assembly stopped this.
> The end result is now that everything that I've got in my pom is being filled 
> into {{runner/tmp/repo_tmp}}.
> {code}
>               <repository>
>                       <scope>provided</scope>
>                       <includeMetadata>false</includeMetadata>
>                       <includes>
>                               
> <include>org.mortbay.jetty.alpn:alpn-boot</include>
>                       </includes>
>                       <outputDirectory>runner/tmp/repo</outputDirectory>
>               </repository>
>       </repositories>
> {code}
> Once the assembly is complete the _tmp folder gets deleted and the end result 
> contains just that one jar file.
> This is kind of a blocker, because I bet people have got used over the years 
> to cleaning the target folder so that they can get a nice assembly each time 
> a dependency is being upgraded despite the efforts of incremental builds. Due 
> to the cleaning there will always be repeated remote downloads because local 
> repository in settings is not utilized.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to