February 2014 - jbosstools-issues

[JBoss JIRA] (JBTIS-245) Please update JBTIS TP dependencies to Luna Alpha1

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-245: -------------------------------- Summary: Please update JBTIS TP dependencies to Luna Alpha1 Key: JBTIS-245 URL: https://issues.jboss.org/browse/JBTIS-245 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, savara, switchyard, teiid Reporter: Paul Leacu Assignee: Paul Leacu Greetings - welcome to Luna! An Alpha1 version of the Eclipse Luna based JBTIS TP is now available in nexus [1]. It's also available here [2] and an integration build of the current Luna JBTIS is available here [3]. I'm still working on dates but if we could get a first cut at the scope involved with upgrading that would help planning this thing immensely. There is SpringIDE and graphiti changes among others. Thanks! [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... [2] http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Al... [3] http://download.jboss.org/jbosstools/updates/integration/luna/integration... -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16579) Warning " Please select a Hybrid Mobile Engine " is displayed always

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16579?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16579: --------------------------------- Assignee: Gorkem Ercan > Warning " Please select a Hybrid Mobile Engine " is displayed always > -------------------------------------------------------------------- > > Key: JBIDE-16579 > URL: https://issues.jboss.org/browse/JBIDE-16579 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Alpha2 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > 1. Open New Hybrid Mobile project dialog > 2. Fill proper data on first page and go to page with Cordova engines > ASSERT: Warning " Please select a Hybrid Mobile Engine " is displayed > 3. Select Cordova Engine > ERROR: Warning " Please select a Hybrid Mobile Engine " is displayed -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16579) Warning " Please select a Hybrid Mobile Engine " is displayed always

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16579?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-16579. ---------------------------------- Resolution: Done > Warning " Please select a Hybrid Mobile Engine " is displayed always > -------------------------------------------------------------------- > > Key: JBIDE-16579 > URL: https://issues.jboss.org/browse/JBIDE-16579 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Alpha2 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > 1. Open New Hybrid Mobile project dialog > 2. Fill proper data on first page and go to page with Cordova engines > ASSERT: Warning " Please select a Hybrid Mobile Engine " is displayed > 3. Select Cordova Engine > ERROR: Warning " Please select a Hybrid Mobile Engine " is displayed -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13312) Unnecessary code generated in web.xml

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13312?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13312: ------------------------------------------- This should be handled by the code changes done in JBIDE-13309 pending a code review. > Unnecessary code generated in web.xml > ------------------------------------- > > Key: JBIDE-13312 > URL: https://issues.jboss.org/browse/JBIDE-13312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.0.0.Final > Reporter: Pete Muir > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > > The new RESTful Webservice wizard is generating a load of unnecessary stuff in the endpoint > {code} > <servlet> > <servlet-name>Resteasy</servlet-name> > <servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher</servlet-class> > </servlet> > <servlet-mapping> > <servlet-name>Resteasy</servlet-name> > <url-pattern>/*</url-pattern> > </servlet-mapping> > <context-param> > <param-name>javax.ws.rs.Application</param-name> > <param-value>org.jboss.samples.rs.webservices.MyRESTApplication</param-value> > </context-param> > <listener> > <listener-class>org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap</listener-class> > </listener> > {code} > None of this is needed -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13310) New RESTful Webservice wizard should generate empty Application impl

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13310?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13310: ------------------------------------------- This should be handled by the code changes done in JBIDE-13309 pending a code review. > New RESTful Webservice wizard should generate empty Application impl > -------------------------------------------------------------------- > > Key: JBIDE-13310 > URL: https://issues.jboss.org/browse/JBIDE-13310 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.0.0.Final > Reporter: Pete Muir > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > > Implementing the various methods is not necessary, and actually causes odd behavior sometimes. The class body should be empty. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13309) New Restful Webservice wizard shouldn't change web.xml by default

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13309?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13309: ------------------------------------------- [~xcoulon] Can you review the changes if you get a chance? I know it looks like a lot of changes, but it's really only a few lines... 1) JBossRSGenerateWizard.java - the default for "updateWebXML" went from true to false. 2) JBossRSGenerateWizardPage.java - I added "name.setEnabled(updateWebXML.getSelection());" at line 142 so the name box would be initially set to the correct state. 3) RSServiceSampleCreationCommand.java - createRESTApplicationClass has changed to reduce the code as suggested by Pete Muir in this JIRA. The rest of the changes github is seeing are due to the Git tooling in Eclipse doing a wholesale file change for some reason - but the rest is the same. > New Restful Webservice wizard shouldn't change web.xml by default > ----------------------------------------------------------------- > > Key: JBIDE-13309 > URL: https://issues.jboss.org/browse/JBIDE-13309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.0.0.Final > Reporter: Pete Muir > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > > We recommend the class-style activation of JAX-RS applications > {code} > /** > * A class extending {@link Application} and annotated with @ApplicationPath is the Java EE 6 > * "no XML" approach to activating JAX-RS. > * > * <p> > * Resources are served relative to the servlet path specified in the {@link ApplicationPath} > * annotation. > * </p> > */ > @ApplicationPath("/rest") > public class JaxRsActivator extends Application { > /* class body intentionally left blank */ > } > {code} > JBDS should offer this as the default approach. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16550) Preferences for Engines

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16550?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-16550: ------------------------------------ Assignee: Gorkem Ercan > Preferences for Engines > ----------------------- > > Key: JBIDE-16550 > URL: https://issues.jboss.org/browse/JBIDE-16550 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > > Add an engines node to the hybrid mobile preferences that enables download and install of new engines, -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16640) Avoid bumping dependencies versions unless it is required

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16640?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-16640: --------------------------------------- sr-latest is good, but AIR we require build against min TP which is Kepler R. > Avoid bumping dependencies versions unless it is required > --------------------------------------------------------- > > Key: JBIDE-16640 > URL: https://issues.jboss.org/browse/JBIDE-16640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.2.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > > Problem occurred when trying to install LiveReload 1.2.0.Alpha2 on Kepler: > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) > Software currently installed: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) > Only one of the following can be installed at once: > Browser Support 3.4.100.v20130527-1656 (org.eclipse.ui.browser 3.4.100.v20130527-1656) > Browser Support 3.4.200.v20131003-1453 (org.eclipse.ui.browser 3.4.200.v20131003-1453) > Cannot satisfy dependency: > From: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) > To: org.eclipse.epp.package.standard.feature.feature.group [2.0.1.20130919-0803] > Cannot satisfy dependency: > From: Eclipse Standard/SDK Feature 2.0.1.20130919-0803 (org.eclipse.epp.package.standard.feature.feature.group 2.0.1.20130919-0803) > To: org.eclipse.platform.feature.group [4.3.1.v20130911-1000] > Cannot satisfy dependency: > From: Eclipse Platform 4.3.1.v20130911-1000 (org.eclipse.platform.feature.group 4.3.1.v20130911-1000) > To: org.eclipse.ui.browser [3.4.100.v20130527-1656] > Cannot satisfy dependency: > From: JBoss Tools LiveReload Core 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.core 1.2.0.Alpha2-v20140207-2102-B6) > To: bundle org.eclipse.ui.browser 3.4.200 > Cannot satisfy dependency: > From: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) > To: org.jboss.tools.livereload.core [1.2.0.Alpha2-v20140207-2102-B6] > {code} > AFAIR, there was no real need to bump org.eclipse.ui.browser from 3.4.100 to 3.4.200. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16640) Avoid bumping dependencies versions unless it is required

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16640?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16640: ------------------------------------- ASTools does not use any api not available in kepler sr-latest. All source imports without error into kepler dev env. > Avoid bumping dependencies versions unless it is required > --------------------------------------------------------- > > Key: JBIDE-16640 > URL: https://issues.jboss.org/browse/JBIDE-16640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.2.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > > Problem occurred when trying to install LiveReload 1.2.0.Alpha2 on Kepler: > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) > Software currently installed: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) > Only one of the following can be installed at once: > Browser Support 3.4.100.v20130527-1656 (org.eclipse.ui.browser 3.4.100.v20130527-1656) > Browser Support 3.4.200.v20131003-1453 (org.eclipse.ui.browser 3.4.200.v20131003-1453) > Cannot satisfy dependency: > From: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) > To: org.eclipse.epp.package.standard.feature.feature.group [2.0.1.20130919-0803] > Cannot satisfy dependency: > From: Eclipse Standard/SDK Feature 2.0.1.20130919-0803 (org.eclipse.epp.package.standard.feature.feature.group 2.0.1.20130919-0803) > To: org.eclipse.platform.feature.group [4.3.1.v20130911-1000] > Cannot satisfy dependency: > From: Eclipse Platform 4.3.1.v20130911-1000 (org.eclipse.platform.feature.group 4.3.1.v20130911-1000) > To: org.eclipse.ui.browser [3.4.100.v20130527-1656] > Cannot satisfy dependency: > From: JBoss Tools LiveReload Core 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.core 1.2.0.Alpha2-v20140207-2102-B6) > To: bundle org.eclipse.ui.browser 3.4.200 > Cannot satisfy dependency: > From: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) > To: org.jboss.tools.livereload.core [1.2.0.Alpha2-v20140207-2102-B6] > {code} > AFAIR, there was no real need to bump org.eclipse.ui.browser from 3.4.100 to 3.4.200. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16640) Avoid bumping dependencies versions unless it is required

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16640?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-16640: --------------------------------------- Try to build it against TP for Kepler SR0, stop believing and say it is or it is not uses new API. > Avoid bumping dependencies versions unless it is required > --------------------------------------------------------- > > Key: JBIDE-16640 > URL: https://issues.jboss.org/browse/JBIDE-16640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.2.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > > Problem occurred when trying to install LiveReload 1.2.0.Alpha2 on Kepler: > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) > Software currently installed: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) > Only one of the following can be installed at once: > Browser Support 3.4.100.v20130527-1656 (org.eclipse.ui.browser 3.4.100.v20130527-1656) > Browser Support 3.4.200.v20131003-1453 (org.eclipse.ui.browser 3.4.200.v20131003-1453) > Cannot satisfy dependency: > From: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) > To: org.eclipse.epp.package.standard.feature.feature.group [2.0.1.20130919-0803] > Cannot satisfy dependency: > From: Eclipse Standard/SDK Feature 2.0.1.20130919-0803 (org.eclipse.epp.package.standard.feature.feature.group 2.0.1.20130919-0803) > To: org.eclipse.platform.feature.group [4.3.1.v20130911-1000] > Cannot satisfy dependency: > From: Eclipse Platform 4.3.1.v20130911-1000 (org.eclipse.platform.feature.group 4.3.1.v20130911-1000) > To: org.eclipse.ui.browser [3.4.100.v20130527-1656] > Cannot satisfy dependency: > From: JBoss Tools LiveReload Core 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.core 1.2.0.Alpha2-v20140207-2102-B6) > To: bundle org.eclipse.ui.browser 3.4.200 > Cannot satisfy dependency: > From: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) > To: org.jboss.tools.livereload.core [1.2.0.Alpha2-v20140207-2102-B6] > {code} > AFAIR, there was no real need to bump org.eclipse.ui.browser from 3.4.100 to 3.4.200. -- 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

12 years, 1 month

1
0
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 February 2014