You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Alexander Poulikakos <al...@ericsson.com> on 2011/10/25 17:44:03 UTC
Is there a workaround for this bug:
http://jira.codehaus.org/browse/MRESOURCES-132
Hi
I have a maven project, with the following resource folder (containing one file):
* src/main/resources
-rw-r--r-- 1 my-user 18737 1740 Oct 25 10:24 log4j.properties
When doing a "project->clean" in eclipse (which triggers the maven Resourcse plugin, I guess) the resource files are moved to the output (bin) folder:
* ${project}/target/classes
-rw------- 1 my-user 18737 1740 Oct 25 10:24 log4j.properties
but it changes the file permission. Is there any way to control this? I would like to preserve the original file
permissions.
There seems to be a bug tracker for this(http://jira.codehaus.org/browse/MRESOURCES-132 ). Are there any possible workarounds?
Thanks,
Alex (Maven newbie)
RE: Is there a workaround for this bug:
http://jira.codehaus.org/browse/MRESOURCES-132
Posted by Alexander Poulikakos <al...@ericsson.com>.
It is not for an official build, it's during development in Eclipse.
A separate process needs to access the *.properties file (from the workspace), and it can not do it, since the Maven Resources plugin (I guess) removes the read access from "others" when compiling in Eclipse.
Any other workarounds available?
/Alex
-----Original Message-----
From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
Sent: den 25 oktober 2011 17:56
To: Maven Users List
Subject: Re: Is there a workaround for this bug: http://jira.codehaus.org/browse/MRESOURCES-132
How would such a build work on windows?
When those resources get bundled up in a jar, there will not be
execute permissions reflected in the jar.
IOW the jar command does not store the extended permissions
information that a zip file can hold.
If you are looking to create zip files with extended permissions I
would recommend using the assembly plugin
On 25 October 2011 16:44, Alexander Poulikakos
<al...@ericsson.com> wrote:
> Hi
>
>
>
> I have a maven project, with the following resource folder (containing one file):
>
> * src/main/resources
>
> -rw-r--r-- 1 my-user 18737 1740 Oct 25 10:24 log4j.properties
>
>
>
> When doing a "project->clean" in eclipse (which triggers the maven Resourcse plugin, I guess) the resource files are moved to the output (bin) folder:
>
> * ${project}/target/classes
>
> -rw------- 1 my-user 18737 1740 Oct 25 10:24 log4j.properties
>
>
>
> but it changes the file permission. Is there any way to control this? I would like to preserve the original file
>
> permissions.
>
>
>
> There seems to be a bug tracker for this(http://jira.codehaus.org/browse/MRESOURCES-132 ). Are there any possible workarounds?
>
>
>
> Thanks,
>
> Alex (Maven newbie)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Is there a workaround for this bug: http://jira.codehaus.org/browse/MRESOURCES-132
Posted by Stephen Connolly <st...@gmail.com>.
How would such a build work on windows?
When those resources get bundled up in a jar, there will not be
execute permissions reflected in the jar.
IOW the jar command does not store the extended permissions
information that a zip file can hold.
If you are looking to create zip files with extended permissions I
would recommend using the assembly plugin
On 25 October 2011 16:44, Alexander Poulikakos
<al...@ericsson.com> wrote:
> Hi
>
>
>
> I have a maven project, with the following resource folder (containing one file):
>
> * src/main/resources
>
> -rw-r--r-- 1 my-user 18737 1740 Oct 25 10:24 log4j.properties
>
>
>
> When doing a "project->clean" in eclipse (which triggers the maven Resourcse plugin, I guess) the resource files are moved to the output (bin) folder:
>
> * ${project}/target/classes
>
> -rw------- 1 my-user 18737 1740 Oct 25 10:24 log4j.properties
>
>
>
> but it changes the file permission. Is there any way to control this? I would like to preserve the original file
>
> permissions.
>
>
>
> There seems to be a bug tracker for this(http://jira.codehaus.org/browse/MRESOURCES-132 ). Are there any possible workarounds?
>
>
>
> Thanks,
>
> Alex (Maven newbie)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org