April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3844) JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment.

by Chandra Shekhar Pandey (JIRA)

[ https://issues.jboss.org/browse/JBDS-3844?page=com.atlassian.jira.plugin.... ] Chandra Shekhar Pandey updated JBDS-3844: ----------------------------------------- Summary: JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment. (was: JBDS 9 with java 8 tries to download maven dependencies with versin 2.0.7 in offline environment.) > JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment. > -------------------------------------------------------------------------------------------------- > > Key: JBDS-3844 > URL: https://issues.jboss.org/browse/JBDS-3844 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.GA > Environment: ALL > Reporter: Chandra Shekhar Pandey > > - Testing in a offline environment with Fuse 6.2.1 offline repository from https://access.redhat.com/solutions/1599973. > - A simple Fuse project when built within JBDS 9.0 GA with java8 in offline mode tries to download maven repository with version 2.0.7. Ultimately fails as 2.0.7 is not available in offline repository and internet is not available. > - Same project when built with JBDS 8.1 and java7 in offline mode with offline repository as above, is able to build successfully as 2.0.6 maven dependencies are already available in offline repo, thus no need to download. > - Why JBDS 9.0 is searching for maven dependencies with 2.0.7 version ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3844) JBDS 9 with java 8 tries to download maven dependencies with versin 2.0.7

by Chandra Shekhar Pandey (JIRA)

Chandra Shekhar Pandey created JBDS-3844: -------------------------------------------- Summary: JBDS 9 with java 8 tries to download maven dependencies with versin 2.0.7 Key: JBDS-3844 URL: https://issues.jboss.org/browse/JBDS-3844 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: build Affects Versions: 9.0.0.GA Environment: ALL Reporter: Chandra Shekhar Pandey - Testing in a offline environment with Fuse 6.2.1 offline repository from https://access.redhat.com/solutions/1599973. - A simple Fuse project when built within JBDS 9.0 GA with java8 in offline mode tries to download maven repository with version 2.0.7. Ultimately fails as 2.0.7 is not available in offline repository and internet is not available. - Same project when built with JBDS 8.1 and java7 in offline mode with offline repository as above, is able to build successfully as 2.0.6 maven dependencies are already available in offline repo, thus no need to download. - Why JBDS 9.0 is searching for maven dependencies with 2.0.7 version ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-626) Move common classes (Eclipse related not included in RedDeer) into org.jboss.tools.common.reddeer module

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-626?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-626. ----------------------------------- pushed > Move common classes (Eclipse related not included in RedDeer) into org.jboss.tools.common.reddeer module > -------------------------------------------------------------------------------------------------------- > > Key: JBTIS-626 > URL: https://issues.jboss.org/browse/JBTIS-626 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > For Example: > * TableHasRow > * JUnitHasFinished > * FileUtils > * ResourceHelper > * ... other utils classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-664) add TransformationToolsTest, refactor Criteria Builder, Expression builder, Reconciler

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-664?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-664. ----------------------------------- pushed > add TransformationToolsTest, refactor Criteria Builder, Expression builder, Reconciler > --------------------------------------------------------------------------------------- > > Key: JBTIS-664 > URL: https://issues.jboss.org/browse/JBTIS-664 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.0.Beta1, 4.2.6.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22221) Typo in New OpenShift 3 Adapter section

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22221: ------------------------------------- Summary: Typo in New OpenShift 3 Adapter section Key: JBIDE-22221 URL: https://issues.jboss.org/browse/JBIDE-22221 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.3.1.Final Reporter: Marián Labuda http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html... contains following sentence {code}From the OpenShift Explorer, right-click on a deployed Service a select the Server Adapter… menu: it will either create a new Server adapter or display one in the Servers view if it already exists.{code} there should be and instead of a (a deployed Service *and* select the) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3840) Installer: upgrade electon-packager to latest version (security fix)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3840?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3840: -------------------------------- Fix Version/s: 10.0.0.Alpha1 > Installer: upgrade electon-packager to latest version (security fix) > -------------------------------------------------------------------- > > Key: JBDS-3840 > URL: https://issues.jboss.org/browse/JBDS-3840 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Component Upgrade > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Priority: Critical > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > The version of electron-packager that we use doesn't check SSL certificates by default because of this issue \[1]. We should upgrade to latest version ASAP (now 7.0.0). > \[1] https://github.com/electron-userland/electron-packager/issues/333 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3841: -------------------------------- Affects Version/s: 9.1.0.GA (was: 9.x) > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3841: ----------------------------- > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3841: -------------------------------- > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3841: -------------------------------- Status: New (was: New) Target Release: 10.0.0.GA > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016