March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-603) Add known issues for jbdsis-8.0.6.CR3

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-603?page=com.atlassian.jira.plugin.... ] Jozef Marko commented on JBTIS-603: ----------------------------------- Knonw issues reviewed for both JBDS8 and JBDS9 tooling. Also enabled "expert" mode for meta-data setting. Please notice this issue contains 2 pull requests. > Add known issues for jbdsis-8.0.6.CR3 > ------------------------------------- > > Key: JBTIS-603 > URL: https://issues.jboss.org/browse/JBTIS-603 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: Jozef Marko > Assignee: Andrej Podhradsky > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-603) Add known issues for jbdsis-8.0.6.CR3

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-603?page=com.atlassian.jira.plugin.... ] Jozef Marko resolved JBTIS-603. ------------------------------- Resolution: Done > Add known issues for jbdsis-8.0.6.CR3 > ------------------------------------- > > Key: JBTIS-603 > URL: https://issues.jboss.org/browse/JBTIS-603 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: Jozef Marko > Assignee: Andrej Podhradsky > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16144) Editing files outside the workspace and served by Live Reload fails in Windows

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16144?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-16144: ---------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Editing files outside the workspace and served by Live Reload fails in Windows > ------------------------------------------------------------------------------ > > Key: JBIDE-16144 > URL: https://issues.jboss.org/browse/JBIDE-16144 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.1.CR1 > Environment: Windows 7 - 64b, JDK 1.7.0_45 x86 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.4.x > > > * In workspace preferences > General > Workspace > enable "Refresh using native hooks or polling" > * Import https://github.com/jbosstools/jbosstools-documentation/tree/master/whatsnew as a project > * Right-click on an html file, open with > Web Browser via Live Reload > * Open the text file in a text editor (sublime text for me),change something, save -> browser reloads eventually > * Make a second change : file can't be saved "Access denied" > * Wait 1 minute, try again, it works. > * repeat, fail ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-603) Add known issues for jbdsis-8.0.6.CR3

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-603?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-603: ------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/662, https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/667 (was: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/662) Affects Version/s: 4.3.0.Beta1 > Add known issues for jbdsis-8.0.6.CR3 > ------------------------------------- > > Key: JBTIS-603 > URL: https://issues.jboss.org/browse/JBTIS-603 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: Jozef Marko > Assignee: Andrej Podhradsky > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21916) Build image function of Docker Tooling shows no message on console

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21916: --------------------------------------- hello [~aupres] Thanks for reporting this issue. May I ask if you have any error in the {{Error Log}} view ? Also, I'm curious to know why your screenshot shows such a Directory value ? Why do you have those strikethrough {{W}} letters in the directory path ? > Build image function of Docker Tooling shows no message on console > ------------------------------------------------------------------ > > Key: JBIDE-21916 > URL: https://issues.jboss.org/browse/JBIDE-21916 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Joseph Hwang > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > Attachments: 2016-03-19_8-47-37.jpg > > > "docker build" command show the message of build process and error on consol like below. > {code} > *_$ docker build --tag=jboss/wildfly:joseph . > Sending build context to Docker daemon 1.021 MB > Step 1 : FROM jboss/wildfly > ---> bda4b726bee1 > Step 2 : MAINTAINER Joseph Hwang "gladitor67(a)naver.com" > ---> Using cache > ---> 8914ffd24e28 > Step 3 : ENV WILDFLY_VERSION 10.0.0.Final > ---> Using cache > ---> 176b7b9a5b7f > Step 4 : ENV JBOSS_HOME /opt/jboss/wildfly > ---> Using cache > ---> 3f8d1e30f787 > Step 5 : RUN cd $HOME && curl -O https://download.jboss.org/wildfly/$WILDFLY_VERSION/wildfly-$WILDFLY_VERS... && unzip wildfly-$WILDFLY_VERSION.zip && mv $HOME/wildfly-$WILDFLY_VERSION $JBOSS_HOME && rm wildfly-$WILDFLY_VERSION.zip > ---> Using cache > ---> 454f6749ff6c > Step 6 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql > ---> Using cache > ---> 2fce5a99913c > Step 7 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql/main > ---> Using cache > ---> 1e4f8bd9aa50 > Step 8 : ADD module.xml $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ > ---> Using cache > ---> 723e4a09b3a0 > Step 9 : ADD mysql-connector-java-5.1.38-bin.jar $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ > ---> Using cache > ---> 7cc730359445 > Step 10 : ADD standalone.xml $JBOSS_HOME/standalone/configuration/ > ---> Using cache > ---> 9ac873838925 > Successfully built 79d34c841245_* > {code} > But in JBossTools there is no message shown on console except progress bar. > !2016-03-19_8-47-37.jpg! > I recommend the 'build image function of docker tooling' to show the build message on console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-602) Fix a test for creating a SY project with intpkg

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-602?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-602. ------------------------------ all related pull requests were pushed to appropriate branches > Fix a test for creating a SY project with intpkg > ------------------------------------------------ > > Key: JBTIS-602 > URL: https://issues.jboss.org/browse/JBTIS-602 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.2.6.CR1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.2.6.CR2 > > > The problem is that the behaviour depends eclipse base (luna or mars) > - detect correct runtime label > - get rid of switchyard vs integration version -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBDS-3705: --------------------------------------- Summary: Cannot install older versions of JBDS from marketplace Key: JBDS-3705 URL: https://issues.jboss.org/browse/JBDS-3705 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: marketplace Environment: Eclipse Luna SR2 for JEE Developers Eclipse Kepler SR2 for JEE Developers Reporter: Andrej Podhradsky Priority: Blocker No matter which version of Eclipse IDE you use, the marketplace still offers only JBDS 9.0.0.GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21916) Build image function of Docker Tooling shows no message on console

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21916: ---------------------------------- Description: "docker build" command show the message of build process and error on consol like below. {code} *_$ docker build --tag=jboss/wildfly:joseph . Sending build context to Docker daemon 1.021 MB Step 1 : FROM jboss/wildfly ---> bda4b726bee1 Step 2 : MAINTAINER Joseph Hwang "gladitor67(a)naver.com" ---> Using cache ---> 8914ffd24e28 Step 3 : ENV WILDFLY_VERSION 10.0.0.Final ---> Using cache ---> 176b7b9a5b7f Step 4 : ENV JBOSS_HOME /opt/jboss/wildfly ---> Using cache ---> 3f8d1e30f787 Step 5 : RUN cd $HOME && curl -O https://download.jboss.org/wildfly/$WILDFLY_VERSION/wildfly-$WILDFLY_VERS... && unzip wildfly-$WILDFLY_VERSION.zip && mv $HOME/wildfly-$WILDFLY_VERSION $JBOSS_HOME && rm wildfly-$WILDFLY_VERSION.zip ---> Using cache ---> 454f6749ff6c Step 6 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql ---> Using cache ---> 2fce5a99913c Step 7 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql/main ---> Using cache ---> 1e4f8bd9aa50 Step 8 : ADD module.xml $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ ---> Using cache ---> 723e4a09b3a0 Step 9 : ADD mysql-connector-java-5.1.38-bin.jar $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ ---> Using cache ---> 7cc730359445 Step 10 : ADD standalone.xml $JBOSS_HOME/standalone/configuration/ ---> Using cache ---> 9ac873838925 Successfully built 79d34c841245_* {code} But in JBossTools there is no message shown on console except progress bar. !2016-03-19_8-47-37.jpg! I recommend the 'build image function of docker tooling' to show the build message on console. was: "docker build" command show the message of build process and error on consol like below. {{*_$ docker build --tag=jboss/wildfly:joseph . Sending build context to Docker daemon 1.021 MB Step 1 : FROM jboss/wildfly ---> bda4b726bee1 Step 2 : MAINTAINER Joseph Hwang "gladitor67(a)naver.com" ---> Using cache ---> 8914ffd24e28 Step 3 : ENV WILDFLY_VERSION 10.0.0.Final ---> Using cache ---> 176b7b9a5b7f Step 4 : ENV JBOSS_HOME /opt/jboss/wildfly ---> Using cache ---> 3f8d1e30f787 Step 5 : RUN cd $HOME && curl -O https://download.jboss.org/wildfly/$WILDFLY_VERSION/wildfly-$WILDFLY_VERS... && unzip wildfly-$WILDFLY_VERSION.zip && mv $HOME/wildfly-$WILDFLY_VERSION $JBOSS_HOME && rm wildfly-$WILDFLY_VERSION.zip ---> Using cache ---> 454f6749ff6c Step 6 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql ---> Using cache ---> 2fce5a99913c Step 7 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql/main ---> Using cache ---> 1e4f8bd9aa50 Step 8 : ADD module.xml $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ ---> Using cache ---> 723e4a09b3a0 Step 9 : ADD mysql-connector-java-5.1.38-bin.jar $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ ---> Using cache ---> 7cc730359445 Step 10 : ADD standalone.xml $JBOSS_HOME/standalone/configuration/ ---> Using cache ---> 9ac873838925 Successfully built 79d34c841245_*}} But in JBossTools there is no message shown on console except progress bar. !2016-03-19_8-47-37.jpg! I recommend the 'build image function of docker tooling' to show the build message on console. > Build image function of Docker Tooling shows no message on console > ------------------------------------------------------------------ > > Key: JBIDE-21916 > URL: https://issues.jboss.org/browse/JBIDE-21916 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Joseph Hwang > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > Attachments: 2016-03-19_8-47-37.jpg > > > "docker build" command show the message of build process and error on consol like below. > {code} > *_$ docker build --tag=jboss/wildfly:joseph . > Sending build context to Docker daemon 1.021 MB > Step 1 : FROM jboss/wildfly > ---> bda4b726bee1 > Step 2 : MAINTAINER Joseph Hwang "gladitor67(a)naver.com" > ---> Using cache > ---> 8914ffd24e28 > Step 3 : ENV WILDFLY_VERSION 10.0.0.Final > ---> Using cache > ---> 176b7b9a5b7f > Step 4 : ENV JBOSS_HOME /opt/jboss/wildfly > ---> Using cache > ---> 3f8d1e30f787 > Step 5 : RUN cd $HOME && curl -O https://download.jboss.org/wildfly/$WILDFLY_VERSION/wildfly-$WILDFLY_VERS... && unzip wildfly-$WILDFLY_VERSION.zip && mv $HOME/wildfly-$WILDFLY_VERSION $JBOSS_HOME && rm wildfly-$WILDFLY_VERSION.zip > ---> Using cache > ---> 454f6749ff6c > Step 6 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql > ---> Using cache > ---> 2fce5a99913c > Step 7 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql/main > ---> Using cache > ---> 1e4f8bd9aa50 > Step 8 : ADD module.xml $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ > ---> Using cache > ---> 723e4a09b3a0 > Step 9 : ADD mysql-connector-java-5.1.38-bin.jar $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ > ---> Using cache > ---> 7cc730359445 > Step 10 : ADD standalone.xml $JBOSS_HOME/standalone/configuration/ > ---> Using cache > ---> 9ac873838925 > Successfully built 79d34c841245_* > {code} > But in JBossTools there is no message shown on console except progress bar. > !2016-03-19_8-47-37.jpg! > I recommend the 'build image function of docker tooling' to show the build message on console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-567) broken link to IS in JBT development site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-567?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-567. ----------------------------------- Verified. This is the same as JBTIS-601 > broken link to IS in JBT development site > ----------------------------------------- > > Key: JBTIS-567 > URL: https://issues.jboss.org/browse/JBTIS-567 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Beta1 > > Attachments: missing-IS-url.png > > > http://download.jboss.org/jbosstools/mars/development/updates/compositeAr... contains a ref to a non-existent IS site. http://download.jboss.org/jbosstools/static/mars/development/updates/inte... is 404'd > !missing-IS-url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3704) The installer gets stuck on Download page and never goes to Getting Started

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3704?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3704: ----------------------------------- Why is the setup method even being called if you choose to install the item? If you look at its code it is apparent it is designed to only be called when you use an existing installation. Specifically in case of JBDS it sets up java path in jbdevstudio.ini if the user chooses to install JDK from us. But this is already part of the installation process, because this java path is defined in the install config xml. There is no use calling it again. > The installer gets stuck on Download page and never goes to Getting Started > --------------------------------------------------------------------------- > > Key: JBDS-3704 > URL: https://issues.jboss.org/browse/JBDS-3704 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Labels: havoc > > It happens if the installer installs JBDS and works fine if it just sets up some already existing one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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