July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3101) Differences in 3rd party time stamps between builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3101?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3101: ---------------------------------- If I had to guess I suspect this MIGHT be due to tycho fetching pack.gz entries and unpacking them with different JDKs (32- or 64-bit, depending on the slave) but it looks like that's not the case as both builds were on RHEL6 64bit. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/devstudio.product_8.0.luna/buildTimeTrend} Success #194 16 min dev190-rhel6-x86_64 Success #193 40 min dev176-rhel6-x86_64{code} > Differences in 3rd party time stamps between builds > --------------------------------------------------- > > Key: JBDS-3101 > URL: https://issues.jboss.org/browse/JBDS-3101 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 8.0.0.Beta3 > Reporter: Martin Malina > Assignee: Nick Boldt > Attachments: dist-diff-grepped.log, dist-diff.log > > > Hi Nick, perhaps you can clear this up. > Sometimes I run the dist-diff tool between builds of JBDS to see what changed. > You can see the latest report between JBDS 8.0.0.Beta3b B193 and Beta3c B194 here: > http://machydra.brq.redhat.com/dist-diff/8.0.0.Beta3b-Beta3c/ > What is certainly expected are the changes in Forge2 and Webservices - those had fixes in them. > But then you can see many differences like these: > {code} > [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!META-INF/MANIFEST.MF > [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!META-INF/ECLIPSE_.SF > [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!META-INF/ECLIPSE_.RSA > [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!about.mappings > {code} > What triggers these is usually a change in the about.mappings file: > {code} > nattura:dist-diff rasp$ diff 1/about.mappings 2/about.mappings > 6c6 > < 0=1.7.2.v20140606-1324 > \ No newline at end of file > --- > > 0=1.7.2.v20140307-0500 > \ No newline at end of file > {code} > See the different time stamp. In case you wondered, that 0 property is used in the about.properties for build id: > {code} > blurb=Eclipse Data Tools Platform Model Base\n\ > \n\ > Version: {featureVersion}\n\ > Build id: {0}\n\ > \n\ > (c) Copyright Eclipse contributors and others 2005, 2007. All rights reserved.\n\ > Visit http://www.eclipse.org/datatools > {code} > Do you know why this is happening? Does every build take the dependencies from upstream again and potentially from a different mirror? Is this ok? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3108) Add ability to "always accept" the hostkey of the SSH connection for cloning git repos

by Catherine Robson (JIRA)

Catherine Robson created JBDS-3108: -------------------------------------- Summary: Add ability to "always accept" the hostkey of the SSH connection for cloning git repos Key: JBDS-3108 URL: https://issues.jboss.org/browse/JBDS-3108 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 8.0.0.Beta2 Reporter: Catherine Robson Each time JBDS does a git clone, it gives me a warning about the hostkey of the SSH connection. As a developer, I will always accept this. I'd like the ability to click an "always accept" checkbox so I don't have to see this pop-up every time. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3107) Create domain dialog - edit domain members error

by Catherine Robson (JIRA)

Catherine Robson created JBDS-3107: -------------------------------------- Summary: Create domain dialog - edit domain members error Key: JBDS-3107 URL: https://issues.jboss.org/browse/JBDS-3107 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: openshift Affects Versions: 8.0.0.Beta2 Reporter: Catherine Robson Assignee: Max Rydahl Andersen Attachments: OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png When creating a new OpenShift domain, if I click "Edit domain members" with the domain name left blank, I get the following error: https://www.evernote.com/shard/s230/sh/ce9003cb-7988-4cdd-a4bc-52b04b9123... This error is not helpful - and it appears the real problem is that to edit domain members I must create the domain first. Suggest that we change the create domain dialog to do the following: 1. Enter domain name (this is all that is shown on the dialog. (Mockup attached ) 2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached) Not sure if there was a reason we didn't add ability to edit the domain members directly here rather than kicking the user back into the openshift web console. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3107) Create domain dialog - edit domain members error

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3107?page=com.atlassian.jira.plugin.... ] Catherine Robson updated JBDS-3107: ----------------------------------- Attachment: OpenshiftDomainCreation_Step1.png OpenshiftDomainCreation_Step2.png > Create domain dialog - edit domain members error > ------------------------------------------------ > > Key: JBDS-3107 > URL: https://issues.jboss.org/browse/JBDS-3107 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Attachments: OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png > > > When creating a new OpenShift domain, if I click "Edit domain members" with the domain name left blank, I get the following error: > https://www.evernote.com/shard/s230/sh/ce9003cb-7988-4cdd-a4bc-52b04b9123... > This error is not helpful - and it appears the real problem is that to edit domain members I must create the domain first. > Suggest that we change the create domain dialog to do the following: > 1. Enter domain name (this is all that is shown on the dialog. (Mockup attached ) > 2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached) > Not sure if there was a reason we didn't add ability to edit the domain members directly here rather than kicking the user back into the openshift web console. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17937) Add a "Nightly" label on N&N when it's not release yet.

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17937?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-17937: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Please review the PR > Add a "Nightly" label on N&N when it's not release yet. > ------------------------------------------------------- > > Key: JBIDE-17937 > URL: https://issues.jboss.org/browse/JBIDE-17937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > > When we start aggregating the N&N for an upcoming version, the page appears in http://tools.jboss.org/documentation/whatsnew/jbosstools, but there's no label yet, because there's no entry for that version in 'products.yml' since it's not been released yet. > In that case, there should be a "Nightly" label and no link to download (that's already the case) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17517) Section titles are not vertically centered compared to the section toolbar actions (apparently only in linux)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17517?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17517: ------------------------------------------ hmm, ok, yes, I the very same of vertical alignement. Even though the alignement seems different in Windows (according to [~fbricon], which I reported this to and which asked me to file an issue) this is then a platform issue? > Section titles are not vertically centered compared to the section toolbar actions (apparently only in linux) > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17517 > URL: https://issues.jboss.org/browse/JBIDE-17517 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta2 > Environment: FC20, gtk3-3.10.9-1.fc20.x86_64 > Reporter: Andre Dietisheim > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.2.0.Beta3 > > Attachments: jboss-central-titles-not-vertically-centered.png, vertCenter.png > > > In JBoss Central, the section titles are not vertically centered when compared to the toolbar actions of the very same section: > !jboss-central-titles-not-vertically-centered.png! > This is apparently only reproducible in Linux (according to [~fbricon] this wont happen in Windows. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17960: ----------------------------------- Component/s: server > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.0.0.GA > Reporter: Karl Pietrzak > Priority: Minor > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-17536 at 7/23/14 12:41 PM: -------------------------------------------------------------- The nightly/luna symlink should be removed once master branch is used for Mars-based development. For Luna-based maintenance, the nightly/luna symlink should point at builds/nightly/core/4.2.luna. was (Author: maxandersen): nightly/luna should be made empty once mars happens and if we start up again point to the luna/ ngithly branch build. > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17951) utilize the tycho testing support for test bundles on JBTIS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17951?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17951: ---------------------------------------- See https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... JBT parent pom already contains a profile to enable this. > utilize the tycho testing support for test bundles on JBTIS > ----------------------------------------------------------- > > Key: JBIDE-17951 > URL: https://issues.jboss.org/browse/JBIDE-17951 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > > Talking with [~rcernich] he was interested in doing testing of already packaged bundles on a packaged eclipse. > [~mickael_istria] did this feature for tycho 0.19 documented at http://wiki.eclipse.org/Tycho/Release_Notes/0.19#Test_Execution > [~rcernich] would this cover you intended use case ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2949: ------------------------------- Fix Version/s: 8.0.0.Beta3 (was: 8.0.0.GA) > Require Java 7 for the IDE > -------------------------- > > Key: JBDS-2949 > URL: https://issues.jboss.org/browse/JBDS-2949 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Fix For: 8.0.0.Beta3 > > > Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1 > Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle) > Forge already requires Java 7. > Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX. -- 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