April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21674: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha2) > Enable hierarchical view by default in Project Explorer > ------------------------------------------------------- > > Key: JBIDE-21674 > URL: https://issues.jboss.org/browse/JBIDE-21674 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Xavier Coulon > Fix For: 4.4.x > > > Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects). > After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20431) Make sure all installed features are shown in Help->About->Installation Details->Features

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20431?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20431: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Make sure all installed features are shown in Help->About->Installation Details->Features > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20431 > URL: https://issues.jboss.org/browse/JBIDE-20431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, common/jst/core, visual-page-editor-core > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > We miss a few features in Help->About->Installation Details->Features such as VPE, browsersim, JST. Maybe more. > See JBIDE-20069 for details how we can fix that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22278) OpenShift Explorer should be made visible when a new Connection is created

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22278?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22278: -------------------------------- Description: OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. Could be done through a connection listener in the UI activator was:OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. Fix Version/s: 4.4.x Story Points: 2 > OpenShift Explorer should be made visible when a new Connection is created > -------------------------------------------------------------------------- > > Key: JBIDE-22278 > URL: https://issues.jboss.org/browse/JBIDE-22278 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Fix For: 4.4.x > > > OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. > Could be done through a connection listener in the UI activator -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22278) OpenShift Explorer should be made visible when a new Connection is created

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22278: ----------------------------------- Summary: OpenShift Explorer should be made visible when a new Connection is created Key: JBIDE-22278 URL: https://issues.jboss.org/browse/JBIDE-22278 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Fred Bricon OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22265) Application wizard: Allow users to reset values of all template parameters

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22265?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22265: ----------------------------------------------- As in JBIDE-22263, the following enhancements are done: 1. Button 'Reset All' is added. 2. Modified values are rendered in italics. 3. Buttons 'Reset' and 'Reset All' are enabled only when they can reset something. > Application wizard: Allow users to reset values of all template parameters > -------------------------------------------------------------------------- > > Key: JBIDE-22265 > URL: https://issues.jboss.org/browse/JBIDE-22265 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > > At the moment we allow users to reset a specific value in the table containing template parameters in New OpenShift Application wizard. It would be nice to have option to reset all template parameters (get default values for all) to have it consistent across wizards. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21621) Include proper version of RedDeer to TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21621?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21621: ------------------------------------ If it's genuinely a snapshot the snapshots/ is reasonable. Don't just throw it in development if it's a pre-release of a milestone. :D > Include proper version of RedDeer to TP > --------------------------------------- > > Key: JBIDE-21621 > URL: https://issues.jboss.org/browse/JBIDE-21621 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13671: ------------------------------------ {quote}Then we have to go all the way and remove build label from version and stop changing versions for plugins/features all together.{quote}If you mean removing the BUILD_ALIAS = Alpha, Beta, CR, Final/GA, I'm not adverse to that idea. But we can still make THIS change and then work to convince people the ALIAS is no longer required. :D Note also that AFAIK this doc is still in effect: https://developer.jboss.org/wiki/JBossProjectVersioning > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13671: ------------------------------------ {quote}How do we map timestamp back to SHA? Is there SHA in manifest somewhere?{quote} Yes. Open any plugin jar and look in its MANIFEST.MF file. {code} Eclipse-SourceReferences: scm:git:https://github.com/jbosstools/jbosst ools-arquillian.git;path="plugins/org.jboss.tools.arquillian.ui";comm itId=8d50f7310ae6b2d4960b39ad606738baa6c81dc6{code} > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13671: ------------------------------------ I'd be OK dropping the Alpha/Beta/CR/Final/GA thing too, but that's a harder one to sell. In that case if nothing changes between an Alpha and a Beta build, the install delta would be that much smaller, rather than requiring users to install everything all over again simply because we decided identical commit in Github should now be called "Beta" instead of "Alpha". The problem with the "w" prefix is that once you've done a `mvn install` to get those bits into your local ~/,m2 so they're available for a downstream build to use (eg., API change in Base, build Base, then build Server to verify) you can't easily remove them from your ~/.m2 cache, and newer builds from remote will be seen as older because the "w" will always beat the "v". So... it's more manual cleanup required (and more downloading the internet). Our current workflow using "v" for both local and remote is better -- it will work for the exact usecase you describe: "install nightly build and then update it [from] local build to test your fixes." The major benefit here is that as we start releasing more frequently (eg., weekly integration builds for QE & downstream consumption by DP installer), the changes between each build will be literally smaller, rather than just looking smaller, Auditing will be simpler because we won't have to check plugins' contents for changes - we can trust that the timestamp shows when the plugin was ACTUALLY last changed in Github. So yes, it's worth it. We've been trying to make this change for 3 years. We tested it for Locus and it works great there. No reason not to roll it out to the rest of the team. > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13671: --------------------------------------- {quote}The whole point here is that it no longer matters in which build the bits are built because we know they're coming from the same SHA in github. So we could add that suffix back onto the update site version qualifier if we want but I'm not sure we need it.{qote} Then we have to go all the way and remove build label from version and stop changing versions for plugins/features all together. How do we map timestamp back to SHA? Is there SHA in manifest somewhere? > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 April 2016