Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 1.4 no longer supports user and group settings for files #49

Open
gruberrolandfiducia opened this issue Aug 29, 2013 · 1 comment

Comments

@gruberrolandfiducia
Copy link

Example:

from('content') {
    into '/usr/share/mypackage/content'
    user 'myuser'
    group 'mygroup'
}

This will result in an exception:

FAILURE: Build failed with an exception.

  • Where:
    Build file '.../build.gradle' line: 39

  • What went wrong:
    A problem occurred evaluating root project '...'.

    org.gradle.api.internal.file.copy.CopySpecImpl_Decorated.setUser(Ljava/lang/Object;)Ljava/lang/Object;

Maybe this was lost with the Gradle 1.7 compatibility changes?

@merscwog
Copy link
Contributor

merscwog commented Nov 8, 2013

This was broken with the 1.7 changes, although user = 'myuser' and group = 'mygroup' will work.

The opposite problem is occurring with some changes being worked on to have the rpm plugin work with Gradle 1.8 (and ideally 1.9+). It supports user 'myuser' and group 'mygroup', but using = results in undesired behavior using Gradle 1.8.

Unfortunately, for Gradle 1.9-rc-3, none of the plugin variants currently work either way for per-copyspec user or group assignment due to internal changes made to Gradle that haven't been worked around yet. Well, technically the current plugin doesn't work with anything newer than Gradle 1.7.

-Spencer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants