The problem with release-plugin

[Radomir Mladenovic]

Hi,

For the last few days I'm trying to release plugin to the official
repository but no luck. I always end up with error:

Importing project to
https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
Please wait...
org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
required for '<https://svn.codehaus.org:443> grails-plugins primary
Subversion repository'

I followed the procedure described on
http://grails.org/Creating+Plugins and I got approval for developer
status. The problem is "grails release-plugin" never asks me about
login credentials.
I've tried to release from two different machines (Linux and Windows),
and I always get the same result (above quoted error).

Thanks for any input.

Regards,
Radomir

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

    http://xircles.codehaus.org/manage_email

[Graeme Rocher-3]

Create ~/.grails/settings.groovy

grails.plugin.repos.discovery.grailsplugins="https://USER:PASSWORD@.../grails-plugins"
user.svn.username.discovery.grailsplugins="USER"
user.svn.username.discovery.grailsplugins="PASSWORD"
grails.plugin.repos.distribution.grailsplugins="https://USER:PASSWORD@.../grails-plugins"
user.svn.username.distribution.grailsplugins="USER"
user.svn.username.distribution.grailsplugins="PASSWORD"

and I released with

grails release-plugin -repository=grailsplugins

On Mon, Jun 22, 2009 at 10:30 AM, Radomir Mladenovic<radomirml@...> wrote:

> Hi,
>
> For the last few days I'm trying to release plugin to the official
> repository but no luck. I always end up with error:
>
> Importing project to
> https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
> Please wait...
> org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
> required for '<https://svn.codehaus.org:443> grails-plugins primary
> Subversion repository'
>
> I followed the procedure described on
> http://grails.org/Creating+Plugins and I got approval for developer
> status. The problem is "grails release-plugin" never asks me about
> login credentials.
> I've tried to release from two different machines (Linux and Windows),
> and I always get the same result (above quoted error).
>
> Thanks for any input.
>
> Regards,
> Radomir
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

--
Graeme Rocher
Head of Grails Development
SpringSource - Weapons for the War on Java Complexity
http://www.springsource.com

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

    http://xircles.codehaus.org/manage_email

[Radomir Mladenovic]

This worked. Thanks Graeme!


On Mon, Jun 22, 2009 at 11:44 AM, Graeme
Rocher<graeme.rocher@...> wrote:

> Create ~/.grails/settings.groovy
>
> grails.plugin.repos.discovery.grailsplugins="https://USER:PASSWORD@.../grails-plugins"
> user.svn.username.discovery.grailsplugins="USER"
> user.svn.username.discovery.grailsplugins="PASSWORD"
> grails.plugin.repos.distribution.grailsplugins="https://USER:PASSWORD@.../grails-plugins"
> user.svn.username.distribution.grailsplugins="USER"
> user.svn.username.distribution.grailsplugins="PASSWORD"
>
> and I released with
>
> grails release-plugin -repository=grailsplugins
>
> On Mon, Jun 22, 2009 at 10:30 AM, Radomir Mladenovic<radomirml@...> wrote:
>> Hi,
>>
>> For the last few days I'm trying to release plugin to the official
>> repository but no luck. I always end up with error:
>>
>> Importing project to
>> https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
>> Please wait...
>> org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
>> required for '<https://svn.codehaus.org:443> grails-plugins primary
>> Subversion repository'
>>
>> I followed the procedure described on
>> http://grails.org/Creating+Plugins and I got approval for developer
>> status. The problem is "grails release-plugin" never asks me about
>> login credentials.
>> I've tried to release from two different machines (Linux and Windows),
>> and I always get the same result (above quoted error).
>>
>> Thanks for any input.
>>
>> Regards,
>> Radomir
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
>
>
> --
> Graeme Rocher
> Head of Grails Development
> SpringSource - Weapons for the War on Java Complexity
> http://www.springsource.com
>
> ---------------------------------------------------------------------
> 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

[Will Droste]

Radomir,

Could you please provide the full stack trace? I'd like to know the issue since I patched an area of that code, so we don't run into the same problem.. 

Dev,

And just a question of curiosity..  Why is a user/password required in either the settings.groovy, BuildConfig.groovy or from the command line given SVN supports storing it encrypted inside the .subversion directory?

Best Regards,

Will

On Mon, Jun 22, 2009 at 4:30 AM, Radomir Mladenovic <radomirml@...> wrote:

Hi,

For the last few days I'm trying to release plugin to the official
repository but no luck. I always end up with error:

Importing project to
https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
Please wait...
org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
required for '<https://svn.codehaus.org:443> grails-plugins primary
Subversion repository'

I followed the procedure described on
http://grails.org/Creating+Plugins and I got approval for developer
status. The problem is "grails release-plugin" never asks me about
login credentials.
I've tried to release from two different machines (Linux and Windows),
and I always get the same result (above quoted error).

Thanks for any input.

Regards,
Radomir

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

   http://xircles.codehaus.org/manage_email

[Radomir Mladenovic]

Hi,

Sorry, I didn't save the exception and I now release-plugin works even
when I remove settings.groovy. :-)
Is there a cached file somewhere that I could remove?

Best regards,
Radomir


On Mon, Jun 22, 2009 at 5:52 PM, Will Droste<will@...> wrote:

> Radomir,
> Could you please provide the full stack trace? I'd like to know the issue
> since I patched an area of that code, so we don't run into the same
> problem..
> Dev,
> And just a question of curiosity..  Why is a user/password required in
> either the settings.groovy, BuildConfig.groovy or from the command line
> given SVN supports storing it encrypted inside the .subversion directory?
> Best Regards,
> Will
>
> On Mon, Jun 22, 2009 at 4:30 AM, Radomir Mladenovic <radomirml@...>
> wrote:
>>
>> Hi,
>>
>> For the last few days I'm trying to release plugin to the official
>> repository but no luck. I always end up with error:
>>
>> Importing project to
>> https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
>> Please wait...
>> org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
>> required for '<https://svn.codehaus.org:443> grails-plugins primary
>> Subversion repository'
>>
>> I followed the procedure described on
>> http://grails.org/Creating+Plugins and I got approval for developer
>> status. The problem is "grails release-plugin" never asks me about
>> login credentials.
>> I've tried to release from two different machines (Linux and Windows),
>> and I always get the same result (above quoted error).
>>
>> Thanks for any input.
>>
>> Regards,
>> Radomir
>>
>> ---------------------------------------------------------------------
>> 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

[Will Droste]

Absolutely :) an interesting thing about SVN is it caches logins.. Some of the code tries to take advantage of that.  The directory should be $USER/.subversion simply doing a move should clear the settings and just replace the copy that is created after getting the stacktrace to return the system to the same state.

Regards,

Will

On Mon, Jun 22, 2009 at 1:01 PM, Radomir Mladenovic <radomirml@...> wrote:

Hi,

Sorry, I didn't save the exception and I now release-plugin works even
when I remove settings.groovy. :-)
Is there a cached file somewhere that I could remove?

Best regards,
Radomir

On Mon, Jun 22, 2009 at 5:52 PM, Will Droste<will@...> wrote:
> Radomir,
> Could you please provide the full stack trace? I'd like to know the issue
> since I patched an area of that code, so we don't run into the same
> problem..
> Dev,
> And just a question of curiosity..  Why is a user/password required in
> either the settings.groovy, BuildConfig.groovy or from the command line
> given SVN supports storing it encrypted inside the .subversion directory?
> Best Regards,
> Will
>
> On Mon, Jun 22, 2009 at 4:30 AM, Radomir Mladenovic <radomirml@...>
> wrote:
>>
>> Hi,
>>
>> For the last few days I'm trying to release plugin to the official
>> repository but no luck. I always end up with error:
>>
>> Importing project to
>> https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
>> Please wait...
>> org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
>> required for '<https://svn.codehaus.org:443> grails-plugins primary
>> Subversion repository'
>>
>> I followed the procedure described on
>> http://grails.org/Creating+Plugins and I got approval for developer
>> status. The problem is "grails release-plugin" never asks me about
>> login credentials.
>> I've tried to release from two different machines (Linux and Windows),
>> and I always get the same result (above quoted error).
>>
>> Thanks for any input.
>>
>> Regards,
>> Radomir
>>
>> ---------------------------------------------------------------------
>> 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

[Radomir Mladenovic]

I've found and even deleted files with my credentials and codehaus
server under ~/.subversion/auth but it still passed release without
error.

However, I remembered that was trying to release from my laptop too so
here's the exception from there:

Enter a SVN commit message:
v0.9.3
Importing project to
https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
Please wait...
org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
required for '<https://svn.codehaus.org:443> grai
ls-plugins primary Subversion repository'
        at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.authenticationFailed(SVNErrorManager.java:47)
        at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.authenticationFailed(SVNErrorManager.java:41)
        at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthentic
ationManager.java:176)
        at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:480)
        at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:257)
        at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:245)
        at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doMakeActivity(DAVConnection.java:295)
        at org.tmatesoft.svn.core.internal.io.dav.DAVCommitEditor.createActivity(DAVCommitEditor.java:415)
        at org.tmatesoft.svn.core.internal.io.dav.DAVCommitEditor.openRoot(DAVCommitEditor.java:96)
        at org.tmatesoft.svn.core.wc.SVNCommitClient.doImport(SVNCommitClient.java:684)
        at org.tmatesoft.svn.core.wc.SVNCommitClient.doImport(SVNCommitClient.java:522)
        at ReleasePlugin$_run_closure7.doCall(ReleasePlugin.groovy:289)
        at ReleasePlugin$_run_closure3.doCall(ReleasePlugin.groovy:116)
        at ReleasePlugin$_run_closure1.doCall(ReleasePlugin.groovy:42)
        at gant.Gant$_dispatch_closure4.doCall(Gant.groovy:324)
        at gant.Gant$_dispatch_closure6.doCall(Gant.groovy:334)
        at gant.Gant$_dispatch_closure6.doCall(Gant.groovy)
        at gant.Gant.withBuildListeners(Gant.groovy:344)
        at gant.Gant.this$2$withBuildListeners(Gant.groovy)
        at gant.Gant$this$2$withBuildListeners.callCurrent(Unknown Source)
        at gant.Gant.dispatch(Gant.groovy:334)
        at gant.Gant.this$2$dispatch(Gant.groovy)
        at gant.Gant.invokeMethod(Gant.groovy)
        at gant.Gant.processTargets(Gant.groovy:495)
        at gant.Gant.processTargets(Gant.groovy:480)
Error occurred with release-plugin: svn: Authentication required for
'<https://svn.codehaus.org:443> grails-plugins primary Subversion
repository'


BTW, I'm using Grails 1.1.1.

Regards,
Radomir


On Mon, Jun 22, 2009 at 8:34 PM, Will Droste<will@...> wrote:

> Absolutely :) an interesting thing about SVN is it caches logins.. Some of
> the code tries to take advantage of that.  The directory should be
> $USER/.subversion simply doing a move should clear the settings and just
> replace the copy that is created after getting the stacktrace to return the
> system to the same state.
> Regards,
> Will
>
> On Mon, Jun 22, 2009 at 1:01 PM, Radomir Mladenovic <radomirml@...>
> wrote:
>>
>> Hi,
>>
>> Sorry, I didn't save the exception and I now release-plugin works even
>> when I remove settings.groovy. :-)
>> Is there a cached file somewhere that I could remove?
>>
>> Best regards,
>> Radomir
>>
>>
>> On Mon, Jun 22, 2009 at 5:52 PM, Will Droste<will@...> wrote:
>> > Radomir,
>> > Could you please provide the full stack trace? I'd like to know the
>> > issue
>> > since I patched an area of that code, so we don't run into the same
>> > problem..
>> > Dev,
>> > And just a question of curiosity..  Why is a user/password required in
>> > either the settings.groovy, BuildConfig.groovy or from the command line
>> > given SVN supports storing it encrypted inside the .subversion
>> > directory?
>> > Best Regards,
>> > Will
>> >
>> > On Mon, Jun 22, 2009 at 4:30 AM, Radomir Mladenovic
>> > <radomirml@...>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> For the last few days I'm trying to release plugin to the official
>> >> repository but no luck. I always end up with error:
>> >>
>> >> Importing project to
>> >> https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
>> >> Please wait...
>> >> org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
>> >> required for '<https://svn.codehaus.org:443> grails-plugins primary
>> >> Subversion repository'
>> >>
>> >> I followed the procedure described on
>> >> http://grails.org/Creating+Plugins and I got approval for developer
>> >> status. The problem is "grails release-plugin" never asks me about
>> >> login credentials.
>> >> I've tried to release from two different machines (Linux and Windows),
>> >> and I always get the same result (above quoted error).
>> >>
>> >> Thanks for any input.
>> >>
>> >> Regards,
>> >> Radomir
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>

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

    http://xircles.codehaus.org/manage_email

[Will Droste]

Thanks.  I'll take a look.

Will

On Mon, Jun 22, 2009 at 1:50 PM, Radomir Mladenovic <radomirml@...> wrote:

I've found and even deleted files with my credentials and codehaus
server under ~/.subversion/auth but it still passed release without
error.

However, I remembered that was trying to release from my laptop too so
here's the exception from there:

Enter a SVN commit message:
v0.9.3

Importing project to
https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
Please wait...
org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
required for '<https://svn.codehaus.org:443> grai
ls-plugins primary Subversion repository'

       at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.authenticationFailed(SVNErrorManager.java:47)
       at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.authenticationFailed(SVNErrorManager.java:41)
       at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthentic
ationManager.java:176)
       at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:480)
       at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:257)
       at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:245)
       at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doMakeActivity(DAVConnection.java:295)
       at org.tmatesoft.svn.core.internal.io.dav.DAVCommitEditor.createActivity(DAVCommitEditor.java:415)
       at org.tmatesoft.svn.core.internal.io.dav.DAVCommitEditor.openRoot(DAVCommitEditor.java:96)
       at org.tmatesoft.svn.core.wc.SVNCommitClient.doImport(SVNCommitClient.java:684)
       at org.tmatesoft.svn.core.wc.SVNCommitClient.doImport(SVNCommitClient.java:522)
       at ReleasePlugin$_run_closure7.doCall(ReleasePlugin.groovy:289)
       at ReleasePlugin$_run_closure3.doCall(ReleasePlugin.groovy:116)
       at ReleasePlugin$_run_closure1.doCall(ReleasePlugin.groovy:42)
       at gant.Gant$_dispatch_closure4.doCall(Gant.groovy:324)
       at gant.Gant$_dispatch_closure6.doCall(Gant.groovy:334)
       at gant.Gant$_dispatch_closure6.doCall(Gant.groovy)
       at gant.Gant.withBuildListeners(Gant.groovy:344)
       at gant.Gant.this$2$withBuildListeners(Gant.groovy)
       at gant.Gant$this$2$withBuildListeners.callCurrent(Unknown Source)
       at gant.Gant.dispatch(Gant.groovy:334)
       at gant.Gant.this$2$dispatch(Gant.groovy)
       at gant.Gant.invokeMethod(Gant.groovy)
       at gant.Gant.processTargets(Gant.groovy:495)
       at gant.Gant.processTargets(Gant.groovy:480)
Error occurred with release-plugin: svn: Authentication required for

'<https://svn.codehaus.org:443> grails-plugins primary Subversion
repository'

BTW, I'm using Grails 1.1.1.

Regards,
Radomir

On Mon, Jun 22, 2009 at 8:34 PM, Will Droste<will@...> wrote:
> Absolutely :) an interesting thing about SVN is it caches logins.. Some of
> the code tries to take advantage of that.  The directory should be
> $USER/.subversion simply doing a move should clear the settings and just
> replace the copy that is created after getting the stacktrace to return the
> system to the same state.
> Regards,
> Will
>
> On Mon, Jun 22, 2009 at 1:01 PM, Radomir Mladenovic <radomirml@...>
> wrote:
>>
>> Hi,
>>
>> Sorry, I didn't save the exception and I now release-plugin works even
>> when I remove settings.groovy. :-)
>> Is there a cached file somewhere that I could remove?
>>
>> Best regards,
>> Radomir
>>
>>
>> On Mon, Jun 22, 2009 at 5:52 PM, Will Droste<will@...> wrote:
>> > Radomir,
>> > Could you please provide the full stack trace? I'd like to know the
>> > issue
>> > since I patched an area of that code, so we don't run into the same
>> > problem..
>> > Dev,
>> > And just a question of curiosity..  Why is a user/password required in
>> > either the settings.groovy, BuildConfig.groovy or from the command line
>> > given SVN supports storing it encrypted inside the .subversion
>> > directory?
>> > Best Regards,
>> > Will
>> >
>> > On Mon, Jun 22, 2009 at 4:30 AM, Radomir Mladenovic
>> > <radomirml@...>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> For the last few days I'm trying to release plugin to the official
>> >> repository but no luck. I always end up with error:
>> >>
>> >> Importing project to
>> >> https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
>> >> Please wait...
>> >> org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
>> >> required for '<https://svn.codehaus.org:443> grails-plugins primary
>> >> Subversion repository'
>> >>
>> >> I followed the procedure described on
>> >> http://grails.org/Creating+Plugins and I got approval for developer
>> >> status. The problem is "grails release-plugin" never asks me about
>> >> login credentials.
>> >> I've tried to release from two different machines (Linux and Windows),
>> >> and I always get the same result (above quoted error).
>> >>
>> >> Thanks for any input.
>> >>
>> >> Regards,
>> >> Radomir
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
>

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

   http://xircles.codehaus.org/manage_email

[Radomir Mladenovic]

I think I ruined my plugin information in the repository somehow (I
guess it was when I was trying release-plugin without the config (to
reproduce error) and was using Ctrl-C to stop it when I saw that it
"worked".

Now, although I was able to install the plugin (logdigger-connector)
from repository before it's not available any more. :-(

I've tried to release again, even increasing version number but I end
up with error:

Plugin meta directory corrupt, checking out again
Importing plugin meta data to
https://svn.codehaus.org:443/grails-plugins/.plugin-meta. Please
wait...
     [copy] Copying 1 file to
/home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta
org.tmatesoft.svn.core.SVNException: svn: File
'/grails-plugins/.plugin-meta/plugins-list.xml' already exists
        at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
        at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
        at org.tmatesoft.svn.core.internal.io.dav.DAVCommitEditor.addFile(DAVCommitEditor.java:235)
        at org.tmatesoft.svn.core.wc.SVNCommitClient.importFile(SVNCommitClient.java:1516)
        at org.tmatesoft.svn.core.wc.SVNCommitClient.importDir(SVNCommitClient.java:1495)
        at org.tmatesoft.svn.core.wc.SVNCommitClient.doImport(SVNCommitClient.java:693)
        at org.tmatesoft.svn.core.wc.SVNCommitClient.doImport(SVNCommitClient.java:522)
        at ReleasePlugin.checkoutOrImportPluginMetadata(ReleasePlugin:195)
        at ReleasePlugin.this$4$checkoutOrImportPluginMetadata(ReleasePlugin)
        at ReleasePlugin$_run_closure4.doCall(ReleasePlugin:171)
        at ReleasePlugin$_run_closure3.doCall(ReleasePlugin:137)
        at ReleasePlugin$_run_closure1.doCall(ReleasePlugin:42)
        at gant.Gant$_dispatch_closure4.doCall(Gant.groovy:324)
        at gant.Gant$_dispatch_closure6.doCall(Gant.groovy:334)
        at gant.Gant$_dispatch_closure6.doCall(Gant.groovy)
        at gant.Gant.withBuildListeners(Gant.groovy:344)
        at gant.Gant.this$2$withBuildListeners(Gant.groovy)
        at gant.Gant$this$2$withBuildListeners.callCurrent(Unknown Source)
        at gant.Gant.dispatch(Gant.groovy:334)
        at gant.Gant.this$2$dispatch(Gant.groovy)
        at gant.Gant.invokeMethod(Gant.groovy)
        at gant.Gant.processTargets(Gant.groovy:495)
        at gant.Gant.processTargets(Gant.groovy:480)
Error occurred with release-plugin: svn: File
'/grails-plugins/.plugin-meta/plugins-list.xml' already exists


Another very strange thing is that each time I call release the script
retrieves the list of plugins which takes more than an hour. Is this
normal? It's very irritating as I have to wait very long before I see
the result of command. :-(

Have to get some sleep now...



On Mon, Jun 22, 2009 at 8:55 PM, Will Droste<will@...> wrote:

> Thanks.  I'll take a look.
> Will
>
> On Mon, Jun 22, 2009 at 1:50 PM, Radomir Mladenovic <radomirml@...>
> wrote:
>>
>> I've found and even deleted files with my credentials and codehaus
>> server under ~/.subversion/auth but it still passed release without
>> error.
>>
>> However, I remembered that was trying to release from my laptop too so
>> here's the exception from there:
>>
>> Enter a SVN commit message:
>> v0.9.3
>> Importing project to
>> https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
>> Please wait...
>> org.tmatesoft.svn.core.SVNAuthenticationException: svn: Authentication
>> required for '<https://svn.codehaus.org:443> grai
>> ls-plugins primary Subversion repository'
>>        at
>> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.authenticationFailed(SVNErrorManager.java:47)
>>        at
>> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.authenticationFailed(SVNErrorManager.java:41)
>>        at
>> org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthentic
>> ationManager.java:176)
>>        at
>> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:480)
>>        at
>> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:257)
>>        at
>> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:245)
>>        at
>> org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doMakeActivity(DAVConnection.java:295)
>>        at
>> org.tmatesoft.svn.core.internal.io.dav.DAVCommitEditor.createActivity(DAVCommitEditor.java:415)
>>        at
>> org.tmatesoft.svn.core.internal.io.dav.DAVCommitEditor.openRoot(DAVCommitEditor.java:96)
>>        at
>> org.tmatesoft.svn.core.wc.SVNCommitClient.doImport(SVNCommitClient.java:684)
>>        at
>> org.tmatesoft.svn.core.wc.SVNCommitClient.doImport(SVNCommitClient.java:522)
>>        at ReleasePlugin$_run_closure7.doCall(ReleasePlugin.groovy:289)
>>        at ReleasePlugin$_run_closure3.doCall(ReleasePlugin.groovy:116)
>>        at ReleasePlugin$_run_closure1.doCall(ReleasePlugin.groovy:42)
>>        at gant.Gant$_dispatch_closure4.doCall(Gant.groovy:324)
>>        at gant.Gant$_dispatch_closure6.doCall(Gant.groovy:334)
>>        at gant.Gant$_dispatch_closure6.doCall(Gant.groovy)
>>        at gant.Gant.withBuildListeners(Gant.groovy:344)
>>        at gant.Gant.this$2$withBuildListeners(Gant.groovy)
>>        at gant.Gant$this$2$withBuildListeners.callCurrent(Unknown Source)
>>        at gant.Gant.dispatch(Gant.groovy:334)
>>        at gant.Gant.this$2$dispatch(Gant.groovy)
>>        at gant.Gant.invokeMethod(Gant.groovy)
>>        at gant.Gant.processTargets(Gant.groovy:495)
>>        at gant.Gant.processTargets(Gant.groovy:480)
>> Error occurred with release-plugin: svn: Authentication required for
>> '<https://svn.codehaus.org:443> grails-plugins primary Subversion
>> repository'
>>
>>
>> BTW, I'm using Grails 1.1.1.
>>
>> Regards,
>> Radomir
>>
>>
>> On Mon, Jun 22, 2009 at 8:34 PM, Will Droste<will@...> wrote:
>> > Absolutely :) an interesting thing about SVN is it caches logins.. Some
>> > of
>> > the code tries to take advantage of that.  The directory should be
>> > $USER/.subversion simply doing a move should clear the settings and just
>> > replace the copy that is created after getting the stacktrace to return
>> > the
>> > system to the same state.
>> > Regards,
>> > Will
>> >
>> > On Mon, Jun 22, 2009 at 1:01 PM, Radomir Mladenovic
>> > <radomirml@...>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> Sorry, I didn't save the exception and I now release-plugin works even
>> >> when I remove settings.groovy. :-)
>> >> Is there a cached file somewhere that I could remove?
>> >>
>> >> Best regards,
>> >> Radomir
>> >>
>> >>
>> >> On Mon, Jun 22, 2009 at 5:52 PM, Will Droste<will@...>
>> >> wrote:
>> >> > Radomir,
>> >> > Could you please provide the full stack trace? I'd like to know the
>> >> > issue
>> >> > since I patched an area of that code, so we don't run into the same
>> >> > problem..
>> >> > Dev,
>> >> > And just a question of curiosity..  Why is a user/password required
>> >> > in
>> >> > either the settings.groovy, BuildConfig.groovy or from the command
>> >> > line
>> >> > given SVN supports storing it encrypted inside the .subversion
>> >> > directory?
>> >> > Best Regards,
>> >> > Will
>> >> >
>> >> > On Mon, Jun 22, 2009 at 4:30 AM, Radomir Mladenovic
>> >> > <radomirml@...>
>> >> > wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> For the last few days I'm trying to release plugin to the official
>> >> >> repository but no luck. I always end up with error:
>> >> >>
>> >> >> Importing project to
>> >> >> https://svn.codehaus.org/grails-plugins/grails-logdigger-connector.
>> >> >> Please wait...
>> >> >> org.tmatesoft.svn.core.SVNAuthenticationException: svn:
>> >> >> Authentication
>> >> >> required for '<https://svn.codehaus.org:443> grails-plugins primary
>> >> >> Subversion repository'
>> >> >>
>> >> >> I followed the procedure described on
>> >> >> http://grails.org/Creating+Plugins and I got approval for developer
>> >> >> status. The problem is "grails release-plugin" never asks me about
>> >> >> login credentials.
>> >> >> I've tried to release from two different machines (Linux and
>> >> >> Windows),
>> >> >> and I always get the same result (above quoted error).
>> >> >>
>> >> >> Thanks for any input.
>> >> >>
>> >> >> Regards,
>> >> >> Radomir
>> >> >>
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> 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
>> >>
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> 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

[Richard Vowles]

It is somewhat a pity that the plugin xml file that everyone downloads from isn't generated from the www.grails.org website. Then people could just point to whereever the zip file for each release was located (svn, github, etc) and the website could manage the meta-data. Just an idea.

On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic <radomirml@...> wrote:

I think I ruined my plugin information in the repository somehow (I
guess it was when I was trying release-plugin without the config (to
reproduce error) and was using Ctrl-C to stop it when I saw that it
"worked".

--
---
Richard Vowles,
Talk to me about development in Grails, Groovy, Java and for the Blackberry
ph: [phone], linkedin, skype:rvowles
get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! - http://tinyurl.com/cmcceh
podcast: http://www.illegalargument.com

[Will Droste]

What version of SVN are you using?? On what OS etc.. Its best to use SVN 1.5 or greater.  

No this is not normal to wait an hour it should be quick.. The process is basically this when a plugin is released the plugin.xml meta data gets updated on the SVN site.  When you do anything plugin related it will check the version of the file (timestamp or svn revision) and update the file.  Which should be quick however the main plugins-list.xml is getting larger since there's a ton of plugins and the file contains all the versions. Everything is deposited in '.grails/1.1' for caching.  

I found the plugin entry and yes it is corrupted.. You'll need to re-release it.. I'm sorry this happened to you. Do you use _Events.groovy?  I've seen an issue releasing plugins w/ that file present.  From the stacktrace it looks like it stopped right in the middle of a commit.  Its odd since it looks like meta information was not created correctly because the commit should have rolledback being SVN and all.

Regards,

Will

On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles <richard@...> wrote:

It is somewhat a pity that the plugin xml file that everyone downloads from isn't generated from the www.grails.org website. Then people could just point to whereever the zip file for each release was located (svn, github, etc) and the website could manage the meta-data. Just an idea.

On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic <radomirml@...> wrote:

I think I ruined my plugin information in the repository somehow (I
guess it was when I was trying release-plugin without the config (to
reproduce error) and was using Ctrl-C to stop it when I saw that it
"worked".

--
---
Richard Vowles,
Talk to me about development in Grails, Groovy, Java and for the Blackberry
ph: [phone], linkedin, skype:rvowles
get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! - http://tinyurl.com/cmcceh
podcast: http://www.illegalargument.com

[Radomir Mladenovic]

Thank you for your comments. I'm on Ubuntu and have SVN 1.5.4.

No, I don't use _Events.groovy.

I understand that plugin list is getting bigger and bigger but it
downloads the complete list each time I try to release. This plugin
list could (should?) have been cached as yesterday I had one
successful deployment. I think meta-info got corrupted when I was
testing behavior without settings.groovy and canceled release process
with Ctrl-C.

Anyway, I deleted "~/.grails/1.1.1/grailsplugins/.plugin-meta" and
will run release-plugin again. I'll let you know how it went.

Best regards,
Radomir



On Tue, Jun 23, 2009 at 7:18 AM, Will Droste<will@...> wrote:

> What version of SVN are you using?? On what OS etc.. Its best to use SVN 1.5
> or greater.
> No this is not normal to wait an hour it should be quick.. The process is
> basically this when a plugin is released the plugin.xml meta data gets
> updated on the SVN site.  When you do anything plugin related it will check
> the version of the file (timestamp or svn revision) and update the file.
>  Which should be quick however the main plugins-list.xml is getting larger
> since there's a ton of plugins and the file contains all the
> versions. Everything is deposited in '.grails/1.1' for caching.
> I found the plugin entry and yes it is corrupted.. You'll need to re-release
> it.. I'm sorry this happened to you. Do you use _Events.groovy?  I've seen
> an issue releasing plugins w/ that file present.  From the stacktrace it
> looks like it stopped right in the middle of a commit.  Its odd since it
> looks like meta information was not created correctly because the commit
> should have rolledback being SVN and all.
> Regards,
> Will
>
> On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles
> <richard@...> wrote:
>>
>> It is somewhat a pity that the plugin xml file that everyone downloads
>> from isn't generated from the www.grails.org website. Then people could just
>> point to whereever the zip file for each release was located (svn, github,
>> etc) and the website could manage the meta-data. Just an idea.
>>
>> On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic <radomirml@...>
>> wrote:
>>>
>>> I think I ruined my plugin information in the repository somehow (I
>>> guess it was when I was trying release-plugin without the config (to
>>> reproduce error) and was using Ctrl-C to stop it when I saw that it
>>> "worked".
>>>
>>
>>
>>
>> --
>> ---
>> Richard Vowles,
>> Talk to me about development in Grails, Groovy, Java and for the
>> Blackberry
>> ph: [phone], linkedin, skype:rvowles
>> get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! -
>> http://tinyurl.com/cmcceh
>> podcast: http://www.illegalargument.com
>
>

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

    http://xircles.codehaus.org/manage_email

[Radomir Mladenovic]

1. Release plugin script complete successfully this time (after 1hour 40minutes) but it's still not possible to install plugin from the repository. Here's the result of release:

Checking out locally to '/home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta'.
     [copy] Copying 1 file to /home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta
Committed revision 53573 of plugins-list.xml.
Plug-in release successfully published


2. When I try to install plugin in another project :

$grails install-plugin logdigger-connector
Welcome to Grails 1.1.1 - http://grails.org/
Licensed under Apache Standard License 2.0
Grails home is set to: /home/radomir/grails-1.1.1

Base Directory: /home/radomir/tmp/test-project
Running script /home/radomir/grails-1.1.1/scripts/InstallPlugin.groovy
Environment set to development
Reading remote plugin list ...
Reading remote plugin list ...
Latest release information is not available for plugin 'logdigger-connector', specify concrete release to install


3. grails list-plugins | grep logdigger

logdigger-connector <no releases>    --  No description available

So, looks now all well in the repository. :-(


4. Regarding plugin meta data caching, I had to rename settings.groovy. Otherwise, why I run "grails list-plugins" it goes to repository server and tries to download all info again (thouse 1.5 hours). Very strange.


Regards,
Radomir

On Tue, Jun 23, 2009 at 10:24 AM, Radomir Mladenovic <radomirml@...> wrote:

Thank you for your comments. I'm on Ubuntu and have SVN 1.5.4.

No, I don't use _Events.groovy.

I understand that plugin list is getting bigger and bigger but it
downloads the complete list each time I try to release. This plugin
list could (should?) have been cached as yesterday I had one
successful deployment. I think meta-info got corrupted when I was
testing behavior without settings.groovy and canceled release process
with Ctrl-C.

Anyway, I deleted "~/.grails/1.1.1/grailsplugins/.plugin-meta" and
will run release-plugin again. I'll let you know how it went.

Best regards,
Radomir

On Tue, Jun 23, 2009 at 7:18 AM, Will Droste<will@...> wrote:
> What version of SVN are you using?? On what OS etc.. Its best to use SVN 1.5
> or greater.
> No this is not normal to wait an hour it should be quick.. The process is
> basically this when a plugin is released the plugin.xml meta data gets
> updated on the SVN site.  When you do anything plugin related it will check
> the version of the file (timestamp or svn revision) and update the file.
>  Which should be quick however the main plugins-list.xml is getting larger
> since there's a ton of plugins and the file contains all the
> versions. Everything is deposited in '.grails/1.1' for caching.
> I found the plugin entry and yes it is corrupted.. You'll need to re-release
> it.. I'm sorry this happened to you. Do you use _Events.groovy?  I've seen
> an issue releasing plugins w/ that file present.  From the stacktrace it
> looks like it stopped right in the middle of a commit.  Its odd since it
> looks like meta information was not created correctly because the commit
> should have rolledback being SVN and all.
> Regards,
> Will
>
> On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles
> <richard@...> wrote:
>>
>> It is somewhat a pity that the plugin xml file that everyone downloads
>> from isn't generated from the www.grails.org website. Then people could just
>> point to whereever the zip file for each release was located (svn, github,
>> etc) and the website could manage the meta-data. Just an idea.
>>
>> On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic <radomirml@...>
>> wrote:
>>>
>>> I think I ruined my plugin information in the repository somehow (I
>>> guess it was when I was trying release-plugin without the config (to
>>> reproduce error) and was using Ctrl-C to stop it when I saw that it
>>> "worked".
>>>
>>
>>
>>
>> --
>> ---
>> Richard Vowles,
>> Talk to me about development in Grails, Groovy, Java and for the
>> Blackberry
>> ph: [phone], linkedin, skype:rvowles
>> get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! -
>> http://tinyurl.com/cmcceh
>> podcast: http://www.illegalargument.com
>
>

[Graeme Rocher-3]

Hmm really not sure why it takes so long for you, I often release
plugins it takes 15 minutes maximum, not hours. Very strange.

There seems to be something generally corrupted about your
installation. It may or may not be a Grails bug, by the sounds of the
amount of time its taking it may be because you have a very slow
internet connection and Grails is giving up reading some of the
plugins and producing an incomplete list

Nevertheless I have regenerated the plugin list and published it
(which you can do by the way with grails release-plugin --pluginlist
and I timed at about 10 minutes to complete)

So it should work now.

Regards,

On Tue, Jun 23, 2009 at 11:41 AM, Radomir Mladenovic<radomirml@...> wrote:

> 1. Release plugin script complete successfully this time (after 1hour
> 40minutes) but it's still not possible to install plugin from the
> repository. Here's the result of release:
>
> Checking out locally to
> '/home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta'.
>      [copy] Copying 1 file to
> /home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta
> Committed revision 53573 of plugins-list.xml.
> Plug-in release successfully published
>
>
> 2. When I try to install plugin in another project :
>
> $grails install-plugin logdigger-connector
> Welcome to Grails 1.1.1 - http://grails.org/
> Licensed under Apache Standard License 2.0
> Grails home is set to: /home/radomir/grails-1.1.1
>
> Base Directory: /home/radomir/tmp/test-project
> Running script /home/radomir/grails-1.1.1/scripts/InstallPlugin.groovy
> Environment set to development
> Reading remote plugin list ...
> Reading remote plugin list ...
> Latest release information is not available for plugin
> 'logdigger-connector', specify concrete release to install
>
>
> 3. grails list-plugins | grep logdigger
>
> logdigger-connector <no releases>    --  No description available
>
> So, looks now all well in the repository. :-(
>
>
> 4. Regarding plugin meta data caching, I had to rename settings.groovy.
> Otherwise, why I run "grails list-plugins" it goes to repository server and
> tries to download all info again (thouse 1.5 hours). Very strange.
>
>
> Regards,
> Radomir
>
>
> On Tue, Jun 23, 2009 at 10:24 AM, Radomir Mladenovic <radomirml@...>
> wrote:
>>
>> Thank you for your comments. I'm on Ubuntu and have SVN 1.5.4.
>>
>> No, I don't use _Events.groovy.
>>
>> I understand that plugin list is getting bigger and bigger but it
>> downloads the complete list each time I try to release. This plugin
>> list could (should?) have been cached as yesterday I had one
>> successful deployment. I think meta-info got corrupted when I was
>> testing behavior without settings.groovy and canceled release process
>> with Ctrl-C.
>>
>> Anyway, I deleted "~/.grails/1.1.1/grailsplugins/.plugin-meta" and
>> will run release-plugin again. I'll let you know how it went.
>>
>> Best regards,
>> Radomir
>>
>>
>>
>> On Tue, Jun 23, 2009 at 7:18 AM, Will Droste<will@...> wrote:
>> > What version of SVN are you using?? On what OS etc.. Its best to use SVN
>> > 1.5
>> > or greater.
>> > No this is not normal to wait an hour it should be quick.. The process
>> > is
>> > basically this when a plugin is released the plugin.xml meta data gets
>> > updated on the SVN site.  When you do anything plugin related it will
>> > check
>> > the version of the file (timestamp or svn revision) and update the file.
>> >  Which should be quick however the main plugins-list.xml is getting
>> > larger
>> > since there's a ton of plugins and the file contains all the
>> > versions. Everything is deposited in '.grails/1.1' for caching.
>> > I found the plugin entry and yes it is corrupted.. You'll need to
>> > re-release
>> > it.. I'm sorry this happened to you. Do you use _Events.groovy?  I've
>> > seen
>> > an issue releasing plugins w/ that file present.  From the stacktrace it
>> > looks like it stopped right in the middle of a commit.  Its odd since it
>> > looks like meta information was not created correctly because the commit
>> > should have rolledback being SVN and all.
>> > Regards,
>> > Will
>> >
>> > On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles
>> > <richard@...> wrote:
>> >>
>> >> It is somewhat a pity that the plugin xml file that everyone downloads
>> >> from isn't generated from the www.grails.org website. Then people could
>> >> just
>> >> point to whereever the zip file for each release was located (svn,
>> >> github,
>> >> etc) and the website could manage the meta-data. Just an idea.
>> >>
>> >> On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic
>> >> <radomirml@...>
>> >> wrote:
>> >>>
>> >>> I think I ruined my plugin information in the repository somehow (I
>> >>> guess it was when I was trying release-plugin without the config (to
>> >>> reproduce error) and was using Ctrl-C to stop it when I saw that it
>> >>> "worked".
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> ---
>> >> Richard Vowles,
>> >> Talk to me about development in Grails, Groovy, Java and for the
>> >> Blackberry
>> >> ph: [phone], linkedin, skype:rvowles
>> >> get 2Gb shared disk space in the cloud - Dropbox, its incredibly
>> >> useful! -
>> >> http://tinyurl.com/cmcceh
>> >> podcast: http://www.illegalargument.com
>> >
>> >
>
>

--
Graeme Rocher
Head of Grails Development
SpringSource - Weapons for the War on Java Complexity
http://www.springsource.com

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

    http://xircles.codehaus.org/manage_email

[Radomir Mladenovic]

Thanks for fixing it Graeme.

I'm not sure that my connection is that slow: (Up/Down) [kbps/kbps]:188 / 2.047 (it's ADSL connection)
My up link is significantly slower but I generally don't have a problem with speed. Download of plugin meta-data is down traffic after all. My impression is that communication with svn.codehaus.org via https is incredibly slow for some reason (at least from my location).

Regards,
Radomir

On Tue, Jun 23, 2009 at 12:58 PM, Graeme Rocher <graeme.rocher@...> wrote:

Hmm really not sure why it takes so long for you, I often release
plugins it takes 15 minutes maximum, not hours. Very strange.

There seems to be something generally corrupted about your
installation. It may or may not be a Grails bug, by the sounds of the
amount of time its taking it may be because you have a very slow
internet connection and Grails is giving up reading some of the
plugins and producing an incomplete list

Nevertheless I have regenerated the plugin list and published it
(which you can do by the way with grails release-plugin --pluginlist
and I timed at about 10 minutes to complete)

So it should work now.

Regards,

On Tue, Jun 23, 2009 at 11:41 AM, Radomir Mladenovic<radomirml@...> wrote:
> 1. Release plugin script complete successfully this time (after 1hour
> 40minutes) but it's still not possible to install plugin from the
> repository. Here's the result of release:
>
> Checking out locally to
> '/home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta'.
>      [copy] Copying 1 file to
> /home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta
> Committed revision 53573 of plugins-list.xml.
> Plug-in release successfully published
>
>
> 2. When I try to install plugin in another project :
>
> $grails install-plugin logdigger-connector
> Welcome to Grails 1.1.1 - http://grails.org/
> Licensed under Apache Standard License 2.0
> Grails home is set to: /home/radomir/grails-1.1.1
>
> Base Directory: /home/radomir/tmp/test-project
> Running script /home/radomir/grails-1.1.1/scripts/InstallPlugin.groovy
> Environment set to development
> Reading remote plugin list ...
> Reading remote plugin list ...
> Latest release information is not available for plugin
> 'logdigger-connector', specify concrete release to install
>
>
> 3. grails list-plugins | grep logdigger
>
> logdigger-connector <no releases>    --  No description available
>
> So, looks now all well in the repository. :-(
>
>
> 4. Regarding plugin meta data caching, I had to rename settings.groovy.
> Otherwise, why I run "grails list-plugins" it goes to repository server and
> tries to download all info again (thouse 1.5 hours). Very strange.
>
>
> Regards,
> Radomir
>
>
> On Tue, Jun 23, 2009 at 10:24 AM, Radomir Mladenovic <radomirml@...>
> wrote:
>>
>> Thank you for your comments. I'm on Ubuntu and have SVN 1.5.4.
>>
>> No, I don't use _Events.groovy.
>>
>> I understand that plugin list is getting bigger and bigger but it
>> downloads the complete list each time I try to release. This plugin
>> list could (should?) have been cached as yesterday I had one
>> successful deployment. I think meta-info got corrupted when I was
>> testing behavior without settings.groovy and canceled release process
>> with Ctrl-C.
>>
>> Anyway, I deleted "~/.grails/1.1.1/grailsplugins/.plugin-meta" and
>> will run release-plugin again. I'll let you know how it went.
>>
>> Best regards,
>> Radomir
>>
>>
>>
>> On Tue, Jun 23, 2009 at 7:18 AM, Will Droste<will@...> wrote:
>> > What version of SVN are you using?? On what OS etc.. Its best to use SVN
>> > 1.5
>> > or greater.
>> > No this is not normal to wait an hour it should be quick.. The process
>> > is
>> > basically this when a plugin is released the plugin.xml meta data gets
>> > updated on the SVN site.  When you do anything plugin related it will
>> > check
>> > the version of the file (timestamp or svn revision) and update the file.
>> >  Which should be quick however the main plugins-list.xml is getting
>> > larger
>> > since there's a ton of plugins and the file contains all the
>> > versions. Everything is deposited in '.grails/1.1' for caching.
>> > I found the plugin entry and yes it is corrupted.. You'll need to
>> > re-release
>> > it.. I'm sorry this happened to you. Do you use _Events.groovy?  I've
>> > seen
>> > an issue releasing plugins w/ that file present.  From the stacktrace it
>> > looks like it stopped right in the middle of a commit.  Its odd since it
>> > looks like meta information was not created correctly because the commit
>> > should have rolledback being SVN and all.
>> > Regards,
>> > Will
>> >
>> > On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles
>> > <richard@...> wrote:
>> >>
>> >> It is somewhat a pity that the plugin xml file that everyone downloads
>> >> from isn't generated from the www.grails.org website. Then people could
>> >> just
>> >> point to whereever the zip file for each release was located (svn,
>> >> github,
>> >> etc) and the website could manage the meta-data. Just an idea.
>> >>
>> >> On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic
>> >> <radomirml@...>
>> >> wrote:
>> >>>
>> >>> I think I ruined my plugin information in the repository somehow (I
>> >>> guess it was when I was trying release-plugin without the config (to
>> >>> reproduce error) and was using Ctrl-C to stop it when I saw that it
>> >>> "worked".
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> ---
>> >> Richard Vowles,
>> >> Talk to me about development in Grails, Groovy, Java and for the
>> >> Blackberry
>> >> ph: [phone], linkedin, skype:rvowles
>> >> get 2Gb shared disk space in the cloud - Dropbox, its incredibly
>> >> useful! -
>> >> http://tinyurl.com/cmcceh
>> >> podcast: http://www.illegalargument.com
>> >
>> >
>
>

--

Graeme Rocher
Head of Grails Development
SpringSource - Weapons for the War on Java Complexity
http://www.springsource.com

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

To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Graeme Rocher-3]

On Tue, Jun 23, 2009 at 12:32 PM, Radomir Mladenovic
<radomirml@...> wrote:
>
> Thanks for fixing it Graeme.
>
> I'm not sure that my connection is that slow: (Up/Down) [kbps/kbps]:188 / 2.047 (it's ADSL connection)
> My up link is significantly slower but I generally don't have a problem with speed. Download of plugin meta-data is down traffic after all. My impression is that communication with svn.codehaus.org via https is incredibly slow for some reason (at least from my location).

Yeah even if you local connection is fast it may be the connection
between you and the codehaus servers is not great :-(

>
> Regards,
> Radomir
>
>
>
> On Tue, Jun 23, 2009 at 12:58 PM, Graeme Rocher <graeme.rocher@...> wrote:
>>
>> Hmm really not sure why it takes so long for you, I often release
>> plugins it takes 15 minutes maximum, not hours. Very strange.
>>
>> There seems to be something generally corrupted about your
>> installation. It may or may not be a Grails bug, by the sounds of the
>> amount of time its taking it may be because you have a very slow
>> internet connection and Grails is giving up reading some of the
>> plugins and producing an incomplete list
>>
>> Nevertheless I have regenerated the plugin list and published it
>> (which you can do by the way with grails release-plugin --pluginlist
>> and I timed at about 10 minutes to complete)
>>
>> So it should work now.
>>
>> Regards,
>>
>> On Tue, Jun 23, 2009 at 11:41 AM, Radomir Mladenovic<radomirml@...> wrote:
>> > 1. Release plugin script complete successfully this time (after 1hour
>> > 40minutes) but it's still not possible to install plugin from the
>> > repository. Here's the result of release:
>> >
>> > Checking out locally to
>> > '/home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta'.
>> >      [copy] Copying 1 file to
>> > /home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta
>> > Committed revision 53573 of plugins-list.xml.
>> > Plug-in release successfully published
>> >
>> >
>> > 2. When I try to install plugin in another project :
>> >
>> > $grails install-plugin logdigger-connector
>> > Welcome to Grails 1.1.1 - http://grails.org/
>> > Licensed under Apache Standard License 2.0
>> > Grails home is set to: /home/radomir/grails-1.1.1
>> >
>> > Base Directory: /home/radomir/tmp/test-project
>> > Running script /home/radomir/grails-1.1.1/scripts/InstallPlugin.groovy
>> > Environment set to development
>> > Reading remote plugin list ...
>> > Reading remote plugin list ...
>> > Latest release information is not available for plugin
>> > 'logdigger-connector', specify concrete release to install
>> >
>> >
>> > 3. grails list-plugins | grep logdigger
>> >
>> > logdigger-connector <no releases>    --  No description available
>> >
>> > So, looks now all well in the repository. :-(
>> >
>> >
>> > 4. Regarding plugin meta data caching, I had to rename settings.groovy.
>> > Otherwise, why I run "grails list-plugins" it goes to repository server and
>> > tries to download all info again (thouse 1.5 hours). Very strange.
>> >
>> >
>> > Regards,
>> > Radomir
>> >
>> >
>> > On Tue, Jun 23, 2009 at 10:24 AM, Radomir Mladenovic <radomirml@...>
>> > wrote:
>> >>
>> >> Thank you for your comments. I'm on Ubuntu and have SVN 1.5.4.
>> >>
>> >> No, I don't use _Events.groovy.
>> >>
>> >> I understand that plugin list is getting bigger and bigger but it
>> >> downloads the complete list each time I try to release. This plugin
>> >> list could (should?) have been cached as yesterday I had one
>> >> successful deployment. I think meta-info got corrupted when I was
>> >> testing behavior without settings.groovy and canceled release process
>> >> with Ctrl-C.
>> >>
>> >> Anyway, I deleted "~/.grails/1.1.1/grailsplugins/.plugin-meta" and
>> >> will run release-plugin again. I'll let you know how it went.
>> >>
>> >> Best regards,
>> >> Radomir
>> >>
>> >>
>> >>
>> >> On Tue, Jun 23, 2009 at 7:18 AM, Will Droste<will@...> wrote:
>> >> > What version of SVN are you using?? On what OS etc.. Its best to use SVN
>> >> > 1.5
>> >> > or greater.
>> >> > No this is not normal to wait an hour it should be quick.. The process
>> >> > is
>> >> > basically this when a plugin is released the plugin.xml meta data gets
>> >> > updated on the SVN site.  When you do anything plugin related it will
>> >> > check
>> >> > the version of the file (timestamp or svn revision) and update the file.
>> >> >  Which should be quick however the main plugins-list.xml is getting
>> >> > larger
>> >> > since there's a ton of plugins and the file contains all the
>> >> > versions. Everything is deposited in '.grails/1.1' for caching.
>> >> > I found the plugin entry and yes it is corrupted.. You'll need to
>> >> > re-release
>> >> > it.. I'm sorry this happened to you. Do you use _Events.groovy?  I've
>> >> > seen
>> >> > an issue releasing plugins w/ that file present.  From the stacktrace it
>> >> > looks like it stopped right in the middle of a commit.  Its odd since it
>> >> > looks like meta information was not created correctly because the commit
>> >> > should have rolledback being SVN and all.
>> >> > Regards,
>> >> > Will
>> >> >
>> >> > On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles
>> >> > <richard@...> wrote:
>> >> >>
>> >> >> It is somewhat a pity that the plugin xml file that everyone downloads
>> >> >> from isn't generated from the www.grails.org website. Then people could
>> >> >> just
>> >> >> point to whereever the zip file for each release was located (svn,
>> >> >> github,
>> >> >> etc) and the website could manage the meta-data. Just an idea.
>> >> >>
>> >> >> On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic
>> >> >> <radomirml@...>
>> >> >> wrote:
>> >> >>>
>> >> >>> I think I ruined my plugin information in the repository somehow (I
>> >> >>> guess it was when I was trying release-plugin without the config (to
>> >> >>> reproduce error) and was using Ctrl-C to stop it when I saw that it
>> >> >>> "worked".
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> ---
>> >> >> Richard Vowles,
>> >> >> Talk to me about development in Grails, Groovy, Java and for the
>> >> >> Blackberry
>> >> >> ph: [phone], linkedin, skype:rvowles
>> >> >> get 2Gb shared disk space in the cloud - Dropbox, its incredibly
>> >> >> useful! -
>> >> >> http://tinyurl.com/cmcceh
>> >> >> podcast: http://www.illegalargument.com
>> >> >
>> >> >
>> >
>> >
>>
>>
>>
>> --
>> Graeme Rocher
>> Head of Grails Development
>> SpringSource - Weapons for the War on Java Complexity
>> http://www.springsource.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>

--
Graeme Rocher
Head of Grails Development
SpringSource - Weapons for the War on Java Complexity
http://www.springsource.com

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

    http://xircles.codehaus.org/manage_email

[Radomir Mladenovic]

Hmm... connection to codehaus doesn't appear to be the problem. Here's the ping result to codehaus, grails.org and google:

ping svn.codehaus.org
7 packets transmitted, 7 received, 0% packet loss, time 6006ms
rtt min/avg/max/mdev = 161.029/232.736/270.433/39.727 ms

ping grails.org
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 173.232/233.825/274.070/32.998 ms

ping www.google.com
10 packets transmitted, 10 received, 0% packet loss, time 9001ms
rtt min/avg/max/mdev = 61.353/126.017/191.837/46.834 ms


The problem is something else I guess.

On Tue, Jun 23, 2009 at 1:37 PM, Graeme Rocher <graeme.rocher@...> wrote:

On Tue, Jun 23, 2009 at 12:32 PM, Radomir Mladenovic
<radomirml@...> wrote:
>
> Thanks for fixing it Graeme.
>
> I'm not sure that my connection is that slow: (Up/Down) [kbps/kbps]:188 / 2.047 (it's ADSL connection)
> My up link is significantly slower but I generally don't have a problem with speed. Download of plugin meta-data is down traffic after all. My impression is that communication with svn.codehaus.org via https is incredibly slow for some reason (at least from my location).

Yeah even if you local connection is fast it may be the connection
between you and the codehaus servers is not great :-(

>
> Regards,
> Radomir
>
>
>
> On Tue, Jun 23, 2009 at 12:58 PM, Graeme Rocher <graeme.rocher@...> wrote:
>>
>> Hmm really not sure why it takes so long for you, I often release
>> plugins it takes 15 minutes maximum, not hours. Very strange.
>>
>> There seems to be something generally corrupted about your
>> installation. It may or may not be a Grails bug, by the sounds of the
>> amount of time its taking it may be because you have a very slow
>> internet connection and Grails is giving up reading some of the
>> plugins and producing an incomplete list
>>
>> Nevertheless I have regenerated the plugin list and published it
>> (which you can do by the way with grails release-plugin --pluginlist
>> and I timed at about 10 minutes to complete)
>>
>> So it should work now.
>>
>> Regards,
>>
>> On Tue, Jun 23, 2009 at 11:41 AM, Radomir Mladenovic<radomirml@...> wrote:
>> > 1. Release plugin script complete successfully this time (after 1hour
>> > 40minutes) but it's still not possible to install plugin from the
>> > repository. Here's the result of release:
>> >
>> > Checking out locally to
>> > '/home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta'.
>> >      [copy] Copying 1 file to
>> > /home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta
>> > Committed revision 53573 of plugins-list.xml.
>> > Plug-in release successfully published
>> >
>> >
>> > 2. When I try to install plugin in another project :
>> >
>> > $grails install-plugin logdigger-connector
>> > Welcome to Grails 1.1.1 - http://grails.org/
>> > Licensed under Apache Standard License 2.0
>> > Grails home is set to: /home/radomir/grails-1.1.1
>> >
>> > Base Directory: /home/radomir/tmp/test-project
>> > Running script /home/radomir/grails-1.1.1/scripts/InstallPlugin.groovy
>> > Environment set to development
>> > Reading remote plugin list ...
>> > Reading remote plugin list ...
>> > Latest release information is not available for plugin
>> > 'logdigger-connector', specify concrete release to install
>> >
>> >
>> > 3. grails list-plugins | grep logdigger
>> >
>> > logdigger-connector <no releases>    --  No description available
>> >
>> > So, looks now all well in the repository. :-(
>> >
>> >
>> > 4. Regarding plugin meta data caching, I had to rename settings.groovy.
>> > Otherwise, why I run "grails list-plugins" it goes to repository server and
>> > tries to download all info again (thouse 1.5 hours). Very strange.
>> >
>> >
>> > Regards,
>> > Radomir
>> >
>> >
>> > On Tue, Jun 23, 2009 at 10:24 AM, Radomir Mladenovic <radomirml@...>
>> > wrote:
>> >>
>> >> Thank you for your comments. I'm on Ubuntu and have SVN 1.5.4.
>> >>
>> >> No, I don't use _Events.groovy.
>> >>
>> >> I understand that plugin list is getting bigger and bigger but it
>> >> downloads the complete list each time I try to release. This plugin
>> >> list could (should?) have been cached as yesterday I had one
>> >> successful deployment. I think meta-info got corrupted when I was
>> >> testing behavior without settings.groovy and canceled release process
>> >> with Ctrl-C.
>> >>
>> >> Anyway, I deleted "~/.grails/1.1.1/grailsplugins/.plugin-meta" and
>> >> will run release-plugin again. I'll let you know how it went.
>> >>
>> >> Best regards,
>> >> Radomir
>> >>
>> >>
>> >>
>> >> On Tue, Jun 23, 2009 at 7:18 AM, Will Droste<will@...> wrote:
>> >> > What version of SVN are you using?? On what OS etc.. Its best to use SVN
>> >> > 1.5
>> >> > or greater.
>> >> > No this is not normal to wait an hour it should be quick.. The process
>> >> > is
>> >> > basically this when a plugin is released the plugin.xml meta data gets
>> >> > updated on the SVN site.  When you do anything plugin related it will
>> >> > check
>> >> > the version of the file (timestamp or svn revision) and update the file.
>> >> >  Which should be quick however the main plugins-list.xml is getting
>> >> > larger
>> >> > since there's a ton of plugins and the file contains all the
>> >> > versions. Everything is deposited in '.grails/1.1' for caching.
>> >> > I found the plugin entry and yes it is corrupted.. You'll need to
>> >> > re-release
>> >> > it.. I'm sorry this happened to you. Do you use _Events.groovy?  I've
>> >> > seen
>> >> > an issue releasing plugins w/ that file present.  From the stacktrace it
>> >> > looks like it stopped right in the middle of a commit.  Its odd since it
>> >> > looks like meta information was not created correctly because the commit
>> >> > should have rolledback being SVN and all.
>> >> > Regards,
>> >> > Will
>> >> >
>> >> > On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles
>> >> > <richard@...> wrote:
>> >> >>
>> >> >> It is somewhat a pity that the plugin xml file that everyone downloads
>> >> >> from isn't generated from the www.grails.org website. Then people could
>> >> >> just
>> >> >> point to whereever the zip file for each release was located (svn,
>> >> >> github,
>> >> >> etc) and the website could manage the meta-data. Just an idea.
>> >> >>
>> >> >> On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic
>> >> >> <radomirml@...>
>> >> >> wrote:
>> >> >>>
>> >> >>> I think I ruined my plugin information in the repository somehow (I
>> >> >>> guess it was when I was trying release-plugin without the config (to
>> >> >>> reproduce error) and was using Ctrl-C to stop it when I saw that it
>> >> >>> "worked".
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> ---
>> >> >> Richard Vowles,
>> >> >> Talk to me about development in Grails, Groovy, Java and for the
>> >> >> Blackberry
>> >> >> ph: [phone], linkedin, skype:rvowles
>> >> >> get 2Gb shared disk space in the cloud - Dropbox, its incredibly
>> >> >> useful! -
>> >> >> http://tinyurl.com/cmcceh
>> >> >> podcast: http://www.illegalargument.com
>> >> >
>> >> >
>> >
>> >
>>
>>
>>
>> --
>> Graeme Rocher
>> Head of Grails Development
>> SpringSource - Weapons for the War on Java Complexity
>> http://www.springsource.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>



--
Graeme Rocher
Head of Grails Development
SpringSource - Weapons for the War on Java Complexity
http://www.springsource.com

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

   http://xircles.codehaus.org/manage_email

[Lee Butts]

I just had the same fight with release-plugin under 1.1.1

How come it no longer prompts me for my password when using the default repository?
Has a JIRA been logged for that?

If this is expected then the Creating Plugins documentation needs updating to include the steps for creating settings.groovy

cheers

Lee

2009/6/23 Radomir Mladenovic <radomirml@...>

Hmm... connection to codehaus doesn't appear to be the problem. Here's the ping result to codehaus, grails.org and google:

ping svn.codehaus.org
7 packets transmitted, 7 received, 0% packet loss, time 6006ms
rtt min/avg/max/mdev = 161.029/232.736/270.433/39.727 ms

ping grails.org
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 173.232/233.825/274.070/32.998 ms

ping www.google.com
10 packets transmitted, 10 received, 0% packet loss, time 9001ms
rtt min/avg/max/mdev = 61.353/126.017/191.837/46.834 ms


The problem is something else I guess.

On Tue, Jun 23, 2009 at 1:37 PM, Graeme Rocher <graeme.rocher@...> wrote:

On Tue, Jun 23, 2009 at 12:32 PM, Radomir Mladenovic
<radomirml@...> wrote:
>
> Thanks for fixing it Graeme.
>
> I'm not sure that my connection is that slow: (Up/Down) [kbps/kbps]:188 / 2.047 (it's ADSL connection)
> My up link is significantly slower but I generally don't have a problem with speed. Download of plugin meta-data is down traffic after all. My impression is that communication with svn.codehaus.org via https is incredibly slow for some reason (at least from my location).

Yeah even if you local connection is fast it may be the connection
between you and the codehaus servers is not great :-(

>
> Regards,
> Radomir
>
>
>
> On Tue, Jun 23, 2009 at 12:58 PM, Graeme Rocher <graeme.rocher@...> wrote:
>>
>> Hmm really not sure why it takes so long for you, I often release
>> plugins it takes 15 minutes maximum, not hours. Very strange.
>>
>> There seems to be something generally corrupted about your
>> installation. It may or may not be a Grails bug, by the sounds of the
>> amount of time its taking it may be because you have a very slow
>> internet connection and Grails is giving up reading some of the
>> plugins and producing an incomplete list
>>
>> Nevertheless I have regenerated the plugin list and published it
>> (which you can do by the way with grails release-plugin --pluginlist
>> and I timed at about 10 minutes to complete)
>>
>> So it should work now.
>>
>> Regards,
>>
>> On Tue, Jun 23, 2009 at 11:41 AM, Radomir Mladenovic<radomirml@...> wrote:
>> > 1. Release plugin script complete successfully this time (after 1hour
>> > 40minutes) but it's still not possible to install plugin from the
>> > repository. Here's the result of release:
>> >
>> > Checking out locally to
>> > '/home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta'.
>> >      [copy] Copying 1 file to
>> > /home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta
>> > Committed revision 53573 of plugins-list.xml.
>> > Plug-in release successfully published
>> >
>> >
>> > 2. When I try to install plugin in another project :
>> >
>> > $grails install-plugin logdigger-connector
>> > Welcome to Grails 1.1.1 - http://grails.org/
>> > Licensed under Apache Standard License 2.0
>> > Grails home is set to: /home/radomir/grails-1.1.1
>> >
>> > Base Directory: /home/radomir/tmp/test-project
>> > Running script /home/radomir/grails-1.1.1/scripts/InstallPlugin.groovy
>> > Environment set to development
>> > Reading remote plugin list ...
>> > Reading remote plugin list ...
>> > Latest release information is not available for plugin
>> > 'logdigger-connector', specify concrete release to install
>> >
>> >
>> > 3. grails list-plugins | grep logdigger
>> >
>> > logdigger-connector <no releases>    --  No description available
>> >
>> > So, looks now all well in the repository. :-(
>> >
>> >
>> > 4. Regarding plugin meta data caching, I had to rename settings.groovy.
>> > Otherwise, why I run "grails list-plugins" it goes to repository server and
>> > tries to download all info again (thouse 1.5 hours). Very strange.
>> >
>> >
>> > Regards,
>> > Radomir
>> >
>> >
>> > On Tue, Jun 23, 2009 at 10:24 AM, Radomir Mladenovic <radomirml@...>
>> > wrote:
>> >>
>> >> Thank you for your comments. I'm on Ubuntu and have SVN 1.5.4.
>> >>
>> >> No, I don't use _Events.groovy.
>> >>
>> >> I understand that plugin list is getting bigger and bigger but it
>> >> downloads the complete list each time I try to release. This plugin
>> >> list could (should?) have been cached as yesterday I had one
>> >> successful deployment. I think meta-info got corrupted when I was
>> >> testing behavior without settings.groovy and canceled release process
>> >> with Ctrl-C.
>> >>
>> >> Anyway, I deleted "~/.grails/1.1.1/grailsplugins/.plugin-meta" and
>> >> will run release-plugin again. I'll let you know how it went.
>> >>
>> >> Best regards,
>> >> Radomir
>> >>
>> >>
>> >>
>> >> On Tue, Jun 23, 2009 at 7:18 AM, Will Droste<will@...> wrote:
>> >> > What version of SVN are you using?? On what OS etc.. Its best to use SVN
>> >> > 1.5
>> >> > or greater.
>> >> > No this is not normal to wait an hour it should be quick.. The process
>> >> > is
>> >> > basically this when a plugin is released the plugin.xml meta data gets
>> >> > updated on the SVN site.  When you do anything plugin related it will
>> >> > check
>> >> > the version of the file (timestamp or svn revision) and update the file.
>> >> >  Which should be quick however the main plugins-list.xml is getting
>> >> > larger
>> >> > since there's a ton of plugins and the file contains all the
>> >> > versions. Everything is deposited in '.grails/1.1' for caching.
>> >> > I found the plugin entry and yes it is corrupted.. You'll need to
>> >> > re-release
>> >> > it.. I'm sorry this happened to you. Do you use _Events.groovy?  I've
>> >> > seen
>> >> > an issue releasing plugins w/ that file present.  From the stacktrace it
>> >> > looks like it stopped right in the middle of a commit.  Its odd since it
>> >> > looks like meta information was not created correctly because the commit
>> >> > should have rolledback being SVN and all.
>> >> > Regards,
>> >> > Will
>> >> >
>> >> > On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles
>> >> > <richard@...> wrote:
>> >> >>
>> >> >> It is somewhat a pity that the plugin xml file that everyone downloads
>> >> >> from isn't generated from the www.grails.org website. Then people could
>> >> >> just
>> >> >> point to whereever the zip file for each release was located (svn,
>> >> >> github,
>> >> >> etc) and the website could manage the meta-data. Just an idea.
>> >> >>
>> >> >> On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic
>> >> >> <radomirml@...>
>> >> >> wrote:
>> >> >>>
>> >> >>> I think I ruined my plugin information in the repository somehow (I
>> >> >>> guess it was when I was trying release-plugin without the config (to
>> >> >>> reproduce error) and was using Ctrl-C to stop it when I saw that it
>> >> >>> "worked".
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> ---
>> >> >> Richard Vowles,
>> >> >> Talk to me about development in Grails, Groovy, Java and for the
>> >> >> Blackberry
>> >> >> ph: [phone], linkedin, skype:rvowles
>> >> >> get 2Gb shared disk space in the cloud - Dropbox, its incredibly
>> >> >> useful! -
>> >> >> http://tinyurl.com/cmcceh
>> >> >> podcast: http://www.illegalargument.com
>> >> >
>> >> >
>> >
>> >
>>
>>
>>
>> --
>> Graeme Rocher
>> Head of Grails Development
>> SpringSource - Weapons for the War on Java Complexity
>> http://www.springsource.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>



--
Graeme Rocher
Head of Grails Development
SpringSource - Weapons for the War on Java Complexity
http://www.springsource.com

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

   http://xircles.codehaus.org/manage_email

[Graeme Rocher-3]

On Thu, Jul 9, 2009 at 10:56 AM, Lee Butts<leebutts@...> wrote:
> I just had the same fight with release-plugin under 1.1.1
>
> How come it no longer prompts me for my password when using the default
> repository?
> Has a JIRA been logged for that?

Yes and its already fixed in 1.2M1

Cheers

>
> If this is expected then the Creating Plugins documentation needs updating
> to include the steps for creating settings.groovy
>
> cheers
>
> Lee
>
> 2009/6/23 Radomir Mladenovic <radomirml@...>
>>
>> Hmm... connection to codehaus doesn't appear to be the problem. Here's the
>> ping result to codehaus, grails.org and google:
>>
>> ping svn.codehaus.org
>> 7 packets transmitted, 7 received, 0% packet loss, time 6006ms
>> rtt min/avg/max/mdev = 161.029/232.736/270.433/39.727 ms
>>
>> ping grails.org
>> 5 packets transmitted, 5 received, 0% packet loss, time 4003ms
>> rtt min/avg/max/mdev = 173.232/233.825/274.070/32.998 ms
>>
>> ping www.google.com
>> 10 packets transmitted, 10 received, 0% packet loss, time 9001ms
>> rtt min/avg/max/mdev = 61.353/126.017/191.837/46.834 ms
>>
>>
>> The problem is something else I guess.
>>
>>
>>
>> On Tue, Jun 23, 2009 at 1:37 PM, Graeme Rocher
>> <graeme.rocher@...> wrote:
>>>
>>> On Tue, Jun 23, 2009 at 12:32 PM, Radomir Mladenovic
>>> <radomirml@...> wrote:
>>> >
>>> > Thanks for fixing it Graeme.
>>> >
>>> > I'm not sure that my connection is that slow: (Up/Down) [kbps/kbps]:188
>>> > / 2.047 (it's ADSL connection)
>>> > My up link is significantly slower but I generally don't have a problem
>>> > with speed. Download of plugin meta-data is down traffic after all. My
>>> > impression is that communication with svn.codehaus.org via https is
>>> > incredibly slow for some reason (at least from my location).
>>>
>>> Yeah even if you local connection is fast it may be the connection
>>> between you and the codehaus servers is not great :-(
>>>
>>> >
>>> > Regards,
>>> > Radomir
>>> >
>>> >
>>> >
>>> > On Tue, Jun 23, 2009 at 12:58 PM, Graeme Rocher
>>> > <graeme.rocher@...> wrote:
>>> >>
>>> >> Hmm really not sure why it takes so long for you, I often release
>>> >> plugins it takes 15 minutes maximum, not hours. Very strange.
>>> >>
>>> >> There seems to be something generally corrupted about your
>>> >> installation. It may or may not be a Grails bug, by the sounds of the
>>> >> amount of time its taking it may be because you have a very slow
>>> >> internet connection and Grails is giving up reading some of the
>>> >> plugins and producing an incomplete list
>>> >>
>>> >> Nevertheless I have regenerated the plugin list and published it
>>> >> (which you can do by the way with grails release-plugin --pluginlist
>>> >> and I timed at about 10 minutes to complete)
>>> >>
>>> >> So it should work now.
>>> >>
>>> >> Regards,
>>> >>
>>> >> On Tue, Jun 23, 2009 at 11:41 AM, Radomir
>>> >> Mladenovic<radomirml@...> wrote:
>>> >> > 1. Release plugin script complete successfully this time (after
>>> >> > 1hour
>>> >> > 40minutes) but it's still not possible to install plugin from the
>>> >> > repository. Here's the result of release:
>>> >> >
>>> >> > Checking out locally to
>>> >> > '/home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta'.
>>> >> >      [copy] Copying 1 file to
>>> >> > /home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta
>>> >> > Committed revision 53573 of plugins-list.xml.
>>> >> > Plug-in release successfully published
>>> >> >
>>> >> >
>>> >> > 2. When I try to install plugin in another project :
>>> >> >
>>> >> > $grails install-plugin logdigger-connector
>>> >> > Welcome to Grails 1.1.1 - http://grails.org/
>>> >> > Licensed under Apache Standard License 2.0
>>> >> > Grails home is set to: /home/radomir/grails-1.1.1
>>> >> >
>>> >> > Base Directory: /home/radomir/tmp/test-project
>>> >> > Running script
>>> >> > /home/radomir/grails-1.1.1/scripts/InstallPlugin.groovy
>>> >> > Environment set to development
>>> >> > Reading remote plugin list ...
>>> >> > Reading remote plugin list ...
>>> >> > Latest release information is not available for plugin
>>> >> > 'logdigger-connector', specify concrete release to install
>>> >> >
>>> >> >
>>> >> > 3. grails list-plugins | grep logdigger
>>> >> >
>>> >> > logdigger-connector <no releases>    --  No description available
>>> >> >
>>> >> > So, looks now all well in the repository. :-(
>>> >> >
>>> >> >
>>> >> > 4. Regarding plugin meta data caching, I had to rename
>>> >> > settings.groovy.
>>> >> > Otherwise, why I run "grails list-plugins" it goes to repository
>>> >> > server and
>>> >> > tries to download all info again (thouse 1.5 hours). Very strange.
>>> >> >
>>> >> >
>>> >> > Regards,
>>> >> > Radomir
>>> >> >
>>> >> >
>>> >> > On Tue, Jun 23, 2009 at 10:24 AM, Radomir Mladenovic
>>> >> > <radomirml@...>
>>> >> > wrote:
>>> >> >>
>>> >> >> Thank you for your comments. I'm on Ubuntu and have SVN 1.5.4.
>>> >> >>
>>> >> >> No, I don't use _Events.groovy.
>>> >> >>
>>> >> >> I understand that plugin list is getting bigger and bigger but it
>>> >> >> downloads the complete list each time I try to release. This plugin
>>> >> >> list could (should?) have been cached as yesterday I had one
>>> >> >> successful deployment. I think meta-info got corrupted when I was
>>> >> >> testing behavior without settings.groovy and canceled release
>>> >> >> process
>>> >> >> with Ctrl-C.
>>> >> >>
>>> >> >> Anyway, I deleted "~/.grails/1.1.1/grailsplugins/.plugin-meta" and
>>> >> >> will run release-plugin again. I'll let you know how it went.
>>> >> >>
>>> >> >> Best regards,
>>> >> >> Radomir
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On Tue, Jun 23, 2009 at 7:18 AM, Will Droste<will@...>
>>> >> >> wrote:
>>> >> >> > What version of SVN are you using?? On what OS etc.. Its best to
>>> >> >> > use SVN
>>> >> >> > 1.5
>>> >> >> > or greater.
>>> >> >> > No this is not normal to wait an hour it should be quick.. The
>>> >> >> > process
>>> >> >> > is
>>> >> >> > basically this when a plugin is released the plugin.xml meta data
>>> >> >> > gets
>>> >> >> > updated on the SVN site.  When you do anything plugin related it
>>> >> >> > will
>>> >> >> > check
>>> >> >> > the version of the file (timestamp or svn revision) and update
>>> >> >> > the file.
>>> >> >> >  Which should be quick however the main plugins-list.xml is
>>> >> >> > getting
>>> >> >> > larger
>>> >> >> > since there's a ton of plugins and the file contains all the
>>> >> >> > versions. Everything is deposited in '.grails/1.1' for caching.
>>> >> >> > I found the plugin entry and yes it is corrupted.. You'll need to
>>> >> >> > re-release
>>> >> >> > it.. I'm sorry this happened to you. Do you use _Events.groovy?
>>> >> >> >  I've
>>> >> >> > seen
>>> >> >> > an issue releasing plugins w/ that file present.  From the
>>> >> >> > stacktrace it
>>> >> >> > looks like it stopped right in the middle of a commit.  Its odd
>>> >> >> > since it
>>> >> >> > looks like meta information was not created correctly because the
>>> >> >> > commit
>>> >> >> > should have rolledback being SVN and all.
>>> >> >> > Regards,
>>> >> >> > Will
>>> >> >> >
>>> >> >> > On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles
>>> >> >> > <richard@...> wrote:
>>> >> >> >>
>>> >> >> >> It is somewhat a pity that the plugin xml file that everyone
>>> >> >> >> downloads
>>> >> >> >> from isn't generated from the www.grails.org website. Then
>>> >> >> >> people could
>>> >> >> >> just
>>> >> >> >> point to whereever the zip file for each release was located
>>> >> >> >> (svn,
>>> >> >> >> github,
>>> >> >> >> etc) and the website could manage the meta-data. Just an idea.
>>> >> >> >>
>>> >> >> >> On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic
>>> >> >> >> <radomirml@...>
>>> >> >> >> wrote:
>>> >> >> >>>
>>> >> >> >>> I think I ruined my plugin information in the repository
>>> >> >> >>> somehow (I
>>> >> >> >>> guess it was when I was trying release-plugin without the
>>> >> >> >>> config (to
>>> >> >> >>> reproduce error) and was using Ctrl-C to stop it when I saw
>>> >> >> >>> that it
>>> >> >> >>> "worked".
>>> >> >> >>>
>>> >> >> >>
>>> >> >> >>
>>> >> >> >>
>>> >> >> >> --
>>> >> >> >> ---
>>> >> >> >> Richard Vowles,
>>> >> >> >> Talk to me about development in Grails, Groovy, Java and for the
>>> >> >> >> Blackberry
>>> >> >> >> ph: [phone], linkedin, skype:rvowles
>>> >> >> >> get 2Gb shared disk space in the cloud - Dropbox, its incredibly
>>> >> >> >> useful! -
>>> >> >> >> http://tinyurl.com/cmcceh
>>> >> >> >> podcast: http://www.illegalargument.com
>>> >> >> >
>>> >> >> >
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Graeme Rocher
>>> >> Head of Grails Development
>>> >> SpringSource - Weapons for the War on Java Complexity
>>> >> http://www.springsource.com
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe from this list, please visit:
>>> >>
>>> >>    http://xircles.codehaus.org/manage_email
>>> >>
>>> >>
>>> >
>>>
>>>
>>>
>>> --
>>> Graeme Rocher
>>> Head of Grails Development
>>> SpringSource - Weapons for the War on Java Complexity
>>> http://www.springsource.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>
>

--
Graeme Rocher
Head of Grails Development
SpringSource - Weapons for the War on Java Complexity
http://www.springsource.com

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

    http://xircles.codehaus.org/manage_email

[Lee Butts]

Awesome - thanks Graeme.

cheers

Lee

2009/7/9 Graeme Rocher <graeme.rocher@...>

On Thu, Jul 9, 2009 at 10:56 AM, Lee Butts<leebutts@...> wrote:
> I just had the same fight with release-plugin under 1.1.1
>
> How come it no longer prompts me for my password when using the default
> repository?
> Has a JIRA been logged for that?

Yes and its already fixed in 1.2M1

Cheers

>
> If this is expected then the Creating Plugins documentation needs updating
> to include the steps for creating settings.groovy
>
> cheers
>
> Lee
>
> 2009/6/23 Radomir Mladenovic <radomirml@...>
>>
>> Hmm... connection to codehaus doesn't appear to be the problem. Here's the
>> ping result to codehaus, grails.org and google:
>>
>> ping svn.codehaus.org
>> 7 packets transmitted, 7 received, 0% packet loss, time 6006ms
>> rtt min/avg/max/mdev = 161.029/232.736/270.433/39.727 ms
>>
>> ping grails.org
>> 5 packets transmitted, 5 received, 0% packet loss, time 4003ms
>> rtt min/avg/max/mdev = 173.232/233.825/274.070/32.998 ms
>>
>> ping www.google.com
>> 10 packets transmitted, 10 received, 0% packet loss, time 9001ms
>> rtt min/avg/max/mdev = 61.353/126.017/191.837/46.834 ms
>>
>>
>> The problem is something else I guess.
>>
>>
>>
>> On Tue, Jun 23, 2009 at 1:37 PM, Graeme Rocher
>> <graeme.rocher@...> wrote:
>>>
>>> On Tue, Jun 23, 2009 at 12:32 PM, Radomir Mladenovic
>>> <radomirml@...> wrote:
>>> >
>>> > Thanks for fixing it Graeme.
>>> >
>>> > I'm not sure that my connection is that slow: (Up/Down) [kbps/kbps]:188
>>> > / 2.047 (it's ADSL connection)
>>> > My up link is significantly slower but I generally don't have a problem
>>> > with speed. Download of plugin meta-data is down traffic after all. My
>>> > impression is that communication with svn.codehaus.org via https is
>>> > incredibly slow for some reason (at least from my location).
>>>
>>> Yeah even if you local connection is fast it may be the connection
>>> between you and the codehaus servers is not great :-(
>>>
>>> >
>>> > Regards,
>>> > Radomir
>>> >
>>> >
>>> >
>>> > On Tue, Jun 23, 2009 at 12:58 PM, Graeme Rocher
>>> > <graeme.rocher@...> wrote:
>>> >>
>>> >> Hmm really not sure why it takes so long for you, I often release
>>> >> plugins it takes 15 minutes maximum, not hours. Very strange.
>>> >>
>>> >> There seems to be something generally corrupted about your
>>> >> installation. It may or may not be a Grails bug, by the sounds of the
>>> >> amount of time its taking it may be because you have a very slow
>>> >> internet connection and Grails is giving up reading some of the
>>> >> plugins and producing an incomplete list
>>> >>
>>> >> Nevertheless I have regenerated the plugin list and published it
>>> >> (which you can do by the way with grails release-plugin --pluginlist
>>> >> and I timed at about 10 minutes to complete)
>>> >>
>>> >> So it should work now.
>>> >>
>>> >> Regards,
>>> >>
>>> >> On Tue, Jun 23, 2009 at 11:41 AM, Radomir
>>> >> Mladenovic<radomirml@...> wrote:
>>> >> > 1. Release plugin script complete successfully this time (after
>>> >> > 1hour
>>> >> > 40minutes) but it's still not possible to install plugin from the
>>> >> > repository. Here's the result of release:
>>> >> >
>>> >> > Checking out locally to
>>> >> > '/home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta'.
>>> >> >      [copy] Copying 1 file to
>>> >> > /home/radomir/.grails/1.1.1/grailsplugins/.plugin-meta
>>> >> > Committed revision 53573 of plugins-list.xml.
>>> >> > Plug-in release successfully published
>>> >> >
>>> >> >
>>> >> > 2. When I try to install plugin in another project :
>>> >> >
>>> >> > $grails install-plugin logdigger-connector
>>> >> > Welcome to Grails 1.1.1 - http://grails.org/
>>> >> > Licensed under Apache Standard License 2.0
>>> >> > Grails home is set to: /home/radomir/grails-1.1.1
>>> >> >
>>> >> > Base Directory: /home/radomir/tmp/test-project
>>> >> > Running script
>>> >> > /home/radomir/grails-1.1.1/scripts/InstallPlugin.groovy
>>> >> > Environment set to development
>>> >> > Reading remote plugin list ...
>>> >> > Reading remote plugin list ...
>>> >> > Latest release information is not available for plugin
>>> >> > 'logdigger-connector', specify concrete release to install
>>> >> >
>>> >> >
>>> >> > 3. grails list-plugins | grep logdigger
>>> >> >
>>> >> > logdigger-connector <no releases>    --  No description available
>>> >> >
>>> >> > So, looks now all well in the repository. :-(
>>> >> >
>>> >> >
>>> >> > 4. Regarding plugin meta data caching, I had to rename
>>> >> > settings.groovy.
>>> >> > Otherwise, why I run "grails list-plugins" it goes to repository
>>> >> > server and
>>> >> > tries to download all info again (thouse 1.5 hours). Very strange.
>>> >> >
>>> >> >
>>> >> > Regards,
>>> >> > Radomir
>>> >> >
>>> >> >
>>> >> > On Tue, Jun 23, 2009 at 10:24 AM, Radomir Mladenovic
>>> >> > <radomirml@...>
>>> >> > wrote:
>>> >> >>
>>> >> >> Thank you for your comments. I'm on Ubuntu and have SVN 1.5.4.
>>> >> >>
>>> >> >> No, I don't use _Events.groovy.
>>> >> >>
>>> >> >> I understand that plugin list is getting bigger and bigger but it
>>> >> >> downloads the complete list each time I try to release. This plugin
>>> >> >> list could (should?) have been cached as yesterday I had one
>>> >> >> successful deployment. I think meta-info got corrupted when I was
>>> >> >> testing behavior without settings.groovy and canceled release
>>> >> >> process
>>> >> >> with Ctrl-C.
>>> >> >>
>>> >> >> Anyway, I deleted "~/.grails/1.1.1/grailsplugins/.plugin-meta" and
>>> >> >> will run release-plugin again. I'll let you know how it went.
>>> >> >>
>>> >> >> Best regards,
>>> >> >> Radomir
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On Tue, Jun 23, 2009 at 7:18 AM, Will Droste<will@...>
>>> >> >> wrote:
>>> >> >> > What version of SVN are you using?? On what OS etc.. Its best to
>>> >> >> > use SVN
>>> >> >> > 1.5
>>> >> >> > or greater.
>>> >> >> > No this is not normal to wait an hour it should be quick.. The
>>> >> >> > process
>>> >> >> > is
>>> >> >> > basically this when a plugin is released the plugin.xml meta data
>>> >> >> > gets
>>> >> >> > updated on the SVN site.  When you do anything plugin related it
>>> >> >> > will
>>> >> >> > check
>>> >> >> > the version of the file (timestamp or svn revision) and update
>>> >> >> > the file.
>>> >> >> >  Which should be quick however the main plugins-list.xml is
>>> >> >> > getting
>>> >> >> > larger
>>> >> >> > since there's a ton of plugins and the file contains all the
>>> >> >> > versions. Everything is deposited in '.grails/1.1' for caching.
>>> >> >> > I found the plugin entry and yes it is corrupted.. You'll need to
>>> >> >> > re-release
>>> >> >> > it.. I'm sorry this happened to you. Do you use _Events.groovy?
>>> >> >> >  I've
>>> >> >> > seen
>>> >> >> > an issue releasing plugins w/ that file present.  From the
>>> >> >> > stacktrace it
>>> >> >> > looks like it stopped right in the middle of a commit.  Its odd
>>> >> >> > since it
>>> >> >> > looks like meta information was not created correctly because the
>>> >> >> > commit
>>> >> >> > should have rolledback being SVN and all.
>>> >> >> > Regards,
>>> >> >> > Will
>>> >> >> >
>>> >> >> > On Mon, Jun 22, 2009 at 8:29 PM, Richard Vowles
>>> >> >> > <richard@...> wrote:
>>> >> >> >>
>>> >> >> >> It is somewhat a pity that the plugin xml file that everyone
>>> >> >> >> downloads
>>> >> >> >> from isn't generated from the www.grails.org website. Then
>>> >> >> >> people could
>>> >> >> >> just
>>> >> >> >> point to whereever the zip file for each release was located
>>> >> >> >> (svn,
>>> >> >> >> github,
>>> >> >> >> etc) and the website could manage the meta-data. Just an idea.
>>> >> >> >>
>>> >> >> >> On Tue, Jun 23, 2009 at 1:08 PM, Radomir Mladenovic
>>> >> >> >> <radomirml@...>
>>> >> >> >> wrote:
>>> >> >> >>>
>>> >> >> >>> I think I ruined my plugin information in the repository
>>> >> >> >>> somehow (I
>>> >> >> >>> guess it was when I was trying release-plugin without the
>>> >> >> >>> config (to
>>> >> >> >>> reproduce error) and was using Ctrl-C to stop it when I saw
>>> >> >> >>> that it
>>> >> >> >>> "worked".
>>> >> >> >>>
>>> >> >> >>
>>> >> >> >>
>>> >> >> >>
>>> >> >> >> --
>>> >> >> >> ---
>>> >> >> >> Richard Vowles,
>>> >> >> >> Talk to me about development in Grails, Groovy, Java and for the
>>> >> >> >> Blackberry
>>> >> >> >> ph: [phone], linkedin, skype:rvowles
>>> >> >> >> get 2Gb shared disk space in the cloud - Dropbox, its incredibly
>>> >> >> >> useful! -
>>> >> >> >> http://tinyurl.com/cmcceh
>>> >> >> >> podcast: http://www.illegalargument.com
>>> >> >> >
>>> >> >> >
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Graeme Rocher
>>> >> Head of Grails Development
>>> >> SpringSource - Weapons for the War on Java Complexity
>>> >> http://www.springsource.com
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe from this list, please visit:
>>> >>
>>> >>    http://xircles.codehaus.org/manage_email
>>> >>
>>> >>
>>> >
>>>
>>>
>>>
>>> --
>>> Graeme Rocher
>>> Head of Grails Development
>>> SpringSource - Weapons for the War on Java Complexity
>>> http://www.springsource.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>
>

--

Graeme Rocher
Head of Grails Development
SpringSource - Weapons for the War on Java Complexity
http://www.springsource.com

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

   http://xircles.codehaus.org/manage_email