[
https://issues.jboss.org/browse/JBIDE-10594?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10594 at 1/6/12 10:02 AM:
-------------------------------------------------------------------
So far I believe that things are not working on OpenShift because the gwt project depends
on
* gwt-user.jar
* validation-api.jar.
These 2 jars are added to the project by a special GWT SDK classpath container,
they're not present in the project itself.
!gwt-sdk-classpath-container.png!
The local deployer traverses the classpath containers, too and includes these jars in the
deployment artifact. Deploying to a local as7 works because these classpath entries are
included.
The OpenShift deployer simply commits the files that are within the repo and these 2 jars
are not within the repo and wont make it to the PaaS.
was (Author: adietish):
So far I believe that things are not working on OpenShift because the gwt project
depends on
* gwt-user.jar
* validation-api.jar.
These 2 jars are added to the project by a special GWT SDK classpath container,
they're not present in the project itself.
!gwt-sdk-classpath-container.png!
The local deployer traverses the classpath containers, too and includes these jars in the
deployment artifact. The OpenShift deployer simply commits the files that are within the
repo and these 2 jars are not within the repo.
Cannot push GWT project to OpenShift
------------------------------------
Key: JBIDE-10594
URL:
https://issues.jboss.org/browse/JBIDE-10594
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: GWT, openshift
Affects Versions: 3.3.0.M5
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
Attachments: gwt-sdk-classpath-container.png
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira