September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23194) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [OpenShift]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23194?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23194. ------------------------------ > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [OpenShift] > ------------------------------------------------------------------- > > Key: JBIDE-23194 > URL: https://issues.jboss.org/browse/JBIDE-23194 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Friendly Jira Robot > Assignee: Andre Dietisheim > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [OpenShift]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [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.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-4065: -------------------------------------- No, we are not agreeing with that. [~rob.stryker] please investigate this use case. > DevStudio 1.1 Installer unfriendly when 1.0 present > --------------------------------------------------- > > Key: JBDS-4065 > URL: https://issues.jboss.org/browse/JBDS-4065 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 10, DevSuite Installer 1.0 had been run > Reporter: Rick Wagner > Assignee: Rob Stryker > > When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK. > Observations: > - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned). > - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory. > - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is? > - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup. > - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-4014: -------------------------------------- Thanks Nick. > Track rh-eclipse46-devstudio-*.rpm version usage > ------------------------------------------------ > > Key: JBDS-4014 > URL: https://issues.jboss.org/browse/JBDS-4014 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexander Kurtakov > Priority: Critical > Fix For: 10.2.0.AM2 > > > We need to distinguish the following use cases: > 1) Devstudio installed via RPM > 2) Devstudio installed via P2 but on top of the "base" eclipse rpm > 3) Devstudio installed traditionally (jar installer or p2) > As a bonus we could want to track if the DTS + devstudio rpms were both installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23180) CDKLaunchController (and others) calling ui-blocking getPassword() even when user not passing credentials

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23180?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23180: ----------------------------------- Priority: Blocker (was: Major) > CDKLaunchController (and others) calling ui-blocking getPassword() even when user not passing credentials > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23180 > URL: https://issues.jboss.org/browse/JBIDE-23180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.2.AM2 > > > Even when a user has unchecked the option to pass credentials to vagrant via environment variables, the user is still being prompted for a username and password. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23135) EAP 7.1 Server adapter

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23135?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23135: ------------------------------------- Jars that are different from our wf9 jars: {code} current jars eap7.1 jars logging: 3.3.0.Final 3.3.0.Final = sasl: 1.0.5.Final 1.0.5.Final = threads: 2.2.1.Final 2.2.1.Final = marshalling: 1.4.10.Final 1.4.11.Final * remoting: 4.0.18.Final 4.0.21.Final * dmr: 1.3.0.Final 1.4.0.Beta1 ** xnio: 3.3.4.Final 3.4.0.Final ** controller: 2.0.10.Final 3.0.0.Alpha8 *** {code} We can see the most likely area for breakage is the controller jars. For now everything seems to work, but its worth noting that we may need yet another jar bundle if somehow there are breakages in the major bump. We curently have 3 jar sets labaled as as7, eap61plus, wildfly9. It would be a shame if we needed a 4th set. For now it seems we don't need one, until we discover some regressions. > EAP 7.1 Server adapter > ---------------------- > > Key: JBIDE-23135 > URL: https://issues.jboss.org/browse/JBIDE-23135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23135) EAP 7.1 Server adapter

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23135?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-23135 at 9/28/16 3:30 PM: -------------------------------------------------------------- Jars that are different from our wf9 jars: {code} current jars eap7.1 jars logging: 3.3.0.Final 3.3.0.Final = sasl: 1.0.5.Final 1.0.5.Final = threads: 2.2.1.Final 2.2.1.Final = marshalling: 1.4.10.Final 1.4.11.Final * remoting: 4.0.18.Final 4.0.21.Final * dmr: 1.3.0.Final 1.4.0.Beta1 ** xnio: 3.3.4.Final 3.4.0.Final ** controller: 2.0.10.Final 3.0.0.Alpha8 *** {code} We can see the most likely area for breakage is the controller jars. For now everything seems to work, but its worth noting that we may need yet another jar bundle if somehow there are breakages in the major bump. We curently have 3 jar sets labaled as as7, eap61plus, wildfly9. It would be a shame if we needed a 4th set. For now it seems we don't need one, until we discover some regressions. was (Author: rob.stryker): Jars that are different from our wf9 jars: {code} current jars eap7.1 jars logging: 3.3.0.Final 3.3.0.Final = sasl: 1.0.5.Final 1.0.5.Final = threads: 2.2.1.Final 2.2.1.Final = marshalling: 1.4.10.Final 1.4.11.Final * remoting: 4.0.18.Final 4.0.21.Final * dmr: 1.3.0.Final 1.4.0.Beta1 ** xnio: 3.3.4.Final 3.4.0.Final ** controller: 2.0.10.Final 3.0.0.Alpha8 *** {code} We can see the most likely area for breakage is the controller jars. For now everything seems to work, but its worth noting that we may need yet another jar bundle if somehow there are breakages in the major bump. We curently have 3 jar sets labaled as as7, eap61plus, wildfly9. It would be a shame if we needed a 4th set. For now it seems we don't need one, until we discover some regressions. > EAP 7.1 Server adapter > ---------------------- > > Key: JBIDE-23135 > URL: https://issues.jboss.org/browse/JBIDE-23135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23250) hibernate New and Noteworthy for 4.4.2.AM1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23250?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23250. ---------------------------------- Resolution: Rejected [~koen.aers] please reopen if there is any N&N for hibernate. I'm closing it now. > hibernate New and Noteworthy for 4.4.2.AM1 > ------------------------------------------ > > Key: JBIDE-23250 > URL: https://issues.jboss.org/browse/JBIDE-23250 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Fix For: 4.4.2.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If hibernate is not listed here check if there are issues that should be added and add them. > Document the ones relevant for hibernate by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23238) Create New and Noteworthy for 4.4.2.AM1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23238?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-23238. ------------------------------------ Resolution: Done > Create New and Noteworthy for 4.4.2.AM1 > --------------------------------------- > > Key: JBIDE-23238 > URL: https://issues.jboss.org/browse/JBIDE-23238 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.4.2.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23273) Implement org.jboss.tools.hibernate.runtime.v_3_6.internal.HibernateMappingExporterFacadeTest#testStart()

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23273?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-23273: --------------------------------- Fix Version/s: 4.4.2.AM2 Assignee: Koen Aers > Implement org.jboss.tools.hibernate.runtime.v_3_6.internal.HibernateMappingExporterFacadeTest#testStart() > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23273 > URL: https://issues.jboss.org/browse/JBIDE-23273 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.2.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.2.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23273) Implement org.jboss.tools.hibernate.runtime.v_3_6.internal.HibernateMappingExporterFacadeTest#testStart()

by Koen Aers (JIRA)

Koen Aers created JBIDE-23273: --------------------------------- Summary: Implement org.jboss.tools.hibernate.runtime.v_3_6.internal.HibernateMappingExporterFacadeTest#testStart() Key: JBIDE-23273 URL: https://issues.jboss.org/browse/JBIDE-23273 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.4.2.AM1 Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016