April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19616) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [OpenShift]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19616?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19616. ------------------------------------ Assignee: Andre Dietisheim Resolution: Done > For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [OpenShift] > -------------------------------------------------------- > > Key: JBIDE-19616 > URL: https://issues.jboss.org/browse/JBIDE-19616 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha2 > > > For JBIDE 4.3.0.Alpha2 [OpenShift]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT) > mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha2x > git push origin jbosstools-4.3.0.Alpha2x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19630) v3 connections: store to default url based persistence vs custom json format

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19630?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19630: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/604, https://github.com/jbosstools/jbosstools-openshift/pull/605 (was: https://github.com/jbosstools/jbosstools-openshift/pull/604) > v3 connections: store to default url based persistence vs custom json format > ---------------------------------------------------------------------------- > > Key: JBIDE-19630 > URL: https://issues.jboss.org/browse/JBIDE-19630 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > In JBIDE-19374 loading/saving was implemented using a custom json based format. We should drop this and use what we use for v2 connections. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3354) Seam 2 is still included in JBDS 9 Alpha1 installed from jar

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3354?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3354: ----------------------------------- Alpha2 no longer has the bulk of Seam plugins, but still contains org.jboss.tools.jsf.vpe.seam. This is caused by the org.jboss.tools.jsf.feature referencing it. We should severe that dependency and move org.jboss.tools.jsf.vpe.seam under the seam module for Beta1 We also still need to decide what to do with seam3 tools > Seam 2 is still included in JBDS 9 Alpha1 installed from jar > ------------------------------------------------------------ > > Key: JBDS-3354 > URL: https://issues.jboss.org/browse/JBDS-3354 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, cdi, seam > Affects Versions: 9.0.0.Alpha1 > Reporter: Martin Malina > Assignee: Fred Bricon > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > It seems to me that we removed the wrong feature. > This is JBDS 8.0.2: > {code} > nattura:features rasp$ ls |grep seam > org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79 > org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116 > org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79 > org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79 > {code} > And this is JBDS 9.0.0.Alpha1 B11: > {code} > nattura:features rasp$ ls |grep seam > org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3 > {code} > When you look at plugins, it looks as follows: > JBDS 8.0.2: > {code} > nattura:plugins rasp$ ls|grep seam > org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79 > org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar > org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar > {code} > JBDS 9.0.0.Alpha1 B11: > {code} > nattura:plugins rasp$ ls|grep seam > org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3 > org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar > {code} > For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19631) Switch Tern.java dependency version range to the only version after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19631?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19631: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Switch Tern.java dependency version range to the only version after code freeze > ------------------------------------------------------------------------------- > > Key: JBIDE-19631 > URL: https://issues.jboss.org/browse/JBIDE-19631 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3354) Seam 2 is still included in JBDS 9 Alpha1 installed from jar

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3354?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3354: ------------------------------ Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.Alpha2) > Seam 2 is still included in JBDS 9 Alpha1 installed from jar > ------------------------------------------------------------ > > Key: JBDS-3354 > URL: https://issues.jboss.org/browse/JBDS-3354 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, cdi, seam > Affects Versions: 9.0.0.Alpha1 > Reporter: Martin Malina > Assignee: Fred Bricon > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > It seems to me that we removed the wrong feature. > This is JBDS 8.0.2: > {code} > nattura:features rasp$ ls |grep seam > org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79 > org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116 > org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79 > org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79 > {code} > And this is JBDS 9.0.0.Alpha1 B11: > {code} > nattura:features rasp$ ls |grep seam > org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3 > {code} > When you look at plugins, it looks as follows: > JBDS 8.0.2: > {code} > nattura:plugins rasp$ ls|grep seam > org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79 > org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar > org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar > {code} > JBDS 9.0.0.Alpha1 B11: > {code} > nattura:plugins rasp$ ls|grep seam > org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3 > org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar > {code} > For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19247) Switch Tern.java dependency version range to the only version after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19247?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-19247. ----------------------------------- Resolution: Done Updated to [0.9.0.201504141710,0.9.0.201504141710] in jbosstools-.4.3.0.Alpha2x branch. > Switch Tern.java dependency version range to the only version after code freeze > ------------------------------------------------------------------------------- > > Key: JBIDE-19247 > URL: https://issues.jboss.org/browse/JBIDE-19247 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19631) Switch Tern.java dependency version range to the only version after code freeze

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-19631: ------------------------------------- Summary: Switch Tern.java dependency version range to the only version after code freeze Key: JBIDE-19631 URL: https://issues.jboss.org/browse/JBIDE-19631 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml/html source editing Affects Versions: 4.3.0.Alpha1 Reporter: Alexey Kazakov Assignee: Denis Golovin Priority: Blocker Fix For: 4.3.0.Alpha2 In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19146) Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19146?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19146: ------------------------------------------ worked in a quick test, postponing for more in-depth testing. > Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final > ----------------------------------------------------------------------------------- > > Key: JBIDE-19146 > URL: https://issues.jboss.org/browse/JBIDE-19146 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > We have to make sure that the new tooling (with the new plugins and the code reorg in JBIDE-19048) can restore a workspace that was created with JBT 4.2.0.Final / JBDS 8.0.0: > - restore opened views (explorer) > - restore connections > - restore server editor(s) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19146) Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19146?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19146: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final > ----------------------------------------------------------------------------------- > > Key: JBIDE-19146 > URL: https://issues.jboss.org/browse/JBIDE-19146 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > We have to make sure that the new tooling (with the new plugins and the code reorg in JBIDE-19048) can restore a workspace that was created with JBT 4.2.0.Final / JBDS 8.0.0: > - restore opened views (explorer) > - restore connections > - restore server editor(s) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19146) Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19146?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19146: ---------------------------------------- Assignee: Andre Dietisheim > Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final > ----------------------------------------------------------------------------------- > > Key: JBIDE-19146 > URL: https://issues.jboss.org/browse/JBIDE-19146 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > We have to make sure that the new tooling (with the new plugins and the code reorg in JBIDE-19048) can restore a workspace that was created with JBT 4.2.0.Final / JBDS 8.0.0: > - restore opened views (explorer) > - restore connections > - restore server editor(s) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 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 April 2015