[JBoss JIRA] (JBIDE-20521) Show In - Web Browser is enabled and do nothing when there are no routes
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20521?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-20521:
---------------------------------------
[~fbricon] I don't have an example or anything particular in my mind, but let's just imagine there would be an OpenShift application without WEB UI which would provide capabilities of a server and just clients would be accessing it to process their requests. Or any other application. Well, honestly, I am not sure if this is real use case or could be.
> Show In - Web Browser is enabled and do nothing when there are no routes
> ------------------------------------------------------------------------
>
> Key: JBIDE-20521
> URL: https://issues.jboss.org/browse/JBIDE-20521
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Fix For: 4.3.1.Beta1
>
>
> When I am having a project with an application without any route, the Show In - Web Browser context menu of a project is enabled for this project and it does not do anything (after click nothing happens). Context menu should be disable if there are no routes for an application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3553:
---------------------------------
Labels: new_and_noteworthy (was: )
> Integrate/Enable CodeRecommenders substring completion in JBDS 9
> ----------------------------------------------------------------
>
> Key: JBDS-3553
> URL: https://issues.jboss.org/browse/JBDS-3553
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: p2-product, target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Labels: new_and_noteworthy
> Fix For: 9.0.1.Beta1
>
>
> Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/
> JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default.
> *Project page/sources:* https://www.eclipse.org/recommenders/manual/
> *Version:* 2.2.4 (part of Mars)
> *License and owner:* EPL, Eclipse Community/CodeTrails
> *Original p2 repo:* included in Mars repository
> *JBoss mirror:* will use our Mars mirror
> *Include Sources:* No
> *Affected JBoss Tools components:* JBDS feature and product
> *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> mistria@mistria-laptop:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff http://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Fina... file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/
> > org.eclipse.recommenders.jdt [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.overrides [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.injection [2.2.4.v20150914-0857]
> > org.eclipse.aether.maven.feature.feature.group [3.1.0.20140706-2237]
> > org.eclipse.aether.transport.http [1.0.1.v20141111]
> > org.eclipse.aether.api [1.0.1.v20141111]
> > org.eclipse.aether.transport.http.feature.feature.jar [1.0.1.v20141111]
> > org.eclipse.aether.transport.file.feature.feature.jar [1.0.1.v20141111]
> > org.eclipse.recommenders.overrides.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.utils [2.2.4.v20150914-0857]
> > org.eclipse.aether.connector.basic.feature.feature.jar [1.0.1.v20141111]
> > org.eclipse.aether.spi [1.0.1.v20141111]
> > com.google.inject.multibindings [3.0.0.v201402270930]
> > org.eclipse.recommenders.completion.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.maven.feature.feature.jar [3.1.0.20140706-2237]
> > org.apache.commons.lang3 [3.1.0.v201403281430]
> > org.eclipse.aether.feature.feature.group [1.0.1.v20141111]
> > org.eclipse.recommenders.types.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.calls.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.connector.basic.feature.feature.group [1.0.1.v20141111]
> > org.apache.commons.pool [1.6.0.v201204271246]
> > org.eclipse.aether.maven [3.1.0.v20140706-2237]
> > org.eclipse.recommenders.models [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.jayes [2.2.4.v20150914-0857]
> > org.eclipse.aether.transport.file [1.0.1.v20141111]
> > org.apache.commons.math [2.1.0.v201105210652]
> > org.eclipse.recommenders.coordinates [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.subwords.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.models.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.transport.http.feature.feature.group [1.0.1.v20141111]
> > org.eclipse.recommenders.chain.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.apidocs [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.rcp.feature.feature.jar [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.constructors [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.calls [2.2.4.v20150914-0857]
> > org.apache.solr.client.solrj [3.5.0.v20150506-0844]
> > org.eclipse.aether.impl [1.0.1.v20141111]
> > org.eclipse.recommenders.jayes.io [2.2.4.v20150914-0857]
> > com.google.inject [3.0.0.v201312141243]
> > org.eclipse.aether.connector.basic [1.0.1.v20141111]
> > ch.qos.logback.slf4j [1.0.7.v201505121915]
> > org.eclipse.aether.util [1.0.1.v20141111]
> > org.eclipse.recommenders.utils.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.net [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.constructors.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.feature.feature.jar [1.0.1.v20141111]
> > org.eclipse.recommenders.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.apidocs.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.transport.file.feature.feature.group [1.0.1.v20141111]
> > org.eclipse.recommenders.rcp.feature.feature.group [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.coordinates.rcp [2.2.4.v20150914-0857]
> === Summary ===
> file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ contains 51 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-21031.
-------------------------------
Resolution: Done
* 784c82b - (HEAD, origin/jbosstools-4.3.x, jbosstools-4.3.x) JBIDE-20947 - fixing bad upversion in maintenance, AS project (64 minutes ago, Rob Stryker)
* 648b542 - JBIDE-20974 - Upversion maintenance (8 days ago, Rob Stryker)
Forgot to reference this jira.
> Version of AS features in 4.3.x branch is greater than in master (4.4.x)
> ------------------------------------------------------------------------
>
> Key: JBIDE-21031
> URL: https://issues.jboss.org/browse/JBIDE-21031
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Versionwatch reports [1] that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1):
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/...
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/...
> But in 9.0.0 we had 3.1.0:
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin...
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin...
> So, in master, we have 3.2.0, which is seen by VW as being a lower version.
> Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0.
> [1] https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch... and https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.versionwatch...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov resolved JBDS-3547.
----------------------------------
Resolution: Done
Merged.
> Eloqua tracking of Eloqua tracked links
> ---------------------------------------
>
> Key: JBDS-3547
> URL: https://issues.jboss.org/browse/JBDS-3547
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: website
> Affects Versions: 9.0.0.GA
> Reporter: David Hladky
> Assignee: Alexey Kazakov
> Fix For: 8.1.1.GA, 9.1.0.Beta1, 9.0.0.GA, 8.1.0.GA, 8.0.0.GA, 7.1.1.GA
>
>
> I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice.
> I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3547:
--------------------------------
> Eloqua tracking of Eloqua tracked links
> ---------------------------------------
>
> Key: JBDS-3547
> URL: https://issues.jboss.org/browse/JBDS-3547
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: website
> Affects Versions: 9.0.0.GA
> Reporter: David Hladky
> Assignee: Alexey Kazakov
> Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1
>
>
> I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice.
> I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3547:
---------------------------------
> Eloqua tracking of Eloqua tracked links
> ---------------------------------------
>
> Key: JBDS-3547
> URL: https://issues.jboss.org/browse/JBDS-3547
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: website
> Affects Versions: 9.0.0.GA
> Reporter: David Hladky
> Assignee: Alexey Kazakov
> Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1
>
>
> I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice.
> I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-20947.
---------------------------------
Resolution: Done
Made a new commit, old commit had incorrect jira number.
* 784c82b - (HEAD, origin/jbosstools-4.3.x, jbosstools-4.3.x) JBIDE-20947 - fixing bad upversion in maintenance, AS project (40 seconds ago, Rob Stryker)
* 648b542 - JBIDE-20974 - Upversion maintenance (8 days ago, Rob Stryker)
Also astools was incorrectly upversioned 2 weeks ago in maintenance stream, hence the second commit.
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1
> -----------------------------------------------
>
> Key: JBIDE-20947
> URL: https://issues.jboss.org/browse/JBIDE-20947
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-20947.
-------------------------------
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1
> -----------------------------------------------
>
> Key: JBIDE-20947
> URL: https://issues.jboss.org/browse/JBIDE-20947
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-20947:
-----------------------------------
Resolution: (was: Done)
Assignee: Rob Stryker (was: Nick Boldt)
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1
> -----------------------------------------------
>
> Key: JBIDE-20947
> URL: https://issues.jboss.org/browse/JBIDE-20947
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years