[JBoss JIRA] (JBIDE-23518) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [aerogear-hybrid]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23518:
-------------------------------------------
Summary: For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [aerogear-hybrid]
Key: JBIDE-23518
URL: https://issues.jboss.org/browse/JBIDE-23518
Project: Tools (JBoss Tools)
Issue Type: Task
Components: aerogear-hybrid
Reporter: Friendly Jira Robot
Priority: Blocker
Fix For: 4.4.2.Final
For JBIDE 4.4.2.Final [aerogear-hybrid]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: all-tests cordova cordovasim feedhenry pom.xml pom.xml.orig README.md site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: all-tests cordova cordovasim feedhenry pom.xml pom.xml.orig README.md site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23516) Server Adapter: DC of debugged java application use nodejs debugging env var
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23516?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23516:
-------------------------------------
Fix Version/s: 4.4.2.Final
> Server Adapter: DC of debugged java application use nodejs debugging env var
> ----------------------------------------------------------------------------
>
> Key: JBIDE-23516
> URL: https://issues.jboss.org/browse/JBIDE-23516
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Marián Labuda
> Labels: debugging, openshift_v3, server_adapter
> Fix For: 4.4.2.Final
>
>
> When debugging an EAP application on OpenShift, deployment config is modified. In nodejs debugging there is added an environment variable DEV_MODE. For java debugging it is not necessary but I found it in deployment config. I compared deployment config before starting debugging and after and it was added by tooling.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23516) Server Adapter: DC of debugged java application use nodejs debugging env var
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23516?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-23516.
--------------------------------------
Assignee: Andre Dietisheim
Resolution: Rejected
> Server Adapter: DC of debugged java application use nodejs debugging env var
> ----------------------------------------------------------------------------
>
> Key: JBIDE-23516
> URL: https://issues.jboss.org/browse/JBIDE-23516
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: debugging, openshift_v3, server_adapter
> Fix For: 4.4.2.Final
>
>
> When debugging an EAP application on OpenShift, deployment config is modified. In nodejs debugging there is added an environment variable DEV_MODE. For java debugging it is not necessary but I found it in deployment config. I compared deployment config before starting debugging and after and it was added by tooling.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4192) Error Logging in devsuite-1.1.0-GA-bundle-installer.exe
by David Hladky (JIRA)
[ https://issues.jboss.org/browse/JBDS-4192?page=com.atlassian.jira.plugin.... ]
David Hladky commented on JBDS-4192:
------------------------------------
So you think the problem is a proxy server in the customer network?
> Error Logging in devsuite-1.1.0-GA-bundle-installer.exe
> -------------------------------------------------------
>
> Key: JBDS-4192
> URL: https://issues.jboss.org/browse/JBDS-4192
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: David Hladky
> Assignee: Denis Golovin
> Priority: Critical
>
> I was contacted twice about similar problem: RHDENG-917. I am not able to find any bad activity in DM log so I need to know what might be wrong (e.g. some curl command to emulate what is goingon).
> Note: lately there was a problem with credential checking on DM using "http". If you are doing it, this is the problem. Please, let me know what it could be. Thank you.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4202) For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4202?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-4202.
----------------------------
Resolution: Done
> For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer]
> -------------------------------------------------------------------
>
> Key: JBDS-4202
> URL: https://issues.jboss.org/browse/JBDS-4202
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: installer
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 10.2.0.GA
>
>
> For JBDS 10.2.0.GA [installer]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.61.0.Final {code} mvn clean verify -Dtpc.version=4.61.0.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4202) For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer]
by Nick Boldt (JIRA)
Nick Boldt created JBDS-4202:
--------------------------------
Summary: For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer]
Key: JBDS-4202
URL: https://issues.jboss.org/browse/JBDS-4202
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 10.2.0.GA
For JBDS 10.2.0.GA [installer]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.61.0.Final {code} mvn clean verify -Dtpc.version=4.61.0.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4175 at 11/24/16 11:49 AM:
-------------------------------------------------------------
Current status:
I've installed everything from Central and only these are still a problem:
||3rd Party||Status in RPM||Status Upstream||Issue||Description or Errors||
|Atlassian_Connector|(x)|(x)|JBDS-4191|would need to fork https://bitbucket.org/atlassian/connector-eclipse/overview and run their Ant build :(
|Spring_IDE|(x)|(/)|JBDS-4190|Fixed in master branch for Spring IDE 3.8.3.CI (no idea when 3.8.3.RELEASE is due): http://dist.springsource.com/snapshot/TOOLS/nightly/e4.6
|JRebel|(x)|(/)|n/a|Fixed in http://update.zeroturnaround.com/update-site-nightly/ - {quote}It's Valerie from JRebel Support Team. The next release should be in a couple of weeks, cannot say any concrete date just jet! :)
Thank you for confirming the fix! It will be available in JRebel 7.0.1 for sure.{quote}
||Red Hat||Status in RPM||Status Upstream||Issue||Description or Errors||
|Teiid Designer|(x)|(/)|JBDS-4189|Fixed in master branch for Teiid Designer 11.0 (but not in integration stack 10.0.0.GA)
|SwitchYard 2.2.0|(x)|(x)|JBDS-4200|slf4j use constraint violation
|rest of integration stack 10.0.0.GA|(/)|(/)|n/a|works OOTB when installed from https://devstudio.jboss.com/10.0/stable/updates/integration-stack/
We will need to make sure this is properly documented in https://issues.jboss.org/browse/RHDEVDOCS-120?focusedCommentId=13327430&p... so users don't break their Eclipse/devstudio rpm installs by installation of these tools.
was (Author: nickboldt):
Current status:
I've installed everything from Central and only these are still a problem:
||3rd Party||Status in RPM||Status Upstream||Issue||Description or Errors||
|Atlassian_Connector|(x)|(x)|JBDS-4191|would need to fork https://bitbucket.org/atlassian/connector-eclipse/overview and run their Ant build :(
|Spring_IDE|(x)|(/)|JBDS-4190|Fixed in master branch for Spring IDE 3.8.3.CI (no idea when 3.8.3.RELEASE is due): http://dist.springsource.com/snapshot/TOOLS/nightly/e4.6
|JRebel|(x)|(/)|n/a|Fixed in http://update.zeroturnaround.com/update-site-nightly/ but no release date for 7.0.1 avail yet
||Red Hat||Status in RPM||Status Upstream||Issue||Description or Errors||
|Teiid Designer|(x)|(/)|JBDS-4189|Fixed in master branch for Teiid Designer 11.0 (but not in integration stack 10.0.0.GA)
|SwitchYard 2.2.0|(x)|(x)|JBDS-4200|slf4j use constraint violation
|rest of integration stack 10.0.0.GA|(/)|(/)|n/a|works OOTB when installed from https://devstudio.jboss.com/10.0/stable/updates/integration-stack/
We will need to make sure this is properly documented in https://issues.jboss.org/browse/RHDEVDOCS-120?focusedCommentId=13327430&p... so users don't break their Eclipse/devstudio rpm installs by installation of these tools.
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.x
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months