[JBoss JIRA] (JBDS-3296) P2 reports several locations without repositories in case product installed on different device from user home directory
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3296?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3296:
-----------------------------
Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-website/pull/163
I think the problem is that I *thought* we had removed all refs to these but maybe this user is running an older pre-GA release, or has an older version of the discovery plugin cached locally.
Anyway, I've recreated the 8.0-development/central/core/ and 8.0/central/core/ folders as composites which point to ../../ so they'll exist and need no maintenance.
For 9.0.0 we will simply remove these entirely, along with the refactoring in JBDS-3208.
> P2 reports several locations without repositories in case product installed on different device from user home directory
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3296
> URL: https://issues.jboss.org/browse/JBDS-3296
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: p2-product
> Affects Versions: 8.0.0.GA, 8.0.1.GA
> Reporter: Denis Golovin
> Fix For: 8.0.1.GA
>
>
> {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0-development/central/core/.
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
> at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
> at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0/central/core/.
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
> at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
> at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (JBDS-3296) P2 reports several locations without repositories in case product installed on different device from user home directory
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3296?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3296:
--------------------------------
Assignee: Nick Boldt
> P2 reports several locations without repositories in case product installed on different device from user home directory
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3296
> URL: https://issues.jboss.org/browse/JBDS-3296
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: p2-product
> Affects Versions: 8.0.0.GA, 8.0.1.GA
> Reporter: Denis Golovin
> Assignee: Nick Boldt
> Fix For: 8.0.1.GA
>
>
> {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0-development/central/core/.
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
> at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
> at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0/central/core/.
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
> at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
> at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (JBDS-3296) P2 reports several locations without repositories in case product installed on different device from user home directory
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3296?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3296:
-----------------------------
Fix Version/s: 8.0.1.GA
> P2 reports several locations without repositories in case product installed on different device from user home directory
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3296
> URL: https://issues.jboss.org/browse/JBDS-3296
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: p2-product
> Affects Versions: 8.0.0.GA, 8.0.1.GA
> Reporter: Denis Golovin
> Assignee: Nick Boldt
> Fix For: 8.0.1.GA
>
>
> {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0-development/central/core/.
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
> at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
> at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0/central/core/.
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
> at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
> at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (JBTIS-376) Update IS site category definitions to include separate Fuse selection.
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-376:
--------------------------------
Summary: Update IS site category definitions to include separate Fuse selection.
Key: JBTIS-376
URL: https://issues.jboss.org/browse/JBTIS-376
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: distribution
Affects Versions: 8.0.0.Beta2, 4.2.0.Alpha2
Reporter: Paul Leacu
Assignee: Paul Leacu
JBoss Central and (soon) Eclipse MarketPlace will have a separate selectable Fuse tooling category. Update the p2 site category defintion as well.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (JBDS-3188) Support of krb5-principal keys in openshift-java-client (eclipse)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3188?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim edited comment on JBDS-3188 at 12/17/14 10:40 AM:
-------------------------------------------------------------------
One needs to add the kerberos key to OpenShift via a key type *krb5-principal* as one can see when querying our internal OSE instance:
{code:sh}
curl -k -H "Accept: application/json; version=1.2" --user adietish:XXXXX https://console.itos.redhat.com/broker/rest/user/ -X GET --proxy http://file.rdu.redhat.com:3128 | json_reformat
{code}
{code:javascript}
"ADD_KEY": {
"href": "https://console.itos.redhat.com/broker/rest/user/keys",
"method": "POST",
"optional_params": [
],
"rel": "Add new SSH key",
"required_params": [
{
"description": "Name of the key",
"invalid_options": [
],
"name": "name",
"type": "string",
"valid_options": [
]
},
{
"description": "Type of Key",
"invalid_options": [
],
"name": "type",
"type": "string",
"valid_options": [
"ssh-rsa",
"ssh-dss",
"ssh-rsa-cert-v01(a)openssh.com",
"ssh-dss-cert-v01(a)openssh.com",
"ssh-rsa-cert-v00(a)openssh.com",
"ssh-dss-cert-v00(a)openssh.com",
"krb5-principal"
]
{code}
was (Author: adietish):
One needs to add the kerberos key to OpenShift via a key type *krb5-principal* as one can see when querying our internal OSE instance:
{code:sh}
curl -k -H "Accept: application/json; version=1.2" --user adietish:XXXXX https://console.itos.redhat.com/broker/rest/user/ -X GET --proxy http://file.rdu.redhat.com:3128 | json_reformat | less
{code}
{code:javascript}
"ADD_KEY": {
"href": "https://console.itos.redhat.com/broker/rest/user/keys",
"method": "POST",
"optional_params": [
],
"rel": "Add new SSH key",
"required_params": [
{
"description": "Name of the key",
"invalid_options": [
],
"name": "name",
"type": "string",
"valid_options": [
]
},
{
"description": "Type of Key",
"invalid_options": [
],
"name": "type",
"type": "string",
"valid_options": [
"ssh-rsa",
"ssh-dss",
"ssh-rsa-cert-v01(a)openssh.com",
"ssh-dss-cert-v01(a)openssh.com",
"ssh-rsa-cert-v00(a)openssh.com",
"ssh-dss-cert-v00(a)openssh.com",
"krb5-principal"
]
{code}
> Support of krb5-principal keys in openshift-java-client (eclipse)
> ------------------------------------------------------------------
>
> Key: JBDS-3188
> URL: https://issues.jboss.org/browse/JBDS-3188
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 8.0.x
> Reporter: Christos Triantafyllidis
> Assignee: Max Rydahl Andersen
>
> The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys.
> This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication.
> https://github.com/openshift/openshift-java-client/blob/master/src/main/j...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (JBDS-3188) Support of krb5-principal keys in openshift-java-client (eclipse)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3188?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim edited comment on JBDS-3188 at 12/17/14 10:40 AM:
-------------------------------------------------------------------
One needs to add the kerberos key to OpenShift via a key type *krb5-principal* as one can see when querying our internal OSE instance:
{code:sh}
curl -k -H "Accept: application/json; version=1.2" --user adietish:XXXXX https://console.itos.redhat.com/broker/rest/user/ -X GET --proxy http://file.rdu.redhat.com:3128 | json_reformat | less
{code}
{code:javascript}
"ADD_KEY": {
"href": "https://console.itos.redhat.com/broker/rest/user/keys",
"method": "POST",
"optional_params": [
],
"rel": "Add new SSH key",
"required_params": [
{
"description": "Name of the key",
"invalid_options": [
],
"name": "name",
"type": "string",
"valid_options": [
]
},
{
"description": "Type of Key",
"invalid_options": [
],
"name": "type",
"type": "string",
"valid_options": [
"ssh-rsa",
"ssh-dss",
"ssh-rsa-cert-v01(a)openssh.com",
"ssh-dss-cert-v01(a)openssh.com",
"ssh-rsa-cert-v00(a)openssh.com",
"ssh-dss-cert-v00(a)openssh.com",
"krb5-principal"
]
{code}
was (Author: adietish):
One needs to add the kerberos key to OpenShift via a key type *krb5-principal* as one can see when querying our internal OSE instance:
{code:sh}
curl -k -H "Accept: application/json; version=1.2" --user adietish:1q5T9o3E$ https://console.itos.redhat.com/broker/rest/user/ -X GET --proxy http://file.rdu.redhat.com:3128 | json_reformat | less
{code}
{code:javascript}
"rel": "Update SSH key",
"required_params": [
{
"description": "Type of Key",
"invalid_options": [
],
"name": "type",
"type": "string",
"valid_options": [
"ssh-rsa",
"ssh-dss",
"ssh-rsa-cert-v01(a)openssh.com",
"ssh-dss-cert-v01(a)openssh.com",
"ssh-rsa-cert-v00(a)openssh.com",
"ssh-dss-cert-v00(a)openssh.com",
"krb5-principal"
]
},
{code}
> Support of krb5-principal keys in openshift-java-client (eclipse)
> ------------------------------------------------------------------
>
> Key: JBDS-3188
> URL: https://issues.jboss.org/browse/JBDS-3188
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 8.0.x
> Reporter: Christos Triantafyllidis
> Assignee: Max Rydahl Andersen
>
> The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys.
> This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication.
> https://github.com/openshift/openshift-java-client/blob/master/src/main/j...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-355:
----------------------------------
Built, tested and pushed https://github.com/jbosstools/jbosstools-integration-stack/pull/265 - 4 new wrapper features available for Eclipse Marketplace. DV is currently scheduled to go GA at the end of January.
> Enable JBDSIS Marketplace entry or entries for product groupings - Luna
> -----------------------------------------------------------------------
>
> Key: JBTIS-355
> URL: https://issues.jboss.org/browse/JBTIS-355
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Attachments: jbtis355.png
>
>
> * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210
> ** include this in com.jboss.devstudio.core.feature instead of the plugin?
> * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290
> * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358
> (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (JBDS-3188) Support of krb5-principal keys in openshift-java-client (eclipse)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3188?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim edited comment on JBDS-3188 at 12/17/14 10:32 AM:
-------------------------------------------------------------------
One needs to add the kerberos key to OpenShift via a key type *krb5-principal* as one can see when querying our internal OSE instance:
{code:sh}
curl -k -H "Accept: application/json; version=1.2" --user adietish:1q5T9o3E$ https://console.itos.redhat.com/broker/rest/user/ -X GET --proxy http://file.rdu.redhat.com:3128 | json_reformat | less
{code}
{code:javascript}
"rel": "Update SSH key",
"required_params": [
{
"description": "Type of Key",
"invalid_options": [
],
"name": "type",
"type": "string",
"valid_options": [
"ssh-rsa",
"ssh-dss",
"ssh-rsa-cert-v01(a)openssh.com",
"ssh-dss-cert-v01(a)openssh.com",
"ssh-rsa-cert-v00(a)openssh.com",
"ssh-dss-cert-v00(a)openssh.com",
"krb5-principal"
]
},
{code}
was (Author: adietish):
One needs to add the kerberos key to OpenShift via a key type "krb5-principal" as one can see here: http://www.openshift.org/documentation/rest_api/key-response-addnewsshkey...
{code:javascript}
"rel": "Update SSH key",
"required_params": [
{
"description": "Type of Key",
"invalid_options": [
],
"name": "type",
"type": "string",
"valid_options": [
"ssh-rsa",
"ssh-dss",
"ssh-rsa-cert-v01(a)openssh.com",
"ssh-dss-cert-v01(a)openssh.com",
"ssh-rsa-cert-v00(a)openssh.com",
"ssh-dss-cert-v00(a)openssh.com",
"krb5-principal"
]
},
{code}
> Support of krb5-principal keys in openshift-java-client (eclipse)
> ------------------------------------------------------------------
>
> Key: JBDS-3188
> URL: https://issues.jboss.org/browse/JBDS-3188
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 8.0.x
> Reporter: Christos Triantafyllidis
> Assignee: Max Rydahl Andersen
>
> The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys.
> This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication.
> https://github.com/openshift/openshift-java-client/blob/master/src/main/j...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months