[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-22382 at 6/3/16 5:54 PM:
-------------------------------------------------------------
Steps to recreate the bug are what?
- have an EAP server in the servers view
- Customize perspective > Action Set Availability : enable Server, Tool Bar visibility : enable Server
was (Author: ldimaggio):
Steps to recreate the bug are what?
Customize perspective > Action Set Availability : enable Server, Tool Bar visibility : enable Server
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Attachments: central-rhd-icon.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[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 edited comment on JBIDE-13671 at 6/3/16 5:46 PM:
------------------------------------------------------------
After much discussion last week [1], we decided we need to do two things to move to jgit timestamps, starting in Sprint 116:
1. Enable 'compare with baselines' for every build's previous /latest/ CI, to ensure that a TP change shows an API break, hopefully
2. move to jgit timestamp, and drop BUILD_ALIAS from the plugins/features... except for o.j.t.foundation.core and c.j.d.core.central, which need a 4th-part qualifier to define which version is which in ide-config.properties.
[1] http://jbds-pm.etherpad.corp.redhat.com/build-next-20160526
was (Author: nickboldt):
After much discussion last week, we decided we need to do two things to move to jgit timestamps, starting in Sprint 116:
1. Enable 'compare with baselines' for every build's previous /latest/ CI, to ensure that a TP change shows an API break, hopefully
2. move to jgit timestamp, and drop BUILD_ALIAS from the plugins/features... except for o.j.t.foundation.core and c.j.d.core.central, which need a 4th-part qualifier to define which version is which in ide-config.properties.
> 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.x
>
> 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, 10 months
[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:
------------------------------------
After much discussion last week, we decided we need to do two things to move to jgit timestamps, starting in Sprint 116:
1. Enable 'compare with baselines' for every build's previous /latest/ CI, to ensure that a TP change shows an API break, hopefully
2. move to jgit timestamp, and drop BUILD_ALIAS from the plugins/features... except for o.j.t.foundation.core and c.j.d.core.central, which need a 4th-part qualifier to define which version is which in ide-config.properties.
> 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.x
>
> 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, 10 months
[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-2044:
---------------------------------
Fix Version/s: 10.x
(was: 10.0.0.GA)
> .eclipseproduct file no longer refers to JBDS
> ---------------------------------------------
>
> Key: JBDS-2044
> URL: https://issues.jboss.org/browse/JBDS-2044
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Labels: discuss
> Fix For: 10.x
>
>
> Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read:
> {code}
> name=JBoss Developer Studio
> id=com.jboss.jbds.all
> version=5.0.0.v201202271832M-H79-Beta1
> {code}
> Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads:
> {code}
> name=Eclipse Platform
> id=org.eclipse.platform
> version=3.7.0
> {code}
> Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3267) JSON Editor
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3267?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov resolved JBDS-3267.
----------------------------------
Resolution: Done
> JSON Editor
> -----------
>
> Key: JBDS-3267
> URL: https://issues.jboss.org/browse/JBDS-3267
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html-source-editing, requirements, upstream
> Reporter: Burr Sutter
> Assignee: Victor Rubezhny
> Fix For: 10.0.0.GA
>
>
> As a Java or Java EE developer, who wishes to test my JAX-RS endpoints as well as edit various JSON files, I need an editor that formats the nested curly braces, helps me to insure that I am not missing (nor have extra) curly braces, missing quotes, helps me to know when to use square brackets, etc. Ideally, the Eclipse Outline view would also work if I am editing a .json file.
> Ideally, we would support both a full JSON editor as well as working within the Web Services Tester.
> http://screencast.com/t/hWAtlMytghV6
> http://screencast.com/t/h4VWGyAuqw
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3799:
---------------------------------
Fix Version/s: 10.x
(was: 10.0.0.GA)
> Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-3799
> URL: https://issues.jboss.org/browse/JBDS-3799
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Priority: Critical
> Labels: havoc
> Fix For: 10.x
>
>
> This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272
> Is causing rsync issues such as:
> default: Rsyncing folder: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> There was an error when attempting to rsync a synced folder.
> Please inspect the error message below for more info.
> Host path: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/
> Guest path: /vagrant
> Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant
> Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.
> dup() in/out/err failed
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3727:
---------------------------------
Fix Version/s: 10.x
(was: 10.0.0.GA)
> Installer fails with not normalized paths
> -----------------------------------------
>
> Key: JBDS-3727
> URL: https://issues.jboss.org/browse/JBDS-3727
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.x
>
>
> The installer accepts installation paths with the following format:
> {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat}
> With such a path it fails immediately after the installation starts with the following exception:
> {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
> at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448)
> at java.lang.Thread.run(Thread.java:745){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months