plugins-list.xml file encoding.

[Luke Daley]

https://svn.codehaus.org/grails-plugins/.plugin-meta/plugins-list.xml

Somehow the plugin list was in iso-8859-1 encoding, which caused  
errors during plugin release.

I have manually converted it back to UTF-8.

Any idea how this could have happened?

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

    http://xircles.codehaus.org/manage_email

[Peter Ledbrook]

> https://svn.codehaus.org/grails-plugins/.plugin-meta/plugins-list.xml
>
> Somehow the plugin list was in iso-8859-1 encoding, which caused errors
> during plugin release.
>
> I have manually converted it back to UTF-8.
>
> Any idea how this could have happened?

Without looking at the code, my guess is that someone released a
plugin and had a default encoding of ISO-8859-1 set somehow. Maybe a
system property? It doesn't look like we explicitly set the encoding
for the XML in 1.1. May have been changed for 1.2 since the plugin
list isn't regenerated each time a plugin is released any more.

Cheers,

Peter

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

    http://xircles.codehaus.org/manage_email

[Bradley Beddoes]

hmm this could well have been my 'fault'

I released a snapshot of Nimble and then just over an hour later I
pushed another one (fixed additional bug for someone as a favour). I
noticed I got this error at that time.

I only used the standard mechanism release mechanism, in my case with
--zip-Only and --snapshot with Grails 1.2-M3.

I do note however that I often get weird exception stacks relating to
input for SVN username, password, commit message etc about no input
source being available. I use Visor on OSX however so I figured it was
more related to that then Grails
(http://docs.blacktree.com/visor/visor) as I generally hide it away
while plugin push occurs. From memory this did occur when I pushed
those snapshots at least twice. When it occurs I have to start the
process over again.

Outside of that if it indeed was caused by me releasing a Nimble
snapshot I have no idea what I did uniquely to cause the issue.

Bradley

On Mon, Nov 9, 2009 at 6:22 PM, Peter Ledbrook <peter@...> wrote:

>> https://svn.codehaus.org/grails-plugins/.plugin-meta/plugins-list.xml
>>
>> Somehow the plugin list was in iso-8859-1 encoding, which caused errors
>> during plugin release.
>>
>> I have manually converted it back to UTF-8.
>>
>> Any idea how this could have happened?
>
> Without looking at the code, my guess is that someone released a
> plugin and had a default encoding of ISO-8859-1 set somehow. Maybe a
> system property? It doesn't look like we explicitly set the encoding
> for the XML in 1.1. May have been changed for 1.2 since the plugin
> list isn't regenerated each time a plugin is released any more.
>
> Cheers,
>
> Peter
>
> ---------------------------------------------------------------------
> 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

[Luke Daley]

On 09/11/2009, at 6:22 PM, Peter Ledbrook wrote:

>> https://svn.codehaus.org/grails-plugins/.plugin-meta/plugins-list.xml
>>
>> Somehow the plugin list was in iso-8859-1 encoding, which caused  
>> errors
>> during plugin release.
>>
>> I have manually converted it back to UTF-8.
>>
>> Any idea how this could have happened?
>
> Without looking at the code, my guess is that someone released a
> plugin and had a default encoding of ISO-8859-1 set somehow. Maybe a
> system property? It doesn't look like we explicitly set the encoding
> for the XML in 1.1. May have been changed for 1.2 since the plugin
> list isn't regenerated each time a plugin is released any more.

I hit this recently.

http://jira.codehaus.org/browse/GRAILS-5321

Fix is trivial and is included in http://github.com/alkemist/grails/tree/release-plugin-fixes-take-2

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

    http://xircles.codehaus.org/manage_email

[Luke Daley]

Side note: I cannot work out how to tell Java to use Utf-8 as the  
default encoding on 10.6.

I am even having weirdness with certain chars (e.g. …) on a fresh  
10.6 install on the command line. Seems like a Mac OS regression.

--

LD.

On 10/11/2009, at 7:30 AM, Bradley Beddoes <bradleybeddoes@...>  
wrote:

> hmm this could well have been my 'fault'
>
> I released a snapshot of Nimble and then just over an hour later I
> pushed another one (fixed additional bug for someone as a favour). I
> noticed I got this error at that time.
>
> I only used the standard mechanism release mechanism, in my case with
> --zip-Only and --snapshot with Grails 1.2-M3.
>
> I do note however that I often get weird exception stacks relating to
> input for SVN username, password, commit message etc about no input
> source being available. I use Visor on OSX however so I figured it was
> more related to that then Grails
> (http://docs.blacktree.com/visor/visor) as I generally hide it away
> while plugin push occurs. From memory this did occur when I pushed
> those snapshots at least twice. When it occurs I have to start the
> process over again.
>
> Outside of that if it indeed was caused by me releasing a Nimble
> snapshot I have no idea what I did uniquely to cause the issue.
>
> Bradley
>
> On Mon, Nov 9, 2009 at 6:22 PM, Peter Ledbrook  
> <peter@...> wrote:
>>> https://svn.codehaus.org/grails-plugins/.plugin-meta/plugins- 
>>> list.xml
>>>
>>> Somehow the plugin list was in iso-8859-1 encoding, which caused  
>>> errors
>>> during plugin release.
>>>
>>> I have manually converted it back to UTF-8.
>>>
>>> Any idea how this could have happened?
>>
>> Without looking at the code, my guess is that someone released a
>> plugin and had a default encoding of ISO-8859-1 set somehow. Maybe a
>> system property? It doesn't look like we explicitly set the encoding
>> for the XML in 1.1. May have been changed for 1.2 since the plugin
>> list isn't regenerated each time a plugin is released any more.
>>
>> Cheers,
>>
>> Peter
>>
>> ---------------------------------------------------------------------
>> 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