[
http://jira.codehaus.org/browse/MWEBLOGIC-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195387#action_195387
]
Mat Schaffer commented on MWEBLOGIC-8:
--------------------------------------
Sorry, guess I missed your comment last december. The extra step of mvn
resources:resources is not desirable. Our workflow is:
- edit
- refresh browser, see change (repeat as needed)
- commit
Anything longer than that is sub-optimal.
We've since moved most of our development to tomcat or jetty, both of which
have maven plugins which support running the contents of src/main/webapp
(jetty:run, tomcat:run). I've used tomcat:run to do this on perforce projects
and haven't had any issues. I haven't had any experience with any other locking
source control systems.
Sorry it took so long to get back to you. Hope that helps.
> Adding support for exploded war deployments using war:inplace
> -------------------------------------------------------------
>
> Key: MWEBLOGIC-8
> URL: http://jira.codehaus.org/browse/MWEBLOGIC-8
> Project: Mojo WebLogic Plugin
> Issue Type: Improvement
> Reporter: Mat Schaffer
> Assignee: Jon Osborn
> Attachments: weblogic-maven-plugin_source-deployments.patch
>
>
> The weblogic deployer supports deployment of an exploded war (such as that
> generated by war:inplace), but the weblogic-maven-plugin does not. The
> attached patch adds support for projectPackaging=source which will attempt to
> deploy the contents of src/main/webapp in the current project.
> Original credit on this patch is to Ilirjan Papa
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
