Publish plugin -- successful however web page has not been updated

[thomas fuller]

Hi Folks,

I have recently updated the Grails Infinispan Plugin so that it's current with the Grails 2.0.4 release. I have published the plugin successfully, however the web page (http://grails.org/plugin/infinispan) for the plugin still shows the old version.

If I recall correctly, this was automatically updated in previous releases, so is this a problem or is did I forget to do something?

Thanks for your help,

Tom

[Graeme Rocher-4]

Please try issue a

grails publish-plugin --pingOnly

And see if it fixes the problem

Thanks

On Fri, Jun 29, 2012 at 3:41 PM, thomas fuller <[hidden email]> wrote:

> Hi Folks,
>
> I have recently updated the Grails Infinispan Plugin so that it's current
> with the Grails 2.0.4 release. I have published the plugin successfully,
> however the web page (http://grails.org/plugin/infinispan) for the plugin
> still shows the old version.
>
> If I recall correctly, this was automatically updated in previous releases,
> so is this a problem or is did I forget to do something?
>
> Thanks for your help,
>
> Tom

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

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

    http://xircles.codehaus.org/manage_email

[pledbrook]

> Please try issue a
>
> grails publish-plugin --pingOnly
>
> And see if it fixes the problem

That won't work because the POMs haven't been published properly:

    http://repo.grails.org/grails/plugins/org/grails/plugins/infinispan/1.0.1/

I haven't worked out yet why this is happening for some plugins but not others.

Peter

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

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

    http://xircles.codehaus.org/manage_email

[thomas fuller]

OK -- is it possible that I've missed something?

The process by which I published was simply to update the grails version of the plugin, go through the test process, and then publish the plugin.

I have run the test application after publishing and it was able to download the plugin and it worked, so that part of the publishing seems to have worked fine.

Tom

On Fri, Jun 29, 2012 at 3:20 PM, Peter Ledbrook <[hidden email]> wrote:

> Please try issue a
>
> grails publish-plugin --pingOnly
>
> And see if it fixes the problem

That won't work because the POMs haven't been published properly:

   http://repo.grails.org/grails/plugins/org/grails/plugins/infinispan/1.0.1/

I haven't worked out yet why this is happening for some plugins but not others.

Peter

--
Peter Ledbrook
Grails Advocate

SpringSource - A Division of VMware

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

   http://xircles.codehaus.org/manage_email

[pledbrook]

> OK -- is it possible that I've missed something?
>
> The process by which I published was simply to update the grails version of
> the plugin, go through the test process, and then publish the plugin.
>
> I have run the test application after publishing and it was able to download
> the plugin and it worked, so that part of the publishing seems to have
> worked fine.

I think there is some underlying issue in either the Release plugin or
the site, but I haven't worked out what. You can manually update the
plugin page in the meantime as it will probably take some time to
track the problem down.

Peter

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

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

    http://xircles.codehaus.org/manage_email

[thomas fuller]

OK -- thanks for your help.

Best,

Tom

On Fri, Jun 29, 2012 at 3:57 PM, Peter Ledbrook <[hidden email]> wrote:

> OK -- is it possible that I've missed something?
>
> The process by which I published was simply to update the grails version of
> the plugin, go through the test process, and then publish the plugin.
>
> I have run the test application after publishing and it was able to download
> the plugin and it worked, so that part of the publishing seems to have
> worked fine.

I think there is some underlying issue in either the Release plugin or
the site, but I haven't worked out what. You can manually update the
plugin page in the meantime as it will probably take some time to
track the problem down.

Peter

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

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

   http://xircles.codehaus.org/manage_email

[Nick Vaidyanathan]

It might help to consider some cleanup of the Release plugin.

• Is the PluginPublisher.java interface used at all, or was that replaced by PluginDeployer?
• There may be some value add in encapsulating java.io.File by creating interfaces and class definitions for PomFile, PluginXml, and PluginPackage. This could push some responsibilities, like parsing the PomFile, out of the deployers and make it easier to test malformed PomFiles.
• This would help to work towards splitting apart some of the messy logic in the publish plugin script for dealing with some of this stuff.

Could the problem be with the website's PluginUpdateService, and have something to do with the MasterPluginList of the release plugin?

Is there a JIRA filed for this?

On Fri, Jun 29, 2012 at 7:57 AM, Peter Ledbrook <[hidden email]> wrote:

> OK -- is it possible that I've missed something?
>
> The process by which I published was simply to update the grails version of
> the plugin, go through the test process, and then publish the plugin.
>
> I have run the test application after publishing and it was able to download
> the plugin and it worked, so that part of the publishing seems to have
> worked fine.

I think there is some underlying issue in either the Release plugin or
the site, but I haven't worked out what. You can manually update the
plugin page in the meantime as it will probably take some time to
track the problem down.

Peter

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

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

   http://xircles.codehaus.org/manage_email

--
Nick Vaidyanathan

PhD Student  - Computer Science - Software Engineering - Artificial Intelligence - Engineering Education

Arizona State University

Lead Visionary- Visionary Software Solutions LLC

@swVisionary