[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-10199: ---------------------------------- Attachment: JBIDE-10199.png Attaching a screenshot of the wizard -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10199: --------------------------------------------- This is why it is almost always better to mark such things as a Warning instead of an Error since it is based on a detection that can and will fail from time to time. I suggest fixing the detection but also make it a warning not an error. -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10199: ---------------------------------------- Fix Version/s: 3.3.0.M5 Priority: Critical (was: Major) Upgrading priority on this issue since the wizard assumes it is targeting EAP5. Which is not the case for most, definitely not AS 7/EAP 6 -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-10199: ------------------------------------------- This patch updates the runtime jar detection routine to actually look for three jars in the project classpath instead. This should support Maven, Glassfish, AS7, AS6, AS5... much more consistently than looking for particular jars in particular locations. It also updates the message that comes back from the jar test to be a warning instead of an error, which allows the wizard to continue despite not finding the jars if the user wishes to do so. -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-10199: -------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-10199: ------------------------------------------- Ok - two questions... 1) As far as the jars go... Should we not add them? Should we add an option to the wizard to add them? What are you looking for here? 2) What's the easiest way to kick off a build via code when the wizard finishes? Can definitely whack something in there. -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10199: --------------------------------------------- as minimum I would have a checkbox (disabled by default) saying something like "[ ] Copy JAX-RS RestEasy Libraries to WEB-INF/lib from the Server" but that just sounds so wrong. -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10199: --------------------------------------------- Well, maybe it was needed for EAP 5 where jax-rs aren't enabled by default? -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10199: --------------------------------------------- runtime directory for EAP is eap/jboss-as leaving the resteasy dir to be at eap/resteasy, i.e. [runtime]/../resteasy that needs checking - correct? I still feel a checkbox is relevant since the user might want to use mvn to get this instead of having to go digg and delete the jars. You could though have the default be enabled or disabled based on which is the most likely (i.e. if runtime does have the jars or classes are already on the classpath of the project don't have the copy the jars flag enabled) -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-10199: -------------------------------------- Attachment: newpatch.txt -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-10199: --------------------------------------- Hi Brian, The simplest manual way is to right-click on the project, then "Configure>Add JAX-RS 1.1 support...". In the related issue (JBIDE-9332), that's part of the scenario to reproduce the bug. -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-10199: ------------------------------------------- Done. Just checked in the tweak. -- 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

[ https://issues.jboss.org/browse/JBIDE-10199?page=com.atlassian.jira.plugi... ] Isaac Rooskov updated JBIDE-10199: ---------------------------------- Release Notes Docs Status: Documented as Resolved Issue Writer: irooskov Release Notes Text: This issue only affected users in the JBoss Developer Studio Early Access program. Users who did not participate in the early access program would not have encountered this issue. Create a Simple Web Service and Create a Sample RESTful Service wizards were not compatible with JBoss Application Server 7. This occurred as the wizards were unable to recognise required JAR files available in the classpath, when JBoss Application Server 7 was specified as the target runtime. To correct this issue the option of adding RESTeasy JARs from the runtime root now exists in the wizards and is enabled or disabled by default depending on the application server chosen. This allows for the wizards to function correctly. An option for the web.xml file to be updated has been added to the Dynamic Web Project wizard for when a user selects to use the facet version of RESTful services in their project. The option is enabled or disabled by default depending on the application server chosen. -- 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