[JBoss JIRA] (JBDS-3373) Remove org.eclipse.jst.server.generic.jonas plugin from JBDS
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3373?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3373:
--------------------------------
> Remove org.eclipse.jst.server.generic.jonas plugin from JBDS
> ------------------------------------------------------------
>
> Key: JBDS-3373
> URL: https://issues.jboss.org/browse/JBDS-3373
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: updatesite
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 9.0.0.Beta1
>
>
> com.jboss.devstudio.core.feature/feature.xml declares
> {quote}
> <import plugin="org.eclipse.jst.server.generic.jonas"/>
> {quote}
> I can't see *any* reason why we'd do that in 2015.
> [~burrsutter], [~ldimaggio], [~maxandersen] : is there any client requirement about JOnAS support?
> [~rob.stryker] does WTP require that plugin in any way?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3450 at 6/3/15 6:41 PM:
----------------------------------------------------------
When I pick the first option here, *Default java*:
!jbds-installer_step4-jvm-selection.png!
I end up with this in my jbdevstudio.ini:
{code}-vm
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
{code}
So... that's definitely problem. Need to remove that from the .ini file when Default is selected.
was (Author: nickboldt):
When I pick the first option here:
!jbds-installer_step4-jvm-selection.png!
I end up with this in my jbdevstudio.ini:
{code}-vm
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
{code}
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Fix For: 9.0.0.Beta2
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3450:
--------------------------------
Assignee: Nick Boldt
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Beta2
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3450:
-----------------------------
Attachment: jbds-installer_step4-jvm-selection.png
When I pick the first option here:
!jbds-installer_step4-jvm-selection.png!
I end up with this in my jbdevstudio.ini:
{code}-vm
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
{code}
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Fix For: 9.0.0.Beta2
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19848) Include Eclipse Docker Tooling in the Target Platforms
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19848?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19848:
------------------------------------
org.eclipse.linuxtools.docker.feature is now in JBT aggregate site, in the CoreTools and GeneralTools categories [1], [2].
[1] https://github.com/jbosstools/jbosstools-build-sites/commit/d03a971be26c3...
[2] http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/al...
But I believe [~maxandersen] wanted it in the same categories as the OpenShift tooling, which would be CoreTools and CloudTools ?
> Include Eclipse Docker Tooling in the Target Platforms
> ------------------------------------------------------
>
> Key: JBIDE-19848
> URL: https://issues.jboss.org/browse/JBIDE-19848
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker, target-platform
> Affects Versions: 4.3.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> *Reason:* Include Eclipse Docker Tooling in JBoss Tools and Dev Studio
> *Project page/sources:* http://eclipse.org/linuxtools
> *Version:* 4.0.0
> *License and owner:* EPL
> *Original p2 repo:* http://download.eclipse.org/linuxtools/updates-docker-nightly/
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/docker/1.0.0.20... (from https://github.com/jbosstools/jbosstools-download.jboss.org/pull/526 )
> *Include Sources:* Yes
> *Affected projects:* Docker tooling should be installable from JBoss Tools update site and should be part of DevStudio
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> see https://github.com/jbosstools/jbosstools-target-platforms/pull/149
> mistria@mistria-laptop:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... file:$(pwd)/target/jbosstools-multiple.target.repo
> > com.fasterxml.jackson.jaxrs.jackson-jaxrs-base [2.5.0.v201504171603]
> > javassist [3.13.0.GA_v201209210905]
> > com.fasterxml.jackson.core.jackson-databind [2.5.0.v201504151636]
> > org.glassfish.hk2.osgi-resource-locator [2.3.0.b10_201505192201]
> > org.eclipse.linuxtools.docker.feature.feature.jar [1.0.0.201506030402]
> > org.objectweb.asm [4.0.0.v201302062210]
> > org.glassfish.jersey.core.jersey-common [2.14.0.v201504171603]
> > org.bouncycastle.bcpkix [1.51.0.v201505131810]
> > org.eclipse.linuxtools.docker.feature.feature.group [1.0.0.201506030402]
> > org.glassfish.hk2.locator [2.3.0.b10_201505192201]
> > jnr.ffi [2.0.1.v201505052040]
> > jnr.x86asm [1.0.2.v201505052040]
> > com.kenai.jffi [1.2.7.v201505052040]
> > com.spotify.docker.client [2.7.18.v201505131810]
> > jnr.constants [0.8.6.v201505052040]
> > org.glassfish.jersey.bundles.repackaged.jersey-guava [2.14.0.v201504151636]
> > org.eclipse.linuxtools.docker.docs [1.0.0.201506030402]
> > com.fasterxml.jackson.datatype.jackson-datatype-guava [2.5.0.v201504151636]
> > org.eclipse.linuxtools.docker.core [1.0.0.201506030402]
> > org.glassfish.hk2.utils [2.3.0.b10_201505192201]
> > com.fasterxml.jackson.core.jackson-annotations [2.5.0.v201504151636]
> > org.bouncycastle.bcprov [1.51.0.v201505131810]
> > com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider [2.5.0.v201504171603]
> > jnr.posix [3.0.9.v201505052040]
> > org.glassfish.hk2.api [2.3.0.b10_201505192201]
> > org.glassfish.jersey.apache.connector [2.14.0.v201504171603]
> > com.fasterxml.jackson.core.jackson-core [2.5.0.v201504151636]
> > javax.ws.rs [2.0.1.v201504171603]
> > org.glassfish.jersey.core.jersey-client [2.14.0.v201504211925]
> > org.eclipse.linuxtools.docker.ui [1.0.0.201506030402]
> > jnr.enxio [0.6.0.v201505052040]
> > org.aopalliance [1.0.0.v201105210816]
> > jnr.unixsocket [0.5.0.v201505052040]
> > org.glassfish.jersey.media.jersey-media-json-jackson [2.14.0.v201504171603]
> === Summary ===
> file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 34 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3373) Remove org.eclipse.jst.server.generic.jonas plugin from JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3373?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3373:
-----------------------------
CDW pm_ack: + (was: ?)
> Remove org.eclipse.jst.server.generic.jonas plugin from JBDS
> ------------------------------------------------------------
>
> Key: JBDS-3373
> URL: https://issues.jboss.org/browse/JBDS-3373
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: updatesite
> Affects Versions: 9.0.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 9.0.0.Beta1
>
>
> com.jboss.devstudio.core.feature/feature.xml declares
> {quote}
> <import plugin="org.eclipse.jst.server.generic.jonas"/>
> {quote}
> I can't see *any* reason why we'd do that in 2015.
> [~burrsutter], [~ldimaggio], [~maxandersen] : is there any client requirement about JOnAS support?
> [~rob.stryker] does WTP require that plugin in any way?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-17698) Server view could show all deployed modules, obtained from the server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17698?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17698:
--------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> Server view could show all deployed modules, obtained from the server
> ---------------------------------------------------------------------
>
> Key: JBIDE-17698
> URL: https://issues.jboss.org/browse/JBIDE-17698
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta2
>
>
> Pavol Srna pointed out to me that when he deletes a project in workspace while it's deployed on a running AS7, it disappears from the server view and he can't undeploy it from Eclipse.
> I understand that this is somewhat expected, but we have a suggestion: Could the server view get its deployed modules from the server via the management api and use that to show the modules? Similar to what the web console of AS7/WildFly/EAP6 shows.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19757:
------------------------------------
[~rob.stryker] the only remaining TODO here is to point the existing /updates/webtools/mars site at the forthcoming JBT 4.3.0.Beta1 site (via symlink or composite site) once JBT 4.3.0.Beta1 is released.
Then we need to test its performance / that it works as expected, and can close this issue.
> Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-19879:
--------------------------------
Labels: new_and_noteworthy (was: )
> Add o.e.remote and o.e.launchbar to TP
> --------------------------------------
>
> Key: JBIDE-19879
> URL: https://issues.jboss.org/browse/JBIDE-19879
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, target-platform
> Affects Versions: 4.3.0.Beta2
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> *Reason:* JBIDE-19711 - WTP servertools integration with CDT launchbar
> *Project page/sources:* ... Requires dependencies on CDT and Launchbar. Launchbar is in http://www.eclipse.org/cdt/ and o.e.remote is in http://www.eclipse.org/ptp/
> *Version:* - Required launchbar is 1.0.0 found in MASTER at their repository. There is no released version yet with the stable API required. Required o.e.remote version is 2.0.0 in MASTER at their repository. There is no released version yet with the stable API required.
> *License and owner:* ... Both are eclipse projects licensed under EPL
> *Original p2 repo:* I am unable to locate the original update sites / p2 repos. PTP does not seem to have an update site URL to the best of my searching (http://download.eclipse.org/tools/ptp/builds/9.0.0/ does not list an update site url, but does have a zip containing an update site). CDT does not list update sites for mars at https://eclipse.org/cdt/downloads.php
> *JBoss mirror:* - Not sure what's applicable here. http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... does have all plugins needed, but none are the API required, as we require the code from Master.
> *Include Sources: - It's always nice to include sources for devs who build tp locally with the fetch-sources flag ;)
> *Affected projects: - jbosstools-server
> *Include in JBDS:* - No, for now.
> *Type of dependency:* distribution
> *List of bundles added/removed:* - At this time, I expect to require org.eclipse.launchbar.core, org.eclipse.launchbar.ui, org.eclipse.remote.core, org.eclipse.remote.ui.
> Unfortunately I'm unable to test if this is sufficient, at the moment. There may be other plugins that are transient deps somehow that I'm not seeing since I don't have a TP to build against that works.
> If applicable:
> *non-p2 repository:* ???
> *non-p2 ids:* ???
> Suggested Patch for TP: - At this point, I have no suggested patch. I do not know how to add a dependency on nightly builds for these two blocks of code. Also, I'm a bit confused why http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... will list a plugin (for example org.eclipse.cdt.core.native_5.8.0.201505050312.jar) but the .target file references a feature group (?) which is not present in the requirements/mars folder, such as <unit id="org.eclipse.cdt.native.feature.group" version="8.7.0.201505050312"/>
> I'm also a bit confused where you're pulling the feature group name / id from, or its version, as the version of the feature group does not seem to match the version of the plugin. Furthermore, the mars repo mentioned above does not seem to include any file matching the string org.eclipse.cdt.native.feature.group
> So I'm not sure how you're converting a required plugin id to a feature group. The devdoc also provides no assistance in this matter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months