archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deng Ching <och...@apache.org>
Subject Re: Re : Re : [VOTE] Release Archiva 1.2.2 (Take 2)
Date Fri, 28 Aug 2009 06:01:31 GMT
Thanks for looking into this Julien :) I guess we can just include MRM-1243
in 1.2.3 if there aren't any release blockers in the staged 1.2.2. I want to
wrap up 1.2.x soon and I'm hoping to release 1.2.3 after a few weeks
anyway..

-Deng

On Thu, Aug 27, 2009 at 10:21 PM, Julien HENRY <henryju@yahoo.fr> wrote:

> Adding Spring filter fix my encoding issue. I've opened a JIRA issue:
> MRM-1243 with a patch.
>
> Sorry for being so long, I will understand if you don't want to restart the
> release again.
>
> Regards,
>
> Julien
>
>
>
>
> ________________________________
> De : Julien HENRY <henryju@yahoo.fr>
> À : dev@archiva.apache.org
> Envoyé le : Jeudi, 27 Août 2009, 14h05mn 39s
> Objet : Re : [VOTE] Release Archiva 1.2.2 (Take 2)
>
> Hi Deng,
>
> I have tested metadata issue and now it works fine.
>
> Concerning encoding issue, here is some details:
>    - when accessing Archiva directly (http://vs0126-picj-ag:8080) there is
> no issue and the browser detects that encoding is ISO-8859-1
>    - when accessing Archiva through the apache mod_proxy (
> http://archiva.mycompany.fr) all characters are messed up. This is because
> browser detects encoding is UTF-8. Forcing encoding to ISO-8859-1 works
> fine.
>
> I set up a Continuum instance with exactly the same configuration, and both
> way (with or without proxy) to access the site make the browser use UTF-8
> (and I have no issue with characters).
>
> As Archiva and Continuum are using the same version of redback the issue
> come from Archiva itself.
>
> I think it can be solved by adding
>
> <filter>
>    <filter-name>encodingFilter</filter-name>
>    <filter-class>
> org.springframework.web.filter.CharacterEncodingFilter</filter-class>
>    <init-param>
>      <param-name>encoding</param-name>
>      <param-value>UTF-8</param-value>
>    </init-param>
>    <init-param>
>      <param-name>forceEncoding</param-name>
>      <param-value>true</param-value>
>    </init-param>
>  </filter>
>
>
>  <filter-mapping>
>    <filter-name>encodingFilter</filter-name>
>    <url-pattern>/*</url-pattern>
>  </filter-mapping>
>
> to Archiva web.xml. I'll test and let you know.
>
> Regards,
>
> Julien
>
>
>
>
> ________________________________
> De : Deng Ching <oching@apache.org>
> À : dev@archiva.apache.org
> Envoyé le : Jeudi, 27 Août 2009, 12h31mn 36s
> Objet : [VOTE] Release Archiva 1.2.2 (Take 2)
>
> Hi All,
>
> The Archiva 1.2.2 release candidate has been staged.
>
> You can take a look at the release notes here:
>
> http://people.apache.org/~oching/archiva/1.2.2/release-notes.html<http://people.apache.org/%7Eoching/archiva/1.2.2/release-notes.html>or
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15292&styleName=Text&projectId=10980&Create=Create
>
> The staging repository where the binaries, including the sources,
> signatures
> and checksums, is here:
>
> http://vmbuild.apache.org/archiva/repository/staged-archiva/
>
> While the site has been staged at:
>
> http://people.apache.org/~oching/archiva/1.2.2/<http://people.apache.org/%7Eoching/archiva/1.2.2/>
>
> Everyone is encouraged to vote and give their feedback :)
>
> [ ] +1 Release it!
> [ ] 0
> [ ] -1 Don't release it, because...
>
> The vote will be open for 72 hours.
>
> Thanks,
> Deng
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message