July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17954) openshift puts info logs when authenticating in error log

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17954?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-17954: ---------------------------------- Fix Version/s: (was: 4.2.0.Beta3) > openshift puts info logs when authenticating in error log > --------------------------------------------------------- > > Key: JBIDE-17954 > URL: https://issues.jboss.org/browse/JBIDE-17954 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.CR1 > > > when logging in I get "User <myuser> was authenticated" in the error log as info messages. > This should not happen by default. Please remove or add only when debug/trace is enabled. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17954) openshift puts info logs when authenticating in error log

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17954?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-17954. ----------------------------------- Labels: (was: respin-b) Resolution: Done > openshift puts info logs when authenticating in error log > --------------------------------------------------------- > > Key: JBIDE-17954 > URL: https://issues.jboss.org/browse/JBIDE-17954 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.CR1 > > > when logging in I get "User <myuser> was authenticated" in the error log as info messages. > This should not happen by default. Please remove or add only when debug/trace is enabled. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2956) Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2956?page=com.atlassian.jira.plugin.... ] Marián Labuda closed JBDS-2956. ------------------------------- Verified in JBDS 8 Beta3c build B194. > Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting" > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-2956 > URL: https://issues.jboss.org/browse/JBDS-2956 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Alpha2 > Environment: 64-bit Fedora 17 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Blocker > Fix For: 8.0.0.Beta3 > > Attachments: jbds800Alpha2report.zip, jbds_part1.png, jbds_part2.png, JBT4.2.0.Alpha2breport.zip, jbt_part1.png, jbt_part2.png, jbt_part3.png, report, springide360-new-ius-added.txt, spring_projects.png > > > After installing Spring IDE into JBDS 8.0.0.Alpha2 there should be option to create associated projects / examples / files... from menu File - Other - Spring, but there is only item for creation Spring bean configuration file. Others are missing. Tests also JBT 4.2.0.Alpha2 and there was not this issue. > See attached file. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3030) Spring conflicting handler message after Spring perspective is reset

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3030?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-3030: ------------------------------------- Still reproducible - JBDS 8.0.0.Beta3 respin-c, OpenJDK 1.8.0_20. > Spring conflicting handler message after Spring perspective is reset > -------------------------------------------------------------------- > > Key: JBDS-3030 > URL: https://issues.jboss.org/browse/JBDS-3030 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 8.0.0.Beta1 > Reporter: Jiri Peterka > Assignee: Fred Bricon > Priority: Minor > Fix For: 8.0.0.CR1 > > > Conflicting handlers for AUTOGEN:::org.springsource.ide.eclipse.commons.launch.actionSet/org.springsource.ide.eclipse.commons.launch.relaunch.action: {ActionDelegateHandlerProxy(null,org.springsource.ide.eclipse.commons.ui.launch.StopProcessPullDownToolbarDelegate)} vs {ActionDelegateHandlerProxy(null,org.springsource.ide.eclipse.commons.ui.launch.RelaunchProcessPullDownToolbarDelegate)} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17904) Make .gitignore addition smarter and add comments to ignored files

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17904?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-17904: ---------------------------------- Description: currently *Any* openshift app creation/import we add the following blindly: {code} target .settings/* !.settings/.jsdtscope .classpath {code} These does not make much sense for most apps besides java. Can't we be a bit more intelligent about it ? i.e. if the project is not a maven project, don't add 'target' if project is not a java project do not add .classpath And then I suggest adding comments to the .gitignore to make it clear what they do: {code} # if you want *all* eclipse settings to be shared comment this out, otherwise leave in. .settings/* # keep .jsdtscope to share javascript validations exclusions to avoid too many false positive warnings !.settings/.jsdtscope {code} was: currently *Any* openshift app creation/import we add the following blindly: target .settings/* !.settings/.jsdtscope .classpath These does not make much sense for most apps besides java. Can't we be a bit more intelligent about it ? i.e. if the project is not a maven project, don't add 'target' if project is not a java project do not add .classpath ..and then I suggest adding comments to the .gitignore to make it clear what they do: # if you want *all* eclipse settings to be shared comment this out, otherwise leave in. .settings/* # keep .jsdtscope to share javascript validations exclusions to avoid too many false positive warnings !.settings/.jsdtscope > Make .gitignore addition smarter and add comments to ignored files > ------------------------------------------------------------------ > > Key: JBIDE-17904 > URL: https://issues.jboss.org/browse/JBIDE-17904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Fix For: 4.3.x > > > currently *Any* openshift app creation/import we add the following blindly: > {code} > target > .settings/* > !.settings/.jsdtscope > .classpath > {code} > These does not make much sense for most apps besides java. > Can't we be a bit more intelligent about it ? > i.e. if the project is not a maven project, don't add 'target' > if project is not a java project do not add .classpath > And then I suggest adding comments to the .gitignore to make it clear what they do: > {code} > # if you want *all* eclipse settings to be shared comment this out, otherwise leave in. > .settings/* > # keep .jsdtscope to share javascript validations exclusions to avoid too many false positive warnings > !.settings/.jsdtscope > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17904) Make .gitignore addition smarter and add comments to ignored files

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17904?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-17904: ---------------------------------- Summary: Make .gitignore addition smarter and add comments to ignored files (was: make .gitignore addition smarter) > Make .gitignore addition smarter and add comments to ignored files > ------------------------------------------------------------------ > > Key: JBIDE-17904 > URL: https://issues.jboss.org/browse/JBIDE-17904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Fix For: 4.3.x > > > currently *Any* openshift app creation/import we add the following blindly: > target > .settings/* > !.settings/.jsdtscope > .classpath > These does not make much sense for most apps besides java. > Can't we be a bit more intelligent about it ? > i.e. if the project is not a maven project, don't add 'target' > if project is not a java project do not add .classpath > ..and then I suggest adding comments to the .gitignore to make it clear what they do: > # if you want *all* eclipse settings to be shared comment this out, otherwise leave in. > .settings/* > # keep .jsdtscope to share javascript validations exclusions to avoid too many false positive warnings > !.settings/.jsdtscope -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17950) Improve rendering on mobile/tablets

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17950?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-17950: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) [~maxandersen], please review the changes > Improve rendering on mobile/tablets > ----------------------------------- > > Key: JBIDE-17950 > URL: https://issues.jboss.org/browse/JBIDE-17950 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > > Some images should be hidden (eg: screenshot on hero-unit) or a smaller size/version should be used (eg: banner). > Some smaller fonts should be used for the hero-unit, too. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3101?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3101: -------------------------------- Attachment: dist-diff-grepped.log dist-diff.log > 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-3101) Differences in 3rd party time stamps between builds

by Martin Malina (JIRA)

Martin Malina created JBDS-3101: ----------------------------------- Summary: 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 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-3100) JBDS 8 splash screen should be improved

by Marián Labuda (JIRA)

Marián Labuda created JBDS-3100: ----------------------------------- Summary: JBDS 8 splash screen should be improved Key: JBDS-3100 URL: https://issues.jboss.org/browse/JBDS-3100 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: ui/branding Affects Versions: 8.0.0.Beta3 Reporter: Marián Labuda There was a usability testing yesterday focused on OpenShift plugin. One note talked about splash screen: {quote} The 8 for JBDS spash screen looks a lot like Oracle 8 when that came out - big red 8. Probably need to do something different for the branding. {quote} -- 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