October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- i.e. in your example above I don't see it as wanting explicit values I see it much more abstract: {code} ${streamurl}/snapshots/builds/ ${streamurl}/snapshots/updates/ ${streamurl}/staging/builds/ ${streamurl}/staging/updates/ {code} and dependent on we doing jboss tools or devstudio $streamurl could be pointing to completely arbitrary urls allowing us to even publish to localhost if we wanted to. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- I saw it before but thought it was a failed cross publish since some jira mentioned that had occurred. Didn't connect the dots before talking with [~dgolovin] which was mentioning how confusing download.jboss.org continues to be, even after we cleaned up for this latest GA. Thus it is not under the covers, it is misleading. I thus suggest to please remove it asap since nothing in our system should rely on v9 or v10 for tools.jboss.org - that is simply just wrong. About having ability to share scripts - I don't follow why it is a problem that you just have one property/variable that is called "stream" (for example) which on jbds is set to <something>/9.0 and <something>/10.0 then in scripts the *only* think you worry about is what the value of "stream" is. Nothing should have to care about it being either neon, mars, 9.0 or 10.0 - no meaning should be giving to this besides "stream". If such things exist today, please point to it to explain, otherwise please remove it on download.jboss.org. About having neon/mars on devstudio.redhat.com - that is definitely much better since it is not conflicting terms; but why create this redundancy of urls when (at least from my POV) there should never be anything that need to know what specific stream we are referring to outside a "stream" variable ? > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21002) Expose additional service ports from deploy docker image wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21002?page=com.atlassian.jira.plugi... ] Jeff Cantrill resolved JBIDE-21002. ----------------------------------- Resolution: Done cherry-picked into master: 66ace82c1813e8f6f92015b84e5e595906cd55bf > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-21002 > URL: https://issues.jboss.org/browse/JBIDE-21002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.4.0.Alpha1 > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21002) Expose additional service ports from deploy docker image wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21002?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21002: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-21002 > URL: https://issues.jboss.org/browse/JBIDE-21002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.4.0.Alpha1 > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21002) Expose additional service ports from deploy docker image wizard

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-21002: ------------------------------------- Summary: Expose additional service ports from deploy docker image wizard Key: JBIDE-21002 URL: https://issues.jboss.org/browse/JBIDE-21002 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Fix For: 4.3.1.Beta1 Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image * Also only remove those which were added * Only reset those which are defaults * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21002) Expose additional service ports from deploy docker image wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21002?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21002: ---------------------------------- Affects Version/s: 4.4.0.Alpha1 (was: 4.3.0.CR1) > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-21002 > URL: https://issues.jboss.org/browse/JBIDE-21002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21001: -------------------------------------- Assignee: Nick Boldt (was: Alexey Kazakov) > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/... > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21001: ---------------------------------------- Go ahead with updating discovery. But we want to keep angularjs in jst/pom.xml to have it available when running tests. There are not direct dependencies but we should make sure our tests pass when angularJS is installed. > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/... > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-20990: ----------------------------------- Assignee: Rob Stryker > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-523: ---------------------------------- Yes - no need to select 'Other...' - I've corrected the test instructions. I'll let these guys speak for themselves but I believe they want to run an installer and be left on restart in the Fuse Integration perspective - ready to go. Basically led by the hand into the Fuse tooling environment. It's certainly trivial to select the perspective but they'd like to eliminate any place the user could get lost. > Create a demonstration/ prototype installer for Fuse Tooling support > -------------------------------------------------------------------- > > Key: JBTIS-523 > URL: https://issues.jboss.org/browse/JBTIS-523 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Optional > Attachments: sai1.png > > > The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go). > Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists: > https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer. > Here's a usability scenario targeting Fuse Tooling: > {code} > Test scenario A: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-d... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar` > 4. Select the Software/Update tab in the JBoss Central view. > 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning. > 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section. > Select the following item: > JBoss Fuse Development > 7. Accept/ respond 'Yes' and restart > 8. Select Window > Perspective > Open Perspective > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario B: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail! > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario C: > > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration > ----------------------------------------------------------------------------- > Test scenario D: (future - not available currently) > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar` > 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer > 5. Accept/ respond 'Yes' and restart > JBDS comes up in the Fuse Integration perspective - read to go. > {code} > Comments welcome! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2015