[jbosstools-issues] [JBoss JIRA] (JBIDE-13168) Wrong URLs in central examples
[
https://issues.jboss.org/browse/JBIDE-13168?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-13168:
-------------------------------------
As a temporary measure, I fixed the default project names for GWT, RF, HTML5 so they match
with the context root described in the readme.
Can't do anything for the multi-ee6 project.
Proper fix require all archetypes to generate the context root dynamically in readme.md
As for the eap6 doc link, either we can get the short url (or current landing page) to be
redirected to the actual doc page, or we need to change all archetypes (quickstarts too?)
to use a different url.
Wrong URLs in central examples
------------------------------
Key: JBIDE-13168
URL: https://issues.jboss.org/browse/JBIDE-13168
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, project-examples
Affects Versions: 4.0.0.CR1
Reporter: Rastislav Wagner
Assignee: Fred Bricon
Labels: respin-b
Fix For: 4.0.0.CR1
According to readme.md in project examples:
*GWT*
{code}This will deploy `target/jboss-as-kitchensink-errai.war`.
The application will be running at the following URL
<http://localhost:8080/jboss-as-kitchensink-errai/>.{code}
should be
{code}target/jboss-gwt-webapp.war
http://localhost:8080/jboss-gwt-webapp/{code}
*HTML5*
{code}The client application will be running at the following URL
<http://localhost:8080/jboss-as-kitchensink-html5-mobile/>.{code}
should be
{code}http://localhost:8080/jboss-html5-webapp{code}
*RICHFACES*
{code}http://localhost:8080/jboss-as-kitchensink-rf/{code}
should be
{code}http://localhost:8080/jboss-richfaces-webapp{code}
*JAVAEE6-MULTI*
{code}http://localhost:8080/jboss-javaee6-multi{code}
should be
{code}http://localhost:8080/jboss-javaee6-multi-web{code}
Also springmvc, javaee6-webapp/javaee6-mult,html5 index.html contains wrong URL
{code}http://red.ht/jbeap-6-docs{code} which points to 404.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira