[jira] Updated: (GERONIMO-4622) Contribution: Linux service script for Geronimo/WAS CE

2009-05-11 Thread viola.lu (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

viola.lu updated GERONIMO-4622:
---

Attachment: gserviceReg.patch

Thanks ivan for your suggestion, and based on it, i updated this patch which 
can autostart after server boot time on Redhat 5.2, Suse 10 Sp2, Aix 
6.1,Solaris 10, and ubuntu (root).
Pls review and apply it.Thanks.



> Contribution: Linux service script for Geronimo/WAS CE  
> 
>
> Key: GERONIMO-4622
> URL: https://issues.apache.org/jira/browse/GERONIMO-4622
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: startup/shutdown
>Affects Versions: 2.1.4
> Environment: RedHat Enterprise Linux v5.3
> WAS CE 2.1.1.2
>Reporter: Amir Mistric
>Assignee: Ivan
>Priority: Trivial
> Attachments: gserviceReg.patch, wasce-linux-service.sh
>
>
> As per suggestion on WAS CE forum, I am attaching a shell script that can be 
> used for Linux services script in Geronimo/WAS CE.
> For more information please [see this 
> thread|http://www.ibm.com/developerworks/forums/thread.jspa?threadID=260135&tstart=0]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-4622) Contribution: Linux service script for Geronimo/WAS CE

2009-05-11 Thread viola.lu (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

viola.lu updated GERONIMO-4622:
---

Attachment: (was: gserviceReg.patch)

> Contribution: Linux service script for Geronimo/WAS CE  
> 
>
> Key: GERONIMO-4622
> URL: https://issues.apache.org/jira/browse/GERONIMO-4622
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: startup/shutdown
>Affects Versions: 2.1.4
> Environment: RedHat Enterprise Linux v5.3
> WAS CE 2.1.1.2
>Reporter: Amir Mistric
>Assignee: Ivan
>Priority: Trivial
> Attachments: gserviceReg.patch, wasce-linux-service.sh
>
>
> As per suggestion on WAS CE forum, I am attaching a shell script that can be 
> used for Linux services script in Geronimo/WAS CE.
> For more information please [see this 
> thread|http://www.ibm.com/developerworks/forums/thread.jspa?threadID=260135&tstart=0]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (DAYTRADER-68) A version of daytrader for Tomcat 6

2009-05-11 Thread Joe Bohn (JIRA)

[ 
https://issues.apache.org/jira/browse/DAYTRADER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708034#action_12708034
 ] 

Joe Bohn commented on DAYTRADER-68:
---

Another issue:   Although there are some problems with building daytrader trunk 
without this patch applied once it is applied there is a new problem:
Project 'org.apache.geronimo.daytrader:daytrader-web' is duplicated in the 
reactor
Looks like there is a conflict because we now have to projects named 
daytrader-web - the original one under modules/web/ and the new one.

> A version of daytrader for Tomcat 6
> ---
>
> Key: DAYTRADER-68
> URL: https://issues.apache.org/jira/browse/DAYTRADER-68
> Project: DayTrader
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: Web Tier
>Affects Versions: 2.2
> Environment: Tomcat 6.0.18
>Reporter: Forrest Xia
>Assignee: Forrest Xia
> Attachments: daytrader-webonly-new.patch, daytrader-webonly-new.zip, 
> daytrader-webonly.patch
>
>
> I have a trimmed version of daytrader for tomcat 6, and want to contribute to 
> daytrader trunk, please help review and commit. thanks!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[BUILD] trunk: Failed for Revision: 773634

2009-05-11 Thread gawor
Geronimo Revision: 773634 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 38 minutes 44 seconds
[INFO] Finished at: Mon May 11 15:41:44 EDT 2009
[INFO] Final Memory: 397M/1010M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/logs-1500-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from codehaus-snapshots
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:44.634
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:13.215) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:30.500) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:35.491) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.105) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:23.505) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:32.217) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:58.271) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:48.017) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:46.748) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:42.102) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:29.904) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:29.106) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:31.466) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:02.192) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:53.718) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:53.618) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.390) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:37.337) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:41.249) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.517) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test

WS-Security support for JAX-WS Web Services

2009-05-11 Thread rahul.soa
Hello everyone,

As you know I am working on the support of ws-security module, so I did some
research about integrating the modules in Apache Geronimo for the same.

For the integrating/enabling WS-Security support, I think we need to have
the following jars and modules in Geronimo:

*Apache CXF:*

For WS-Security support we need to have following jar files from the CXF:

- bcprov-jdk15.jar
- xalan.jar
- serializer.jar
- wss4j.jar
- xmlsec.jar


*Apache Axis2*

1. We need to integrate "Rampart*" module of axis2,

2. for step 1, need to download the Java Cryptography Extension (JCE)
Unlimited Strength Jurisdiction Policy Files corresponding to JDK version
and extract the jar files local_policy.jar and US_export_policy.jar to
$JAVA_HOME/jre/lib/security

3. for step 1, need to download bouncycastle according to java version
separately

*Rampart is the security module of Axis2


Please let me know if I am missing something and please also guide me how
can I get them in Geronimo.

Thanks in advance.

Regards,
Rahul


Re: WS-Security support for JAX-WS Web Services

2009-05-11 Thread David Jencks


On May 11, 2009, at 3:24 PM, rahul.soa wrote:


Hello everyone,

As you know I am working on the support of ws-security module, so I  
did some research about integrating the modules in Apache Geronimo  
for the same.


For the integrating/enabling WS-Security support, I think we need to  
have the following jars and modules in Geronimo:


Apache CXF:

For WS-Security support we need to have following jar files from the  
CXF:


- bcprov-jdk15.jar


Previously when we used some bouncy castle classes the jar included  
some classes that may well have infringed some us patents.  I think I  
saw somewhere that bouncy castle had finally released a jar without  
thses classes.  We should verify that this jar does not contain these  
classes.  Also, we have copies of a bunch of the bc classes we need  
for other purposes in the geronimo-crypto module, so we should check  
that we don't already have the needed classes.


- xalan.jar


really?  I'd like to know why the xml transform support in the jdk is  
not sufficient.


- serializer.jar
- wss4j.jar
- xmlsec.jar


Apache Axis2

1. We need to integrate "Rampart*" module of axis2,

2. for step 1, need to download the Java Cryptography Extension  
(JCE) Unlimited Strength Jurisdiction Policy Files corresponding to  
JDK version and extract the jar files local_policy.jar and  
US_export_policy.jar to $JAVA_HOME/jre/lib/security


These are not something we can include, right?  they'd have to be  
installed by the end user?



3. for step 1, need to download bouncycastle according to java  
version separately


*Rampart is the security module of Axis2


Please let me know if I am missing something and please also guide  
me how can I get them in Geronimo.


That depends partly on the classloader relationships needed between  
the main cxf/axis2 jars and these new ones.  If appropriate cxf/axis2  
jars and these jars can be in a classloader that is a child of the cxf/ 
axis2 "main" plugin classloaders, you should probably make cxf-wss and  
axis2-wss plugins with all the security related jars as dependencies.   
If this doesn't work and the classes need to be in the main cxf/axis2  
plugin classloader then you probably need to just add these as  
dependencies.


thanks
david jencks





Thanks in advance.

Regards,
Rahul




Re: WS-Security support for JAX-WS Web Services

2009-05-11 Thread Daniel Kulp
On Mon May 11 2009 7:16:46 pm David Jencks wrote:
> On May 11, 2009, at 3:24 PM, rahul.soa wrote:
> > Hello everyone,
> >
> > As you know I am working on the support of ws-security module, so I
> > did some research about integrating the modules in Apache Geronimo
> > for the same.
> >
> > For the integrating/enabling WS-Security support, I think we need to
> > have the following jars and modules in Geronimo:
> >
> > Apache CXF:
> >
> > For WS-Security support we need to have following jar files from the
> > CXF:
> >
> > - bcprov-jdk15.jar
>
> Previously when we used some bouncy castle classes the jar included
> some classes that may well have infringed some us patents.  I think I
> saw somewhere that bouncy castle had finally released a jar without
> thses classes.  We should verify that this jar does not contain these
> classes.  Also, we have copies of a bunch of the bc classes we need
> for other purposes in the geronimo-crypto module, so we should check
> that we don't already have the needed classes.

Version 140 and later in maven have the patent covered algorithms removed.   
Not an issue anymore.

>
> > - xalan.jar
>
> really?  I'd like to know why the xml transform support in the jdk is
> not sufficient.

xmlsec uses some of the internal xalan classes.   I could never get a good 
reason as to why. 

> > - serializer.jar

This goes with Xalan.


> > - wss4j.jar
> > - xmlsec.jar

Note:  all of those jars will be required for Axis2 as well.


> > Apache Axis2
> >
> > 1. We need to integrate "Rampart*" module of axis2,
> >
> > 2. for step 1, need to download the Java Cryptography Extension
> > (JCE) Unlimited Strength Jurisdiction Policy Files corresponding to
> > JDK version and extract the jar files local_policy.jar and
> > US_export_policy.jar to $JAVA_HOME/jre/lib/security
>
> These are not something we can include, right?  they'd have to be
> installed by the end user?

Correct.   However, for unit tests and such, we can PROBABLY use less secure 
algorithms.   I have someone looking into the same issue for the CXF test 
cases.   We don't want to make every developer have to install the strong 
crypto libraries.  Basically, if the user needs the strong crypto stuff, they 
WILL need to download and install the strong crypto libs from Sun.

Dan

> > 3. for step 1, need to download bouncycastle according to java
> > version separately
> >
> > *Rampart is the security module of Axis2
> >
> >
> > Please let me know if I am missing something and please also guide
> > me how can I get them in Geronimo.
>
> That depends partly on the classloader relationships needed between
> the main cxf/axis2 jars and these new ones.  If appropriate cxf/axis2
> jars and these jars can be in a classloader that is a child of the cxf/
> axis2 "main" plugin classloaders, you should probably make cxf-wss and
> axis2-wss plugins with all the security related jars as dependencies.
> If this doesn't work and the classes need to be in the main cxf/axis2
> plugin classloader then you probably need to just add these as
> dependencies.
>
> thanks
> david jencks
>
> > Thanks in advance.
> >
> > Regards,
> > Rahul

-- 
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog


Latest trunk builds are not the "latest".

2009-05-11 Thread Shawn Jiang
The trunk binary here was built on 15-Apr-2009 according to
http://people.apache.org/builds/geronimo/server/binaries/trunk/latest/


<http://people.apache.org/builds/geronimo/server/binaries/trunk/latest/>While
the latest binary here
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/
 indicates
the latest build should be 12-May-2009

Is there any problem with the build system ?
-- 
Shawn


Re: Latest trunk builds are not the "latest".

2009-05-11 Thread David Jencks
I strongly suspect that the testsuite has been failing since 15 april,  
thus preventing copying to the "latest" location.


Personally I get more and different testsuite failures locally on my  
mac, but I haven't looked very hard into why.  Can anyone supply info  
on the test failure that is occurring in the automated builds?


thanks
david jencks

On May 11, 2009, at 6:31 PM, Shawn Jiang wrote:


The trunk binary here was built on 15-Apr-2009  according to 
http://people.apache.org/builds/geronimo/server/binaries/trunk/latest/


While the latest binary here http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/ 
  indicates the latest build should be 12-May-2009


Is there any problem with the build system ?
--
Shawn




[BUILD] trunk: Failed for Revision: 773734

2009-05-11 Thread gawor
Geronimo Revision: 773734 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 36 minutes 23 seconds
[INFO] Finished at: Mon May 11 21:39:30 EDT 2009
[INFO] Final Memory: 666M/1003M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/logs-2100-tomcat/test.log
 
 
[INFO] Using assembly artifact: 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding: 
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
 into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to: 
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:40.789
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to 
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:00.359) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:28.421) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:33.552) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.033) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:29.953) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:28.862) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:53.673) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:51.151) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:42.502) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:43.436) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:30.752) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:32.012) 
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:33.224) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:01.048) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:54.579) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:53.158) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.438) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:38.380) Java 
returned: 1
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:38.305) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:31.912) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:29.101) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web

Re: Latest trunk builds are not the "latest".

2009-05-11 Thread Jarek Gawor
Yep. The 'latest' link is updated when all testsuite test pass.

You can browse the results at:
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/
(under logs-- directories).

For example for enterprise-testsuite/sec-tests see
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/logs-2100-tomcat/enterprise-testsuite/sec-tests/sec-ear/target/surefire-reports/org.apache.geronimo.mavenplugins.geronimo.server.RunClientMojo.txt

Jarek

On Mon, May 11, 2009 at 10:07 PM, David Jencks  wrote:
> I strongly suspect that the testsuite has been failing since 15 april, thus
> preventing copying to the "latest" location.
> Personally I get more and different testsuite failures locally on my mac,
> but I haven't looked very hard into why.  Can anyone supply info on the test
> failure that is occurring in the automated builds?
> thanks
> david jencks
> On May 11, 2009, at 6:31 PM, Shawn Jiang wrote:
>
> The trunk binary here was built on 15-Apr-2009 according to
> http://people.apache.org/builds/geronimo/server/binaries/trunk/latest/
>
> While the latest binary
> here http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/  indicates
> the latest build should be 12-May-2009
> Is there any problem with the build system ?
> --
> Shawn
>
>


Re: Latest trunk builds are not the "latest".

2009-05-11 Thread David Blevins
Hmmm.  I seem to recall mid April being the time that we realized we  
weren't getting updated openejb snapshots due to the nexus switch.  I  
suspect it might some left over "must updated the clients to use the  
right JNDI name" due to the fix that Manu made a few months back that  
made it so the jndi name elements in the openejb-jar.xml worked again.



-David


On May 11, 2009, at 7:31 PM, Jarek Gawor wrote:


Yep. The 'latest' link is updated when all testsuite test pass.

You can browse the results at:
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/
(under logs-- directories).

For example for enterprise-testsuite/sec-tests see
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/logs-2100-tomcat/enterprise-testsuite/sec-tests/sec-ear/target/surefire-reports/org.apache.geronimo.mavenplugins.geronimo.server.RunClientMojo.txt

Jarek

On Mon, May 11, 2009 at 10:07 PM, David Jencks  
 wrote:
I strongly suspect that the testsuite has been failing since 15  
april, thus

preventing copying to the "latest" location.
Personally I get more and different testsuite failures locally on  
my mac,
but I haven't looked very hard into why.  Can anyone supply info on  
the test

failure that is occurring in the automated builds?
thanks
david jencks
On May 11, 2009, at 6:31 PM, Shawn Jiang wrote:

The trunk binary here was built on 15-Apr-2009 according to
http://people.apache.org/builds/geronimo/server/binaries/trunk/ 
latest/


While the latest binary
here http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/ 
  indicates

the latest build should be 12-May-2009
Is there any problem with the build system ?
--
Shawn








[BUILD] trunk: Failed for Revision: 773795

2009-05-11 Thread gawor
Geronimo Revision: 773795 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090512/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090512/unit-test-reports
 
[INFO] 
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: process}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/plugins/openjpa/openjpa/src/main/resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[INFO] Generated: 
/home/geronimo/geronimo/trunk/plugins/openjpa/openjpa/target/resources/META-INF/plan.xml
[INFO] [car:verify-no-dependency-change]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[INFO] [car:package]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[INFO] Packaging module configuration: 
/home/geronimo/geronimo/trunk/plugins/openjpa/openjpa/target/resources/META-INF/plan.xml
[INFO] Started deployer: 
org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
[INFO] [car:prepare-metadata]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[INFO] [car:archive-car]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[INFO] Building jar: 
/home/geronimo/geronimo/trunk/plugins/openjpa/openjpa/target/openjpa-2.2-SNAPSHOT.car
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: openjpa-2.2-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing 
/home/geronimo/geronimo/trunk/plugins/openjpa/openjpa/target/openjpa-2.2-SNAPSHOT.car
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/configs/openjpa/2.2-SNAPSHOT/openjpa-2.2-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO] 
[INFO] Building Geronimo Plugins, OpenEJB :: OpenEJB
[INFO]task-segment: [install]
[INFO] 
Downloading: 
http://people.apache.org/repo/m2-incubating-repository//commons-logging/commons-logging-api/1.1/commons-logging-api-1.1.pom
Downloading: 
http://repo.exist.com/maven2/commons-logging/commons-logging-api/1.1/commons-logging-api-1.1.pom
5K downloaded
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[INFO] [remote-resources:process {execution: process}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[INFO] Generated: 
/home/geronimo/geronimo/trunk/plugins/openejb/openejb/target/resources/META-INF/plan.xml
[INFO] [car:verify-no-dependency-change]
[WARNING] Component returned which is not the same manager. Ignored. 
component=org.apache.maven.profiles.activation.fileprofileactiva...@2b6a2b6a
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Dependencies have changed:
Added dependencie