October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-940) Create a test for checking whether a runtime detection also creates a server

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-940?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-940: ------------------------------------ Summary: Create a test for checking whether a runtime detection also creates a server (was: Create a test for checking whether a runtime detections also creates a server) > Create a test for checking whether a runtime detection also creates a server > ---------------------------------------------------------------------------- > > Key: JBTIS-940 > URL: https://issues.jboss.org/browse/JBTIS-940 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > > Create a test for checking whether a runtime detections also creates a server. For more info please see FUSETOOLS-2176. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-940) Create a test for checking whether a runtime detections also creates a server

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-940: --------------------------------------- Summary: Create a test for checking whether a runtime detections also creates a server Key: JBTIS-940 URL: https://issues.jboss.org/browse/JBTIS-940 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.4.0.Alpha1 Reporter: Andrej Podhradsky Assignee: Tomáš Sedmík Create a test for checking whether a runtime detections also creates a server. For more info please see FUSETOOLS-2176. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4129) Bundled JDK is trying to install from non existing location

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4129?page=com.atlassian.jira.plugin.... ] Jan Richter reassigned JBDS-4129: --------------------------------- Assignee: Denis Golovin > Bundled JDK is trying to install from non existing location > ----------------------------------------------------------- > > Key: JBDS-4129 > URL: https://issues.jboss.org/browse/JBDS-4129 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Environment: Windows 10 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > > OpenJDK fails to install from bundled installer, it is trying to execute the msi from the location it would normally be downloaded into by the online installer. But it is just not there, since it's bundled instead. > {noformat} > Thu, 20 Oct 2016 18:53:13 GMT-INFO: jdk - Execute msiexec /i,C:\Users\jbossqa\AppData\Local\Temp\jdk.msi,INSTALLDIR=c:\DevelopmentSuite\jdk8,/qn,/norestart,/Lviwe,c:\DevelopmentSuite\openjdk.log > Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk - Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log > Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk - > Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk failed to install: Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4129) Bundled JDK is trying to install from non existing location

by Jan Richter (JIRA)

Jan Richter created JBDS-4129: --------------------------------- Summary: Bundled JDK is trying to install from non existing location Key: JBDS-4129 URL: https://issues.jboss.org/browse/JBDS-4129 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.AM2 Environment: Windows 10 Reporter: Jan Richter Priority: Blocker OpenJDK fails to install from bundled installer, it is trying to execute the msi from the location it would normally be downloaded into by the online installer. But it is just not there, since it's bundled instead. {noformat} Thu, 20 Oct 2016 18:53:13 GMT-INFO: jdk - Execute msiexec /i,C:\Users\jbossqa\AppData\Local\Temp\jdk.msi,INSTALLDIR=c:\DevelopmentSuite\jdk8,/qn,/norestart,/Lviwe,c:\DevelopmentSuite\openjdk.log Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk - Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk - Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk failed to install: Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4129) Bundled JDK is trying to install from non existing location

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4129?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4129: ------------------------------ Affects Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > Bundled JDK is trying to install from non existing location > ----------------------------------------------------------- > > Key: JBDS-4129 > URL: https://issues.jboss.org/browse/JBDS-4129 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Environment: Windows 10 > Reporter: Jan Richter > Priority: Blocker > > OpenJDK fails to install from bundled installer, it is trying to execute the msi from the location it would normally be downloaded into by the online installer. But it is just not there, since it's bundled instead. > {noformat} > Thu, 20 Oct 2016 18:53:13 GMT-INFO: jdk - Execute msiexec /i,C:\Users\jbossqa\AppData\Local\Temp\jdk.msi,INSTALLDIR=c:\DevelopmentSuite\jdk8,/qn,/norestart,/Lviwe,c:\DevelopmentSuite\openjdk.log > Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk - Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log > Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk - > Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk failed to install: Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-4059: ---------------------------------- Just to recap, we need to verify that: * installing rh-eclipse46-devstudio.10.2 into rh-eclipse46 beta works * o.j.t.vpe and o.j.t.xulrunner features are not installed * vpe.preview feature is installled * run tests like [~vkadlcik] did before > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-934) Wrong core version in JBTIS TP 4.4.0.CR1-SNAPSHOT

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-934?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-934. ----------------------------------- Verified with JBTIS TP 4.4.0.CR1 > Wrong core version in JBTIS TP 4.4.0.CR1-SNAPSHOT > ------------------------------------------------- > > Key: JBTIS-934 > URL: https://issues.jboss.org/browse/JBTIS-934 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.0.CR1-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.4.0.CR1-TP > > > I noticed that JBTIS TP 4.4.0.CR1-SNAPSHOT at > https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > defines the following repository > http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.2.AM1/ > which is supposed for JBT 4.4.2 / Devstudio 10.2.0 (which will be released later than Devstudio-IS 10.0.0.GA). > I think that there should be the stable one which is 4.4.1.Final. Please correct me if I'm wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4128) Missing a checkbox for creating a server in New EAP Runtime wizard

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBDS-4128: --------------------------------------- Summary: Missing a checkbox for creating a server in New EAP Runtime wizard Key: JBDS-4128 URL: https://issues.jboss.org/browse/JBDS-4128 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: runtime Affects Versions: 10.2.0.AM2 Environment: Red Hat JBoss Developer Studio Version: 10.2.0.AM2 Build id: AM2-v20161014-1657-B6205 Build date: 20161014-1657 Reporter: Andrej Podhradsky Attachments: new_server_checkbox.png There is no checkbox for creating a server in New EAP Runtime wizard. !new_server_checkbox.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23380: ------------------------------------- [~mickael_istria] \o/ reverted parent pom did the trick ;-) > MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23380 > URL: https://issues.jboss.org/browse/JBIDE-23380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > At a minimum, the mojo should: > foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all. > However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm. > So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23380: ---------------------------------------- I've reverted the change. [~ibuziuk] Please update to new parent pom (-U flag in Maven build). > MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23380 > URL: https://issues.jboss.org/browse/JBIDE-23380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > At a minimum, the mojo should: > foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all. > However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm. > So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016