July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17733) Remove EGit from Central Discovery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17733: ----------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Remove EGit from Central Discovery > ---------------------------------- > > Key: JBIDE-17733 > URL: https://issues.jboss.org/browse/JBIDE-17733 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Fix For: 4.2.0.CR1 > > Attachments: eclipse-platform-installs-jbt-beta3-OK.png, eclipse-standard-installs-jbt-beta3-OK.png > > > Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed. > So we should remove EGit from our Central discovery catalogs. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17573) Download Runtimes window lacks properties when opened

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17573?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17573. --------------------------------- Resolution: Done Marking as resolved just to ensure martin will test it with the other b3 issues, but, I'm not convinced its fixed. It's possible, though :D > Download Runtimes window lacks properties when opened > ----------------------------------------------------- > > Key: JBIDE-17573 > URL: https://issues.jboss.org/browse/JBIDE-17573 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2a B121 > OS X > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.0.Beta3 > > Attachments: runtime-details.png > > > When I open the Download Runtimes dialog, the first item is automatically selected (currently GateIn Portal 3.6.0), but the information box in the lower part of the window does not display Project URL and Download URL: > !runtime-details.png! > Once you change the selection to something else (and then even back to the first item), the properties are displayed alright. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17773) Misaligned buttons

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17773?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17773. --------------------------------- Assignee: Rob Stryker Resolution: Done Changed some code that seems to fix it in my UI, though it wasn't an obvious misalignment on my screen. Hope it fixes it. > Misaligned buttons > ------------------ > > Key: JBIDE-17773 > URL: https://issues.jboss.org/browse/JBIDE-17773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Arun Gupta > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > Attachments: Screen Shot 2014-07-02 at 4.20.16 PM.png > > > 4.2 beta2 + Luna > Adding a new WildFly server > Buttons to specify configuration file are misaligned, as shown in the snapshot. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17619: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta3) > Console for remote server disappears when workspace is switched > --------------------------------------------------------------- > > Key: JBIDE-17619 > URL: https://issues.jboss.org/browse/JBIDE-17619 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.x > > > This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped. > The only thing that helped me here was to delete the server and create a new one. > I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17619: ------------------------------------- Not immediately able to replicate. Will try again after b3 and see whats causing it. > Console for remote server disappears when workspace is switched > --------------------------------------------------------------- > > Key: JBIDE-17619 > URL: https://issues.jboss.org/browse/JBIDE-17619 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.x > > > This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped. > The only thing that helped me here was to delete the server and create a new one. > I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17773) Misaligned buttons

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17773?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17773: -------------------------------- Fix Version/s: 4.2.0.Beta3 > Misaligned buttons > ------------------ > > Key: JBIDE-17773 > URL: https://issues.jboss.org/browse/JBIDE-17773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Arun Gupta > Fix For: 4.2.0.Beta3 > > Attachments: Screen Shot 2014-07-02 at 4.20.16 PM.png > > > 4.2 beta2 + Luna > Adding a new WildFly server > Buttons to specify configuration file are misaligned, as shown in the snapshot. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17281: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Alpha1) > parent/pom.xml build/plugins should reference plugins defined build/pluginManagement > ------------------------------------------------------------------------------------ > > Key: JBIDE-17281 > URL: https://issues.jboss.org/browse/JBIDE-17281 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Fix For: 4.3.x > > > The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and dcluttering in jbosstools modules like: > - remove <version>${tychoVersion}</version> > - move jacoco plugin to tests/pom.xml > - move update site manipulations to site/pom.xml > - etc -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3080) Cannot update from JBoss Developer Studio Version: 8.0.0.Beta1 to Beta2

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBDS-3080?page=com.atlassian.jira.plugin.... ] Marek Novotny commented on JBDS-3080: ------------------------------------- [~mickael_istria] no connection issue is related to this, as I can workaround it by Installing new software from the same URL. > Cannot update from JBoss Developer Studio Version: 8.0.0.Beta1 to Beta2 > ----------------------------------------------------------------------- > > Key: JBDS-3080 > URL: https://issues.jboss.org/browse/JBDS-3080 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Marek Novotny > Assignee: Nick Boldt > Priority: Blocker > Fix For: 8.0.0.Beta3 > > > I cannot update from JBoss Developer Studio Version: 8.0.0.Beta1 > Build id: Beta1-v20140408-2350-B93 > Build date: 20140408-2350 > I got the following error while tried Check update on JBoss Central: > {noformat} > Some sites could not be found. See the error log for more detail. > No repository found at http://download.jboss.org/jbosstools/updates/development/luna/. > No repository found at https://devstudio.jboss.com/updates/8.0-development/. > No repository found at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/. > {noformat} > All three URLs are valid update sites or should be. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3025) Installer duplicates last folder in path causing errors (Mac OS X)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3025?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3025: -------------------------------- Fix Version/s: 8.0.0.Beta3 > Installer duplicates last folder in path causing errors (Mac OS X) > ------------------------------------------------------------------ > > Key: JBDS-3025 > URL: https://issues.jboss.org/browse/JBDS-3025 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Reporter: Michelle Murray > Assignee: Denis Golovin > Fix For: 8.0.0.Beta3 > > Attachments: Installer_jrelocationerror.png > > > Mac OS X Mavericks > Universal installer, step 4 - choose JVM: > * Click 'Specific Java JVM' > * Click Browse to locate JDK or JRE > * Navigate to find folder and click ok in file browser > the last folder is added twice to the displayed path > In most cases this path now doesn't exist and causes error messages to this extent. > !Installer_jrelocationerror.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17769) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Freemarker]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17769?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-17769. --------------------------------- Resolution: Done > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Freemarker] > -------------------------------------------------------- > > Key: JBIDE-17769 > URL: https://issues.jboss.org/browse/JBIDE-17769 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta3 > > > For JBIDE 4.2.0.Beta3 [Freemarker]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3 > [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Beta3x > git push origin jbosstools-4.2.0.Beta3x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and > * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014