geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] [Commented] (GERONIMODEVTOOLS-744) More flexible no-redeployment option
Date Wed, 22 Jun 2011 06:01:49 GMT


Jarek Gawor commented on GERONIMODEVTOOLS-744:

Added support for more flexible no-redeployment option in the following revisions: 1134919,
1135267, 1135268, and 1135290.

No-redeployment option is only supported on web modules (Java EE & OSGI bundles, standalone
or embedded). Modified files that are not on the include file list or are on the exclude file
list will cause the entire module to be re-deployed. Otherwise, a simple file copy or delete
is performed. The no-redeployment option only works on web modules that have "document base"
(i.e. publish directory) set. That is, GEP searches for WebModule mbeans with a specific "contextPath"
and looks up their "docBase" directory. 

> More flexible no-redeployment option
> ------------------------------------
>                 Key: GERONIMODEVTOOLS-744
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: New Feature
>          Components: eclipse-plugin
>    Affects Versions: 3.0
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>             Fix For: 3.0
> It would be nice to let user specify a list of file extensions that do not cause the
application to be re-deployed if one of the files with a matching extension is modified. Instead
the given file would be simply copied and the application left running as is.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message