January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4247) Replace 7Zip self extracting executable

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4247: ----------------------------------- Summary: Replace 7Zip self extracting executable Key: JBDS-4247 URL: https://issues.jboss.org/browse/JBDS-4247 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.3.0.AM2 Environment: Windows Reporter: Denis Golovin Implement simple installer based on [go-bindata:https://github.com/jteeuwen/go-bindata]. It would do simple thing similar to other self-extracting installers, unpack specific Asset from executable and run it. In case of windows installer it would speedup installation. because instead of extracting everything for bundle installer as 7Zip does, it would pull only installer first and run it. Then every specific installer selected for installation would first pull data out of installer executable with go-bindata. This approach would fix several opened issues that should be addressed upstream in 7Zip selexecuatble. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1015: ----------------------------------- Just so we don't lose it - here's the javax.crypto bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=284465 > Latest JBDSIS Target Platform cannot be used locally > ---------------------------------------------------- > > Key: JBTIS-1015 > URL: https://issues.jboss.org/browse/JBTIS-1015 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: a1.png, a2.png, a3.png, a4.png, a5.png, b1.png, b2.png, commons.io available in folder.png, commons.io not visible in update site.png > > > Current state of understanding: > There are 2 different bugs: > * when using local "Directory": the jars which should be exploded in folder stay in jars > ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself? > ** the implication is that we can't start a CDK server with such a TP > * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance) > ** looks like a p2 bugs > ** the implication is that the TP doesn't resolve at all > If one of these two bugs can be fixed, we will have a way to consume a local Target Platform. > see [JBTIS-1008] for original discussions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1016) Update fuse/karaf runtime for 10.1.0 release

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1016: --------------------------------- Summary: Update fuse/karaf runtime for 10.1.0 release Key: JBTIS-1016 URL: https://issues.jboss.org/browse/JBTIS-1016 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 10.1.0.GA Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 10.1.0.CR1 Pick up jboss-fuse-karaf-6.3.0.redhat-224 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4246) Implement minishift cdk-setup in devsuite installer

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4246: ----------------------------------- Summary: Implement minishift cdk-setup in devsuite installer Key: JBDS-4246 URL: https://issues.jboss.org/browse/JBDS-4246 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.2.0.AM2 Environment: Windows, mac OS, Linux Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.3.0.AM2 Instead of downloading three resources from three different URL's installer will need to download only one and run with 'cdk-setup' parameter during installation -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21857 at 1/12/17 1:00 PM: ------------------------------------------------------------------- [~tmader] as discussed above, the "Hot Code Replace Failed" dialog always shows up, after there was a 1st "not code replaceable" change. Do you know how to prevent this (aka only show the "Hot Code Replace Failed" if there really is a change that's not "hot code replaceable" - not always as it is now)? was (Author: adietish): [~tmader] as discussed above, the "Hot Code Replace Failed" dialog always shows up, as soon as it once popped up. Do you know how to prevent this (aka only show the "Hot Code Replace Failed" if there really is a change that's not "hot code replaceable" - not always as it is now)? > Hot code replacement 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: Andre Dietisheim > Fix For: 4.4.3.AM2 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > 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 (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21857: ------------------------------------------ [~tmader] as discussed above, the "Hot Code Replace Failed" dialog always shows up, as soon as it once popped up. Do you know how to prevent this (aka only show the "Hot Code Replace Failed" if there really is a change that's not "hot code replaceable" - not always as it is now)? > Hot code replacement 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: Andre Dietisheim > Fix For: 4.4.3.AM2 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > 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 (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23756) Moved/Refactored AS itests have lost the possibility to run against specific eap build

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23756?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-23756: ------------------------------------ Hi [~rob.stryker], any strong opinion on how you would like to see this implemented? If not I'll attempt to add another 'scope' (or something like that..) to ServerRuntimesTest. > Moved/Refactored AS itests have lost the possibility to run against specific eap build > -------------------------------------------------------------------------------------- > > Key: JBIDE-23756 > URL: https://issues.jboss.org/browse/JBIDE-23756 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, server > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.4.3.AM2 > > > AS itests have been moved to jbosstools-server component repo and refactored/optimized. > But the refactored implementation in jbosstools-server doesn't support running itests against specific EAP build (as it has in integration-tests repo), which breaks eap team compatibility jobs listed here [1] > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-JBDS/ > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-JBDS/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23756) Moved/Refactored AS itests have lost the possibility to run against specific eap build

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23756?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-23756: ---------------------------------- Assignee: Pavol Srna > Moved/Refactored AS itests have lost the possibility to run against specific eap build > -------------------------------------------------------------------------------------- > > Key: JBIDE-23756 > URL: https://issues.jboss.org/browse/JBIDE-23756 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, server > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.4.3.AM2 > > > AS itests have been moved to jbosstools-server component repo and refactored/optimized. > But the refactored implementation in jbosstools-server doesn't support running itests against specific EAP build (as it has in integration-tests repo), which breaks eap team compatibility jobs listed here [1] > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-JBDS/ > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-JBDS/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23623 at 1/12/17 12:06 PM: -------------------------------------------------------------- OK, I've applied a few fixes, which resolved the problem LOCALLY when run in a bash shell. https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.4.x We can test this again when it's time to branch for GA/Final in 2.5 weeks. was (Author: nickboldt): OK, I've applied a few fixes. We can test this again when it's time to branch for GA/Final. > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.Final > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23623 at 1/12/17 12:06 PM: -------------------------------------------------------------- OK, I've applied a few fixes, which resolved the problem LOCALLY when run in a bash shell. https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.4.x We can test this again when it's time to branch for GA/Final in 2 weeks. was (Author: nickboldt): OK, I've applied a few fixes, which resolved the problem LOCALLY when run in a bash shell. https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.4.x We can test this again when it's time to branch for GA/Final in 2.5 weeks. > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.Final > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 2017