[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
[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
[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
[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
[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
[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