March 2012 - jbosstools-issues - Jboss List Archives

[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

6
6
0 / 0

[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

7
12
0 / 0

[JBoss JIRA] (JBIDE-10243) Improve cheatsheets

by Snjezana Peco (Created) (JIRA)

Improve cheatsheets ------------------- Key: JBIDE-10243 URL: https://issues.jboss.org/browse/JBIDE-10243 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.3.0.M4 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M5 If a created project contains the cheatsheet.xml file, the Project Example engine should run the cheat sheet using that file. If a created project contains readme.html, the Project Example engine should open it in a browser. -- 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

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2258) Provide a plugin for JAX-RS resp. Resteasy

by Juergen Zimmermann (JIRA)

Provide a plugin for JAX-RS resp. Resteasy ------------------------------------------ Key: JBIDE-2258 URL: http://jira.jboss.com/jira/browse/JBIDE-2258 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1.0.CR1 Reporter: Juergen Zimmermann NetBeans 6.1 provides a plugin for Sun's Jersey being the reference implementation of JAX-RS (= Java API for RESTful Web Services): https://jersey.dev.java.net/servlets/ReadMsg?list=users&msgNo=1293 Resteasy is the upcoming implementation of JAX-RS for JBoss -- see http://wiki.jboss.org/wiki/RESTeasyJAXRS It would be nice to also have a JAX-RS plugin for Resteasy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
12
0 / 0

[JBoss JIRA] (JBIDE-10851) title of application configuration is misleading

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10851: ------------------------------------------- Summary: title of application configuration is misleading Key: JBIDE-10851 URL: https://issues.jboss.org/browse/JBIDE-10851 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Environment: Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 the page have changed meaning so title/description should get updated Here is my suggestion: "Application Configuration" -> "Setup OpenShift Application" "Select an existing or create a new OpenShift Express Application." -- 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

4
6
0 / 0

[JBoss JIRA] (JBIDE-11141) Set the "location" field to the existing project location in the import wizard

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-11141: ------------------------------------- Summary: Set the "location" field to the existing project location in the import wizard Key: JBIDE-11141 URL: https://issues.jboss.org/browse/JBIDE-11141 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.CR1 When importing an existing application to merge with an existing project, the "Location" field in the cloning settings should be set to the existing project location, not the default value. -- 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

4
6
0 / 0

[JBoss JIRA] (JBIDE-11221) Order cartridges and application types alphabetically

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11221: --------------------------------------- Summary: Order cartridges and application types alphabetically Key: JBIDE-11221 URL: https://issues.jboss.org/browse/JBIDE-11221 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Lucia Jelinkova Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 The embedded cartridges and application types seem to be in no particular order (I've got feeling that it actually changes the order from time to time). Could you order them alphabetically? # in wizard the combobox with application type # in wizard the table with embeddable cartridges # in wizard the list of OpenShift applications # in OpenShift Console view the during the embedding of new cartridges the list of cartridges -- 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

6
6
0 / 0

[JBoss JIRA] (JBIDE-11235) Recognize EAP/WFK maven repositories and add them into ~/.m2/settings.xml

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11235: ------------------------------------------- Summary: Recognize EAP/WFK maven repositories and add them into ~/.m2/settings.xml Key: JBIDE-11235 URL: https://issues.jboss.org/browse/JBIDE-11235 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime detection, maven Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Fix For: 3.3.0.Beta2, 3.3.0.CR1 Not sure if this should be in runtime detection or better done as a quickfix on missing dependencies. But being able to scan for/recognize local on disk maven repositories and provide a quickfix to change settings.xml to include the basic xml setup for having them enabled would be good. -- 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

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-8838) add source feature to JBT components; generate source plugins w/ Tycho

by Nick Boldt (JIRA)

add source feature to JBT components; generate source plugins w/ Tycho ---------------------------------------------------------------------- Key: JBIDE-8838 URL: https://issues.jboss.org/browse/JBIDE-8838 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M2 As per example done in https://bugs.eclipse.org/bugs/show_bug.cgi?id=344515 and http://wiki.eclipse.org/Minerva#Source, the rest of JBT needs source features/plugins. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

8
63
0 / 0

[JBoss JIRA] Created: (JBIDE-9309) Easily adding full JBoss AS source

by arjan tijms (JIRA)

Easily adding full JBoss AS source ---------------------------------- Key: JBIDE-9309 URL: https://issues.jboss.org/browse/JBIDE-9309 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: arjan tijms Assignee: Rob Stryker The JBoss AS server runtime from JBoss tools adds a library container to the classpath of an Eclipse project. This container provides a large amount of jar files that make up JBoss AS itself and the Java EE services it offers. Attaching the source code for this is notoriously difficult. Because it concerns a large amount of jar files, attaching source code for each jar is a rather tedious job. For JBoss AS 5, the fact that the location of jars in the source archive was completely different from the structure exposed in Eclipse or the binary build of JBoss AS, made it very hard to actually locate the correct source jar. Sometimes even names were different, making it even harder. For JBoss AS 6, the source archive does not even contain the source for the majority of the JBoss AS artifacts. Source for 'core functionality' (from the point of view of the Java EE developer), like Servlet and JSF is missing. The user has to hunt the Internet to find the correct source for the correct version that JBoss AS 6 uses. This makes an already tedious job even more tedious. I would like to request functionality where the user can point to a single _jboss-src.xyz_ file that contains all sources. JBoss tools should then automatically attach the right source from the archive to the right jar from the library container. Alternatively the user could point to a maven repository (but this should not make the Eclipse project dependent on maven). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

10
30
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2012