Plugin authors: new approach to publishing plugins

[pledbrook]

Hi everyone,

As announced on the user list, I deployed a new app to beta.grails.org
that includes some enhancements around plugins. To take advantage of
these improvements, you currently need to use the Maven Publisher
plugin. If you're not scared off by the name (it doesn't required you
to install or use Maven!), you can find out how to publish plugins
with it on this thread:

    http://grails.1312388.n4.nabble.com/New-features-on-beta-grails-org-td3083225.html

At some point the publish-plugin command is likely to be rolled into
Grails core, but for now it would be good if people could give the
Maven Publisher plugin a spin. There's also documentation for the
plugin on the GitHub project page:

    https://github.com/grails-plugins/grails-maven-publisher-plugin

Thanks,

Peter

(Still waiting for the first proper tweet to the @grailsplugins account)

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

On 15/12/2010, at 1:29 AM, Peter Ledbrook wrote:

> Hi everyone,
>
> As announced on the user list, I deployed a new app to beta.grails.org
> that includes some enhancements around plugins. To take advantage of
> these improvements, you currently need to use the Maven Publisher
> plugin. If you're not scared off by the name (it doesn't required you
> to install or use Maven!), you can find out how to publish plugins
> with it on this thread:
>
>    http://grails.1312388.n4.nabble.com/New-features-on-beta-grails-org-td3083225.html
>
> At some point the publish-plugin command is likely to be rolled into
> Grails core, but for now it would be good if people could give the
> Maven Publisher plugin a spin. There's also documentation for the
> plugin on the GitHub project page:
>
>    https://github.com/grails-plugins/grails-maven-publisher-plugin

The plugin does not publish to the beta version of the site, so this doesn't work. I hacked the plugin to ping  beta.grails.org but it didn't update the twitter account.

Version 0.7.3 of the plugin also has an issue where it doesn't append / to URIs before trying to resolve the URI for the plugin.

It also doesn't support providing credentials via any other mechanism than input at command line which is uncool. It should support reading credentials from the args map and from user's settings.groovy.

The same thing needs to be done for repository definitions, so users can put their user/pass in settings.groovy


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[pledbrook]

Thanks for trying this.

>> At some point the publish-plugin command is likely to be rolled into
>> Grails core, but for now it would be good if people could give the
>> Maven Publisher plugin a spin. There's also documentation for the
>> plugin on the GitHub project page:
>>
>>    https://github.com/grails-plugins/grails-maven-publisher-plugin
>
> The plugin does not publish to the beta version of the site, so this doesn't work. I hacked the plugin to ping  beta.grails.org but it didn't update the twitter account.

Hack it? You just need to add a portal definition to your
BuildConfig.groovy as described in the other e-mail and the GitHub
docs page.

Twitter issue seems to be down to this:

    Caused by: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target

That will be fun to fix :(

> Version 0.7.3 of the plugin also has an issue where it doesn't append / to URIs before trying to resolve the URI for the plugin.

That's me thinking that URI.resolve() does a helpful thing :( If File
can handle trailing slashes or not, why can't URI. Thanks for the
report - I'll sort that out.

> It also doesn't support providing credentials via any other mechanism than input at command line which is uncool. It should support reading credentials from the args map and from user's settings.groovy.
>
> The same thing needs to be done for repository definitions, so users can put their user/pass in settings.groovy

These can be added in the repository definition, which you can put
into settings.groovy. But yes, should look into user-specific
settings.

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[pledbrook]

> Twitter issue seems to be down to this:
>
>    Caused by: javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to
> find valid certification path to requested target
>
> That will be fun to fix :(

Just need to add SmartCom as a trusted authority. Bit rusty on
keytool, but shouldn't be too hard.

There was also a problem with the JSON sent to the server (parse
error). Can you post whatever's in the project's target/pom.xml file?
Even better would be the JSON sent to the server.

Thanks,

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

On 15/12/2010, at 7:07 PM, Peter Ledbrook wrote:

> That's me thinking that URI.resolve() does a helpful thing :( If File
> can handle trailing slashes or not, why can't URI. Thanks for the
> report - I'll sort that out.

I think you can just append a trailing slash here if there isn't one.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Sébastien Blanc]

Hi Peter,

I'm about to release a plugin and it's not reallt clear what I have to do to follow the "new way". Before I publish it with the maven-publisher do I have to to a "plugin-release" and is the portal url beta.grails.org still relevant ?

Thanks,

Seb

On Wed, Dec 15, 2010 at 10:54 AM, Luke Daley <[hidden email]> wrote:

On 15/12/2010, at 7:07 PM, Peter Ledbrook wrote:

> That's me thinking that URI.resolve() does a helpful thing :( If File
> can handle trailing slashes or not, why can't URI. Thanks for the
> report - I'll sort that out.

I think you can just append a trailing slash here if there isn't one.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Sébastien Blanc]

I just give it a try by doing :

grails publish-plugin --portal=beta 

The plugin is commited and released on codehaus but after that i'm getting this error :

"Error executing script PublishPlugin: No such property: portals for class: DistributionManagementInfo

"

On Wed, Jan 12, 2011 at 8:33 PM, Sébastien Blanc <[hidden email]> wrote:

Hi Peter,

I'm about to release a plugin and it's not reallt clear what I have to do to follow the "new way". Before I publish it with the maven-publisher do I have to to a "plugin-release" and is the portal url beta.grails.org still relevant ?

Thanks,

Seb

On Wed, Dec 15, 2010 at 10:54 AM, Luke Daley <[hidden email]> wrote:

On 15/12/2010, at 7:07 PM, Peter Ledbrook wrote:

> That's me thinking that URI.resolve() does a helpful thing :( If File
> can handle trailing slashes or not, why can't URI. Thanks for the
> report - I'll sort that out.

I think you can just append a trailing slash here if there isn't one.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[pledbrook]

> I just give it a try by doing :
> grails publish-plugin --portal=beta
> The plugin is commited and released on codehaus but after that i'm getting
> this error :
> "Error executing script PublishPlugin: No such property: portals for class:
> DistributionManagementInfo
> "

Which version of the plugin do you have installed?

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Sébastien Blanc]

0.7.2

On Thu, Jan 13, 2011 at 10:21 AM, Peter Ledbrook <[hidden email]> wrote:

> I just give it a try by doing :
> grails publish-plugin --portal=beta
> The plugin is commited and released on codehaus but after that i'm getting
> this error :
> "Error executing script PublishPlugin: No such property: portals for class:
> DistributionManagementInfo
> "

Which version of the plugin do you have installed?

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------

To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[pledbrook]

> 0.7.2

Portals were added in 0.7.3 I believe. I strongly recommend you
upgrade to 0.7.5 before publishing a plugin though. It fixes an issue
with the plugin synchronisation that happens between grails.org and
the plugin repository.

BTW, if you can hold off, I plan to migrate beta.grails.org to
grails.org this weekend. You then won't have to specify
beta.grails.org (since grails.org itself will have the portal REST
interface).

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Ken Roberts-2]

This may be more appropriate for the user list, but since you have a thread going I would like to ask a quick question.

I would like to set one of these portals up on our local server for proprietary code.  Do you have a link to a HOWTO for setting one up?  What exactly is the portal?

Thanks.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[pledbrook]

> This may be more appropriate for the user list, but since you have a thread going I would like to ask a quick question.
>
> I would like to set one of these portals up on our local server for proprietary code.  Do you have a link to a HOWTO for setting one up?  What exactly is the portal?

The portal is one part of the grails.org website, which is of course a
Grails application for which the source code is freely available:

    https://github.com/grails/grails-samples/tree/master/grails.org/

There is a plan to extract the plugin portal (everything under
http://grails.org/plugin/) as a Grails plugin, but that hasn't
happened yet. Nonetheless, you can get hold of the grails.org
application and host a version locally. You could then just use the
portal part.

One thing to be aware of: there are some Autobase data migrations that
won't mix well with creating the database via the dbCreate setting.
I'm not sure what the best approach is in this case. The ideal is to
add the relevant database records that tell Liquibase that the
migrations have already been applied. Burt could perhaps use this as a
case study for what the database migrations plugin should be able to
do :)

Hope that helps,

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Ken Roberts-2]

Peter,

It does help, but the outcome is that I don't want to work that hard for it just yet.  :)

I definitely want to get my zip files out of the source repository, I was hoping though that it could be posted to something like a more traditional server.  Say a basic file server with authentication.  It would be really neat if we could publish it to a specific shared folder, or web server, or something that could be entirely handled by a network drive.  Maybe an scp repository?

Thanks.


On Jan 13, 2011, at 11:59 AM, Peter Ledbrook wrote:

>> This may be more appropriate for the user list, but since you have a thread going I would like to ask a quick question.
>>
>> I would like to set one of these portals up on our local server for proprietary code.  Do you have a link to a HOWTO for setting one up?  What exactly is the portal?
>
> The portal is one part of the grails.org website, which is of course a
> Grails application for which the source code is freely available:
>
>    https://github.com/grails/grails-samples/tree/master/grails.org/
>
> There is a plan to extract the plugin portal (everything under
> http://grails.org/plugin/) as a Grails plugin, but that hasn't
> happened yet. Nonetheless, you can get hold of the grails.org
> application and host a version locally. You could then just use the
> portal part.
>
> One thing to be aware of: there are some Autobase data migrations that
> won't mix well with creating the database via the dbCreate setting.
> I'm not sure what the best approach is in this case. The ideal is to
> add the relevant database records that tell Liquibase that the
> migrations have already been applied. Burt could perhaps use this as a
> case study for what the database migrations plugin should be able to
> do :)
>
> Hope that helps,
>
> Peter
>
> --
> Peter Ledbrook
> Grails Advocate
> SpringSource - A Division of VMware
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Sébastien Blanc]

Okay, 

0.7.2 was the default version that was installed after doing grails install-plugin maven-publisher but it's maybe because of my "old" grails version (1.3.4), I'm updating to 1.3..6 and wait for your migration this weekend. BTW I've already published my plugin the "old way" (release-plugin), can I still publish it using the maven publisher ?

Seb

On Thu, Jan 13, 2011 at 10:46 AM, Peter Ledbrook <[hidden email]> wrote:

> 0.7.2

Portals were added in 0.7.3 I believe. I strongly recommend you
upgrade to 0.7.5 before publishing a plugin though. It fixes an issue
with the plugin synchronisation that happens between grails.org and
the plugin repository.

BTW, if you can hold off, I plan to migrate beta.grails.org to
grails.org this weekend. You then won't have to specify
beta.grails.org (since grails.org itself will have the portal REST
interface).

Peter

--

Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

On 14/01/2011, at 2:48 AM, Ken Roberts wrote:

> This may be more appropriate for the user list, but since you have a thread going I would like to ask a quick question.
>
> I would like to set one of these portals up on our local server for proprietary code.  Do you have a link to a HOWTO for setting one up?  What exactly is the portal?

I think you are really asking about an artifact repository opposed to a copy of the Grails plugin portal.

Maven popularised/rationalised the idea of a repository to store built artifacts, and the maven-publisher plugin can both push to and consume from all of the popular repositories.

I use Artifactory - http://www.jfrog.org/products.php
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Ken Roberts-2]

On Jan 13, 2011, at 6:04 PM, Luke Daley wrote:

>
> On 14/01/2011, at 2:48 AM, Ken Roberts wrote:
>
>> This may be more appropriate for the user list, but since you have a thread going I would like to ask a quick question.
>>
>> I would like to set one of these portals up on our local server for proprietary code.  Do you have a link to a HOWTO for setting one up?  What exactly is the portal?
>
> I think you are really asking about an artifact repository opposed to a copy of the Grails plugin portal.
>
> Maven popularised/rationalised the idea of a repository to store built artifacts, and the maven-publisher plugin can both push to and consume from all of the popular repositories.
>
> I use Artifactory - http://www.jfrog.org/products.php

That's more like it!

I'm gonna try this when I get the chance!

Thanks.  And sorry for the user-esque question in the middle of a dev thread.




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[pledbrook]

> Okay,
> 0.7.2 was the default version that was installed after doing grails
> install-plugin maven-publisher but it's maybe because of my "old" grails
> version (1.3.4), I'm updating to 1.3..6 and wait for your migration this
> weekend. BTW I've already published my plugin the "old way"
> (release-plugin), can I still publish it using the maven publisher ?

It has nothing to do with the version of Grails. That suggests your
cached master plugin list is not being updated.

You can republish you plugin using the publish-plugin command, but
you're unlikely to have an associated tweet to @grailsplugins. That's
because only new versions are tweeted and by the time you run
publish-plugin, the database on grails.org will already have the
latest version in it.

In fact, it's only worth using publish-plugin now if you have added
extra metadata to your plugin, such as a link to the SCM system used,
the licence, etc.

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email