May 2016 - jbosstools-issues - Jboss List Archives

[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: -------------------------------------- Tried to establish a jmx connection to cdk pod via jmx remoting: does not work because the startup script passes -bmanagment=127.0.0.1, so can't forward the port. > 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: Thomas Mäder > Priority: Blocker > Fix For: 4.4.x > > 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-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 edited comment on JBIDE-21857 at 5/9/16 11:52 AM: --------------------------------------------------------------- Tried to establish a jmx connection to cdk pod via jmx remoting: does not work because the startup script passes -bmanagement=127.0.0.1, so can't forward the port. was (Author: tmader): Tried to establish a jmx connection to cdk pod via jmx remoting: does not work because the startup script passes -bmanagment=127.0.0.1, so can't forward the port. > 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: Thomas Mäder > Priority: Blocker > Fix For: 4.4.x > > 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-22311) Adopt Tycho 0.24

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22311?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22311: ------------------------------------ Note that Tycho 0.25 is now available. We probably want to skip this in favour of the newer one. See @aurelien's PR to move up to 0.25 on that other jira. (Don't have the # handy.) > Adopt Tycho 0.24 > ---------------- > > Key: JBIDE-22311 > URL: https://issues.jboss.org/browse/JBIDE-22311 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 4.4.x > > > In order to take advantage of several improvements in Tycho ( https://wiki.eclipse.org/Tycho/Release_Notes/0.24 ), we should consider adopting its 0.24 release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13671: --------------------------------------------- [~mickael_istria] okey - so yes, our current use of SNAPSHOT for dependencies makes that happen and we don't notice it since we don't compare with latest milestone, just the GA release builds. > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-700) Update devstudio composites for JBDSIS 10.0.0.Alpha1 staging

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-700: -------------------------------- Summary: Update devstudio composites for JBDSIS 10.0.0.Alpha1 staging Key: JBTIS-700 URL: https://issues.jboss.org/browse/JBTIS-700 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 10.0.0.Alpha1 Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 10.0.0.Alpha1 Initial infrastructure for 10.0.x IS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-699) SwitchYard tooling : Removal of camel-netty / addition of camel-netty4

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-699?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick reassigned JBTIS-699: --------------------------------------- Assignee: Brian Fitzpatrick > SwitchYard tooling : Removal of camel-netty / addition of camel-netty4 > ---------------------------------------------------------------------- > > Key: JBTIS-699 > URL: https://issues.jboss.org/browse/JBTIS-699 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: switchyard > Reporter: Tom Cunningham > Assignee: Brian Fitzpatrick > > camel-netty is a deprecated camel component (see note at top) : http://camel.apache.org/netty.html > We'd like to deprecate the SwitchYard camel-netty component in Fuse 6.3 and then remove it in Fuse 7. The plan would be to provide a camel-netty4 component as a replacement (see ENTESB-5466). This JIRA should represent the tooling work needed around that change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3705) Cannot install older versions of JBDS from marketplace

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3705?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBDS-3705: ------------------------------------ Fix Version/s: 9.1.0.GA (was: 10.x) > Cannot install older versions of JBDS from marketplace > ------------------------------------------------------ > > Key: JBDS-3705 > URL: https://issues.jboss.org/browse/JBDS-3705 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: marketplace > Environment: Eclipse Luna SR2 for JEE Developers > Eclipse Kepler SR2 for JEE Developers > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Priority: Blocker > Fix For: 9.1.0.GA > > Attachments: jbds-old-versions.png > > > No matter which version of Eclipse IDE you use, the marketplace still offers only JBDS 9.1.0.GA (or JBT 4.3.1.Final) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3705) Cannot install older versions of JBDS from marketplace

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3705?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBDS-3705. ----------------------------------- Resolution: Done Verified with Kepler (JBDS 7.1.1), Luna (JBDS 8.1.0) and Mars (JBDS 9.1.0). > Cannot install older versions of JBDS from marketplace > ------------------------------------------------------ > > Key: JBDS-3705 > URL: https://issues.jboss.org/browse/JBDS-3705 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: marketplace > Environment: Eclipse Luna SR2 for JEE Developers > Eclipse Kepler SR2 for JEE Developers > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Priority: Blocker > Fix For: 9.1.0.GA > > Attachments: jbds-old-versions.png > > > No matter which version of Eclipse IDE you use, the marketplace still offers only JBDS 9.1.0.GA (or JBT 4.3.1.Final) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-699) SwitchYard tooling : Removal of camel-netty / addition of camel-netty4

by Tom Cunningham (JIRA)

Tom Cunningham created JBTIS-699: ------------------------------------ Summary: SwitchYard tooling : Removal of camel-netty / addition of camel-netty4 Key: JBTIS-699 URL: https://issues.jboss.org/browse/JBTIS-699 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: switchyard Reporter: Tom Cunningham camel-netty is a deprecated camel component (see note at top) : http://camel.apache.org/netty.html We'd like to deprecate the SwitchYard camel-netty component in Fuse 6.3 and then remove it in Fuse 7. The plan would be to provide a camel-netty4 component as a replacement (see ENTESB-5466). This JIRA should represent the tooling work needed around that change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22299) Application Wizard: Make OpenShift templates distinquished from builder images more explicit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22299?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22299: ------------------------------------------ [~mlabuda] I agree, but we should ideally match the web-ui as much as we can and it makes sense since a consistent user experience across frontend makes users feel "at home" right away. > Application Wizard: Make OpenShift templates distinquished from builder images more explicit > -------------------------------------------------------------------------------------------- > > Key: JBIDE-22299 > URL: https://issues.jboss.org/browse/JBIDE-22299 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: templates-and-builderimages.png > > > We are now supporting builder images in New OpenShift Application wizard, they are displayed together in one tree. User has to read labels in parenthesis to know whether its a builder or not (there is not explicit saying whether it is a template or not). It would be nice to have it distinguished more explicit. > Web UI use flash for templates and build icon for builder images. > !templates-and-builderimages.png! > We could use same in our wizard on the left side of each tree item to be aware of what we are going to work with (because following wizard pages are different for builder images than for templates). -- 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 May 2016