April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-527) com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-527?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-527: ---------------------------------- Okay - this is now fixed with this commit: https://github.com/jbosstools/jbosstools-integration-stack/commit/d6caed8... I'll wait until after 9.0.0.GA is released before building an integration 9.0.1.Beta1. WIll keep this open until then. > com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-527 > URL: https://issues.jboss.org/browse/JBTIS-527 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.1.GA > > > Looking in https://devstudio.redhat.com/9.0/stable/updates/integration-stack/9.0.0.A... I see these 4 IUs: > {code} > com.jboss.devstudio.integration-stack.bpr.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.ds.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.fuse.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.soa.feature.feature.jar 9.0.0.201510070121 > {code} > They should be versioned like everything else in JBT/JBDS/IS, using a full qualifier like: > * 9.0.0.Alpha2-v20151006-2058-B148 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick edited comment on JBTIS-654 at 4/22/16 1:18 PM: ------------------------------------------------------------------ [~pleacu] Couple of questions regarding runtime configuration in the installer... I agree that not everybody will want a fuse-only tooling installer, but I think from an evaluator point of view it would be awesome to get a one-click-and-go install process that not only installs JBDS + Fuse tooling in a location of the user's choosing, but pre-configures a Fuse runtime as well. If we want to compete in the same space as Mulesoft and Talend, having some sort of all-in-one installer as an option would definitely help get us part of the way. Can we add such options to the installer as we move to the next phase of this effort? was (Author: bfitzpat): [~pleacu] Couple of questions regarding runtime configuration in the installer... I agree that not everybody will want a fuse-only tooling installer, but I think from an evaluator point of view it would be awesome to get a one-click-and-go install process that not only installs JBDS + Fuse tooling in a location of the user's choosing, but pre-configures a Fuse runtime as well. If we want to compete in the same space as Mulesoft and Talend, having some sort of all-in-one installer as an option would definitely help get us part of the way. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-21857: -------------------------------------- I have filed a bug @eclipse.org in order to start a conversation whether there is a better way to solve this than calling System.gc(): https://bugs.eclipse.org/bugs/show_bug.cgi?id=492265 > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-654: ----------------------------------------- [~pleacu] Couple of questions regarding runtime configuration in the installer... I agree that not everybody will want a fuse-only tooling installer, but I think from an evaluator point of view it would be awesome to get a one-click-and-go install process that not only installs JBDS + Fuse tooling in a location of the user's choosing, but pre-configures a Fuse runtime as well. If we want to compete in the same space as Mulesoft and Talend, having some sort of all-in-one installer as an option would definitely help get us part of the way. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3856) Installer - Implement POC UI test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3856?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3856. ---------------------------- Resolution: Done Please log developer platform installer issues as Project = *JBDS*, component = *platform-installer*. > Installer - Implement POC UI test > --------------------------------- > > Key: JBDS-3856 > URL: https://issues.jboss.org/browse/JBDS-3856 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 9.1.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3856) Installer - Implement POC UI test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3856?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3856: ----------------------------- Project: Developer Studio (JBoss Developer Studio) (was: Tools (JBoss Tools)) Key: JBDS-3856 (was: JBIDE-21914) Docs QE Status: NEW Component/s: platform-installer (was: install-tests) Affects Version/s: 9.1.0.GA (was: 4.3.1.CR1) Fix Version/s: 9.1.0.GA (was: 4.3.1.Final) > Installer - Implement POC UI test > --------------------------------- > > Key: JBDS-3856 > URL: https://issues.jboss.org/browse/JBDS-3856 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 9.1.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-21857: -------------------------------------- Did some experimenting: # The jolokia agent in the eap image used in cdk uses ssh with credentials specific to OpenShift. I haven't been able to connect to that instance # I have succeeded to start a second jolokia agent by adding a "-javaagent:jolokia.jar..." to the JAVA_OPTS_PREPEND. I was able to connect to the agent with a local browser after forwarding the proper port. This would make it possible to start a jolokia connection when setting up the container for debug (we already add environment variables & forward ports when we start debugging). What's not yet clear is how or if we can access the jolokia connection when only having a debug target and an IServer in hand. > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22236) Update Hibernate 5.1 runtime dependency on Hibernate Tools to 5.1.0.Alpha3

by Koen Aers (JIRA)

Koen Aers created JBIDE-22236: --------------------------------- Summary: Update Hibernate 5.1 runtime dependency on Hibernate Tools to 5.1.0.Alpha3 Key: JBIDE-22236 URL: https://issues.jboss.org/browse/JBIDE-22236 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Reporter: Koen Aers Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22234) Update Hibernate 5.0 runtime dependency on Hibernate Tools to 5.0.0.CR1

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22234?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-22234. ------------------------------- Resolution: Done > Update Hibernate 5.0 runtime dependency on Hibernate Tools to 5.0.0.CR1 > ----------------------------------------------------------------------- > > Key: JBIDE-22234 > URL: https://issues.jboss.org/browse/JBIDE-22234 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22234) Update Hibernate 5.0 runtime dependency on Hibernate Tools to 5.0.0.CR1

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22234?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-22234: ------------------------------ Summary: Update Hibernate 5.0 runtime dependency on Hibernate Tools to 5.0.0.CR1 (was: Update Hibernate 5.1 runtime dependency on Hibernate Tools to 5.0.0.CR1) > Update Hibernate 5.0 runtime dependency on Hibernate Tools to 5.0.0.CR1 > ----------------------------------------------------------------------- > > Key: JBIDE-22234 > URL: https://issues.jboss.org/browse/JBIDE-22234 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016