geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2028) Plugin export errors don't stop process, but cause it to fail much later
Date Fri, 27 Jun 2008 18:57:45 GMT

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

Donald Woods closed GERONIMO-2028.
----------------------------------

    Resolution: Cannot Reproduce

This seems to have been fixed in 2.1.1 and 2.2.  Please reopen if you have a concrete scenario
that reproduces the failure on a later server version.

> Plugin export errors don't stop process, but cause it to fail much later
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-2028
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2028
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Plugins
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>            Assignee: Donald Woods
>
> When exporting a plugin, if there are any errors loading the existing XML document, the
console goes on to the export screen and just renders it entirely empty (including the module
ID).  It should instead produce an error message.
> To reproduce, edit repository/geronimo/welcome-jetty/1.1-SNAPSHOT/welcome-jetty-1.1-SNAPSHOT.car/META-INF/geronimo-plugin.xml
to make it invalid, go to the console, select the plugins screen, pick geronimo/welcome-jetty/*
as the configuration to export, and click the export button.  You presently get a screen with
a bunch of blank text fields, and should instead get an error message / page.

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


Mime
View raw message