Frege / frege-gradle-plugin

Gradle plugin for compiling Frege projects
BSD 3-Clause "New" or "Revised" License
25 stars 10 forks source link

Gradle plugin 0.3 does not seem available from Jitpack #12

Open mperry opened 9 years ago

mperry commented 9 years ago

13 addresses this with the 0.4-SNAPSHOT version, available on Sonatype.

mperry commented 9 years ago

Need to investigate the cause and whether jitpack will give us a better, faster and easier release cycle.

Dierk commented 9 years ago

It is less work to create a release using jitpack but the downside is that all users of the plugin need to have the jitpack repo configured, which is kind of cumbersome (the same is true if Sonatype needs to be configured). I consider this a failed experiment. Whatever people rely upon must finally be available on mavenCentral. I feel it would be good enough to have a howToRelease.txt in the project root such that all authorized developers can release without too much effort.

Dierk commented 9 years ago

I finally think that using the gradle plugin portal would be the most convenient option. We can publish there and later just use apply plugin:'org.frege-lang' without any further configuration.

I started to work on this in the PluginPortal branch. The publishPlugins task is currently missing the .asc files and I have no idea how to properly call the signing task...

mperry commented 9 years ago

You should be able to edit gradle.properties and set signingEnabled to true. This will then produce the asc files on a build, providing you have your keys setup.

Dierk commented 9 years ago

Hm, I get

Cannot perform signing task ':signArchives' because it has no configured signatory

Am 03.09.2015 um 14:28 schrieb Mark Perry notifications@github.com:

You should be able to edit gradle.properties and set signingEnabled to true. This will then produce the asc files on a build, providing you have your keys setup.

— Reply to this email directly or view it on GitHub.

mperry commented 9 years ago

I would guess you don't have your keys setup, but I would be suprised if you have not needed to do this previously given your involvement in various communities.

I think you might be missing these from your user gradle.properties:

signing.keyId=YourKeyId
signing.password=YourPublicKeyPassword
signing.secretKeyRingFile=PathToYourKeyRingFile

See: http://central.sonatype.org/pages/gradle.html http://central.sonatype.org/pages/working-with-pgp-signatures.html

Dierk commented 9 years ago

it may be that I have too many ;-)

Dierk

sent from:mobile

Am 04.09.2015 um 01:12 schrieb Mark Perry notifications@github.com:

I would guess you don't have your keys setup, but I would be suprised if you have not needed to do this previously given your involvement in various communities.

— Reply to this email directly or view it on GitHub.