July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3967) Snapshots updatesite points to staging/../10.0.1.AM2 which does not exist

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3967?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3967. ---------------------------- Fix Version/s: 10.1.0.AM2 Resolution: Done Temporary issue caused by an incomplete staging process. > Snapshots updatesite points to staging/../10.0.1.AM2 which does not exist > ------------------------------------------------------------------------- > > Key: JBDS-3967 > URL: https://issues.jboss.org/browse/JBDS-3967 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.AM2 > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.1.0.AM2 > > > https://devstudio.redhat.com/10.0/snapshots/updates points to https://devstudio.redhat.com/10.0/staging/updates/core/10.0.1.AM2 which does not exist making integration tests repository not buildable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22675) Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22675?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22675: ---------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.x) > Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title > ------------------------------------------------------------------------------- > > Key: JBIDE-22675 > URL: https://issues.jboss.org/browse/JBIDE-22675 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitry Bocharov > Priority: Minor > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.1.AM2 > > > OpenShift 3 Server adapter wizard opened from context menu of a service in OpenShift Explorer view does not have title. Shell has title "". Server adapter wizard opened via Servers view or through shell menu File - New does have title "New Server" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22675) Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22675?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22675. --------------------------------- Verified in devstudio 10.0.1.AM2 AM2-v20160715-2233-B5663. > Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title > ------------------------------------------------------------------------------- > > Key: JBIDE-22675 > URL: https://issues.jboss.org/browse/JBIDE-22675 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitry Bocharov > Priority: Minor > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.1.AM2 > > > OpenShift 3 Server adapter wizard opened from context menu of a service in OpenShift Explorer view does not have title. Shell has title "". Server adapter wizard opened via Servers view or through shell menu File - New does have title "New Server" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-809) Cannot install Fuse tooling from EA without GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-809?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-809: ----------------------------------------- Hi [~pleacu], let's wait with the CR3 for other bugs. > Cannot install Fuse tooling from EA without GA > ---------------------------------------------- > > Key: JBTIS-809 > URL: https://issues.jboss.org/browse/JBTIS-809 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.1.GA > Environment: JBDS-IS 9.0.1.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Cannot install Fuse tooling from EA without GA due to the following error > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) > Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta3-v20160713-1902-B959 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta3-v20160713-1902-B959) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found > {code} > the missing gemini feature is available in GA update site. This is not a critical issue since this is not a common use case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22677) rsync stuck on OSX

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22677?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22677: ------------------------------------ I can't sync on Windows: {code:shell} Publishing failed Error renaming C:\work\runtime-JBossTools\.metadata\.plugins\org.eclipse.wst.server.core\tmp3928377488311031738.MF to C:\work\runtime-JBossTools\.metadata\.plugins\org.jboss.ide.eclipse.as.core\test1@eap-app\deploy\ROOT.war\META-INF\MANIFEST.MF. This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. You may adjust these settings in the server editor. Could not sync C:\work\runtime-JBossTools\.metadata\.plugins\org.jboss.ide.eclipse.as.core\test1@eap-app\deploy to all pods running the service eap-app OpenShiftBinaryCapability process exited: I0719 18:16:25.374353 5412 portforward.go:213] Forwarding from 127.0.0.1:60826 -> 47831 I0719 18:16:25.386635 5412 portforward.go:213] Forwarding from [::1]:60826 -> 47831 I0719 18:16:25.399345 5412 portforward.go:247] Handling connection for 60826 rsync: opendir "/cygdrive/c/work/runtime-JBossTools/.metadata/.plugins/org.jboss.ide.eclipse.as.core/test1(a)eap-app/deploy/ROOT.war" failed: Permission denied (13) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2] error: exit status 23 {code} I even tried with RedHat JDK (as I thought this has been fixed) but without great success > rsync stuck on OSX > ------------------ > > Key: JBIDE-22677 > URL: https://issues.jboss.org/browse/JBIDE-22677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.x > > > I deployed an eap app from the eap64-basic-s2i template, then created an openshift 3 server. > On server startup, publishing fails to complete after 5 minutes and a thread dump shows rsync is still blocking in the background. > {noformat} > "pool-40-thread-1" #231 prio=5 os_prio=31 tid=0x00007f9a55dd0000 nid=0xeb9f runnable [0x000000013199a000] > java.lang.Thread.State: RUNNABLE > at java.io.FileInputStream.readBytes(Native Method) > at java.io.FileInputStream.read(FileInputStream.java:255) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > - locked <0x00000007b3d45cb8> (a java.lang.UNIXProcess$ProcessPipeInputStream) > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) > - locked <0x00000007b3d49d50> (a java.io.InputStreamReader) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:161) > at java.io.BufferedReader.readLine(BufferedReader.java:324) > - locked <0x00000007b3d49d50> (a java.io.InputStreamReader) > at java.io.BufferedReader.readLine(BufferedReader.java:389) > at org.jboss.tools.openshift.core.server.RSync.lambda$0(RSync.java:152) > at org.jboss.tools.openshift.core.server.RSync$$Lambda$181/1635081930.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > I'm deploying on CDK 2.1RC5 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22757: ---------------------------------------- Is this really a blocker? What does it prevent from working? The proposed change is good IMO. I also like the fact that we have a more explicit name (BUILD_TIMESTAMP rather than BUILD_ID). Why not using directly the maven.build.timestamp property directly though? > jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug) > ----------------------------------------------------------------- > > Key: JBIDE-22757 > URL: https://issues.jboss.org/browse/JBIDE-22757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.1.AM2 > > Attachments: buildID-broken.png > > > Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER. > [1] https://issues.jenkins-ci.org/browse/JENKINS-26520 > [2] https://issues.jenkins-ci.org/browse/JENKINS-26626 > So instead of timestamped build folders, we're seeing things like this: > !buildID-broken.png|thumbnail! > Workaround until fixed in Jenkins: > {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code} > Or, try using BUILD_TIMESTAMP instead? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22757: ------------------------------------ Trying this fix in parent pom: https://github.com/jbosstools/jbosstools-build/pull/227 > jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug) > ----------------------------------------------------------------- > > Key: JBIDE-22757 > URL: https://issues.jboss.org/browse/JBIDE-22757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.1.AM2 > > Attachments: buildID-broken.png > > > Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER. > [1] https://issues.jenkins-ci.org/browse/JENKINS-26520 > [2] https://issues.jenkins-ci.org/browse/JENKINS-26626 > So instead of timestamped build folders, we're seeing things like this: > !buildID-broken.png|thumbnail! > Workaround until fixed in Jenkins: > {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code} > Or, try using BUILD_TIMESTAMP instead? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22676) Context menu Server Adapter of a service in properties view does not work

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22676?page=com.atlassian.jira.plugi... ] Jeff MAURY resolved JBIDE-22676. -------------------------------- Resolution: Cannot Reproduce Bug > Context menu Server Adapter of a service in properties view does not work > ------------------------------------------------------------------------- > > Key: JBIDE-22676 > URL: https://issues.jboss.org/browse/JBIDE-22676 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.1.AM2 > > > When I have selected a project with an applicaiton in OpenShift Explorer view, I can handle the service also in properties view. But context menu item "Server Adapter..." in context menu of the service in properties view does nothing. No wizard is opened, nor any error in error log is shown. Context menu item in OpenShift explorer works ok. Only the one in properties view is affected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22676) Context menu Server Adapter of a service in properties view does not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22676?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22676: --------------------------------------- I cannot reproduce it neither anymore. Probably it has been fixed somewhere along the way, since this issue is 3 weeks old. > Context menu Server Adapter of a service in properties view does not work > ------------------------------------------------------------------------- > > Key: JBIDE-22676 > URL: https://issues.jboss.org/browse/JBIDE-22676 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.1.AM2 > > > When I have selected a project with an applicaiton in OpenShift Explorer view, I can handle the service also in properties view. But context menu item "Server Adapter..." in context menu of the service in properties view does nothing. No wizard is opened, nor any error in error log is shown. Context menu item in OpenShift explorer works ok. Only the one in properties view is affected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22765) In FTL file in editor are missing directives in code assistant

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-22765: ------------------------------------- Summary: In FTL file in editor are missing directives in code assistant Key: JBIDE-22765 URL: https://issues.jboss.org/browse/JBIDE-22765 Project: Tools (JBoss Tools) Issue Type: Bug Components: freemarker Affects Versions: 4.4.1.AM2 Environment: Fedora 24, x86_64, devstudio: Version: 10.0.1.AM2 Build id: AM2-v20160715-2233-B5663 Build date: 20160715-2233 Reporter: Ondrej Dockal Priority: Critical In .ftl file when using <# and opening code assistant, there are missing directives: compress, nt and setting. I checked http://freemarker.org/docs/ref_directive_alphaidx.html for supported directives but did not find any reason we are missing those mentioned above. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016