[
https://issues.apache.org/jira/browse/TOBAGO-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740158#comment-16740158
]
Hudson commented on TOBAGO-1970:
--------------------------------
SUCCESS: Integrated in Jenkins build Tobago Trunk #1641 (See
[https://builds.apache.org/job/Tobago%20Trunk/1641/])
TOBAGO-1970: Configure web.xml listeners via JARs (for Mojarra, MyFaces,
(lofwyr: rev e4b9b2a05727d56b4288f6397d131243263d174d)
* (edit) tobago-example/tobago-example-demo/src/main/webapp/WEB-INF/web.xml
* (edit) tobago-example/pom.xml
> Configure web.xml listeners via JARs (for Mojarra, MyFaces, OWB, etc.)
> ----------------------------------------------------------------------
>
> Key: TOBAGO-1970
> URL: https://issues.apache.org/jira/browse/TOBAGO-1970
> Project: MyFaces Tobago
> Issue Type: Task
> Components: Build, Demo
> Reporter: Udo Schnurpfeil
> Assignee: Udo Schnurpfeil
> Priority: Major
> Fix For: 5.0.0
>
>
> Currently, there is a need sometimes to comment in/out listeners in the
> web.xml to run the example WAR in different application servers. With Servlet
> 3.0 web-fragments, we can include these configurations via a JAR. So we can
> build different versions via Maven profiles.
> * tobago-config-myfaces
> * tobago-config-mojarra
> * tobago-config-owb
> The current was also includes override-?.xml files with hardcoded paths,
> which was not so nice.
> With a similar JAR we can switch the demo to "Development" project stage:
> * tobago-config-dev
> using mvn -Pdev
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
