[
https://issues.apache.org/jira/browse/MNG-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653378#comment-17653378
]
Moshe Elisha edited comment on MNG-7656 at 1/1/23 7:38 AM:
-----------------------------------------------------------
Thanks, [~michael-o] .
I think I was able to prove my point. Please see attached log.
Using alpha-2, the dependency JARs are downloaded and stored in the local repo
with
{{- r w - r - - r - -}}
Using alpha-3, the dependency JARs are downloaded and stored in the local repo
with
{{- r w - - - - - - -}}
Please see attached maven.log
was (Author: elishamoshe):
Thanks, [~michael-o] .
I think I was able to prove my point. Please see attached log.
Using alpha-2, the dependency JARs are downloaded and stored in the local repo
with
{{-rw-r--r--}}
Using alpha-3, the dependency JARs are downloaded and stored in the local repo
with
{{-rw-------}}
Please see attached maven.log
> Dependencies copied to target have stricter permissions
> -------------------------------------------------------
>
> Key: MNG-7656
> URL: https://issues.apache.org/jira/browse/MNG-7656
> Project: Maven
> Issue Type: Bug
> Affects Versions: 4.0.0-alpha-3
> Reporter: Moshe Elisha
> Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: maven.log
>
>
> Dependency JARs that were copied during "clean install" to target have read
> and write permissions only to the user/owner and no permissions at all to the
> group and others.("-rw-------")
> Not sure if the issue is when maven downloads the JARs from the repo or when
> the JARs are copied from the repo to the target (using
> "dependency:3.4.0:copy-dependencies")
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
