[jira] Closed: (GERONIMO-2204) ProxyMethodInterceptor doesn't handle finalize appropriately

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

David Jencks closed GERONIMO-2204.
----------------------------------

    Resolution: Won't Fix

We turned off proxies in the server so there isnt much reason to work on this any more.

> ProxyMethodInterceptor doesn't handle finalize appropriately
> ------------------------------------------------------------
>
>                 Key: GERONIMO-2204
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2204
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: kernel
>    Affects Versions: 1.1, 1.1.1, 1.1.2, 1.1.x, 1.2
>            Reporter: David Jencks
>            Assignee: David Jencks
>            Priority: Minor
>             Fix For: Wish List
>
>
> A user noticed that while debugging in eclipse (or idea with break-on-exceptions turned on) this method
from ProxyMethodInterceptor throws UnsupportedOperationException when finalize is called on a proxy object:
>     public final Object intercept(final Object object, final Method method, final Object[] args, final

[jira] Closed: (GERONIMO-3683) Unable to view the installed geronimo plugins

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

David Jencks closed GERONIMO-3683.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1

If someone wants to test 2.0.3 and theres a problem they are welcome to assign this to themselves and reopen.

> Unable to view the installed geronimo plugins
> ---------------------------------------------
>
>                 Key: GERONIMO-3683
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3683
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Plugins
>    Affects Versions: 2.0.1, 2.0.2
>         Environment: Windows XP
>            Reporter: anish pathadan
>            Assignee: David Jencks
>             Fix For: 2.1
>
>
> I have installed a geronimo plugin created by myself in my geronimo server.When I tried to access the
plugins from a different server using the following url

[jira] Assigned: (GERONIMO-1567) Plan XML files aren't included in Geronimo distributions (was included in M5 release)

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

David Jencks reassigned GERONIMO-1567:
--------------------------------------

    Assignee: David Jencks  (was: Jason Dillon)

> Plan XML files aren't included in Geronimo distributions (was included in M5 release)
> -------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-1567
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-1567
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: car-maven-plugin
>    Affects Versions: 1.0
>            Reporter: John Sisson
>            Assignee: David Jencks
>             Fix For: 2.1
>
>
> It was a combination of an oversight and the idea that being able to add gbeans using config.xml could
replace the need to modify and redeploy the plans we supply.

--

-- 
This message is automatically generated by JIRA.
-

[jira] Closed: (GERONIMO-1567) Plan XML files aren't included in Geronimo distributions (was included in M5 release)

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

David Jencks closed GERONIMO-1567.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0.x)
                   2.1

The car-maven-plugin is including the updated plan files in the generated cars now.

> Plan XML files aren't included in Geronimo distributions (was included in M5 release)
> -------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-1567
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-1567
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: car-maven-plugin
>    Affects Versions: 1.0
>            Reporter: John Sisson
>            Assignee: Jason Dillon
>             Fix For: 2.1
>
>
> It was a combination of an oversight and the idea that being able to add gbeans using config.xml could
replace the need to modify and redeploy the plans we supply.

[jira] Assigned: (GERONIMO-3466) car-maven-plugin can not generate server plugin which includes EJB

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

David Jencks reassigned GERONIMO-3466:
--------------------------------------

    Assignee: David Jencks

> car-maven-plugin can not generate server plugin which includes EJB
> ------------------------------------------------------------------
>
>                 Key: GERONIMO-3466
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3466
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: car-maven-plugin
>    Affects Versions: 2.0.1
>            Reporter: YunFeng Ma
>            Assignee: David Jencks
>             Fix For: 2.0.x
>
>         Attachments: calculator-stateless-ear.zip
>
>
> openejb-deployer configuration depends on openejb configuration, and openejb configuration depends
on j2ee-server configuration. That means car-maven-plugin has to start all the depended
configurations, not only the openejb-deployer configuration. This caused the following error.
> {code}

[jira] Closed: (GERONIMO-3250) geronimo-kernel should be module?

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

David Jencks closed GERONIMO-3250.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1
         Assignee: David Jencks

geronimo-kernel should not be in the remote-deploy lib dir, that is an error in that module's pom.

In geronimo 2.1 the geronimo-kernel module is actually in the local repo.  Previously its always been in lib
as it is only accessed from a startup classpath specified in a manifest.  In the future the copy in the g. repo
may be used.

> geronimo-kernel should be module?
> ---------------------------------
>
>                 Key: GERONIMO-3250
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3250
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: dependencies
>    Affects Versions: 2.0-M6
>         Environment: 2.0-M6-rc1
>            Reporter: Alexander Zynevich
>            Assignee: David Jencks

[BUILD] 2.1: Failed for Revision: 617327

Geronimo Revision: 617327 built with tests included

See the full build-2100.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080131/build-2100.log

Download the binaries from http://geronimo.apache.org/maven/server/binaries/trunk/20080131
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 30 minutes 33 seconds
[INFO] Finished at: Thu Jan 31 21:45:20 EST 2008
[INFO] Final Memory: 309M/998M
[INFO] ------------------------------------------------------------------------

TESTSUITE RESULTS (Failures only)
=================================
See detailed results at http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html

Assembly: tomcat
=================================
See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080131/logs-2100-tomcat/test.log

 
Assembly: jetty
=================================
See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080131/logs-2100-jetty/test.log

[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 75.454 sec <<< FAILURE!

Re: [ANNOUNCE] Viet Nguyen as Geronimo's most recent committer

Congrats Viet!

Thanks,
Gianny

On 31/01/2008, at 2:47 PM, Kevan Miller wrote:

> All,
> I'd like to welcome Viet Nguyen as a new committer on the Geronimo  
> project. Viet has made a number of contributions to Geronimo,  
> including our new monitoring capabilities, the J2G conversion tool,  
> as well as a number of bug fixes, and other helpful contributions.
>
> Let's lay some props on Viet!
>
> --kevan

Re: [VOTE] Release the specs

[jira] Closed: (GERONIMO-2025) Undeploy and redeploy with no version leaves dangling entries in config.xml

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

Kevan Miller closed GERONIMO-2025.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0.x)
         Assignee: Kevan Miller  (was: Rakesh Midha)

In 2.1, undeployed apps are not left in config.xml

May still be a problem in branches/2.0, but won't plan on fixing there.

> Undeploy and redeploy with no version leaves dangling entries in config.xml
> ---------------------------------------------------------------------------
>
>                 Key: GERONIMO-2025
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2025
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment, kernel
>    Affects Versions: 1.1, 2.0.x, 2.1
>            Reporter: Aaron Mulder
>            Assignee: Kevan Miller
>             Fix For: 2.1
>
>         Attachments: removeunwantedconfig.patch
>
>
> If you deploy an application with no version and then undeploy it, we leave an entry for it (with a timestamp
version number) in config.xml, just marked as load=false.
> If you later deploy the application again, you get a new timestamp version number and a new entry is written
into config.xml.  Do this (undeploy/deploy) a few times and config.xml gets kind of messy.
> It would be be good to delete entries from config.xml on undeploy if they have no actual settings.
> It would be good to detect that a previous version is in conifg.xml but not in the repository and delete the
settings from config.xml if the artifact has no version number and a newer copy is deployed.
> This is not a huge priority since nothing breaks, it just makes config.xml kind of crufty.

--

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