January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13392) Can openshift tools in JBT 3.3 run with egit 2.x?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13392?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13392: ------------------------------------ [~maxandersen] JBIDE-12338 added support for installing on top of egit 2.0, not 2.x. So installs will still fail (http://marketplace.eclipse.org/node/618010) for users w/ egit 2.2. > Can openshift tools in JBT 3.3 run with egit 2.x? > ------------------------------------------------- > > Key: JBIDE-13392 > URL: https://issues.jboss.org/browse/JBIDE-13392 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 3.3.1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Fix For: 3.3.2 > > Attachments: JBIDE13392.patch.txt > > > JBT 3.3.x Indigo target platform includes egit 1.2. > org.jboss.tools.openshift.express.ui depends on org.eclipse.egit.ui;bundle-version="1.0.0", which means anyone with egit 2.x already installed won't be able to install the OpenShift tools: > {code} > Cannot complete the install because of a conflicting dependency. Software being installed: > JBoss OpenShift Tools 2.3.1.v20120715-0255-H145-Final (org.jboss.tools.openshift.express.feature.feature.group 2.3.1.v20120715-0255-H145-Final) > Software currently installed: > Eclipse EGit 2.2.0.201212191850-r (org.eclipse.egit.feature.group 2.2.0.201212191850-r) > Only one of the following can be installed at once: > Git Team Provider UI 2.2.0.201212191850-r (org.eclipse.egit.ui 2.2.0.201212191850-r) > Git Team Provider UI 1.2.0.201112121913 (org.eclipse.egit.ui 1.2.0.201112121913) > Because: > org.jboss.tools.openshift.express.ui 2.3.1.v20120715-0255-H145-Final requires org.eclipse.egit.ui [1.0.0,2.0.0) > {code} > Can openshift tools run w/ egit 2.x? Can we simply extend the version compliance ranges in the plugins to allow [1.0.0,3.0.0) ? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13392) Can openshift tools in JBT 3.3 run with egit 2.x?

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13392?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13392: ------------------------------------------ IMHO *1.0.0* resolves to *[1.0.0, INFINITY)* - see OSGI R4.3 Spec, Chapter 3.2.6, page 29: {quote} If a version range is specified as a single version, it must be interpreted as the range [version,∞). {quote} *[1.0.0, 3.0.0)* would therefore not change anything? > Can openshift tools in JBT 3.3 run with egit 2.x? > ------------------------------------------------- > > Key: JBIDE-13392 > URL: https://issues.jboss.org/browse/JBIDE-13392 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 3.3.1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Fix For: 3.3.2 > > Attachments: JBIDE13392.patch.txt > > > JBT 3.3.x Indigo target platform includes egit 1.2. > org.jboss.tools.openshift.express.ui depends on org.eclipse.egit.ui;bundle-version="1.0.0", which means anyone with egit 2.x already installed won't be able to install the OpenShift tools: > {code} > Cannot complete the install because of a conflicting dependency. Software being installed: > JBoss OpenShift Tools 2.3.1.v20120715-0255-H145-Final (org.jboss.tools.openshift.express.feature.feature.group 2.3.1.v20120715-0255-H145-Final) > Software currently installed: > Eclipse EGit 2.2.0.201212191850-r (org.eclipse.egit.feature.group 2.2.0.201212191850-r) > Only one of the following can be installed at once: > Git Team Provider UI 2.2.0.201212191850-r (org.eclipse.egit.ui 2.2.0.201212191850-r) > Git Team Provider UI 1.2.0.201112121913 (org.eclipse.egit.ui 1.2.0.201112121913) > Because: > org.jboss.tools.openshift.express.ui 2.3.1.v20120715-0255-H145-Final requires org.eclipse.egit.ui [1.0.0,2.0.0) > {code} > Can openshift tools run w/ egit 2.x? Can we simply extend the version compliance ranges in the plugins to allow [1.0.0,3.0.0) ? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13393) create install tests to verify use cases exposed here for m2e and egit

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13393?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13393: ------------------------------------ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stabl... {quote} Test installing m2e 1.0, 1.1, 1.2, 1.3 into Eclipse 3.7.2 Then install JBT 3.3 org.jboss.tools.maven.feature and org.jboss.tools.community.central.feature features. {quote} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stabl... {quote} Test installing egit 1.2, 2.0, 2.1 into Eclipse 3.7.2 Then install JBT 3.3 org.jboss.tools.openshift.egit.integration.feature and org.jboss.tools.openshift.express.feature features. {quote} > create install tests to verify use cases exposed here for m2e and egit > ---------------------------------------------------------------------- > > Key: JBIDE-13393 > URL: https://issues.jboss.org/browse/JBIDE-13393 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng, testing, updatesite > Affects Versions: 3.3.1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 3.3.2 > > > Need to set up install tests which will verify what happens if: > 1. Install m2e 1.2 > 2. install JBT 3.3.x > 1. Install egit 1.2 > 2. install JBT 3.3.x > 1. Install egit 1.3 > 2. install JBT 3.3.x > 1. Install egit 2.0 > 2. install JBT 3.3.x > 1. Install egit 2.2 > 2. install JBT 3.3.x -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13392) Can openshift tools in JBT 3.3 run with egit 2.x?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13392?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13392: ------------------------------- Attachment: JBIDE13392.patch.txt Patch to tweak MANIFEST.MF files to allow installation onto egit 2.x, and to upversion features/plugins to 2.3.2: [^JBIDE13392.patch.txt] [~adietish], [~maxandersen] - please review. > Can openshift tools in JBT 3.3 run with egit 2.x? > ------------------------------------------------- > > Key: JBIDE-13392 > URL: https://issues.jboss.org/browse/JBIDE-13392 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 3.3.1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Fix For: 3.3.2 > > Attachments: JBIDE13392.patch.txt > > > JBT 3.3.x Indigo target platform includes egit 1.2. > org.jboss.tools.openshift.express.ui depends on org.eclipse.egit.ui;bundle-version="1.0.0", which means anyone with egit 2.x already installed won't be able to install the OpenShift tools: > {code} > Cannot complete the install because of a conflicting dependency. Software being installed: > JBoss OpenShift Tools 2.3.1.v20120715-0255-H145-Final (org.jboss.tools.openshift.express.feature.feature.group 2.3.1.v20120715-0255-H145-Final) > Software currently installed: > Eclipse EGit 2.2.0.201212191850-r (org.eclipse.egit.feature.group 2.2.0.201212191850-r) > Only one of the following can be installed at once: > Git Team Provider UI 2.2.0.201212191850-r (org.eclipse.egit.ui 2.2.0.201212191850-r) > Git Team Provider UI 1.2.0.201112121913 (org.eclipse.egit.ui 1.2.0.201112121913) > Because: > org.jboss.tools.openshift.express.ui 2.3.1.v20120715-0255-H145-Final requires org.eclipse.egit.ui [1.0.0,2.0.0) > {code} > Can openshift tools run w/ egit 2.x? Can we simply extend the version compliance ranges in the plugins to allow [1.0.0,3.0.0) ? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13376) jbosstools-build-sites/aggregate/build.xml index page generation produces feature versions of 0.0.0 instead of actual versions (if using category.xml instead of site.xml)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13376?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13376: ------------------------------------ Probably won't get fixed. Would rather migrate functionality we still care about from jbosstools-build-sites/aggregate/build.xml into mistria's mojo for building index.html and inserting associate sites into content.jar. > jbosstools-build-sites/aggregate/build.xml index page generation produces feature versions of 0.0.0 instead of actual versions (if using category.xml instead of site.xml) > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13376 > URL: https://issues.jboss.org/browse/JBIDE-13376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > jbosstools-build-sites/aggregate/build.xml index page generation produces feature versions of 0.0.0 instead of actual versions (if using category.xml instead of site.xml) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13376) jbosstools-build-sites/aggregate/build.xml index page generation produces feature versions of 0.0.0 instead of actual versions (if using category.xml instead of site.xml)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13376?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13376: ------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Alpha1) > jbosstools-build-sites/aggregate/build.xml index page generation produces feature versions of 0.0.0 instead of actual versions (if using category.xml instead of site.xml) > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13376 > URL: https://issues.jboss.org/browse/JBIDE-13376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > jbosstools-build-sites/aggregate/build.xml index page generation produces feature versions of 0.0.0 instead of actual versions (if using category.xml instead of site.xml) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13394) Test failures in integrationtests site build

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13394: ---------------------------------- Summary: Test failures in integrationtests site build Key: JBIDE-13394 URL: https://issues.jboss.org/browse/JBIDE-13394 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: testing Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Martin Malina Successfully built https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... but these tests failed: {code} [INFO] org.jboss.ide.eclipse.as.ui.bot.test .............. FAILURE [2:31.629s] [INFO] org.jboss.tools.cdi.reddeer ....................... FAILURE [11.814s] [INFO] org.jboss.tools.deltaspike.ui.bot.test ............ SKIPPED [INFO] org.jboss.tools.runtime.as.ui.bot.test ............ FAILURE [3:38.606s] {code} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-12974. -------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.1.x) Resolution: Done Site is building OK. Closing. [~mmalina] can resolve when satisfied or reopen if more to do. Will open separate JIRA for the test failures. > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13316) Improve versioning for TP using standard Maven way

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13316 at 1/17/13 11:32 AM: -------------------------------------------------------------- I believe this was agreed to on yesterday's call: {quote}one Git branch for each version of TPs{quote} Thus, we would want something like this: https://github.com/jbosstools/jbosstools-targetplatforms/tree/4.20.5.Final/ (SR0d TPs for JBT and JBDS) https://github.com/jbosstools/jbosstools-targetplatforms/tree/4.21.3.Final/ (SR1b TPs for JBT and JBDS) https://github.com/jbosstools/jbosstools-targetplatforms/tree/4.30.0.Final/ (M4 TPs for JBT and JBDS) Or would you want a branch for JBT and a separate branch for JBDS for each version of the TP? was (Author: nickboldt): I believe this was agreed to on yesterday's call: {quote}one Git branch for each version of TPs{quote} Thus, we would want something like this: https://github.com/jbosstools/jbosstools-targetplatforms/tree/4.20.5.Final/ (SR0d TPs for JBT and JBDS) https://github.com/jbosstools/jbosstools-targetplatforms/tree/4.21.3.Final/ (SR1b TPs for JBT and JBDS) https://github.com/jbosstools/jbosstools-targetplatforms/tree/4.30.0.Final/ (M4 TPs for JBT and JBDS) > Improve versioning for TP using standard Maven way > -------------------------------------------------- > > Key: JBIDE-13316 > URL: https://issues.jboss.org/browse/JBIDE-13316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned. > Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13316) Improve versioning for TP using standard Maven way

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13316: ------------------------------------ I believe this was agreed to on yesterday's call: {quote}one Git branch for each version of TPs{quote} Thus, we would want something like this: https://github.com/jbosstools/jbosstools-targetplatforms/tree/4.20.5.Final/ (SR0d TPs for JBT and JBDS) https://github.com/jbosstools/jbosstools-targetplatforms/tree/4.21.3.Final/ (SR1b TPs for JBT and JBDS) https://github.com/jbosstools/jbosstools-targetplatforms/tree/4.30.0.Final/ (M4 TPs for JBT and JBDS) > Improve versioning for TP using standard Maven way > -------------------------------------------------- > > Key: JBIDE-13316 > URL: https://issues.jboss.org/browse/JBIDE-13316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned. > Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs. -- 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, 5 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 January 2013