[JBoss JIRA] (JBTIS-918) additional features screen in standalone installer: s/location/feature
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-918?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-918.
-----------------------------------
Closed as a duplicate issue
> additional features screen in standalone installer: s/location/feature
> ----------------------------------------------------------------------
>
> Key: JBTIS-918
> URL: https://issues.jboss.org/browse/JBTIS-918
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: build
> Reporter: Misha Ali
> Assignee: Paul Leacu
> Attachments: devstudioIS.png
>
>
> Not sure if the component is correct, so please reassign if required. I was testing the standalone installer for documentation and notices that the features listed in the installer are under the title "location", which doesn't seem accurate in this context. Screenshot attached, logging a bug to fix this minor issue for a later release.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-984) Update info about Early Access components in RH Central
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-984?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-984:
------------------------------------
Description:
Devstudio 10.1.0.GA with the following VM args
-Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/devstudio-directory.xml
-Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/
-Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/
says that the Fuse tooling in on Early Access and is available in 9.x (EDIT: now I noticed that there is "Also available in 9.x" - do we need this?)
was:
Devstudio 10.1.0.GA with the following VM args
-Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/devstudio-directory.xml
-Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/
-Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/
says that the Fuse tooling in on Early Access and is available in 9.x
> Update info about Early Access components in RH Central
> -------------------------------------------------------
>
> Key: JBTIS-984
> URL: https://issues.jboss.org/browse/JBTIS-984
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: Devstudio IS 10.0.0.CR4
> Reporter: Andrej Podhradsky
> Attachments: devstudio-is-10.0.0.CR4-central.png
>
>
> Devstudio 10.1.0.GA with the following VM args
> -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/devstudio-directory.xml
> -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/
> -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/
> says that the Fuse tooling in on Early Access and is available in 9.x (EDIT: now I noticed that there is "Also available in 9.x" - do we need this?)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-984) Update info about Early Access components in RH Central
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-984:
---------------------------------------
Summary: Update info about Early Access components in RH Central
Key: JBTIS-984
URL: https://issues.jboss.org/browse/JBTIS-984
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: distribution
Affects Versions: 10.0.0.CR1
Environment: Devstudio IS 10.0.0.CR4
Reporter: Andrej Podhradsky
Attachments: devstudio-is-10.0.0.CR4-central.png
Devstudio 10.1.0.GA with the following VM args
-Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/devstudio-directory.xml
-Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/
-Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/
says that the Fuse tooling in on Early Access and is available in 9.x
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-911) Cannot install all features from the zip file in offline mode
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-911?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-911.
-----------------------------------
Verified with Devstudio IS 10.0.0.CR4
> Cannot install all features from the zip file in offline mode
> -------------------------------------------------------------
>
> Key: JBTIS-911
> URL: https://issues.jboss.org/browse/JBTIS-911
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.Alpha1
> Environment: RHDS 10.0.0.GA-v20160615-1853-B33
> RHDS-IS 10.0.0.Alpha1 EA zip file
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.0.0.GA
>
>
> Cannot install all features from the zip file, e.g. com.jboss.devstudio.integration-stack.bpr.feature.feature.group.
> Note that this feature is visible for users only if they uncheck 'Group items by category'. All features listed in categories (which are visible by default) can be installed without any problem.
> Here is the error if we try to install com.jboss.devstudio.integration-stack.bpr.feature.feature.group in offline mode
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220)
> Missing requirement: JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM6, Drools) 10.0.0.Alpha1-v20160913-1348-B220 (com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.0.0.Alpha1-v20160913-1348-B220) requires 'org.eclipse.rse.feature.group 0.0.0' but it could not be found
> {code}
> Issue is with the IS TP - need to import org.eclipse.rse from neon RC4
> *Reason:* Import org.eclipse.rse from neon RC4
> *Project page/sources:*
> *Version:* .3.3.0
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* Integration Stack
> *Include in JBDS:* Yes (devstudiois)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> === Summary ===
> [pleacu@pleacu-2-laptop x86_64]$ cat ~/temp/diff-tpea
> > org.eclipse.rse.core.feature.jar [3.7.1.201603211627]
> > org.eclipse.rse.doc.user [3.4.100.201403101646]
> > org.eclipse.rse.connectorservice.local [2.1.400.201403100950]
> > org.eclipse.rse.subsystems.processes.dstore [2.1.400.201403100950]
> > org.eclipse.dstore.core [3.4.0.201501311530]
> > org.eclipse.rse.importexport [1.2.300.201403100950]
> > org.eclipse.rse.processes.ui [3.0.400.201403100950]
> > org.eclipse.rse.subsystems.files.dstore [2.1.300.201403100950]
> > org.eclipse.rse.connectorservice.ssh [2.1.300.201505220524]
> > org.eclipse.rse.ui [3.3.200.201601281257]
> > org.eclipse.rse.connectorservice.dstore [3.1.301.201403100950]
> > org.eclipse.dstore.extra [2.1.400.201403100950]
> > org.eclipse.rse.subsystems.processes.core [3.1.300.201403100950]
> > org.eclipse.rse.ftp.feature.group [3.7.1.201603211627]
> > org.eclipse.rse.feature.group [3.7.1.201603211627]
> > org.eclipse.rse [3.5.0.201403100950]
> > org.eclipse.rse.dstore.feature.jar [3.7.0.201603211627]
> > org.eclipse.rse.ssh.feature.group [3.7.0.201603211627]
> > org.eclipse.rse.subsystems.files.core [3.3.1.201403100950]
> > org.eclipse.rse.subsystems.shells.local [2.1.400.201403100950]
> > org.eclipse.rse.local.feature.jar [3.7.0.201603211627]
> > org.eclipse.rse.subsystems.shells.dstore [2.1.400.201403100950]
> > org.eclipse.rse.subsystems.shells.telnet [1.2.300.201403100950]
> > org.eclipse.rse.services.local [2.2.1.201507180454]
> > org.eclipse.rse.files.ui [3.2.200.201507172213]
> > org.eclipse.rse.subsystems.processes.shell.linux [1.1.400.201403100950]
> > org.eclipse.rse.useractions.feature.jar [3.7.0.201603211627]
> > org.eclipse.rse.subsystems.files.local [2.1.300.201403251512]
> > org.eclipse.rse.services [3.3.0.201506120731]
> > org.eclipse.rse.subsystems.shells.ssh [2.1.400.201403100950]
> > org.eclipse.rse.ssh.feature.jar [3.7.0.201603211627]
> > org.eclipse.rse.dstore.security [3.0.400.201403100950]
> > org.eclipse.rse.core.feature.group [3.7.1.201603211627]
> > org.eclipse.rse.core [3.3.100.201603151753]
> > org.eclipse.rse.subsystems.files.ssh [2.1.300.201403100950]
> > org.eclipse.rse.ftp.feature.jar [3.7.1.201603211627]
> > org.eclipse.rse.subsystems.files.ftp [2.2.100.201601281414]
> > org.eclipse.rse.services.files.ftp [3.0.500.201403100950]
> > org.eclipse.rse.subsystems.processes.local [2.1.400.201403100950]
> > org.eclipse.rse.efs [2.1.401.201507172212]
> > org.eclipse.rse.shells.ui [3.0.500.201403271554]
> > org.eclipse.rse.telnet.feature.group [3.7.0.201603211627]
> > org.eclipse.rse.useractions.feature.group [3.7.0.201603211627]
> > org.eclipse.rse.dstore.feature.group [3.7.0.201603211627]
> > org.eclipse.rse.useractions [1.1.500.201403100950]
> > org.eclipse.rse.services.ssh [3.2.100.201403281521]
> > org.eclipse.rse.connectorservice.telnet [1.2.300.201505220524]
> > org.eclipse.rse.local.feature.group [3.7.0.201603211627]
> > org.apache.commons.net [3.2.0.v201305141515]
> > org.eclipse.rse.services.telnet [2.0.400.201403100950]
> > org.eclipse.rse.efs.ui [2.1.400.201403100950]
> > org.eclipse.rse.services.dstore [3.3.0.201406041609]
> > org.eclipse.rse.subsystems.shells.core [3.1.300.201403271554]
> > org.eclipse.rse.telnet.feature.jar [3.7.0.201603211627]
> > org.eclipse.rse.feature.jar [3.7.1.201603211627]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 55 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-23489:
------------------------------------
{quote}
(as hudson)
scl enable rh-eclipse46 bash
mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
{quote}
Hi [~nickboldt], this does not work either :/
> Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23489
> URL: https://issues.jboss.org/browse/JBIDE-23489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.2.AM3
> Reporter: Pavol Srna
> Fix For: 4.4.2.Final
>
>
> We need to find a way how to run automated tests agains devstudio rpm.
> I've tried the following paths:
> 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
> 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> But none of the above works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23490) Provide ability to link pods when no service is available
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-23490 at 11/15/16 3:56 AM:
-------------------------------------------------------------------
I don't see the link between the 2 issues.
The [JBIDE-21627] idea is to provide a way to expose whatever OpenShift resources user wants, here I'm asking to be able to bind an Openshift Server Adapter to a pod instead of a service.
was (Author: aurelien.pupier):
I don't see the link between the 2 issues.
The [JBIDE-21627] idea is to provide a way to create whatever OpenShift resources user wants, here I'm asking to be able to bind an Openshift Server Adapter to a pod instead of a service.
> Provide ability to link pods when no service is available
> ---------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy
> Fix For: 4.4.2.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a pod to deploy a new version.
> it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23490) Provide ability to link pods when no service is available
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-23490:
-----------------------------------------
I don't see the link between the 2 issues.
The [JBIDE-21627] idea is to provide a way to create whatever OpenShift resources user wants, here I'm asking to be able to bind an Openshift Server Adapter to a pod instead of a service.
> Provide ability to link pods when no service is available
> ---------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy
> Fix For: 4.4.2.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a pod to deploy a new version.
> it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months