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

configTar task requires java plugin to be applied #276

Open
jmcampanini opened this issue Mar 30, 2018 · 1 comment
Open

configTar task requires java plugin to be applied #276

jmcampanini opened this issue Mar 30, 2018 · 1 comment

Comments

@jmcampanini
Copy link
Member

jmcampanini commented Mar 30, 2018

// technically it needs the java-base plugin

issue

when attempting to publish a publication with configTar as an artifact, gradle throws an error that the file is not present, since the file is JUST the extension:

> Failed to publish publication 'config' to repository 'maven-config'
   > Invalid publication 'config': artifact file does not exist: '.asset.config.tgz'

considering we're:

  • not setting default values using java plugin
  • not setting the values in configTar

we're ending up producing a filename that's just the extension due to the AbstractArchiveTask::getArchiveName method

the gradle docs even include information about applying the java plugin:

Why are you using the Java plugin?

The Java plugin adds a number of default values for the archive tasks. You can use the archive tasks without using the Java plugin, if you like. You will need to provide values for some additional properties.

proposed fixes:

  • A. apply the java-base plugin in the config plugin. considering the primary (but not only) audience of the config tar task is java applications, this isn't horrible
  • B. fully configure the file name of the configTar task, similar to how the distTar task does it
@jmcampanini
Copy link
Member Author

seems that this is related to #203

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

1 participant