9:32 a.m.
FYI, last night Jason created a branch for the M4 release.[1] Similar to
the M2 release, the final QE tasks for the release will be done on that
branch, with the expectation that the final M4 tag will be essentially
the same as the root of the branch.
The M4 release will probably come out early next week.
AS trunk is now open for normal development work toward AS 6.0 final.
[1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
9:40 a.m.
Any plans of releasing with a clean testsuite?
AFAICT, last time I've seen blue on the screen was 5 months ago:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test...
Brian Stansberry wrote:
FYI, last night Jason created a branch for the M4 release.[1] Similar
to
the M2 release, the final QE tasks for the release will be done on that
branch, with the expectation that the final M4 tag will be essentially
the same as the root of the branch.
The M4 release will probably come out early next week.
AS trunk is now open for normal development work toward AS 6.0 final.
[1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
10:08 a.m.
On 7/22/10 9:40 AM, Dimitris Andreadis wrote:
Any plans of releasing with a clean testsuite?
Not for M4. Jason's comment on the JIRA task for the release[1]
indicates the known failures that should not block the release.
[1] https://jira.jboss.org/browse/JBQA-3551
AFAICT, last time I've seen blue on the screen was 5 months ago:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test...
Yeah. Geez, folks, can we please clean this up?
Brian Stansberry wrote:
> FYI, last night Jason created a branch for the M4 release.[1] Similar to
> the M2 release, the final QE tasks for the release will be done on that
> branch, with the expectation that the final M4 tag will be essentially
> the same as the root of the branch.
>
> The M4 release will probably come out early next week.
>
> AS trunk is now open for normal development work toward AS 6.0 final.
>
> [1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
10:30 a.m.
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test...
>
Yeah. Geez, folks, can we please clean this up?
This one
*
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test...
looks somehow expected, but the behavior changed a bit.
We explicitly build "illegal" resources
<!-- build test-java-class-isolation.sar -->
<mkdir dir="${build.resources}/isolation/java/org/jboss/test"/>
<copy
file="${build.classes}/org/jboss/test/isolation/mbean/JavaClassIsolationMBean.class"
tofile="${build.resources}/isolation/java/org/jboss/test/Test.class"/>
<mkdir dir="${build.resources}/isolation/java/rmi/registry"/>
<copy
file="${build.classes}/org/jboss/test/isolation/mbean/JavaClassIsolationMBean.class"
tofile="${build.resources}/isolation/java/rmi/registry/Registry.class"/>
<jar destfile="${build.lib}/test-java-class-isolation.sar">
<fileset dir="${build.classes}">
<include name="org/jboss/test/isolation/mbean/**"/>
</fileset>
<fileset dir="${build.resources}/isolation/">
<include name="META-INF/*.xml"/>
<include name="java/**"/>
</fileset>
</jar>
only to test them here
public void test() throws Exception
{
// Use our scoped classloader
ClassLoader cl = getClass().getClassLoader();
// Should be able to find the class as a resource
URL resource = cl.getResource("java/org/jboss/test/Test.class");
if (resource == null)
throw new RuntimeException("Unable to find resource
java/org/jboss/test/Test.class");
// Should not be able to load the resource
try
{
cl.loadClass("java.org.jboss.test.Test");
throw new RuntimeException("Should not be able to load class");
}
catch (ClassNotFoundException expected) // HERE --- we get security exception now
instead
{
// Should not be able to load it
log.info("Got expected exception", expected);
}
// Should be able to load the resgistry class even though it is in our deployment
cl.loadClass("java.rmi.registry.Registry");
}
resulting in
DEPLOYMENTS IN ERROR:
Deployment
"vfs:///qa/services/hudson/hudson_workspace/workspace/JBoss-AS-6.0.x-testSuite-sun16/JBossAS/testsuite/output/lib/test-java-class-isolation.sar"
is in error due to the following reason(s): java.lang.SecurityException: Prohibited
package name: java.org.jboss.test
The question is what was changed in our CL layer. :-)
10:52 a.m.
Thanks. I created https://jira.jboss.org/browse/JBAS-8237 which is a
child of a container JIRA to clean up all the failures:
https://jira.jboss.org/browse/JBAS-8236
On 7/22/10 10:30 AM, Ales Justin wrote:
This one
*http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSuite-sun16/lastCompletedBuild/testReport/org.jboss.test.isolation.test/JavaClassIsolationUnitTestCase/testJavaClassIsNotLoadedFromIsolatedClassLoader/
looks somehow expected, but the behavior changed a bit.
We explicitly build "illegal" resources
<!-- build test-java-class-isolation.sar -->
<mkdir dir="${build.resources}/isolation/java/org/jboss/test"/>
<copy
file="${build.classes}/org/jboss/test/isolation/mbean/JavaClassIsolationMBean.class"
tofile="${build.resources}/isolation/java/org/jboss/test/Test.class"/>
<mkdir dir="${build.resources}/isolation/java/rmi/registry"/>
<copy
file="${build.classes}/org/jboss/test/isolation/mbean/JavaClassIsolationMBean.class"
tofile="${build.resources}/isolation/java/rmi/registry/Registry.class"/>
<jar destfile="${build.lib}/test-java-class-isolation.sar">
<fileset dir="${build.classes}">
<include name="org/jboss/test/isolation/mbean/**"/>
</fileset>
<fileset dir="${build.resources}/isolation/">
<include name="META-INF/*.xml"/>
<include name="java/**"/>
</fileset>
</jar>
only to test them here
public void test() throws Exception
{
// Use our scoped classloader
ClassLoader cl = getClass().getClassLoader();
// Should be able to find the class as a resource
URL resource = cl.getResource("java/org/jboss/test/Test.class");
if (resource == null)
throw new RuntimeException("Unable to find resource
java/org/jboss/test/Test.class");
// Should not be able to load the resource
try
{
cl.loadClass("java.org.jboss.test.Test");
throw new RuntimeException("Should not be able to load class");
}
catch (ClassNotFoundException expected) // HERE --- we get security exception now
instead
{
// Should not be able to load it
log.info("Got expected exception", expected);
}
// Should be able to load the resgistry class even though it is in our deployment
cl.loadClass("java.rmi.registry.Registry");
}
resulting in
DEPLOYMENTS IN ERROR:
Deployment
"vfs:///qa/services/hudson/hudson_workspace/workspace/JBoss-AS-6.0.x-testSuite-sun16/JBossAS/testsuite/output/lib/test-java-class-isolation.sar"
is in error due to the following reason(s): java.lang.SecurityException: Prohibited
package name: java.org.jboss.test
The question is what was changed in our CL layer.:-)
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
11:49 a.m.
I have created subtasks under JBAS-8236 for all the recurring failures.
If you're knowledgable about the area being tested, please assign
yourself to the relevant JIRAs.
On 7/22/10 10:52 AM, Brian Stansberry wrote:
Thanks. I created https://jira.jboss.org/browse/JBAS-8237 which is a
child of a container JIRA to clean up all the failures:
https://jira.jboss.org/browse/JBAS-8236
On 7/22/10 10:30 AM, Ales Justin wrote:
> This one
>
*http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSuite-sun16/lastCompletedBuild/testReport/org.jboss.test.isolation.test/JavaClassIsolationUnitTestCase/testJavaClassIsNotLoadedFromIsolatedClassLoader/
>
> looks somehow expected, but the behavior changed a bit.
>
> We explicitly build "illegal" resources
>
> <!-- build test-java-class-isolation.sar -->
> <mkdir dir="${build.resources}/isolation/java/org/jboss/test"/>
> <copy
>
file="${build.classes}/org/jboss/test/isolation/mbean/JavaClassIsolationMBean.class"
>
> tofile="${build.resources}/isolation/java/org/jboss/test/Test.class"/>
>
> <mkdir dir="${build.resources}/isolation/java/rmi/registry"/>
> <copy
>
file="${build.classes}/org/jboss/test/isolation/mbean/JavaClassIsolationMBean.class"
>
>
tofile="${build.resources}/isolation/java/rmi/registry/Registry.class"/>
>
> <jar destfile="${build.lib}/test-java-class-isolation.sar">
> <fileset dir="${build.classes}">
> <include name="org/jboss/test/isolation/mbean/**"/>
> </fileset>
> <fileset dir="${build.resources}/isolation/">
> <include name="META-INF/*.xml"/>
> <include name="java/**"/>
> </fileset>
> </jar>
>
> only to test them here
>
> public void test() throws Exception
> {
> // Use our scoped classloader
> ClassLoader cl = getClass().getClassLoader();
>
> // Should be able to find the class as a resource
> URL resource = cl.getResource("java/org/jboss/test/Test.class");
> if (resource == null)
> throw new RuntimeException("Unable to find resource
> java/org/jboss/test/Test.class");
>
> // Should not be able to load the resource
> try
> {
> cl.loadClass("java.org.jboss.test.Test");
> throw new RuntimeException("Should not be able to load class");
> }
> catch (ClassNotFoundException expected) // HERE --- we get security
> exception now instead
> {
> // Should not be able to load it
> log.info("Got expected exception", expected);
> }
>
> // Should be able to load the resgistry class even though it is in our
> deployment
> cl.loadClass("java.rmi.registry.Registry");
> }
>
> resulting in
>
> DEPLOYMENTS IN ERROR:
> Deployment
>
"vfs:///qa/services/hudson/hudson_workspace/workspace/JBoss-AS-6.0.x-testSuite-sun16/JBossAS/testsuite/output/lib/test-java-class-isolation.sar"
> is in error due to the following reason(s):
> java.lang.SecurityException: Prohibited package name: java.org.jboss.test
>
> The question is what was changed in our CL layer.:-)
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
9:43 a.m.
I saw some RestEasy-int commit that should probably be applied to this branch as well --
if not yet done.
----
Message: 5
Date: Thu, 22 Jul 2010 05:27:53 -0400
From: jboss-cvs-commits(a)lists.jboss.org
Subject: [jboss-cvs] JBossAS SVN: r107017 -
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers.
To: jboss-cvs-commits(a)lists.jboss.org
Message-ID:
<201007220927.o6M9RrEL015390(a)svn01.web.mwc.hst.phx2.redhat.com>
Content-Type: text/plain; charset=UTF-8
Author: richard.opalka(a)jboss.com
Date: 2010-07-22 05:27:52 -0400 (Thu, 22 Jul 2010)
New Revision: 107017
Modified:
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
Log:
[JBAS-8234] fixing CCE
Modified:
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
===================================================================
---
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java 2010-07-22
09:02:39 UTC (rev 107016)
+++
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java 2010-07-22
09:27:52 UTC (rev 107017)
@@ -146,7 +146,8 @@
{
Thread.currentThread().getContextClassLoader().loadClass(CDI_INJECTOR_FACTORY_CLASS);
// don't set this param if CDI is not in classpath
- if (((VFSDeploymentUnit) du).getMetaDataFile("beans.xml") != null)
+ final boolean isVFSDU = du instanceof VFSDeploymentUnit;
+ if (isVFSDU && ((VFSDeploymentUnit)
du).getMetaDataFile("beans.xml") != null)
{
log.debug("***** Found CDI, adding injector factory class");
setContextParameter(webdata, "resteasy.injector.factory",
CDI_INJECTOR_FACTORY_CLASS);
On Jul 22, 2010, at 4:32 PM, Brian Stansberry wrote:
FYI, last night Jason created a branch for the M4 release.[1] Similar
to
the M2 release, the final QE tasks for the release will be done on that
branch, with the expectation that the final M4 tag will be essentially
the same as the root of the branch.
The M4 release will probably come out early next week.
AS trunk is now open for normal development work toward AS 6.0 final.
[1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
9:57 a.m.
Can the
resteasy-int/test pom be run in QE?
Steps:
1. startup jboss
2. cd resteasy-int/test
3. mvn install
Ales Justin wrote:
I saw some RestEasy-int commit that should probably be applied to
this
branch as well -- if not yet done.
----
Message: 5
Date: Thu, 22 Jul 2010 05:27:53 -0400
From: jboss-cvs-commits(a)lists.jboss.org
<mailto:jboss-cvs-commits@lists.jboss.org>
Subject: [jboss-cvs] JBossAS SVN: r107017 -
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers.
To: jboss-cvs-commits(a)lists.jboss.org
<mailto:jboss-cvs-commits@lists.jboss.org>
Message-ID:
<201007220927.o6M9RrEL015390(a)svn01.web.mwc.hst.phx2.redhat.com
<mailto:201007220927.o6M9RrEL015390@svn01.web.mwc.hst.phx2.redhat.com>>
Content-Type: text/plain; charset=UTF-8
Author: richard.opalka(a)jboss.com <mailto:richard.opalka@jboss.com>
Date: 2010-07-22 05:27:52 -0400 (Thu, 22 Jul 2010)
New Revision: 107017
Modified:
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
Log:
[JBAS-8234] fixing CCE
Modified:
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
===================================================================
---
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
2010-07-22 09:02:39 UTC (rev 107016)
+++
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
2010-07-22 09:27:52 UTC (rev 107017)
@@ -146,7 +146,8 @@
{
Thread.currentThread().getContextClassLoader().loadClass(CDI_INJECTOR_FACTORY_CLASS);
// don't set this param if CDI is not in classpath
- if (((VFSDeploymentUnit) du).getMetaDataFile("beans.xml") != null)
+ final boolean isVFSDU = du instanceof VFSDeploymentUnit;
+ if (isVFSDU && ((VFSDeploymentUnit)
du).getMetaDataFile("beans.xml") != null)
{
log.debug("***** Found CDI, adding injector factory class");
setContextParameter(webdata, "resteasy.injector.factory",
CDI_INJECTOR_FACTORY_CLASS);
On Jul 22, 2010, at 4:32 PM, Brian Stansberry wrote:
> FYI, last night Jason created a branch for the M4 release.[1] Similar to
> the M2 release, the final QE tasks for the release will be done on that
> branch, with the expectation that the final M4 tag will be essentially
> the same as the root of the branch.
>
> The M4 release will probably come out early next week.
>
> AS trunk is now open for normal development work toward AS 6.0 final.
>
> [1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
> --
> Brian Stansberry
> Lead, AS Clustering
> JBoss by Red Hat
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> <mailto:jboss-development@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-development
------------------------------------------------------------------------
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10:09 a.m.
I've added that to https://jira.jboss.org/browse/JBQA-3551
On 7/22/10 9:57 AM, Bill Burke wrote:
Can the
resteasy-int/test pom be run in QE?
Steps:
1. startup jboss
2. cd resteasy-int/test
3. mvn install
Ales Justin wrote:
> I saw some RestEasy-int commit that should probably be applied to this
> branch as well -- if not yet done.
>
> ----
>
> Message: 5
> Date: Thu, 22 Jul 2010 05:27:53 -0400
> From: jboss-cvs-commits(a)lists.jboss.org
> <mailto:jboss-cvs-commits@lists.jboss.org>
> Subject: [jboss-cvs] JBossAS SVN: r107017 -
> trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers.
>
> To: jboss-cvs-commits(a)lists.jboss.org
> <mailto:jboss-cvs-commits@lists.jboss.org>
> Message-ID:
> <201007220927.o6M9RrEL015390(a)svn01.web.mwc.hst.phx2.redhat.com
> <mailto:201007220927.o6M9RrEL015390@svn01.web.mwc.hst.phx2.redhat.com>>
> Content-Type: text/plain; charset=UTF-8
>
> Author: richard.opalka@jboss.com<mailto:richard.opalka@jboss.com>
> Date: 2010-07-22 05:27:52 -0400 (Thu, 22 Jul 2010)
> New Revision: 107017
>
> Modified:
>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
> Log:
> [JBAS-8234] fixing CCE
>
> Modified:
>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
> ===================================================================
> ---
>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
> 2010-07-22 09:02:39 UTC (rev 107016)
> +++
>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
> 2010-07-22 09:27:52 UTC (rev 107017)
> @@ -146,7 +146,8 @@
> {
>
Thread.currentThread().getContextClassLoader().loadClass(CDI_INJECTOR_FACTORY_CLASS);
> // don't set this param if CDI is not in classpath
> - if (((VFSDeploymentUnit) du).getMetaDataFile("beans.xml") !=
null)
> + final boolean isVFSDU = du instanceof VFSDeploymentUnit;
> + if (isVFSDU&& ((VFSDeploymentUnit)
> du).getMetaDataFile("beans.xml") != null)
> {
> log.debug("***** Found CDI, adding injector factory class");
> setContextParameter(webdata, "resteasy.injector.factory",
> CDI_INJECTOR_FACTORY_CLASS);
>
>
> On Jul 22, 2010, at 4:32 PM, Brian Stansberry wrote:
>
>> FYI, last night Jason created a branch for the M4 release.[1] Similar to
>> the M2 release, the final QE tasks for the release will be done on that
>> branch, with the expectation that the final M4 tag will be essentially
>> the same as the root of the branch.
>>
>> The M4 release will probably come out early next week.
>>
>> AS trunk is now open for normal development work toward AS 6.0 final.
>>
>> [1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
>> --
>> Brian Stansberry
>> Lead, AS Clustering
>> JBoss by Red Hat
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> <mailto:jboss-development@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
10:17 a.m.
Richard,
Does this need to go in M4?
Rajesh,
If it needs to go in and I port it to the release branch this morning,
will that screw things up for you guys?
On 7/22/10 9:43 AM, Ales Justin wrote:
I saw some RestEasy-int commit that should probably be applied to
this
branch as well -- if not yet done.
----
Message: 5
Date: Thu, 22 Jul 2010 05:27:53 -0400
From: jboss-cvs-commits(a)lists.jboss.org
<mailto:jboss-cvs-commits@lists.jboss.org>
Subject: [jboss-cvs] JBossAS SVN: r107017 -
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers.
To: jboss-cvs-commits(a)lists.jboss.org
<mailto:jboss-cvs-commits@lists.jboss.org>
Message-ID:
<201007220927.o6M9RrEL015390(a)svn01.web.mwc.hst.phx2.redhat.com
<mailto:201007220927.o6M9RrEL015390@svn01.web.mwc.hst.phx2.redhat.com>>
Content-Type: text/plain; charset=UTF-8
Author: richard.opalka(a)jboss.com <mailto:richard.opalka@jboss.com>
Date: 2010-07-22 05:27:52 -0400 (Thu, 22 Jul 2010)
New Revision: 107017
Modified:
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
Log:
[JBAS-8234] fixing CCE
Modified:
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
===================================================================
---
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
2010-07-22 09:02:39 UTC (rev 107016)
+++
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
2010-07-22 09:27:52 UTC (rev 107017)
@@ -146,7 +146,8 @@
{
Thread.currentThread().getContextClassLoader().loadClass(CDI_INJECTOR_FACTORY_CLASS);
// don't set this param if CDI is not in classpath
- if (((VFSDeploymentUnit) du).getMetaDataFile("beans.xml") != null)
+ final boolean isVFSDU = du instanceof VFSDeploymentUnit;
+ if (isVFSDU && ((VFSDeploymentUnit) du).getMetaDataFile("beans.xml")
!= null)
{
log.debug("***** Found CDI, adding injector factory class");
setContextParameter(webdata, "resteasy.injector.factory",
CDI_INJECTOR_FACTORY_CLASS);
On Jul 22, 2010, at 4:32 PM, Brian Stansberry wrote:
> FYI, last night Jason created a branch for the M4 release.[1] Similar to
> the M2 release, the final QE tasks for the release will be done on that
> branch, with the expectation that the final M4 tag will be essentially
> the same as the root of the branch.
>
> The M4 release will probably come out early next week.
>
> AS trunk is now open for normal development work toward AS 6.0 final.
>
> [1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
> --
> Brian Stansberry
> Lead, AS Clustering
> JBoss by Red Hat
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> <mailto:jboss-development@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
10:26 a.m.
I didn't put this commit in, so don't know what it is
Brian Stansberry wrote:
Richard,
Does this need to go in M4?
Rajesh,
If it needs to go in and I port it to the release branch this morning,
will that screw things up for you guys?
On 7/22/10 9:43 AM, Ales Justin wrote:
> I saw some RestEasy-int commit that should probably be applied to this
> branch as well -- if not yet done.
>
> ----
>
> Message: 5
> Date: Thu, 22 Jul 2010 05:27:53 -0400
> From: jboss-cvs-commits(a)lists.jboss.org
> <mailto:jboss-cvs-commits@lists.jboss.org>
> Subject: [jboss-cvs] JBossAS SVN: r107017 -
> trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers.
>
> To: jboss-cvs-commits(a)lists.jboss.org
> <mailto:jboss-cvs-commits@lists.jboss.org>
> Message-ID:
> <201007220927.o6M9RrEL015390(a)svn01.web.mwc.hst.phx2.redhat.com
> <mailto:201007220927.o6M9RrEL015390@svn01.web.mwc.hst.phx2.redhat.com>>
> Content-Type: text/plain; charset=UTF-8
>
> Author: richard.opalka(a)jboss.com <mailto:richard.opalka@jboss.com>
> Date: 2010-07-22 05:27:52 -0400 (Thu, 22 Jul 2010)
> New Revision: 107017
>
> Modified:
>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
> Log:
> [JBAS-8234] fixing CCE
>
> Modified:
>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
> ===================================================================
> ---
>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
> 2010-07-22 09:02:39 UTC (rev 107016)
> +++
>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
> 2010-07-22 09:27:52 UTC (rev 107017)
> @@ -146,7 +146,8 @@
> {
>
Thread.currentThread().getContextClassLoader().loadClass(CDI_INJECTOR_FACTORY_CLASS);
> // don't set this param if CDI is not in classpath
> - if (((VFSDeploymentUnit) du).getMetaDataFile("beans.xml") != null)
> + final boolean isVFSDU = du instanceof VFSDeploymentUnit;
> + if (isVFSDU && ((VFSDeploymentUnit)
du).getMetaDataFile("beans.xml")
> != null)
> {
> log.debug("***** Found CDI, adding injector factory class");
> setContextParameter(webdata, "resteasy.injector.factory",
> CDI_INJECTOR_FACTORY_CLASS);
>
>
> On Jul 22, 2010, at 4:32 PM, Brian Stansberry wrote:
>
>> FYI, last night Jason created a branch for the M4 release.[1] Similar to
>> the M2 release, the final QE tasks for the release will be done on that
>> branch, with the expectation that the final M4 tag will be essentially
>> the same as the root of the branch.
>>
>> The M4 release will probably come out early next week.
>>
>> AS trunk is now open for normal development work toward AS 6.0 final.
>>
>> [1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
>> --
>> Brian Stansberry
>> Lead, AS Clustering
>> JBoss by Red Hat
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> <mailto:jboss-development@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10:59 a.m.
The JIRA[1] is not closed and is marked for 6.0.0.Final, so I'm not
porting this unless Bill, you tell me you want it and Rajesh says it's ok.
[1] https://jira.jboss.org/browse/JBAS-8234
On 7/22/10 10:26 AM, Bill Burke wrote:
I didn't put this commit in, so don't know what it is
Brian Stansberry wrote:
> Richard,
>
> Does this need to go in M4?
>
> Rajesh,
>
> If it needs to go in and I port it to the release branch this morning,
> will that screw things up for you guys?
>
>
> On 7/22/10 9:43 AM, Ales Justin wrote:
>> I saw some RestEasy-int commit that should probably be applied to this
>> branch as well -- if not yet done.
>>
>> ----
>>
>> Message: 5
>> Date: Thu, 22 Jul 2010 05:27:53 -0400
>> From: jboss-cvs-commits(a)lists.jboss.org
>> <mailto:jboss-cvs-commits@lists.jboss.org>
>> Subject: [jboss-cvs] JBossAS SVN: r107017 -
>> trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers.
>>
>> To: jboss-cvs-commits(a)lists.jboss.org
>> <mailto:jboss-cvs-commits@lists.jboss.org>
>> Message-ID:
>> <201007220927.o6M9RrEL015390(a)svn01.web.mwc.hst.phx2.redhat.com
>> <mailto:201007220927.o6M9RrEL015390@svn01.web.mwc.hst.phx2.redhat.com>>
>> Content-Type: text/plain; charset=UTF-8
>>
>> Author: richard.opalka@jboss.com<mailto:richard.opalka@jboss.com>
>> Date: 2010-07-22 05:27:52 -0400 (Thu, 22 Jul 2010)
>> New Revision: 107017
>>
>> Modified:
>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>> Log:
>> [JBAS-8234] fixing CCE
>>
>> Modified:
>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>> ===================================================================
>> ---
>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>> 2010-07-22 09:02:39 UTC (rev 107016)
>> +++
>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>> 2010-07-22 09:27:52 UTC (rev 107017)
>> @@ -146,7 +146,8 @@
>> {
>>
Thread.currentThread().getContextClassLoader().loadClass(CDI_INJECTOR_FACTORY_CLASS);
>> // don't set this param if CDI is not in classpath
>> - if (((VFSDeploymentUnit) du).getMetaDataFile("beans.xml") != null)
>> + final boolean isVFSDU = du instanceof VFSDeploymentUnit;
>> + if (isVFSDU&& ((VFSDeploymentUnit)
du).getMetaDataFile("beans.xml")
>> != null)
>> {
>> log.debug("***** Found CDI, adding injector factory class");
>> setContextParameter(webdata, "resteasy.injector.factory",
>> CDI_INJECTOR_FACTORY_CLASS);
>>
>>
>> On Jul 22, 2010, at 4:32 PM, Brian Stansberry wrote:
>>
>>> FYI, last night Jason created a branch for the M4 release.[1] Similar to
>>> the M2 release, the final QE tasks for the release will be done on that
>>> branch, with the expectation that the final M4 tag will be essentially
>>> the same as the root of the branch.
>>>
>>> The M4 release will probably come out early next week.
>>>
>>> AS trunk is now open for normal development work toward AS 6.0 final.
>>>
>>> [1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
>>> --
>>> Brian Stansberry
>>> Lead, AS Clustering
>>> JBoss by Red Hat
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development(a)lists.jboss.org
>>> <mailto:jboss-development@lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
>
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
1:30 p.m.
Richard Opalka put it in. Looks like a possible bug fix, looks pretty
harmless.
Brian Stansberry wrote:
The JIRA[1] is not closed and is marked for 6.0.0.Final, so I'm
not
porting this unless Bill, you tell me you want it and Rajesh says it's ok.
[1] https://jira.jboss.org/browse/JBAS-8234
On 7/22/10 10:26 AM, Bill Burke wrote:
> I didn't put this commit in, so don't know what it is
>
> Brian Stansberry wrote:
>> Richard,
>>
>> Does this need to go in M4?
>>
>> Rajesh,
>>
>> If it needs to go in and I port it to the release branch this morning,
>> will that screw things up for you guys?
>>
>>
>> On 7/22/10 9:43 AM, Ales Justin wrote:
>>> I saw some RestEasy-int commit that should probably be applied to this
>>> branch as well -- if not yet done.
>>>
>>> ----
>>>
>>> Message: 5
>>> Date: Thu, 22 Jul 2010 05:27:53 -0400
>>> From: jboss-cvs-commits(a)lists.jboss.org
>>> <mailto:jboss-cvs-commits@lists.jboss.org>
>>> Subject: [jboss-cvs] JBossAS SVN: r107017 -
>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers.
>>>
>>>
>>> To: jboss-cvs-commits(a)lists.jboss.org
>>> <mailto:jboss-cvs-commits@lists.jboss.org>
>>> Message-ID:
>>> <201007220927.o6M9RrEL015390(a)svn01.web.mwc.hst.phx2.redhat.com
>>>
<mailto:201007220927.o6M9RrEL015390@svn01.web.mwc.hst.phx2.redhat.com>>
>>> Content-Type: text/plain; charset=UTF-8
>>>
>>> Author: richard.opalka@jboss.com<mailto:richard.opalka@jboss.com>
>>> Date: 2010-07-22 05:27:52 -0400 (Thu, 22 Jul 2010)
>>> New Revision: 107017
>>>
>>> Modified:
>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>
>>> Log:
>>> [JBAS-8234] fixing CCE
>>>
>>> Modified:
>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>
>>> ===================================================================
>>> ---
>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>
>>> 2010-07-22 09:02:39 UTC (rev 107016)
>>> +++
>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>
>>> 2010-07-22 09:27:52 UTC (rev 107017)
>>> @@ -146,7 +146,8 @@
>>> {
>>>
Thread.currentThread().getContextClassLoader().loadClass(CDI_INJECTOR_FACTORY_CLASS);
>>>
>>> // don't set this param if CDI is not in classpath
>>> - if (((VFSDeploymentUnit) du).getMetaDataFile("beans.xml") !=
null)
>>> + final boolean isVFSDU = du instanceof VFSDeploymentUnit;
>>> + if (isVFSDU&& ((VFSDeploymentUnit)
du).getMetaDataFile("beans.xml")
>>> != null)
>>> {
>>> log.debug("***** Found CDI, adding injector factory class");
>>> setContextParameter(webdata, "resteasy.injector.factory",
>>> CDI_INJECTOR_FACTORY_CLASS);
>>>
>>>
>>> On Jul 22, 2010, at 4:32 PM, Brian Stansberry wrote:
>>>
>>>> FYI, last night Jason created a branch for the M4 release.[1]
>>>> Similar to
>>>> the M2 release, the final QE tasks for the release will be done on
>>>> that
>>>> branch, with the expectation that the final M4 tag will be essentially
>>>> the same as the root of the branch.
>>>>
>>>> The M4 release will probably come out early next week.
>>>>
>>>> AS trunk is now open for normal development work toward AS 6.0 final.
>>>>
>>>> [1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
>>>> --
>>>> Brian Stansberry
>>>> Lead, AS Clustering
>>>> JBoss by Red Hat
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development(a)lists.jboss.org
>>>> <mailto:jboss-development@lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>
>>>
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>>
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
3:31 p.m.
I ported it to the M4 branch.
On 7/22/10 1:30 PM, Bill Burke wrote:
Richard Opalka put it in. Looks like a possible bug fix, looks
pretty
harmless.
Brian Stansberry wrote:
> The JIRA[1] is not closed and is marked for 6.0.0.Final, so I'm not
> porting this unless Bill, you tell me you want it and Rajesh says it's
> ok.
>
> [1] https://jira.jboss.org/browse/JBAS-8234
>
> On 7/22/10 10:26 AM, Bill Burke wrote:
>> I didn't put this commit in, so don't know what it is
>>
>> Brian Stansberry wrote:
>>> Richard,
>>>
>>> Does this need to go in M4?
>>>
>>> Rajesh,
>>>
>>> If it needs to go in and I port it to the release branch this morning,
>>> will that screw things up for you guys?
>>>
>>>
>>> On 7/22/10 9:43 AM, Ales Justin wrote:
>>>> I saw some RestEasy-int commit that should probably be applied to this
>>>> branch as well -- if not yet done.
>>>>
>>>> ----
>>>>
>>>> Message: 5
>>>> Date: Thu, 22 Jul 2010 05:27:53 -0400
>>>> From: jboss-cvs-commits(a)lists.jboss.org
>>>> <mailto:jboss-cvs-commits@lists.jboss.org>
>>>> Subject: [jboss-cvs] JBossAS SVN: r107017 -
>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers.
>>>>
>>>>
>>>> To: jboss-cvs-commits(a)lists.jboss.org
>>>> <mailto:jboss-cvs-commits@lists.jboss.org>
>>>> Message-ID:
>>>> <201007220927.o6M9RrEL015390(a)svn01.web.mwc.hst.phx2.redhat.com
>>>>
<mailto:201007220927.o6M9RrEL015390@svn01.web.mwc.hst.phx2.redhat.com>>
>>>>
>>>> Content-Type: text/plain; charset=UTF-8
>>>>
>>>> Author: richard.opalka@jboss.com<mailto:richard.opalka@jboss.com>
>>>> Date: 2010-07-22 05:27:52 -0400 (Thu, 22 Jul 2010)
>>>> New Revision: 107017
>>>>
>>>> Modified:
>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>>
>>>> Log:
>>>> [JBAS-8234] fixing CCE
>>>>
>>>> Modified:
>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>>
>>>> ===================================================================
>>>> ---
>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>>
>>>> 2010-07-22 09:02:39 UTC (rev 107016)
>>>> +++
>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>>
>>>> 2010-07-22 09:27:52 UTC (rev 107017)
>>>> @@ -146,7 +146,8 @@
>>>> {
>>>>
Thread.currentThread().getContextClassLoader().loadClass(CDI_INJECTOR_FACTORY_CLASS);
>>>>
>>>> // don't set this param if CDI is not in classpath
>>>> - if (((VFSDeploymentUnit) du).getMetaDataFile("beans.xml") !=
null)
>>>> + final boolean isVFSDU = du instanceof VFSDeploymentUnit;
>>>> + if (isVFSDU&& ((VFSDeploymentUnit)
du).getMetaDataFile("beans.xml")
>>>> != null)
>>>> {
>>>> log.debug("***** Found CDI, adding injector factory class");
>>>> setContextParameter(webdata, "resteasy.injector.factory",
>>>> CDI_INJECTOR_FACTORY_CLASS);
>>>>
>>>>
>>>> On Jul 22, 2010, at 4:32 PM, Brian Stansberry wrote:
>>>>
>>>>> FYI, last night Jason created a branch for the M4 release.[1]
>>>>> Similar to
>>>>> the M2 release, the final QE tasks for the release will be done on
>>>>> that
>>>>> branch, with the expectation that the final M4 tag will be
>>>>> essentially
>>>>> the same as the root of the branch.
>>>>>
>>>>> The M4 release will probably come out early next week.
>>>>>
>>>>> AS trunk is now open for normal development work toward AS 6.0
final.
>>>>>
>>>>> [1] https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
>>>>> --
>>>>> Brian Stansberry
>>>>> Lead, AS Clustering
>>>>> JBoss by Red Hat
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development(a)lists.jboss.org
>>>>> <mailto:jboss-development@lists.jboss.org>
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>
>>>>
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>
>>>
>>
>
>
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
2:16 a.m.
Yes, it was a bug fix (there was a regression in our hudson).
Thanks Brian for porting it downstream.
Richard
On 07/22/2010 10:31 PM, Brian Stansberry wrote:
I ported it to the M4 branch.
On 7/22/10 1:30 PM, Bill Burke wrote:
> Richard Opalka put it in. Looks like a possible bug fix, looks pretty
> harmless.
>
> Brian Stansberry wrote:
>> The JIRA[1] is not closed and is marked for 6.0.0.Final, so I'm not
>> porting this unless Bill, you tell me you want it and Rajesh says it's
>> ok.
>>
>> [1] https://jira.jboss.org/browse/JBAS-8234
>>
>> On 7/22/10 10:26 AM, Bill Burke wrote:
>>> I didn't put this commit in, so don't know what it is
>>>
>>> Brian Stansberry wrote:
>>>> Richard,
>>>>
>>>> Does this need to go in M4?
>>>>
>>>> Rajesh,
>>>>
>>>> If it needs to go in and I port it to the release branch this morning,
>>>> will that screw things up for you guys?
>>>>
>>>>
>>>> On 7/22/10 9:43 AM, Ales Justin wrote:
>>>>> I saw some RestEasy-int commit that should probably be applied to
this
>>>>> branch as well -- if not yet done.
>>>>>
>>>>> ----
>>>>>
>>>>> Message: 5
>>>>> Date: Thu, 22 Jul 2010 05:27:53 -0400
>>>>> From: jboss-cvs-commits(a)lists.jboss.org
>>>>> <mailto:jboss-cvs-commits@lists.jboss.org>
>>>>> Subject: [jboss-cvs] JBossAS SVN: r107017 -
>>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers.
>>>>>
>>>>>
>>>>> To: jboss-cvs-commits(a)lists.jboss.org
>>>>> <mailto:jboss-cvs-commits@lists.jboss.org>
>>>>> Message-ID:
>>>>> <201007220927.o6M9RrEL015390(a)svn01.web.mwc.hst.phx2.redhat.com
>>>>>
<mailto:201007220927.o6M9RrEL015390@svn01.web.mwc.hst.phx2.redhat.com>>
>>>>>
>>>>> Content-Type: text/plain; charset=UTF-8
>>>>>
>>>>> Author:
richard.opalka@jboss.com<mailto:richard.opalka@jboss.com>
>>>>> Date: 2010-07-22 05:27:52 -0400 (Thu, 22 Jul 2010)
>>>>> New Revision: 107017
>>>>>
>>>>> Modified:
>>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>>>
>>>>> Log:
>>>>> [JBAS-8234] fixing CCE
>>>>>
>>>>> Modified:
>>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>>>
>>>>> ===================================================================
>>>>> ---
>>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>>>
>>>>> 2010-07-22 09:02:39 UTC (rev 107016)
>>>>> +++
>>>>>
trunk/resteasy-int/jar/src/main/java/org/jboss/resteasy/integration/deployers/ResteasyIntegrationDeployer.java
>>>>>
>>>>> 2010-07-22 09:27:52 UTC (rev 107017)
>>>>> @@ -146,7 +146,8 @@
>>>>> {
>>>>>
Thread.currentThread().getContextClassLoader().loadClass(CDI_INJECTOR_FACTORY_CLASS);
>>>>>
>>>>> // don't set this param if CDI is not in classpath
>>>>> - if (((VFSDeploymentUnit) du).getMetaDataFile("beans.xml")
!= null)
>>>>> + final boolean isVFSDU = du instanceof VFSDeploymentUnit;
>>>>> + if (isVFSDU&& ((VFSDeploymentUnit)
du).getMetaDataFile("beans.xml")
>>>>> != null)
>>>>> {
>>>>> log.debug("***** Found CDI, adding injector factory
class");
>>>>> setContextParameter(webdata, "resteasy.injector.factory",
>>>>> CDI_INJECTOR_FACTORY_CLASS);
>>>>>
>>>>>
>>>>> On Jul 22, 2010, at 4:32 PM, Brian Stansberry wrote:
>>>>>
>>>>>> FYI, last night Jason created a branch for the M4 release.[1]
>>>>>> Similar to
>>>>>> the M2 release, the final QE tasks for the release will be done
on
>>>>>> that
>>>>>> branch, with the expectation that the final M4 tag will be
>>>>>> essentially
>>>>>> the same as the root of the branch.
>>>>>>
>>>>>> The M4 release will probably come out early next week.
>>>>>>
>>>>>> AS trunk is now open for normal development work toward AS 6.0
final.
>>>>>>
>>>>>> [1]
https://svn.jboss.org/repos/jbossas/branches/6.0.0.20100721-M4
>>>>>> --
>>>>>> Brian Stansberry
>>>>>> Lead, AS Clustering
>>>>>> JBoss by Red Hat
>>>>>> _______________________________________________
>>>>>> jboss-development mailing list
>>>>>> jboss-development(a)lists.jboss.org
>>>>>> <mailto:jboss-development@lists.jboss.org>
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>
>>
--
Richard Opalka
ropalka(a)redhat.com
JBoss, by Red Hat
Office: +420 222 365 200
Mobile: +420 731 186 942
5270
days inactive
5271
days old
jboss-development@lists.jboss.org
14 comments
5 participants
participants (5)
-
Ales Justin -
Bill Burke -
Brian Stansberry -
Dimitris Andreadis -
Richard Opalka