[JBoss JIRA] (JBTIS-698) JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment.
by Jonathan Anstey (JIRA)
[ https://issues.jboss.org/browse/JBTIS-698?page=com.atlassian.jira.plugin.... ]
Jonathan Anstey commented on JBTIS-698:
---------------------------------------
Yeah, it's not related to tooling. the maven-bundle-plugin has a dependency on maven 2.0.7.
> JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment.
> --------------------------------------------------------------------------------------------------
>
> Key: JBTIS-698
> URL: https://issues.jboss.org/browse/JBTIS-698
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE
> Affects Versions: 9.0.0.GA
> Environment: ALL
> Reporter: Chandra Shekhar Pandey
> Assignee: Lars Heinemann
> Attachments: TestProjectin_JBDS9.zip
>
>
> - 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, 10 months
[JBoss JIRA] (JBDS-3934) Uninstall process results in odd things
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3934?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3934:
----------------------------------
Also please note that if your workflow is as follows you *can* uninstall a product but you must do a COLD restart (shut down devstudio entirely, not just restart it).
* Install Eclipse Neon.0 JavaEE bundle or equivalent
* Help > Install new > https://devstudio.jboss.com/10.0/staging/updates/ > uncheck "show only categorized items" > install the "Branded Product" feature
* COLD restart (shut down eclipse entirely and start it up again) rather than just restarting when prompted
* Help > About should now show you're running devstudio, not Eclipse
* Help > About > Install details > uninstall ... and remove devstudio
* COLD restart (shut down eclipse entirely and start it up again) rather than just restarting when prompted
* Now you should be back to running just Eclipse.
If on the other hand you installed from the installer .jar, there's no way to uninstall the product because there's no older product underneath to which to revert.
And if you install from the update site, Marketplace, or any other BYOE scenario that doesn't involve installing the hidden "Branded Product" feature, again, there's no product to uninstall so the best you can do is uninstall features that sit atop Eclipse.
> Uninstall process results in odd things
> ---------------------------------------
>
> Key: JBDS-3934
> URL: https://issues.jboss.org/browse/JBDS-3934
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 10.0.0.GA
> Environment: Fedora 23
> Reporter: Misha Ali
> Attachments: error.log, uninstall.png, uninstalled_but_running.png
>
>
> I've tried to uninstall devstudio 10 GA a few times and got odd results. I'm trying to replicate one of the odd results, so I'll talk about the really odd one I just encountered:
> 1. Uninstalling by selecting both the the eclipse test instance and devstudio 10 results in restarting devstudio but without these two components available to uninstall. Surely uninstall should just remove devstudio and then exit devstudio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3934) Uninstall process results in odd things
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3934?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3934:
---------------------------------
Component/s: upstream
> Uninstall process results in odd things
> ---------------------------------------
>
> Key: JBDS-3934
> URL: https://issues.jboss.org/browse/JBDS-3934
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 10.0.0.GA
> Environment: Fedora 23
> Reporter: Misha Ali
> Attachments: error.log, uninstall.png, uninstalled_but_running.png
>
>
> I've tried to uninstall devstudio 10 GA a few times and got odd results. I'm trying to replicate one of the odd results, so I'll talk about the really odd one I just encountered:
> 1. Uninstalling by selecting both the the eclipse test instance and devstudio 10 results in restarting devstudio but without these two components available to uninstall. Surely uninstall should just remove devstudio and then exit devstudio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22570) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22570?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22570:
------------------------------------
Since master branch is still for 4.4.1 / Neon.1, are you sure you wanted to bump your minor version rather than your service version? I would have expected 3.1.1 rather than 3.2.0, etc.
> For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central]
> ----------------------------------------------------------
>
> Key: JBIDE-22570
> URL: https://issues.jboss.org/browse/JBIDE-22570
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Affects Versions: 4.4.1.Alpha1
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Alpha1
>
>
> For JBIDE 4.4.1.Alpha1 [Central]: Please perform the following tasks:
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22575) Extract CDK's Docker registry from vagrant service-manager env
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22575?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22575:
-----------------------------------
Fix Version/s: 4.4.0.Final
> Extract CDK's Docker registry from vagrant service-manager env
> --------------------------------------------------------------
>
> Key: JBIDE-22575
> URL: https://issues.jboss.org/browse/JBIDE-22575
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441).
> With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK:
> {quote}
> vagrant service-manager env
> # docker env:
> # Set the following environment variables to enable access to the
> # docker daemon running inside of the vagrant virtual machine:
> export DOCKER_HOST=tcp://10.1.2.2:2376
> export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> export DOCKER_TLS_VERIFY=1
> export DOCKER_API_VERSION=1.21
> # openshift env:
> # You can access the OpenShift console on: https://10.1.2.2:8443/console
> # To use OpenShift CLI, run: oc login https://10.1.2.2:8443
> export OPENSHIFT_URL=https://10.1.2.2:8443
> export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console
> export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io
> {quote}
> We should store the docker registry with a https:// prefix, if the value is not a URL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22575) Extract CDK's Docker registry from vagrant service-manager env
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22575?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22575:
-----------------------------------
Labels: respin-a (was: )
> Extract CDK's Docker registry from vagrant service-manager env
> --------------------------------------------------------------
>
> Key: JBIDE-22575
> URL: https://issues.jboss.org/browse/JBIDE-22575
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441).
> With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK:
> {quote}
> vagrant service-manager env
> # docker env:
> # Set the following environment variables to enable access to the
> # docker daemon running inside of the vagrant virtual machine:
> export DOCKER_HOST=tcp://10.1.2.2:2376
> export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> export DOCKER_TLS_VERIFY=1
> export DOCKER_API_VERSION=1.21
> # openshift env:
> # You can access the OpenShift console on: https://10.1.2.2:8443/console
> # To use OpenShift CLI, run: oc login https://10.1.2.2:8443
> export OPENSHIFT_URL=https://10.1.2.2:8443
> export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console
> export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io
> {quote}
> We should store the docker registry with a https:// prefix, if the value is not a URL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22575) Extract CDK's Docker registry from vagrant service-manager env
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22575?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22575:
-------------------------------------
the hard coded url would still be used by default when no DOCKER-REGISTRY is exposed by the service-manager (i.e CDK 2.0)
> Extract CDK's Docker registry from vagrant service-manager env
> --------------------------------------------------------------
>
> Key: JBIDE-22575
> URL: https://issues.jboss.org/browse/JBIDE-22575
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Assignee: Rob Stryker
>
> The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441).
> With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK:
> {quote}
> vagrant service-manager env
> # docker env:
> # Set the following environment variables to enable access to the
> # docker daemon running inside of the vagrant virtual machine:
> export DOCKER_HOST=tcp://10.1.2.2:2376
> export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> export DOCKER_TLS_VERIFY=1
> export DOCKER_API_VERSION=1.21
> # openshift env:
> # You can access the OpenShift console on: https://10.1.2.2:8443/console
> # To use OpenShift CLI, run: oc login https://10.1.2.2:8443
> export OPENSHIFT_URL=https://10.1.2.2:8443
> export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console
> export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io
> {quote}
> We should store the docker registry with a https:// prefix, if the value is not a URL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22575) Extract CDK's Docker registry from vagrant service-manager env
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22575?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-22575 at 6/8/16 9:22 AM:
-------------------------------------------------------------
the hard coded url would still be used by default when no DOCKER_REGISTRY is exposed by the service-manager (i.e CDK 2.0)
was (Author: fbricon):
the hard coded url would still be used by default when no DOCKER-REGISTRY is exposed by the service-manager (i.e CDK 2.0)
> Extract CDK's Docker registry from vagrant service-manager env
> --------------------------------------------------------------
>
> Key: JBIDE-22575
> URL: https://issues.jboss.org/browse/JBIDE-22575
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Assignee: Rob Stryker
>
> The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441).
> With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK:
> {quote}
> vagrant service-manager env
> # docker env:
> # Set the following environment variables to enable access to the
> # docker daemon running inside of the vagrant virtual machine:
> export DOCKER_HOST=tcp://10.1.2.2:2376
> export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> export DOCKER_TLS_VERIFY=1
> export DOCKER_API_VERSION=1.21
> # openshift env:
> # You can access the OpenShift console on: https://10.1.2.2:8443/console
> # To use OpenShift CLI, run: oc login https://10.1.2.2:8443
> export OPENSHIFT_URL=https://10.1.2.2:8443
> export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console
> export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io
> {quote}
> We should store the docker registry with a https:// prefix, if the value is not a URL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-729) Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-729?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-729:
----------------------------------
[~maxandersen] - good point Max - Birt itself references org.eclipse.core.runtime.compatibility
https://bugs.eclipse.org/bugs/show_bug.cgi?id=483950
That appears to have been fixed last Feb for Neon. Don't know if TD references it independently.
Ref:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=394739
> Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists
> ---------------------------------------------------------------------------
>
> Key: JBTIS-729
> URL: https://issues.jboss.org/browse/JBTIS-729
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform, teiid
> Affects Versions: 4.4.0.Alpha1-TP, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Barry LaFond
> Fix For: 4.4.0.Alpha1-TP
>
>
> org.eclipse.core.runtime.compatibility was removed from the JBT and devstudio target platforms because nothing in JBT/devstudio requires it any more.
> As a result, when you try to install Teiid Designer into the staged JBT 4.4.0.Final or devstudio 10.0.0.GA via Central, you get this error:
> {code}
> !MESSAGE Missing requirement: Teiid DataTools Connectivity 10.0.0.Beta3-v20160218-1807-B4076 (org.teiid.datatools.connectivity.feature.feature.group 10.0.0.Beta3-v20160218-1807-B4076) requires 'org.eclipse.core.runtime.compatibility [3.2.200,4.0.0)' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22575) Extract CDK's Docker registry from vagrant service-manager env
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22575?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22575:
-----------------------------------
Assignee: Rob Stryker
> Extract CDK's Docker registry from vagrant service-manager env
> --------------------------------------------------------------
>
> Key: JBIDE-22575
> URL: https://issues.jboss.org/browse/JBIDE-22575
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Assignee: Rob Stryker
>
> The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441).
> With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK:
> {quote}
> vagrant service-manager env
> # docker env:
> # Set the following environment variables to enable access to the
> # docker daemon running inside of the vagrant virtual machine:
> export DOCKER_HOST=tcp://10.1.2.2:2376
> export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> export DOCKER_TLS_VERIFY=1
> export DOCKER_API_VERSION=1.21
> # openshift env:
> # You can access the OpenShift console on: https://10.1.2.2:8443/console
> # To use OpenShift CLI, run: oc login https://10.1.2.2:8443
> export OPENSHIFT_URL=https://10.1.2.2:8443
> export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console
> export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io
> {quote}
> We should store the docker registry with a https:// prefix, if the value is not a URL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months