[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:
-----------------------------------------
Steps to Reproduce:
- Download offline repository from https://access.redhat.com/solutions/1599973.
- Run attached simple project with JBDS9 and java8 in offline environment.
- It try to download maven dependencies with version 2.0.7, ideally it should not as we are using offline repository.
- In offline environment, following error is received while building project:
{code}
Unresolveable build extension: Plugin org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-model:jar:2.0.7, org.apache.maven:maven-project:jar:2.0.7, org.apache.maven:maven-plugin-registry:jar:2.0.7, org.apache.maven:maven-plugin-api:jar:2.0.7: Could not transfer artifact org.apache.maven:maven-model:jar:2.0.7 from/to release.fusesource.org (http://repo.fusesource.com/nexus/content/repositories/releases): repo.fusesource.com: unknown error: Unknown host repo.fusesource.com: unknown error -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 8, column 14
{code}
- I checked in a system with internet availability and found that it tries to download following maven dependency:
{code}
[root@dhcp3-200 maven]# cd /home/cpandey/.m2/repository/org/apache/maven/maven-project/2.0.7/
[root@dhcp3-200 2.0.7]# ls -ltr
total 132
-rw-r--r--. 1 cpandey cpandey 40 Jun 4 2009 maven-project-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 2637 Jun 4 2009 maven-project-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 116546 Apr 20 12:05 maven-project-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-project-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 166 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 104
-rw-r--r--. 1 cpandey cpandey 40 Jun 8 2009 maven-model-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 3047 Jun 8 2009 maven-model-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 86438 Apr 20 12:05 maven-model-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-model-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 164 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 48
-rw-r--r--. 1 cpandey cpandey 40 Jun 8 2009 maven-plugin-registry-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 1946 Jun 8 2009 maven-plugin-registry-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 28925 Apr 20 12:05 maven-plugin-registry-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-plugin-registry-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 174 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 32
-rw-r--r--. 1 cpandey cpandey 40 Nov 16 2009 maven-plugin-api-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 1455 Nov 16 2009 maven-plugin-api-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 12860 Apr 20 12:05 maven-plugin-api-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-plugin-api-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 169 Apr 20 12:05 _remote.repositories
{code}
- When checked with JBDS 8.1 and java7, I don't see these jar getting download and build is successful.
was:
- Download offline repository from https://access.redhat.com/solutions/1599973.
- Run attached simple project with JBDS9 and java8 in offline environment.
- It try to download maven dependencies with version 2.0.7, ideally it should not as we are using offline repository.
- In offline environment, following error is received while building project:
~~~
Unresolveable build extension: Plugin org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-model:jar:2.0.7, org.apache.maven:maven-project:jar:2.0.7, org.apache.maven:maven-plugin-registry:jar:2.0.7, org.apache.maven:maven-plugin-api:jar:2.0.7: Could not transfer artifact org.apache.maven:maven-model:jar:2.0.7 from/to release.fusesource.org (http://repo.fusesource.com/nexus/content/repositories/releases): repo.fusesource.com: unknown error: Unknown host repo.fusesource.com: unknown error -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 8, column 14
~~~
- I checked in a system with internet availability and found that it tries to download following maven dependency:
{code}
[root@dhcp3-200 maven]# cd /home/cpandey/.m2/repository/org/apache/maven/maven-project/2.0.7/
[root@dhcp3-200 2.0.7]# ls -ltr
total 132
-rw-r--r--. 1 cpandey cpandey 40 Jun 4 2009 maven-project-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 2637 Jun 4 2009 maven-project-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 116546 Apr 20 12:05 maven-project-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-project-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 166 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 104
-rw-r--r--. 1 cpandey cpandey 40 Jun 8 2009 maven-model-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 3047 Jun 8 2009 maven-model-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 86438 Apr 20 12:05 maven-model-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-model-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 164 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 48
-rw-r--r--. 1 cpandey cpandey 40 Jun 8 2009 maven-plugin-registry-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 1946 Jun 8 2009 maven-plugin-registry-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 28925 Apr 20 12:05 maven-plugin-registry-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-plugin-registry-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 174 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 32
-rw-r--r--. 1 cpandey cpandey 40 Nov 16 2009 maven-plugin-api-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 1455 Nov 16 2009 maven-plugin-api-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 12860 Apr 20 12:05 maven-plugin-api-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-plugin-api-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 169 Apr 20 12:05 _remote.repositories
{code}
- When checked with JBDS 8.1 and java7, I don't see these jar getting download and build is successful.
> 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 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:
-----------------------------------------
Steps to Reproduce:
- Download offline repository from https://access.redhat.com/solutions/1599973.
- Run attached simple project with JBDS9 and java8 in offline environment.
- It try to download maven dependencies with version 2.0.7, ideally it should not as we are using offline repository.
- In offline environment, following error is received while building project:
~~~
Unresolveable build extension: Plugin org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-model:jar:2.0.7, org.apache.maven:maven-project:jar:2.0.7, org.apache.maven:maven-plugin-registry:jar:2.0.7, org.apache.maven:maven-plugin-api:jar:2.0.7: Could not transfer artifact org.apache.maven:maven-model:jar:2.0.7 from/to release.fusesource.org (http://repo.fusesource.com/nexus/content/repositories/releases): repo.fusesource.com: unknown error: Unknown host repo.fusesource.com: unknown error -> [Help 2]
[ERROR] Unknown packaging: bundle @ line 8, column 14
~~~
- I checked in a system with internet availability and found that it tries to download following maven dependency:
{code}
[root@dhcp3-200 maven]# cd /home/cpandey/.m2/repository/org/apache/maven/maven-project/2.0.7/
[root@dhcp3-200 2.0.7]# ls -ltr
total 132
-rw-r--r--. 1 cpandey cpandey 40 Jun 4 2009 maven-project-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 2637 Jun 4 2009 maven-project-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 116546 Apr 20 12:05 maven-project-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-project-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 166 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 104
-rw-r--r--. 1 cpandey cpandey 40 Jun 8 2009 maven-model-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 3047 Jun 8 2009 maven-model-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 86438 Apr 20 12:05 maven-model-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-model-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 164 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 48
-rw-r--r--. 1 cpandey cpandey 40 Jun 8 2009 maven-plugin-registry-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 1946 Jun 8 2009 maven-plugin-registry-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 28925 Apr 20 12:05 maven-plugin-registry-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-plugin-registry-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 174 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 32
-rw-r--r--. 1 cpandey cpandey 40 Nov 16 2009 maven-plugin-api-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 1455 Nov 16 2009 maven-plugin-api-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 12860 Apr 20 12:05 maven-plugin-api-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-plugin-api-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 169 Apr 20 12:05 _remote.repositories
{code}
- When checked with JBDS 8.1 and java7, I don't see these jar getting download and build is successful.
was:
- Download offline repository from https://access.redhat.com/solutions/1599973.
- Run attached simple project with JBDS9 and java8 in offline environment.
- It try to download maven dependencies with version 2.0.7, ideally it should not as we are using offline repository.
- I checked in a system with internet availability and found that it tries to download following maven dependency:
{code}
[root@dhcp3-200 maven]# cd /home/cpandey/.m2/repository/org/apache/maven/maven-project/2.0.7/
[root@dhcp3-200 2.0.7]# ls -ltr
total 132
-rw-r--r--. 1 cpandey cpandey 40 Jun 4 2009 maven-project-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 2637 Jun 4 2009 maven-project-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 116546 Apr 20 12:05 maven-project-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-project-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 166 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 104
-rw-r--r--. 1 cpandey cpandey 40 Jun 8 2009 maven-model-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 3047 Jun 8 2009 maven-model-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 86438 Apr 20 12:05 maven-model-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-model-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 164 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 48
-rw-r--r--. 1 cpandey cpandey 40 Jun 8 2009 maven-plugin-registry-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 1946 Jun 8 2009 maven-plugin-registry-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 28925 Apr 20 12:05 maven-plugin-registry-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-plugin-registry-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 174 Apr 20 12:05 _remote.repositories
[root@dhcp3-200 2.0.7]# ls -ltr
total 32
-rw-r--r--. 1 cpandey cpandey 40 Nov 16 2009 maven-plugin-api-2.0.7.pom.sha1
-rw-r--r--. 1 cpandey cpandey 1455 Nov 16 2009 maven-plugin-api-2.0.7.pom
-rw-rw-r--. 1 cpandey cpandey 12860 Apr 20 12:05 maven-plugin-api-2.0.7.jar
-rw-rw-r--. 1 cpandey cpandey 40 Apr 20 12:05 maven-plugin-api-2.0.7.jar.sha1
-rw-rw-r--. 1 cpandey cpandey 169 Apr 20 12:05 _remote.repositories
{code}
- When checked with JBDS 8.1 and java7, I don't see these jar getting download and build is successful.
> 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-3845) Copyright notice refers to 2015, not 2016
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-3845?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier updated JBDS-3845:
----------------------------------
Description: It is the same issue, two years in a row, maybe we can put a test in place to check the year? Or automate the replacement at build time?
> Copyright notice refers to 2015, not 2016
> -----------------------------------------
>
> Key: JBDS-3845
> URL: https://issues.jboss.org/browse/JBDS-3845
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 9.1.0.GA
> Reporter: Aurélien Pupier
> Attachments: screenshot-1.png
>
>
> It is the same issue, two years in a row, maybe we can put a test in place to check the year? Or automate the replacement at build time?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22210) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Playground]
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22210?page=com.atlassian.jira.plugi... ]
Mickael Istria closed JBIDE-22210.
----------------------------------
Resolution: Rejected
One of the commits was ported to branch, other ones are specific to master branch.
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Playground]
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22210
> URL: https://issues.jboss.org/browse/JBIDE-22210
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: playground
> Reporter: Rob Stryker
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Playground]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-playground at https://github.com/jbosstools/jbosstools-playground/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "476620" is the last common ancestor of jbosstools-4.3.x and master
> 476620 is 4 commits ago in branch master
> 476620 is 8 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-playground//commit/c97d38ca3d141...
> - https://github.com/jbosstools/jbosstools-playground//commit/c6e3153a43e7c...
> - https://github.com/jbosstools/jbosstools-playground//commit/15c2c008ae837...
> - https://github.com/jbosstools/jbosstools-playground//commit/c82b4104d8df7...
> - https://github.com/jbosstools/jbosstools-playground//commit/16de3723185fd...
> - https://github.com/jbosstools/jbosstools-playground//commit/9758d0bfd73a8...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Playground task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22201?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-22201:
-------------------------------------------
{quote}
You indicate that simply pasting the url into a browser shows the URL is available, so maybe it's the case that it wasn't available when we first try to make the connection?
{quote}
That would be my guess as well.
{quote}
As I understood it, /healthz should be 100% available once the vagrant up command completes.
{quote}
That's not quite right. First of all, _vagrant up_ needs to complete without error. It can also exit with an error code due to some provisioning steps not completing. In this case OpenShift might not be up and neither is the health URL reachable. What can be said though is, that if the health URL is reachable, OpenShift is up and running. In fact the OpenShift service startup scripts in the CDK itself use the health URL to wait for Opensift to successfully start.
So provided there is no bug in the service startup scripts and _vagrant up_ returns with an exit code of 0, the health URL should indeed be reachable.
{quote}
I was told that absolutely nothing done during vagrant up is asynchronous
{quote}
That's correct.
{quote}
or, /healthz did return but did not return "ok".
{quote}
BTW, technically I don't think it is the "ok" one should check, but the HTTP return code. It needs to be 200, everything else should be considered an error.
> Error contacting OpenShift after CDK is started
> -----------------------------------------------
>
> Key: JBIDE-22201
> URL: https://issues.jboss.org/browse/JBIDE-22201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
>
> Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
> {code}
> Error contacting OpenShift
> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
> {code}
> When you actually copy&paste that url into a browser, you will get "ok".
> This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora 22).
--
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 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 versin 2.0.7 in offline environment. (was: JBDS 9 with java 8 tries to download maven dependencies with versin 2.0.7)
> JBDS 9 with java 8 tries to download maven dependencies with versin 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