February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-10541) If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10541?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10541: ------------------------------------- Fix Version/s: 4.1.0.Alpha2 (was: 4.1.0.Alpha1) > If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10541 > URL: https://issues.jboss.org/browse/JBIDE-10541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha2 > > > Currently the dialog showing up when committing/pushing is confusing since it says there are no changes which is not correct if comparing to opehsfnit remote repo. > Should make a check against the fetched upstream and see what has changed since that is a fast local operation. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2340) Move jbds.target to JBDS svn

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2340?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-2340: --------------------------------- Fix Version/s: LATER (was: 6.0.x) (was: 7.0.0.Alpha1) > Move jbds.target to JBDS svn > ---------------------------- > > Key: JBDS-2340 > URL: https://issues.jboss.org/browse/JBDS-2340 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build > Reporter: Mickael Istria > Assignee: Nick Boldt > Labels: f2f2012 > Fix For: LATER > > > The jbds.target file should reside in JBDS SVN. > It must contain what we want in JBDS: latest versions of all 3rd-party dependencies. > No Birt, No GWT. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13003) No support for inheritance in JAX-RS API scan

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13003?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-13003: ---------------------------------- Fix Version/s: 4.1.0.Alpha2 (was: 4.1.x) > No support for inheritance in JAX-RS API scan > --------------------------------------------- > > Key: JBIDE-13003 > URL: https://issues.jboss.org/browse/JBIDE-13003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.0.0.Alpha2 > Reporter: Ron Ratovsky > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha2 > > > Assume: > class BaseRest { > @POST > public Response save(Object o) { > .... > } > } > @Path("/url") > class RealRest extends BaseRest {} > The JAX-RS tools won't add a "POST /url" entry to the JAX-RS calls overview. > While not tested (due to another bug) - they may also apply to definitions of @PathParam's in the parent class. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13509) WS Component N&N

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13509?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-13509: ------------------------------------- Assignee: Brian Fitzpatrick (was: Xavier Coulon) Brian, I have nothing about JAX-RS to mention in the N&N for 4.1.0.Alpha1. I'm assigning you this issue in case you have something to write about WS. > WS Component N&N > ---------------- > > Key: JBIDE-13509 > URL: https://issues.jboss.org/browse/JBIDE-13509 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Webservices > Reporter: Alexey Kazakov > Assignee: Brian Fitzpatrick > Fix For: 4.1.0.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13463) Replace eclipse-update-site for aggregator by eclipse-repository

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13463?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13463: ----------------------------------- Fix Version/s: 4.1.0.Alpha2 (was: 4.1.0.Alpha1) > Replace eclipse-update-site for aggregator by eclipse-repository > ---------------------------------------------------------------- > > Key: JBIDE-13463 > URL: https://issues.jboss.org/browse/JBIDE-13463 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > The "eclipse-update-site" packaging type we've been using for aggregate sites is deprecated. Moreover it now shows some limitations (doesn't support pack.gz and other new Tycho stuff) that make it worth migrating to "eclipse-repository". -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2460) replace included p2-director.zip with upstream version from tycho-standalone-p2-director

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2460?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2460: -------------------------------------- For this use-case, it might be better to use the tycho-p2-director:materialize-products goal: http://www.eclipse.org/tycho/sitedocs/tycho-p2/tycho-p2-director-plugin/m... > replace included p2-director.zip with upstream version from tycho-standalone-p2-director > ---------------------------------------------------------------------------------------- > > Key: JBDS-2460 > URL: https://issues.jboss.org/browse/JBDS-2460 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyDependencies, Build, installer > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Alpha2 > > > To build JBDS installer we need p2-director.zip [0], which is 9M and doesn't include sources. Ideally, we could just use something from Eclipse.org at build-time, and COULD include sources. > [0] https://svn.jboss.org/repos/devstudio/trunk/product/installer/p2-director... > I looked at tycho-standalone-p2-director [1,2] but it's only an update site -- it lacks equinox.launcher fragments for the various platforms on which we run. > [1] https://github.com/eclipse/tycho/tree/master/tycho-bundles/tycho-standalo... > [2] http://search.maven.org/remotecontent?filepath=org/eclipse/tycho/tycho-st... > So... maybe we need to do something similar but include the binary bits too, so that we can produce something similar to what's in this zip [3] ? -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13150) When started using "java", Failing Central install shows no UI

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13150?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-13150. ------------------------------------ Resolution: Cannot Reproduce Bug This issue requires Central to be broken. I prefer not breaking Central on purpose to reproduce the issue. In any case, it makes installation test failing (pop-up or not pop-up), so this is a minor issue. Closing. > When started using "java", Failing Central install shows no UI > -------------------------------------------------------------- > > Key: JBIDE-13150 > URL: https://issues.jboss.org/browse/JBIDE-13150 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, testing > Affects Versions: 4.1.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.1.0.Alpha1 > > > This was discovered while trying to debug some Installation Tests. We start Eclipse that way: https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scri... (java -jar ... -product ... -application org.eclipse.swtbot.swtbottestapplication -testProduct ... -testApplication ...). > When running SWTBot to perform tests that install all Software from Central, when those are failing due to bad p2 plan; then there is no pop-up to warn about failing plan. > When starting Eclipse normally, we can see a pop-up telling which "Problems occured". -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) merge contents of coretests and soatests sites into new integrationtests site (was: add missing IUs to coretests and soatests sites)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12974: ---------------------------------------- I'm ok with having shared framework in both sites. An alternative could be to have the SOA-tests site reference the Core-test site (using associateSite in repository-utils Mojo). > merge contents of coretests and soatests sites into new integrationtests site (was: add missing IUs to coretests and soatests sites) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.0.Alpha1 > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip (or at least document the limitations)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2456 at 2/11/13 1:36 AM: ----------------------------------------------------------- IzPack is no longer included in SVN, and can be fetched from http://dist.codehaus.org/izpack/releases/ p2-director.zip should also be replaced by remote fetch but need to find where the zip lives. Closest thing I've found is: http://search.maven.org/remotecontent?filepath=org/eclipse/tycho/tycho-st... which is sourced from: https://github.com/eclipse/tycho/tree/master/tycho-bundles/tycho-standalo... However, it does NOT include an executable (and is missing equinox.launcher.[os-fragments]) so would need to be run from <java> instead of <exec> in product/installer/src/config/install-pack-universal.xml, by calling an existing Eclipse install (or sourcing from the target platform site?) Anyway, by including p2-director.zip in the source zip, one should be able to now build JBDS from the source zip, following the instructions in the root pom.xml. Respinning to include some changes to the way sources are packaged. [~mmurray]: can you attempt to build from source, after unpacking this zip? http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_tr... was (Author: nickboldt): IzPack is no longer included in SVN, and can be fetched from http://dist.codehaus.org/izpack/releases/ p2-director.zip should also be replaced by remote fetch but need to find where the zip lives. Closest thing I've found is: http://search.maven.org/remotecontent?filepath=org/eclipse/tycho/tycho-st... which is sourced from: https://github.com/eclipse/tycho/tree/master/tycho-bundles/tycho-standalo... However, it does NOT include an executable (and is missing equinox.launcher.[os-fragments]) so would need to be run from <java> instead of <exec> in product/installer/src/config/install-pack-universal.xml, by calling an existing Eclipse install (or sourcing from the target platform site?) Anyway, by including p2-director.zip in the source zip, one should be able to now build JBDS from the source zip, following the instructions in the root pom.xml. Respinning to include some changes to the way sources are packaged. However, it seems either my changes aren't being picked up or are being overwritten when built in Jenkins. Will need to investigate why this works locally but not in Jenkins. :( > JBDS should be buildable from source zip (or at least document the limitations) > ------------------------------------------------------------------------------- > > Key: JBDS-2456 > URL: https://issues.jboss.org/browse/JBDS-2456 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.0.GA, 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Alpha2 > > > As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing: > {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote} > It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either). > Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3 -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13149) Central software can't install

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13149?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-13149. ---------------------------------- Fix Version/s: (was: 4.1.x) Resolution: Cannot Reproduce Bug Latest installation tests (from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... ) show that installation of JBT + Central behaves correctly on Kepler M4. > Central software can't install > ------------------------------ > > Key: JBIDE-13149 > URL: https://issues.jboss.org/browse/JBIDE-13149 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Mickael Istria > Assignee: Snjezana Peco > > Spotted by installation tests, while trying to install everything from Central: > {quote} > ontains: Your original request has been modified. > Contains: "Mylyn Context Connector: Eclipse IDE" is already present because other installed software requires it. It will be added to the installed software list. > Contains: "Mylyn Commons" is already present because other installed software requires it. It will be added to the installed software list. > Contains: "Mylyn Context Connector: Java Development" is already present because other installed software requires it. It will be added to the installed software list. > Contains: "JBoss Tools Common - Mylyn" is already installed, so an update will be performed instead. > Contains: "Mylyn Task-Focused Interface" is already present because other installed software requires it. It will be added to the installed software list. > Contains: "Mylyn Task List" is already present because other installed software requires it. It will be added to the installed software list. > Contains: "Mylyn Context Connector: Team Support" is already present because other installed software requires it. It will be added to the installed software list. > Contains: "Google Plugin for Eclipse 4.2" is already present because other installed software requires it. It will be added to the installed software list. > Contains: "Mylyn Tasks Connector: Bugzilla" is already present because other installed software requires it. It will be added to the installed software list. > Contains: Cannot complete the install because of a conflicting dependency. > Contains: Software being installed: JBoss Tools Common - Mylyn 3.4.0.Beta2-v20121114-2253-B23 (org.jboss.tools.common.mylyn.feature.feature.group 3.4.0.Beta2-v20121114-2253-B23) > Contains: Software currently installed: org.jboss.tools.common.mylyn.feature.source.feature.group 3.4.0.Alpha1-v20121123-2241-B69 > Contains: Only one of the following can be installed at once: > Contains: JBoss Tools Common - Mylyn 3.4.0.Beta2-v20121114-2253-B23 (org.jboss.tools.common.mylyn.feature.feature.jar 3.4.0.Beta2-v20121114-2253-B23) > Contains: JBoss Tools Common - Mylyn 3.4.0.Alpha1-v20121123-2241-B69 (org.jboss.tools.common.mylyn.feature.feature.jar 3.4.0.Alpha1-v20121123-2241-B69) > Contains: Cannot satisfy dependency: > Contains: From: JBoss Tools Common - Mylyn 3.4.0.Alpha1-v20121123-2241-B69 (org.jboss.tools.common.mylyn.feature.feature.group 3.4.0.Alpha1-v20121123-2241-B69) > Contains: To: org.jboss.tools.common.mylyn.feature.feature.jar [3.4.0.Alpha1-v20121123-2241-B69] > Contains: Cannot satisfy dependency: > Contains: From: JBoss Tools Common - Mylyn 3.4.0.Beta2-v20121114-2253-B23 (org.jboss.tools.common.mylyn.feature.feature.group 3.4.0.Beta2-v20121114-2253-B23) > Contains: To: org.jboss.tools.common.mylyn.feature.feature.jar [3.4.0.Beta2-v20121114-2253-B23] > Contains: Cannot satisfy dependency: > Contains: From: org.jboss.tools.common.mylyn.feature.source.feature.group 3.4.0.Alpha1-v20121123-2241-B69 > Contains: To: org.jboss.tools.common.mylyn.feature.feature.group [3.4.0.Alpha1-v20121123-2241-B69] > {quote} -- 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

13 years, 4 months

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 2013