[
https://issues.jboss.org/browse/RFPL-3665?page=com.atlassian.jira.plugin....
]
Martin Tomasek updated RFPL-3665:
---------------------------------
Description:
# create a new Ant project and deploy it to WildFly 8.1 and Tomcat 7
# create a new Maven project and deploy it to WildFly 8.1 and Tomcat 7
# try to import existing Maven project
# 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 SANPSHOT 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
There are detail information about concrete steps. I stronghly recommended to change order
of steps and swap step 1 with step 2.
# create a new Maven project and deploy it to WildFly 8.1 and Tomcat 7 - Use richfaces
archetype. Archetype will be located here
[
https://repository.jboss.org/nexus/content/groups/staging/archetype-catal...].
Download it and in JDBS Window -> Preferences -> Maven archetypes -> Add Remote
Catalog and enter url of archetype. Then New -> Maven Project -> Show latest version
only must be un select. Filter org.richfaces find 4.5.1.Final or version which you want to
verify. ArtefactId should be richfaces-archetype-simpleapp. Activate jee6 profile if you
want to deploy on Wildfly 8.x, deactivate profile if you want to deploy to Tomcat 7.
Deploy must be done by add applicaton to server. It could be performed via right click on
application server and choose add.
# create a new Ant project and deploy it to WildFly 8.1 and Tomcat 7 - New->JSF
Project. Choose Kickstars without libs. Then open your workspace. From previous project
copy richbean.java, index.xhtml, web.xml and template.xml. In web.xml remove resource
servlet. Navigate to this project and backup current libs. Navigate to your workspace
directory. Ensure that you have deployed previous project on tomcat. go to
.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps where should be app. Locate
lib and copy them to this project lib. Deploy project on tomcat using add button in JDBS
and test it. If works then empty lib folder. Copy libs from backups. Open wildfly 8.x.
directory in standalone there will be war of previous project copy libs from that war to
this new project. Deploy on Wildfly 8.x. using add button. Before retest open and close
your firefox or chrome.
# try to import existing Maven project - importovat si napr showcase a nadeployovats
https://repository.jboss.org/nexus/content/groups/staging/org/richfaces/r...
or version which you want to verify. Download distribution in zip file. Extract it. In
JDBS Import project and import Showcase. If you want to deploy Showcase to tomcat then no
addional action is required just check if there is path to tomcat resource in deployment
assembly. If you want to deploy Showcase on Wildfly then activate profile jbass71 and
ensure that there is path to Wildfly webcontent in deployment assembly.
http://localhost:8080/richfaces-showcase/ - Tomcat
http://localhost:8080/showcase/ - Wildfly
# The last steps has sever sub steps. This steps can be performed when RichFaces are in
maven central repository. Do following:
1) I use latest stable JBDS, e.g. for this release 8.0.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.
was:
# create a new Ant project and deploy it to WildFly 8.1 and Tomcat 7
# create a new Maven project and deploy it to WildFly 8.1 and Tomcat 7
# try to import existing Maven project
# 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 SANPSHOT 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
Test RichFaces with JBDS 8
--------------------------
Key: RFPL-3665
URL:
https://issues.jboss.org/browse/RFPL-3665
Project: RichFaces Planning
Issue Type: Sub-task
Components: QE
Reporter: Pavol Pitonak
Assignee: Martin Tomasek
Fix For: 4.5.1.Final
# create a new Ant project and deploy it to WildFly 8.1 and Tomcat 7
# create a new Maven project and deploy it to WildFly 8.1 and Tomcat 7
# try to import existing Maven project
# 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 SANPSHOT 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
There are detail information about concrete steps. I stronghly recommended to change
order of steps and swap step 1 with step 2.
# create a new Maven project and deploy it to WildFly 8.1 and Tomcat 7 - Use richfaces
archetype. Archetype will be located here
[
https://repository.jboss.org/nexus/content/groups/staging/archetype-catal...].
Download it and in JDBS Window -> Preferences -> Maven archetypes -> Add Remote
Catalog and enter url of archetype. Then New -> Maven Project -> Show latest version
only must be un select. Filter org.richfaces find 4.5.1.Final or version which you want to
verify. ArtefactId should be richfaces-archetype-simpleapp. Activate jee6 profile if you
want to deploy on Wildfly 8.x, deactivate profile if you want to deploy to Tomcat 7.
Deploy must be done by add applicaton to server. It could be performed via right click on
application server and choose add.
# create a new Ant project and deploy it to WildFly 8.1 and Tomcat 7 - New->JSF
Project. Choose Kickstars without libs. Then open your workspace. From previous project
copy richbean.java, index.xhtml, web.xml and template.xml. In web.xml remove resource
servlet. Navigate to this project and backup current libs. Navigate to your workspace
directory. Ensure that you have deployed previous project on tomcat. go to
.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps where should be app. Locate
lib and copy them to this project lib. Deploy project on tomcat using add button in JDBS
and test it. If works then empty lib folder. Copy libs from backups. Open wildfly 8.x.
directory in standalone there will be war of previous project copy libs from that war to
this new project. Deploy on Wildfly 8.x. using add button. Before retest open and close
your firefox or chrome.
# try to import existing Maven project - importovat si napr showcase a nadeployovats
https://repository.jboss.org/nexus/content/groups/staging/org/richfaces/r...
or version which you want to verify. Download distribution in zip file. Extract it. In
JDBS Import project and import Showcase. If you want to deploy Showcase to tomcat then no
addional action is required just check if there is path to tomcat resource in deployment
assembly. If you want to deploy Showcase on Wildfly then activate profile jbass71 and
ensure that there is path to Wildfly webcontent in deployment assembly.
http://localhost:8080/richfaces-showcase/ - Tomcat
http://localhost:8080/showcase/ - Wildfly
# The last steps has sever sub steps. This steps can be performed when RichFaces are in
maven central repository. Do following:
1) I use latest stable JBDS, e.g. for this release 8.0.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.8#6338)