gawor | 1 Feb 04:08 2009
Picon

[BUILD] trunk: Failed for Revision: 739669

Geronimo Revision: 739669 built with tests included

See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090131/build-2100.log

Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20090131
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 37 minutes 55 seconds
[INFO] Finished at: Sat Jan 31 21:42:02 EST 2009
[INFO] Final Memory: 634M/976M
[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/20090131/logs-2100-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...
(Continue reading)

gawor | 1 Feb 04:13 2009
Picon

[BUILD] branches/2.0: Failed for Revision: 739664

Geronimo Revision: 739664 built with tests included

See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090131/build-2000.log

Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.0/20090131
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 33 minutes 38 seconds
[INFO] Finished at: Sat Jan 31 20:38:18 EST 2009
[INFO] Final Memory: 223M/929M
[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/2.0/20090131/logs-2000-tomcat/test.log

[INFO] Running console-testsuite.basic-console
[INFO] Tests run: 38, Failures: 12, Errors: 0, Skipped: 0, Time elapsed: 3,753.002 sec <<< FAILURE!

Assembly: jetty
=================================
See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.0/20090131/logs-2000-jetty/test.log

David Jencks (JIRA | 1 Feb 19:23 2009
Picon

[jira] Commented: (GERONIMO-4523) Security Realm based Group-Role Mapping


    [
https://issues.apache.org/jira/browse/GERONIMO-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669417#action_12669417
] 

David Jencks commented on GERONIMO-4523:
----------------------------------------

So far it doesn't look completely possible to have a default realm, but I'll keep trying :-)  It's would
certainly make life easier for everyone.  I like your ideas about a UI for configuring the principal-role
mapping but I'm not going to be able to implement them in the forseeable future.  

It looks like the changes needed for this feature are much more extensive than we can put into 2.1.4 so I'm
afraid it will have to wait for 2.2.

The problem I'm having is with where to put some flags about how to set up jacc.... 

                <xsd:attribute name="doas-current-caller" type="xsd:boolean" default="false">
                    <xsd:annotation>
                        <xsd:documentation>
                            Set this attribute to "true" if the work is to be performed
                            as the calling Subject.
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:attribute>
                <xsd:attribute name="use-context-handler" type="xsd:boolean" default="false">
                    <xsd:annotation>
                        <xsd:documentation>
                            Set this attribute to "true" if the installed JACC policy
                            contexts will use PolicyContextHandlers.
(Continue reading)

gawor | 2 Feb 04:10 2009
Picon

[BUILD] trunk: Failed for Revision: 739895

Geronimo Revision: 739895 built with tests included

See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090201/build-2100.log

Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20090201
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 38 minutes 12 seconds
[INFO] Finished at: Sun Feb 01 21:43:00 EST 2009
[INFO] Final Memory: 625M/972M
[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/20090201/logs-2100-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...
(Continue reading)

Guillaume Nodet (JIRA | 2 Feb 10:35 2009
Picon

[jira] Commented: (GSHELL-156) Disable system bell by default


    [
https://issues.apache.org/jira/browse/GSHELL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669535#action_12669535
] 

Guillaume Nodet commented on GSHELL-156:
----------------------------------------

Though it would not harm to have a system property to control that.  We can leave the current behavior as is in
gshell and switch it off in servicemix ...

> Disable system bell by default
> ------------------------------
>
>                 Key: GSHELL-156
>                 URL: https://issues.apache.org/jira/browse/GSHELL-156
>             Project: GShell
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Commands - Shell
>    Affects Versions: 1.0-alpha-2
>         Environment: Windows
>            Reporter: Chris Custine
>            Assignee: Jason Dillon
>            Priority: Minor
>         Attachments: nobell.patch
>
>
> On WIndows, attempting to backspace at the beginning of a line causes the system bell to sound, thereby
knocking many a user off their chair.  I would recommend disabling this for the sake of Windows users.  *nix
(Continue reading)

Donald Woods (JIRA | 2 Feb 14:21 2009
Picon

[jira] Updated: (GERONIMO-4426) Add a new Log Level portlet to the Server Logs page to allow dynamic changing of Logger levels


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

Donald Woods updated GERONIMO-4426:
-----------------------------------

    Fix Version/s:     (was: 2.2)
                   Wish List
         Assignee:     (was: Donald Woods)

moving to wish list

> Add a new Log Level portlet to the Server Logs page to allow dynamic changing of Logger levels
> ----------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4426
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4426
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: console, Logging
>            Reporter: Donald Woods
>            Priority: Minor
>             Fix For: Wish List
>
>
> Create a new portlet that will allow users to dynamically change the Logger level for any logger class in
the server.
> The changes will not be preserved after a server restart, as this is only geared towards helping with
(Continue reading)

Ivan (JIRA | 2 Feb 15:25 2009
Picon

[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory


    [
https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669610#action_12669610
] 

Ivan commented on GERONIMO-4251:
--------------------------------

Thanks, Frank
One thing I want to confirm is that whether all the entries in the class-path be relative URLs, which means
/myLibs and /x/aDirectory in your example should be something like myLibs and x/aDirectory ?

> Class-Path entry in WAR manifest didn't work if entry is a directory
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-4251
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4251
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>         Environment: Geronimo 2.1.2 on Windows XP
>            Reporter: Frank Meilinger
>            Assignee: Ivan
>             Fix For: 2.1.4, 2.2
>
>
> Hi,
> it's not possible to define an Class-Path element in the WARs manifest, if it's a directory.  I try to access
jar files packed in the EARs lib/ directory from within a WAR module.
(Continue reading)

Frank Meilinger (JIRA | 2 Feb 15:43 2009
Picon

[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory


    [
https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669616#action_12669616
] 

Frank Meilinger commented on GERONIMO-4251:
-------------------------------------------

Hi Ivan,

Yes. I think the path "/" means the root of the ear-file. So I think you are right, the directory "/myLibs"
should have the same meaning as the directory name "myLibs" becaue the "current directory" makes sense to
be the root of the acual ear-file.

example of ear-file structure:

/
  /lib
  /META-INF
  /myLibs

In this sample, an class-path entry of "myLibs" should be the same as "/myLibs" because "/" is the root of the ear.

Greetings,
 Frank

> Class-Path entry in WAR manifest didn't work if entry is a directory
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-4251
(Continue reading)

Ivan (JIRA | 2 Feb 15:49 2009
Picon

[jira] Updated: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory


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

Ivan updated GERONIMO-4251:
---------------------------

    Attachment: Geronimo-4251.patch

Please help to review the patch. Currently, it allows the relative URLs in the class-path attribute.
Thanks !

> Class-Path entry in WAR manifest didn't work if entry is a directory
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-4251
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4251
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>         Environment: Geronimo 2.1.2 on Windows XP
>            Reporter: Frank Meilinger
>            Assignee: Ivan
>             Fix For: 2.1.4, 2.2
>
>         Attachments: Geronimo-4251.patch
>
>
> Hi,
(Continue reading)

David Jencks (JIRA | 2 Feb 18:36 2009
Picon

[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory


    [
https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669664#action_12669664
] 

David Jencks commented on GERONIMO-4251:
----------------------------------------

Someone needs to look at the spec again.... my recollection is that relative urls are relative to the
location of the module in the ear.  So if your module is at the ear root relative and absolute mean the same
thing but if your module is at /foo/bar/myModule.jar then ../baz/myLib.jar would be the same as /foo/baz/myLib.jar

> Class-Path entry in WAR manifest didn't work if entry is a directory
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-4251
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4251
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>         Environment: Geronimo 2.1.2 on Windows XP
>            Reporter: Frank Meilinger
>            Assignee: Ivan
>             Fix For: 2.1.4, 2.2
>
>         Attachments: Geronimo-4251.patch
>
>
> Hi,
(Continue reading)


Gmane