[JBoss JIRA] (RFPL-3882) Update the release-notes
by Michal Petrov (JIRA)
Michal Petrov created RFPL-3882:
-----------------------------------
Summary: Update the release-notes
Key: RFPL-3882
URL: https://issues.jboss.org/browse/RFPL-3882
Project: RichFaces Planning
Issue Type: Sub-task
Components: release
Affects Versions: 4.5.6
Reporter: Michal Petrov
Assignee: Michal Petrov
Fix For: 4.5.6
Update the release notes in dist/src/main/resources/txt/release-notes.txt. Copy and paste the release notes from the RF jira version for this release.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3878?page=com.atlassian.jira.plugin.... ]
Matej Novotny resolved RFPL-3878.
---------------------------------
Resolution: Done
Upgraded Weld version on master branch.
This will effect versions used in both - Metamer and Showcase.
Furthermore, explicit Weld version is only used in Tomcat containers; WF comes with its own version - see comment above.
> Showcase & Tomcat & Push - Context already active exception
> -----------------------------------------------------------
>
> Key: RFPL-3878
> URL: https://issues.jboss.org/browse/RFPL-3878
> Project: RichFaces Planning
> Issue Type: Bug
> Components: examples
> Affects Versions: 4.5.6
> Environment: Tomcat 8
> Showcase app
> Mojarra
> Reporter: Matej Novotny
> Assignee: Matej Novotny
> Fix For: 4.5.7
>
>
> When running Showcase push tests, there are exceptions in the log. Here is an example of one:
> {code}
> 02:36:37 SEVERE: Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.environment.servlet.Listener
> 02:36:37 java.lang.IllegalStateException: WELD-000335: Context is already active
> 02:36:37 at org.jboss.weld.context.http.LazyHttpConversationContextImpl.activate(LazyHttpConversationContextImpl.java:57)
> 02:36:37 at org.jboss.weld.servlet.ConversationContextActivator.activate(ConversationContextActivator.java:107)
> 02:36:37 at org.jboss.weld.servlet.ConversationContextActivator.activateConversationContext(ConversationContextActivator.java:93)
> 02:36:37 at org.jboss.weld.servlet.HttpContextLifecycle.requestInitialized(HttpContextLifecycle.java:225)
> 02:36:37 at org.jboss.weld.servlet.WeldInitialListener.requestInitialized(WeldInitialListener.java:160)
> 02:36:37 at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestInitialized(ForwardingServletListener.java:42)
> 02:36:37 at org.apache.catalina.core.StandardContext.fireRequestInitEvent(StandardContext.java:5902)
> 02:36:37 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> 02:36:37 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> 02:36:37 at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
> 02:36:37 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
> 02:36:37 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
> 02:36:37 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
> 02:36:37 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
> 02:36:37 at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223)
> 02:36:37 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1517)
> 02:36:37 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1474)
> 02:36:37 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 02:36:37 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 02:36:37 at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> 02:36:37 at java.lang.Thread.run(Thread.java:745)
> {code}
> [Here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...] is a sample of Jenkins job, where there is such exception. Just switch to full log and CTRL+ F for "Context is already active".
> It does not affect the test results - CDI push test still passes (the other one - for UUID - is problematic/unstable because it measures time).
> What I found out so far:
> * Cannot be reproduced with Metamer (neither via automated nor manual way)
> * Only appears when server is started via Arq. (e.g. not manually) meaning this is likely to be a configuration issue. Once started manually, one can do exactly what the test does but never gets the exception.
> * Configs used for Tomcat are:
> ** tomcat-users.xml -> copied over from build resources, does not affect it
> ** arquillian.xml -> tried to temper with settings, changed for those in QA repo (there are slight differences) but to no avail
> ** tried to start tomcat manually with the above settings, but still cannot reproduce it
> * I checked the related WELD issue (335), but that was resolved long ago, we are using 2.2.6 version atm (in all repos)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3878?page=com.atlassian.jira.plugin.... ]
Matej Novotny commented on RFPL-3878:
-------------------------------------
Indeed, that will do the trick, thanks [~jstefek]. I checked this and we use *2.2.6* - managed in {{richfaces/build/pom.xml}}. As for differences between RF and QA repo, I think metamer uses different mechanism for push test (synchronous?) hence this exception will not show. Nevertheless, updating Weld will resolve this and it seems to cause no additional problems.
In order to update Weld and to keep up with version used in WildFly, here is some information:
* WF 8.2 uses 2.2.6
** this version is too low and will cause these exceptions
* WF 9 uses 2.2.12
** its currently in CR2 so its likely to hit Final any time soon
** I think we should stick to version in WF 9
> Showcase & Tomcat & Push - Context already active exception
> -----------------------------------------------------------
>
> Key: RFPL-3878
> URL: https://issues.jboss.org/browse/RFPL-3878
> Project: RichFaces Planning
> Issue Type: Bug
> Components: examples
> Affects Versions: 4.5.6
> Environment: Tomcat 8
> Showcase app
> Mojarra
> Reporter: Matej Novotny
> Assignee: Matej Novotny
> Fix For: 4.5.7
>
>
> When running Showcase push tests, there are exceptions in the log. Here is an example of one:
> {code}
> 02:36:37 SEVERE: Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.environment.servlet.Listener
> 02:36:37 java.lang.IllegalStateException: WELD-000335: Context is already active
> 02:36:37 at org.jboss.weld.context.http.LazyHttpConversationContextImpl.activate(LazyHttpConversationContextImpl.java:57)
> 02:36:37 at org.jboss.weld.servlet.ConversationContextActivator.activate(ConversationContextActivator.java:107)
> 02:36:37 at org.jboss.weld.servlet.ConversationContextActivator.activateConversationContext(ConversationContextActivator.java:93)
> 02:36:37 at org.jboss.weld.servlet.HttpContextLifecycle.requestInitialized(HttpContextLifecycle.java:225)
> 02:36:37 at org.jboss.weld.servlet.WeldInitialListener.requestInitialized(WeldInitialListener.java:160)
> 02:36:37 at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestInitialized(ForwardingServletListener.java:42)
> 02:36:37 at org.apache.catalina.core.StandardContext.fireRequestInitEvent(StandardContext.java:5902)
> 02:36:37 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> 02:36:37 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> 02:36:37 at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
> 02:36:37 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
> 02:36:37 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
> 02:36:37 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
> 02:36:37 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
> 02:36:37 at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223)
> 02:36:37 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1517)
> 02:36:37 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1474)
> 02:36:37 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 02:36:37 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 02:36:37 at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> 02:36:37 at java.lang.Thread.run(Thread.java:745)
> {code}
> [Here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...] is a sample of Jenkins job, where there is such exception. Just switch to full log and CTRL+ F for "Context is already active".
> It does not affect the test results - CDI push test still passes (the other one - for UUID - is problematic/unstable because it measures time).
> What I found out so far:
> * Cannot be reproduced with Metamer (neither via automated nor manual way)
> * Only appears when server is started via Arq. (e.g. not manually) meaning this is likely to be a configuration issue. Once started manually, one can do exactly what the test does but never gets the exception.
> * Configs used for Tomcat are:
> ** tomcat-users.xml -> copied over from build resources, does not affect it
> ** arquillian.xml -> tried to temper with settings, changed for those in QA repo (there are slight differences) but to no avail
> ** tried to start tomcat manually with the above settings, but still cannot reproduce it
> * I checked the related WELD issue (335), but that was resolved long ago, we are using 2.2.6 version atm (in all repos)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3878?page=com.atlassian.jira.plugin.... ]
Matej Novotny updated RFPL-3878:
--------------------------------
Fix Version/s: 4.5.7
> Showcase & Tomcat & Push - Context already active exception
> -----------------------------------------------------------
>
> Key: RFPL-3878
> URL: https://issues.jboss.org/browse/RFPL-3878
> Project: RichFaces Planning
> Issue Type: Bug
> Components: examples
> Affects Versions: 4.5.6
> Environment: Tomcat 8
> Showcase app
> Mojarra
> Reporter: Matej Novotny
> Assignee: Matej Novotny
> Fix For: 4.5.7
>
>
> When running Showcase push tests, there are exceptions in the log. Here is an example of one:
> {code}
> 02:36:37 SEVERE: Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.environment.servlet.Listener
> 02:36:37 java.lang.IllegalStateException: WELD-000335: Context is already active
> 02:36:37 at org.jboss.weld.context.http.LazyHttpConversationContextImpl.activate(LazyHttpConversationContextImpl.java:57)
> 02:36:37 at org.jboss.weld.servlet.ConversationContextActivator.activate(ConversationContextActivator.java:107)
> 02:36:37 at org.jboss.weld.servlet.ConversationContextActivator.activateConversationContext(ConversationContextActivator.java:93)
> 02:36:37 at org.jboss.weld.servlet.HttpContextLifecycle.requestInitialized(HttpContextLifecycle.java:225)
> 02:36:37 at org.jboss.weld.servlet.WeldInitialListener.requestInitialized(WeldInitialListener.java:160)
> 02:36:37 at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestInitialized(ForwardingServletListener.java:42)
> 02:36:37 at org.apache.catalina.core.StandardContext.fireRequestInitEvent(StandardContext.java:5902)
> 02:36:37 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> 02:36:37 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> 02:36:37 at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
> 02:36:37 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
> 02:36:37 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
> 02:36:37 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
> 02:36:37 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
> 02:36:37 at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223)
> 02:36:37 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1517)
> 02:36:37 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1474)
> 02:36:37 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 02:36:37 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 02:36:37 at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> 02:36:37 at java.lang.Thread.run(Thread.java:745)
> {code}
> [Here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...] is a sample of Jenkins job, where there is such exception. Just switch to full log and CTRL+ F for "Context is already active".
> It does not affect the test results - CDI push test still passes (the other one - for UUID - is problematic/unstable because it measures time).
> What I found out so far:
> * Cannot be reproduced with Metamer (neither via automated nor manual way)
> * Only appears when server is started via Arq. (e.g. not manually) meaning this is likely to be a configuration issue. Once started manually, one can do exactly what the test does but never gets the exception.
> * Configs used for Tomcat are:
> ** tomcat-users.xml -> copied over from build resources, does not affect it
> ** arquillian.xml -> tried to temper with settings, changed for those in QA repo (there are slight differences) but to no avail
> ** tried to start tomcat manually with the above settings, but still cannot reproduce it
> * I checked the related WELD issue (335), but that was resolved long ago, we are using 2.2.6 version atm (in all repos)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (RFPL-3878) Showcase & Tomcat & Push - Context already active exception
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3878?page=com.atlassian.jira.plugin.... ]
Matej Novotny reassigned RFPL-3878:
-----------------------------------
Assignee: Matej Novotny
> Showcase & Tomcat & Push - Context already active exception
> -----------------------------------------------------------
>
> Key: RFPL-3878
> URL: https://issues.jboss.org/browse/RFPL-3878
> Project: RichFaces Planning
> Issue Type: Bug
> Components: examples
> Affects Versions: 4.5.6
> Environment: Tomcat 8
> Showcase app
> Mojarra
> Reporter: Matej Novotny
> Assignee: Matej Novotny
> Fix For: 4.5.7
>
>
> When running Showcase push tests, there are exceptions in the log. Here is an example of one:
> {code}
> 02:36:37 SEVERE: Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.environment.servlet.Listener
> 02:36:37 java.lang.IllegalStateException: WELD-000335: Context is already active
> 02:36:37 at org.jboss.weld.context.http.LazyHttpConversationContextImpl.activate(LazyHttpConversationContextImpl.java:57)
> 02:36:37 at org.jboss.weld.servlet.ConversationContextActivator.activate(ConversationContextActivator.java:107)
> 02:36:37 at org.jboss.weld.servlet.ConversationContextActivator.activateConversationContext(ConversationContextActivator.java:93)
> 02:36:37 at org.jboss.weld.servlet.HttpContextLifecycle.requestInitialized(HttpContextLifecycle.java:225)
> 02:36:37 at org.jboss.weld.servlet.WeldInitialListener.requestInitialized(WeldInitialListener.java:160)
> 02:36:37 at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.requestInitialized(ForwardingServletListener.java:42)
> 02:36:37 at org.apache.catalina.core.StandardContext.fireRequestInitEvent(StandardContext.java:5902)
> 02:36:37 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> 02:36:37 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
> 02:36:37 at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
> 02:36:37 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
> 02:36:37 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
> 02:36:37 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
> 02:36:37 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
> 02:36:37 at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223)
> 02:36:37 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1517)
> 02:36:37 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1474)
> 02:36:37 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 02:36:37 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 02:36:37 at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> 02:36:37 at java.lang.Thread.run(Thread.java:745)
> {code}
> [Here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...] is a sample of Jenkins job, where there is such exception. Just switch to full log and CTRL+ F for "Context is already active".
> It does not affect the test results - CDI push test still passes (the other one - for UUID - is problematic/unstable because it measures time).
> What I found out so far:
> * Cannot be reproduced with Metamer (neither via automated nor manual way)
> * Only appears when server is started via Arq. (e.g. not manually) meaning this is likely to be a configuration issue. Once started manually, one can do exactly what the test does but never gets the exception.
> * Configs used for Tomcat are:
> ** tomcat-users.xml -> copied over from build resources, does not affect it
> ** arquillian.xml -> tried to temper with settings, changed for those in QA repo (there are slight differences) but to no avail
> ** tried to start tomcat manually with the above settings, but still cannot reproduce it
> * I checked the related WELD issue (335), but that was resolved long ago, we are using 2.2.6 version atm (in all repos)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (RFPL-3873) Test RichFaces with JBDS 8.1.0
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3873?page=com.atlassian.jira.plugin.... ]
Matej Novotny resolved RFPL-3873.
---------------------------------
Resolution: Done
This issue got a bit lost in time and space after the release (e.g. sorry for the delay). Nevertheless I finished it now - everything works just fine.
> Test RichFaces with JBDS 8.1.0
> ------------------------------
>
> Key: RFPL-3873
> URL: https://issues.jboss.org/browse/RFPL-3873
> Project: RichFaces Planning
> Issue Type: Sub-task
> Components: QE
> Reporter: Pavol Pitonak
> Assignee: Matej Novotny
> Fix For: 4.5.6
>
>
> *In case of any changes and/or inaccuracy be sure to update this description.*
> # create a new Maven project and deploy it to WildFly 8.2 and Tomcat 8
> #* File -> New -> Other
> #* Select {{Maven Project}}
> #* Once prompted to choose archetype, add new repository to Catalog
> #** As address you are going to need the staging repo URL
> #* Choose simple-app from the newly added repo (e.g. with correct RF version)
> #* Test with Tomcat (no changes needed)
> #* Test with Wildfly
> #** Need to activate {{jee6}} profile
> # create a new Ant project and deploy it to WildFly 8.2 and Tomcat 8
> #* File -> New -> Other
> #* Select {{JSF Project}} & when prompted choose 'Kickstars without libs'
> #* Don't forget to use JSF 2.2
> #* Finish the wizard, you can install Wildfly and Tomcat servers at this point
> #* Get RF Distribution (from staged repo in ZIP format) and add JAR files (with RF and mandatory libs) to this new project
> #* Download javax.faces JAR (or myfaces) => this is *only* needed for Tomcat so add only if you wish to deploy app there
> #* As a template you can use RF simple-app archetype and copy following things to ant project, if possible preserve the structure:
> #** RichBean.java
> #** index.xhtml
> #** templates (whole folder)
> #* Add following to the web.xml (it only maps index page to localhost:8080/app_name)
> #** {code}<welcome-file-list>
> <welcome-file>faces/index.xhtml</welcome-file>
> </welcome-file-list>{code}
> #* At this point, app should be buildable and deployable and accessible at {{localhost:8080/app_name}}
> #* Test on Wildfly
> #* Add JSF implementation JAR to libraries, rebuild and test on Tomcat
> #** Based on JSF impl chosen you might come across following bug: https://java.net/jira/browse/JAVASERVERFACES-3400
> #** Workaround is to change RichBean from {{ViewScoped}} to {{SessionScoped}}
> # Try to import existing Maven project
> #* Make use of Showcase in RF distribution ZIP and import that
> #* To deploy with Tomcat no additional settings is needed
> #* To deploy with Wildfly tou need to activate {{jbas71 profile}}
> # create new project from JBoss Central
> add 4.
> According to the RFPL-2204 it should be verified that the project can be generated only from Maven Central, steps to do that:
> In addition to this, a manual verification of the archetype in JBoss tools is required. Steps to test a SNAPSHOT of the archetype in JBoss tools are as follows:
> (03:05:35 PM) Snjeza: you can create project example user site pointing to whatever project example descriptor you want
> (03:06:09 PM) bleathem: Snjeza: how do you do that?
> (03:09:12 PM) Snjeza: bleathem: Call Window>Preferences>JBoss Tools>Project Examples and click the Add button. Project example xml file can be in your local file system
> (03:09:53 PM) bleathem: Snjeza: and how do I make a project example xml file? Can I just copy one from somehwere else?
> (03:15:10 PM) Snjeza: bleathem: you can copy the following http://download.jboss.org/jbosstools/examples/project-examples-shared-3.3... and change the version of your richfaces archetype
> (03:33:58 PM) Snjeza: bleathem: You have to check the Show experimental sites checkbox if you want user sites to be shown
> *The last step has sever substeps. This steps can be performed when RichFaces are in maven central repository. Do the following:*
> 1) I use latest stable JBDS, e.g. for this release *8.1.0* downloaded from this site https://www.jboss.org/products/devstudio/download/
> 2) Download particular project-examples-shared-VERSION.xml from this site. I download the file with the biggest version number. http://download.jboss.org/jbosstools/examples/
> 4) Alter the project-examples-shared-VERSION.xml in this way
> comment lines <stacksId>richfaces-archetype-kitchensink</stacksId> and <stacksType>richfaces-kitchensink</stacksType>
> un-comment lines which contain comment: unnecessary when a stacksId is used (only for richfaces part).
> change the version of the richfaces-archetype-kitchensink to the released one, e.g. for this release 4.5.0.Beta1
> save it
> 5) In JBDS, Preferences --> JBoss Tools --> Project Examples --> add new site, which points to the edited .xml file.
> 6) Shut down JBDS
> in your local ~/.m2/settings.xml turn off all JBoss repositories (or in other global settings). So Any project will be built only from Maven central repositories.
> Remove all richfaces artifacts from your local repository, so they will be downloaded when necessary.
> 7) Start JBDS.
> 8) In JBoss Central (the start page), click on the Project Exampels Wizard, located next to Start from sample header
> 9) Check show experimental sites
> 10) From select box choose your site.
> 11) Create RichFaces project.
> 12) It should download artifacts only from Maven Central, and it should be deployable. Test it only on Wildfly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months