Fwd: Mandatory svnpubsub migration by Jan 2013

Begin forwarded message:

> From: Joe Schaefer <joe_schaefer@...>
> Subject: Mandatory svnpubsub migration by Jan 2013
> Date: February 8, 2012 7:26:48 AM EST
> To: Apache Infrastructure <infrastructure@...>
> Reply-To: private@...
> Reply-To: Joe Schaefer <joe_schaefer@...>
> 
> [PLEASE DO NOT RESPOND TO THIS POST! DIRECT ALL FURTHER
> INQUIRIES TO infrastructure@...]
> 
> FYI: infrastructure policy regarding website hosting has
> changed as of November 2011: we are requiring all websites
> and dist/ dirs to be svnpubsub or ASF CMS backed by the end of 2012.
> If your PMC has already met this requirement congratulations,
> you can ignore the remainder of this post.
> 
> As stated on http://www.apache.org/dev/project-site.html#svnpubsub
> we are migrating our webserver infrastructure to 100% svnpubsub
> over the course of 2012.  If your site does not currently make
> use of this technology, it is time to consider a migration effort,
> as rsync-based sites will be PERMANENTLY FROZEN in Jan 2013 due 
> 
> to infra disabling the hourly rsync jobs.  While we recommend
> migrating to the ASF CMS [0] for Anakia based or Confluence based
> sites, and have provided tooling [1] to help facilitate this,
> we are only mandating svnpubsub (which the CMS uses itself).
> 

[jira] [Created] (GERONIMO-6270) Re-enable multiple instances support in one installation

Re-enable multiple instances support in one installation
--------------------------------------------------------

                 Key: GERONIMO-6270
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6270
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
    Affects Versions: 3.0-beta-1
            Reporter: Forrest Xia

We need to investigate how to re-enable the multiple instances support in one installation.

Refer to 
https://issues.apache.org/jira/browse/GERONIMO-6175
https://issues.apache.org/jira/browse/GERONIMO-6174
https://issues.apache.org/jira/browse/GERONIMO-5987

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-6269) Geronimo 2.2.1 gives " Cannot find any provider supporting AES" when starting on various Linux platforms

Geronimo 2.2.1 gives " Cannot find any provider supporting AES" when starting on various Linux platforms
--------------------------------------------------------------------------------------------------------

                 Key: GERONIMO-6269
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6269
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: startup/shutdown
    Affects Versions: 2.2.1
         Environment: Server #1
=========
Centos 5 (2.6.18-92.1.22.el5) on x86 hardware
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode)

Server #2
=========
Red Hat Linux AS 4 (2.6.9-42.ELsmp) on x86 hardware
ava version "1.6.0_30"
Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
Java HotSpot(TM) Client VM (build 20.5-b03, mixed mode, sharing)

JAVA_HOME=/usr/java/latest
JRE_HOME=/usr/java/latest

            Reporter: Michael Peoples

A fresh installation of Geronimo 2.2.1 on both of the above servers results in errors such as the ones listed

[jira] [Created] (GERONIMO-6268) JCDI tck case "InjectionIntoWebServiceEndPointTest.testInjectionIntoWebServiceEndpoint" failed

JCDI tck case "InjectionIntoWebServiceEndPointTest.testInjectionIntoWebServiceEndpoint" failed
----------------------------------------------------------------------------------------------

                 Key: GERONIMO-6268
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6268
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: OpenWebBeans
    Affects Versions: 3.0-beta-1
            Reporter: Forrest Xia
            Assignee: Forrest Xia
             Fix For: 3.0, 3.0-beta-2

We have one JCDI tck failure as following:

java.lang.AssertionError
	at org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest.testInjectionIntoWebServiceEndpoint(InjectionIntoWebServiceEndPointTest.java:50)
	at org.jboss.testharness.AbstractTest.run(AbstractTest.java:244)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:74)
	at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
... Removed 29 stack frames

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-6267) Enable JSF 2.1 support for 3.0-beta and trunk

Enable JSF 2.1 support for 3.0-beta and trunk
---------------------------------------------

                 Key: GERONIMO-6267
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6267
             Project: Geronimo
          Issue Type: New Feature
      Security Level: public (Regular issues)
          Components: myfaces
    Affects Versions: 3.0, 3.0-beta-2
            Reporter: Forrest Xia
            Priority: Minor

JSF 2.0 does not officially support Java 7, we might want to upgrade JSF to 2.1 to enable Java 7 support.

Draft idea as following:
1. Use myfaces-bundle-2.1.5.jar directly
2. Upgrade GeronimoFactoryFinderProvider to support a new factory class "FaceletCacheFactory"
3. Run tck to see if any problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-6266) The jndi prefix URL could not work before the web application is totally started

The jndi prefix URL could not work before the web application is totally started
--------------------------------------------------------------------------------

                 Key: GERONIMO-6266
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6266
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Tomcat
    Affects Versions: 3.0-beta-1, 3.0
            Reporter: Ivan

If the those load-on-startup servlets use the servletContext.getResource method to get a jndi prefix
URL, they could not get the contents by URL.openStream method, as the resources are only binded to the web
application classloader while the TomcatWebApp GBean is started.
Although we have binded the resources with the current thread, it seems to be ignored in Tomcat codes. I
opened a bug entry in Tomcat community, https://issues.apache.org/bugzilla/show_bug.cgi?id=52563
If they did not accept it or we have no chance to include the change in the 3.0-beta-2 release, there should be
workaround codes to make it work in Geronimo.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

PASS! [VOTE] Release geronimo-jsp_2.2_spec 1.1

[jira] [Created] (GERONIMO-6265) Default jndi context (no prefix)

Default jndi context (no prefix)
--------------------------------

                 Key: GERONIMO-6265
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6265
             Project: Geronimo
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: naming
    Affects Versions: 3.0
            Reporter: David Jencks
            Assignee: David Jencks
             Fix For: 3.0

Aries jndi has special handling for the default (no prefix) jndi context.  We should come up with an
InitialContextFactoryBuilder service that supplies an InitialContextFactory that supplies a WritableContext.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: AHP 3.7.3 support Maven 3?

[VOTE] Release Geronimo Tomcat 7.0.23.1

[VOTE] Release geronimo-jsp_2.2_spec 1.1