Re: [VOTE] release of MyFaces Core 2.1.14
+1 2014/1/7 Leonardo Uribe : > Hi, > > I was running the needed tasks to get the 2.1.14 release of Apache > MyFaces core out. > > The artifacts passed all TCK tests. > > Please note that this vote concerns all of the following parts: > 1. Maven artifact group "org.apache.myfaces.shared" v4.1.12 [1] > 2. Maven artifact group "org.apache.myfaces.core" v2.1.14 [1] > > The artifacts were deployed on nexus repo [1] and to my private > Apache account [3] for binary and source packages. > > The release notes could be found at [4]. > > Also the clirr test does not show binary incompatibilities with myfaces-api. > > Please take a look at the "2.1.14" artifacts and vote! > > Please note: This vote is "majority approval" with a minimum of three > +1 votes (see [3]). > > > [ ] +1 for community members who have reviewed the bits > [ ] +0 > [ ] -1 for fatal flaws that should cause these bits not to be released, > and why.. > > > Thanks, > Leonardo Uribe > > [1] > https://repository.apache.org/content/repositories/orgapachemyfaces-017/org/apache/myfaces/ > [2] http://www.apache.org/foundation/voting.html#ReleaseVotes > [3] http://people.apache.org/~lu4242/myfaces2114binsrc > [4] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12325347
Re: [VOTE] release of MyFaces Core 2.2.0
+1 2014/1/7 Leonardo Uribe : > Hi, > > I was running the needed tasks to get the 2.2.0 release of Apache > MyFaces core out. > > The artifacts passed the TCK test of Feb 2013 (jsftck-2.2_26-Feb-2013.zip). > > Please note that this vote concerns all of the following parts: > 1. Maven artifact group "org.apache.myfaces.shared" v4.2.1 [1] > 2. Maven artifact group "org.apache.myfaces.core" v2.2.0 [1] > > The artifacts were deployed on nexus repo [1] and to my private > Apache account [3] for binary and source packages. > > The release notes could be found at [4]. > > Also the clirr test does not show binary incompatibilities with myfaces-api. > > Please take a look at the "2.2.0" artifacts and vote! > > Please note: This vote is "majority approval" with a minimum of three > +1 votes (see [3]). > > > [ ] +1 for community members who have reviewed the bits > [ ] +0 > [ ] -1 for fatal flaws that should cause these bits not to be released, > and why.. > > > Thanks, > Leonardo Uribe > > [1] > https://repository.apache.org/content/repositories/orgapachemyfaces-018/org/apache/myfaces/ > [2] http://www.apache.org/foundation/voting.html#ReleaseVotes > [3] http://people.apache.org/~lu4242/myfaces220binsrc > [4] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12316396
Re: [VOTE] release of MyFaces Core 2.0.20
+1 2014/1/7 Leonardo Uribe : > Hi, > > I was running the needed tasks to get the 2.0.20 release of Apache > MyFaces core out. > > The artifacts passed all TCK tests. > > Please note that this vote concerns all of the following parts: > 1. Maven artifact group "org.apache.myfaces.shared" v4.0.20 [1] > 2. Maven artifact group "org.apache.myfaces.core" v2.0.20 [1] > > The artifacts were deployed on nexus repo [1] and to my private > Apache account [3] for binary and source packages. > > The release notes could be found at [4]. > > Also the clirr test does not show binary incompatibilities with myfaces-api. > > Please take a look at the "2.0.20" artifacts and vote! > > Please note: This vote is "majority approval" with a minimum of three > +1 votes (see [3]). > > > [ ] +1 for community members who have reviewed the bits > [ ] +0 > [ ] -1 for fatal flaws that should cause these bits not to be released, > and why.. > > > Thanks, > Leonardo Uribe > > [1] > https://repository.apache.org/content/repositories/orgapachemyfaces-016/org/apache/myfaces/ > [2] http://www.apache.org/foundation/voting.html#ReleaseVotes > [3] http://people.apache.org/~lu4242/myfaces2020binsrc > [4] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12325349
[VOTE] release of MyFaces Core 2.2.0
Hi, I was running the needed tasks to get the 2.2.0 release of Apache MyFaces core out. The artifacts passed the TCK test of Feb 2013 (jsftck-2.2_26-Feb-2013.zip). Please note that this vote concerns all of the following parts: 1. Maven artifact group "org.apache.myfaces.shared" v4.2.1 [1] 2. Maven artifact group "org.apache.myfaces.core" v2.2.0 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the "2.2.0" artifacts and vote! Please note: This vote is "majority approval" with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-018/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces220binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12316396
[VOTE] release of MyFaces Core 2.1.14
Hi, I was running the needed tasks to get the 2.1.14 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group "org.apache.myfaces.shared" v4.1.12 [1] 2. Maven artifact group "org.apache.myfaces.core" v2.1.14 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the "2.1.14" artifacts and vote! Please note: This vote is "majority approval" with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-017/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces2114binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12325347
[VOTE] release of MyFaces Core 2.0.20
Hi, I was running the needed tasks to get the 2.0.20 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote concerns all of the following parts: 1. Maven artifact group "org.apache.myfaces.shared" v4.0.20 [1] 2. Maven artifact group "org.apache.myfaces.core" v2.0.20 [1] The artifacts were deployed on nexus repo [1] and to my private Apache account [3] for binary and source packages. The release notes could be found at [4]. Also the clirr test does not show binary incompatibilities with myfaces-api. Please take a look at the "2.0.20" artifacts and vote! Please note: This vote is "majority approval" with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Leonardo Uribe [1] https://repository.apache.org/content/repositories/orgapachemyfaces-016/org/apache/myfaces/ [2] http://www.apache.org/foundation/voting.html#ReleaseVotes [3] http://people.apache.org/~lu4242/myfaces2020binsrc [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&version=12325349
[jira] [Resolved] (EXTCDI-312) support for weld 2.0.x
[ https://issues.apache.org/jira/browse/EXTCDI-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTCDI-312. - Resolution: Fixed Fix Version/s: 1.0.6 > support for weld 2.0.x > -- > > Key: EXTCDI-312 > URL: https://issues.apache.org/jira/browse/EXTCDI-312 > Project: MyFaces CODI > Issue Type: Improvement > Components: JEE-JSF12-Module, JEE-JSF20-Module >Affects Versions: 1.0.5 >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek > Fix For: 1.0.6 > > > in case of weld 1.x and 2.1.x instances of type > javax.enterprise.context.spi.Contextual also implement > javax.enterprise.inject.spi.Bean. however, that isn't the case with weld > 2.0.x. > -> we can backport the workaround used in deltaspike. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (EXTCDI-312) support for weld 2.0.x
Gerhard Petracek created EXTCDI-312: --- Summary: support for weld 2.0.x Key: EXTCDI-312 URL: https://issues.apache.org/jira/browse/EXTCDI-312 Project: MyFaces CODI Issue Type: Improvement Components: JEE-JSF12-Module, JEE-JSF20-Module Affects Versions: 1.0.5 Reporter: Gerhard Petracek Assignee: Gerhard Petracek in case of weld 1.x and 2.1.x instances of type javax.enterprise.context.spi.Contextual also implement javax.enterprise.inject.spi.Bean. however, that isn't the case with weld 2.0.x. -> we can backport the workaround used in deltaspike. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TRINIDAD-2441) URLUtil to escape a URL and remove invalid characters
[ https://issues.apache.org/jira/browse/TRINIDAD-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan updated TRINIDAD-2441: Status: Patch Available (was: Open) > URLUtil to escape a URL and remove invalid characters > - > > Key: TRINIDAD-2441 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2441 > Project: MyFaces Trinidad > Issue Type: Improvement > Components: Infrastructure >Affects Versions: 2.1.0-core >Reporter: Scott O'Bryan >Assignee: Scott O'Bryan >Priority: Minor > Fix For: 2.1.1-core > > > URLUtils has a number of different types of encodings to aid URL's that go > out to the client. Currently there is no utility to simply remove any > invalid characters and encode them using %XX notation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TRINIDAD-2441) URLUtil to escape a URL and remove invalid characters
[ https://issues.apache.org/jira/browse/TRINIDAD-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan updated TRINIDAD-2441: Resolution: Fixed Fix Version/s: 2.1.1-core Status: Resolved (was: Patch Available) > URLUtil to escape a URL and remove invalid characters > - > > Key: TRINIDAD-2441 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2441 > Project: MyFaces Trinidad > Issue Type: Improvement > Components: Infrastructure >Affects Versions: 2.1.0-core >Reporter: Scott O'Bryan >Assignee: Scott O'Bryan >Priority: Minor > Fix For: 2.1.1-core > > > URLUtils has a number of different types of encodings to aid URL's that go > out to the client. Currently there is no utility to simply remove any > invalid characters and encode them using %XX notation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (TRINIDAD-2441) URLUtil to escape a URL and remove invalid characters
Scott O'Bryan created TRINIDAD-2441: --- Summary: URLUtil to escape a URL and remove invalid characters Key: TRINIDAD-2441 URL: https://issues.apache.org/jira/browse/TRINIDAD-2441 Project: MyFaces Trinidad Issue Type: Improvement Components: Infrastructure Affects Versions: 2.1.0-core Reporter: Scott O'Bryan Assignee: Scott O'Bryan Priority: Minor URLUtils has a number of different types of encodings to aid URL's that go out to the client. Currently there is no utility to simply remove any invalid characters and encode them using %XX notation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (TRINIDAD-2440) Need utility in URLEncoder to escape illegal characters in a URL using %XX notation
Scott O'Bryan created TRINIDAD-2440: --- Summary: Need utility in URLEncoder to escape illegal characters in a URL using %XX notation Key: TRINIDAD-2440 URL: https://issues.apache.org/jira/browse/TRINIDAD-2440 Project: MyFaces Trinidad Issue Type: Improvement Components: Infrastructure Affects Versions: 2.1.0-core Reporter: Scott O'Bryan Assignee: Scott O'Bryan Priority: Minor URLEncoder has a number of URL encoding utils, but there should be a method to us %XX notation for illegal characters with no other encoding. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (TOMAHAWK-1672) Wrong SessionKey name in session
Eduardo Garcia created TOMAHAWK-1672:
Summary: Wrong SessionKey name in session
Key: TOMAHAWK-1672
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1672
Project: MyFaces Tomahawk
Issue Type: Bug
Components: Captcha
Affects Versions: 1.1.15-SNAPSHOT
Environment: JRE 1.6, JRE 1.7, MyFaces 2.1, Tomcat 7
Reporter: Eduardo Garcia
When using this component and try to validate the Captcha sessionkeyname
against an input String (using the example approach), I found that the
SessionKeyName value is null. But what is really happening is that the
SessionKeyName varname is wrong. For example, insted of been
"captchaSessionKeyName", when I list my session vars, it shows
"captchaSessionKeyName_mySessionKeyName" (name appended twice or more).
A work around for this while get patched, in order to get the session key name
could be:
public final static String SESSION_KEY_NAME = "mySessionKeyName";
HttpSession httpsession = (HttpSession)
FacesContext.getCurrentInstance().getExternalContext().getSession(true);
Enumeration keys = httpsession.getAttributeNames();
String captchaValue = null;
while (keys.hasMoreElements())
{
String key = (String)keys.nextElement();
if(key.contains(SESSION_KEY_NAME))
captchaValue = (String) httpsession.getAttribute(key);
}
if (captchaValue.equalsIgnoreCase(value)) {
//... your validations here...
}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
Re: [VOTE] Release Tobago 1.5.12
Hello, here is my +1 Regards Bernd On Tue, Jan 7, 2014 at 9:22 AM, Volker Weber wrote: > Hi, > > +1 > > Regards, > Volker > > > 2014/1/6 Udo Schnurpfeil >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hello, >> >> I would like to release Tobago 1.5.12. >> >> For a detail list please consult the release notes: >> >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&version=12325597 >> >> The version is available at the staging repository (Nexus). >> >> Staging repository: >> >> https://repository.apache.org/content/repositories/orgapachemyfaces-005/ >> >> The Vote is open for 72h. >> >> [ ] +1 >> [ ] +0 >> [ ] -1 >> >> Regards, >> >> Udo >> >> -BEGIN PGP SIGNATURE- >> Version: GnuPG/MacGPG2 v2.0.22 (Darwin) >> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >> >> iQIcBAEBAgAGBQJSypw4AAoJEAEbRra2zTKA59QP/RC2bv8EJk8rnCac6VtQlxL5 >> QCRmf9VDggzFLx7Iu1GcNqOxXaN0H4JshVJIsjLroHzqfkV72weJCMze7FN+r6Ns >> gf7m/YgSgpb2nMcMqrU31h8CAFLQEAm3QhrodVnDuHJzl7gRpue72B2lobeaUpLG >> TcJIIwa6x50er+dvV0mNywDvFrwKdO93yy+iMg8+1k37SRkK2UPj1Ko/rf7JXdRU >> R8jmw+zlPVTefEi258bHbUcB6qJyEQFGkD7tQd0fsNds9kvg11Fqf/Ho4zpMLvFw >> 6aIy/j2ihKJ7HkagWXIovyaIECTkSyU8Mg5U+wH7Cnas5gjtnH1kuuJ+A6fXzj/F >> sWUJv85btmojSIZUamEZdGv7BhLtn2us9NoeDEHQrTG+E0H8J0q2ajwuENRXzhpz >> j145sXRTcmyL5XuWXD0yvWZAZv/pbB6c/AQoFSoNgoRq5MxrpzftTJjXn4StjjKW >> 5dPaM/74Ym2g0WlouT2QwJv0ys3lLOk+sYD6vWzrmY6P3k/hFxfpIOlLfjm1MzQc >> EbOpYePtFAodQcoxSUb2qQqYdp9kl6e9v/pTplIo3p6k250h2MzUyu+NjM5qsfMi >> qVQ0HxGup26BO2u2qn+smoEWVRmkMAxC+t0tbh7qegk2mNvnS2axqA/RLIlZXX09 >> LWDGKOVFoS619qHc4AWn >> =utyQ >> -END PGP SIGNATURE- > > > > > -- > inexso - information exchange solutions GmbH > Ofener Straße 30 | 26121 Oldenburg > www.inexso.de
Result of: [VOTE] Release Tobago 2.0.0-alpha-3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, thank you for voting for the release. The result is +1 weber (binding) bommel (binding) grantsmith (binding) werpu (binding) so I will proceed with the next steps for the release. Regards, Udo Am 04.01.14 15:29, schrieb Udo Schnurpfeil: > Hello, > > I would like to release Tobago 2.0.0-alpha-3. > > For a detail list please consult the release notes: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&version=12325247 > > The version is available at the staging repository (Nexus). > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachemyfaces-001/ > > The Vote is open for 72h. > > [ ] +1 [ ] +0 [ ] -1 > > Regards, > > Udo > > -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSzA/jAAoJEAEbRra2zTKARdcP/1gN7K0/5d4O6EsvM7guGU31 9hBUDp+iDl9VeSSE9nC/r9F3gNm/KZPBbym7OMXI9T9sB3rlfLIPNdOIqr+0Wm8/ BMEEZdLPh6+pDJdL4y57BNFNsOT/klXTkcBQ8zoWc46C91KmP1bzpHhT2QB6brOF oGKM67iu2DQuzmBrpjj2gMIpP3BloAwEThoZ4Rkpvg5CuVOH1WkD2RIeN5K5r4Ip iPdWDUblnIGsEKtUCssir80S4BlvoA3Qg26z3HnvCVswXBNksUePtpSO6B9nLfok sc56nrPFA+5jW779DXVrjhdTwrZyUa7aEVhvwGytHYYTYEkrYlmiqMJ4/tmNCowF WJvs55BALVjXyIfzKxoklXtwrCx68ru/S3oAyuZcrgPIEtKe/ZDWuHXKEmAVwR2t NT/ZDlPErMn/TVAjMHs2DTrjtM31ZSO1b+KAj6HB7TWhLnKQ4Z8lAlDL5FTUwslg +3j7AQTCmAdz0v8pakLO81t33t6HwYPjcBfiil/Dyzxg4EWSWur9Zn5wRM1CO5Uo 07Inf4jLm/A1z9jF+KhbtiW1Hjb0tYfn/x0kpIRUsoIEl/Sj9y6LYVCDB6DookQ4 FApenGmsVXmjxsnDC2R670XnLP/iBg6SFJhXaNW7g647N5UzBUkJGXEDhVjl9vtp MIpCtjmEq9Z5q38hTvVQ =ui2q -END PGP SIGNATURE-
Re: [VOTE] Release Tobago 1.5.12
Hi, +1 Regards, Volker 2014/1/6 Udo Schnurpfeil > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, > > I would like to release Tobago 1.5.12. > > For a detail list please consult the release notes: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&version=12325597 > > The version is available at the staging repository (Nexus). > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachemyfaces-005/ > > The Vote is open for 72h. > > [ ] +1 > [ ] +0 > [ ] -1 > > Regards, > > Udo > > -BEGIN PGP SIGNATURE- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBAgAGBQJSypw4AAoJEAEbRra2zTKA59QP/RC2bv8EJk8rnCac6VtQlxL5 > QCRmf9VDggzFLx7Iu1GcNqOxXaN0H4JshVJIsjLroHzqfkV72weJCMze7FN+r6Ns > gf7m/YgSgpb2nMcMqrU31h8CAFLQEAm3QhrodVnDuHJzl7gRpue72B2lobeaUpLG > TcJIIwa6x50er+dvV0mNywDvFrwKdO93yy+iMg8+1k37SRkK2UPj1Ko/rf7JXdRU > R8jmw+zlPVTefEi258bHbUcB6qJyEQFGkD7tQd0fsNds9kvg11Fqf/Ho4zpMLvFw > 6aIy/j2ihKJ7HkagWXIovyaIECTkSyU8Mg5U+wH7Cnas5gjtnH1kuuJ+A6fXzj/F > sWUJv85btmojSIZUamEZdGv7BhLtn2us9NoeDEHQrTG+E0H8J0q2ajwuENRXzhpz > j145sXRTcmyL5XuWXD0yvWZAZv/pbB6c/AQoFSoNgoRq5MxrpzftTJjXn4StjjKW > 5dPaM/74Ym2g0WlouT2QwJv0ys3lLOk+sYD6vWzrmY6P3k/hFxfpIOlLfjm1MzQc > EbOpYePtFAodQcoxSUb2qQqYdp9kl6e9v/pTplIo3p6k250h2MzUyu+NjM5qsfMi > qVQ0HxGup26BO2u2qn+smoEWVRmkMAxC+t0tbh7qegk2mNvnS2axqA/RLIlZXX09 > LWDGKOVFoS619qHc4AWn > =utyQ > -END PGP SIGNATURE- > -- inexso - information exchange solutions GmbH Ofener Straße 30 | 26121 Oldenburg www.inexso.de
