[JBoss JIRA] (JBIDE-10055) Remove openshift plugins, tests, sources, features from ~/trunk/as/
by Nick Boldt (Created) (JIRA)
Remove openshift plugins, tests, sources, features from ~/trunk/as/
-------------------------------------------------------------------
Key: JBIDE-10055
URL: https://issues.jboss.org/browse/JBIDE-10055
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
Remove openshift plugins, tests, sources, features from ~/trunk/as/
Remove all TODO markers in pom.xml, site.xml, etc. pertaining to removing stuff that's now in ~/trunk/openshift/
--
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
13 years, 10 months
[JBoss JIRA] (JBIDE-11224) Ensure GWT tooling and m2e-wtp are configured for same output directory
by Jonathan Fuerth (JIRA)
Jonathan Fuerth created JBIDE-11224:
---------------------------------------
Summary: Ensure GWT tooling and m2e-wtp are configured for same output directory
Key: JBIDE-11224
URL: https://issues.jboss.org/browse/JBIDE-11224
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Reporter: Jonathan Fuerth
The output location for the GWT compiler differs when it is run through Maven vs. when it is run through the Google Eclipse plugin. What we want is for the Google Eclipse Plugin to target the same webapp directory as m2e-wtp and maven-gwt-plugin do.
Specific example of the issue:
1. Create a project from the Errai Kitchen Sink quickstart (you can create it with mvn archetype:generate -DarchetypeGroupId=org.jboss.errai.archetypes -DarchetypeArtifactId=kitchensink-quickstart -Dversion=2.0.Beta1)
2. From within Eclipse, run maven package on the project. Notice the GWT compiler writes its output to src/main/webapp/KitchenSink/**. This is good, because WTP is configured to use src/main/webapp.
3. At this point, you can run as web application on AS 7.1, and it will work. But this is GWT production mode, so changes made to client side code will not show up until the GWT compiler gets run again.
4. Try to launch Dev Mode (Run As -> Web Application Running on an External Server). Note the error message (the directory the GWT tooling was looking for doesn't exist) **This demonstrates the configuration problem this issue describes. GWT Dev Mode within Eclipse should be looking for the webapp in the same place as gwt-maven-plugin (and WTP)**
5. Run the GWT compiler from within eclipse (Google -> GWT Compile Project) **This is a workaround. It should produce the same javascript output as gwt-maven-plugin did**
6. Now launch Dev Mode again (Run As -> Web Application Running on an External Server). It works this time, because of the second copy of the javascript output.
Note: there's a video of this entire process, including the workarounds, at http://www.youtube.com/watch?v=KaLjOjBPVp0
--
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
13 years, 10 months
[JBoss JIRA] Created: (JBDS-1839) JAX-RS maven integration plugin is missing in extra site
by Libor Zoubek (JIRA)
JAX-RS maven integration plugin is missing in extra site
--------------------------------------------------------
Key: JBDS-1839
URL: https://issues.jboss.org/browse/JBDS-1839
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: 3rdPartyCertification, maven
Affects Versions: 5.0.0.M3
Reporter: Libor Zoubek
Fix For: 5.0.0.M4
I was verifying JBIDE-9290 on JBDS with m2e. JAX-RS configurator is missing there. It will definitely make sence to include this plugin when jax-rs tooling becomes part of JBDS. But it might make sense to include it before.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months