July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17527) revise Early Access disclaimer copy

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17527?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-17527 at 7/4/14 6:13 AM: ------------------------------------------------------------- How about adding : {quote} Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk! Enabling Early Access will enable an additional software site from which these incubating components can be installed. Be aware some of these Early Access features will be accessible and update-able during Eclipse updates. I understand these conditions, and still want to enable Early Access features. {quote} was (Author: fbricon): How about adding : {quote} Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk! Enabling Early Access features will enable an additional software site from which these incubating components can be installed. Be aware that when updating Eclipse, this may cause some features to be updated unexpectedly. I understand these conditions, and still want to enable Early Access features. {quote} > revise Early Access disclaimer copy > ----------------------------------- > > Key: JBIDE-17527 > URL: https://issues.jboss.org/browse/JBIDE-17527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Michelle Murray > Labels: early-access > Fix For: 4.2.0.Beta3 > > > Copy needs a bit of a rewrite. > Old: > {quote} > *Early Access Features* > Early Access features contains new functionality and fixes that are under development. You are encouraged to use these and give feedback but be aware: They are NOT officially supported, and NOT guaranteed to work correctly in your installation nor is it guaranteed it will end up in the final version. Use them at your own risk! > [ ] I understand those conditions, and I still want to access Early Access features. > {quote} > Proposed: > {quote} > *Early Access features* > Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk! > [ ] I understand these conditions, and still want to enable Early Access features. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17393) Show on main Central page the "Early Access" status

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17393?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17393: ---------------------------------------- [~mmurray] [~mmusaji] [~maxandersen] As a corollary of latest disccussions about early-access, I'd be glad if you could suggest some ways to give this information to the user. I didn't have good ideas on that topic. > Show on main Central page the "Early Access" status > --------------------------------------------------- > > Key: JBIDE-17393 > URL: https://issues.jboss.org/browse/JBIDE-17393 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: early-access > Fix For: 4.2.0.Beta3 > > > The main Central page (not Software one) should show the "Early Access" status. It can be one of > * No Early Access component installed, no Early Access enabled (shows nothing) > * No Early Access component installed, Early Access enabled (shows Early Access enabled) > * at least 1 Early Access component installed, Early Access Enabled > * at least 1 Early Access component installed, Early Access not Enabled -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17527) revise Early Access disclaimer copy

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17527?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-17527 at 7/4/14 5:42 AM: ------------------------------------------------------------- How about adding : {quote} Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk! Enabling Early Access features will enable an additional software site from which these incubating components can be installed. Be aware that when updating Eclipse, this may cause some features to be updated unexpectedly. I understand these conditions, and still want to enable Early Access features. {quote} was (Author: fbricon): How about adding : "An additional software site will be enabled from which these incubating components can be installed. Be aware that when updating Eclipse, this may cause some features to be updated unexpectedly." > revise Early Access disclaimer copy > ----------------------------------- > > Key: JBIDE-17527 > URL: https://issues.jboss.org/browse/JBIDE-17527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Michelle Murray > Labels: early-access > Fix For: 4.2.0.Beta3 > > > Copy needs a bit of a rewrite. > Old: > {quote} > *Early Access Features* > Early Access features contains new functionality and fixes that are under development. You are encouraged to use these and give feedback but be aware: They are NOT officially supported, and NOT guaranteed to work correctly in your installation nor is it guaranteed it will end up in the final version. Use them at your own risk! > [ ] I understand those conditions, and I still want to access Early Access features. > {quote} > Proposed: > {quote} > *Early Access features* > Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk! > [ ] I understand these conditions, and still want to enable Early Access features. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17527) revise Early Access disclaimer copy

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17527?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-17527: ------------------------------------- How about adding : "An additional software site will be enabled from which these incubating components can be installed. Be aware that when updating Eclipse, this may cause some features to be updated unexpectedly." > revise Early Access disclaimer copy > ----------------------------------- > > Key: JBIDE-17527 > URL: https://issues.jboss.org/browse/JBIDE-17527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Michelle Murray > Labels: early-access > Fix For: 4.2.0.Beta3 > > > Copy needs a bit of a rewrite. > Old: > {quote} > *Early Access Features* > Early Access features contains new functionality and fixes that are under development. You are encouraged to use these and give feedback but be aware: They are NOT officially supported, and NOT guaranteed to work correctly in your installation nor is it guaranteed it will end up in the final version. Use them at your own risk! > [ ] I understand those conditions, and I still want to access Early Access features. > {quote} > Proposed: > {quote} > *Early Access features* > Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk! > [ ] I understand these conditions, and still want to enable Early Access features. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16645) Seam Portlet deployed on EPP 5.2 is in error

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16645?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-16645. ----------------------------------- Resolution: Cannot Reproduce Bug This issue is no more reproducible. Verified with JBDS 8.0 Beta2-v20140617-2058-B166 > Seam Portlet deployed on EPP 5.2 is in error > -------------------------------------------- > > Key: JBIDE-16645 > URL: https://issues.jboss.org/browse/JBIDE-16645 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.2.0.Alpha2 > Environment: EPP-5.2.2.GA with Seam 2.2.5.EAP5 > Reporter: Radoslav Rábara > Assignee: Radoslav Rábara > Fix For: 4.2.0.CR1 > > Attachments: epp52-server-log > > > Seam portal project deployed on EPP 5.2 is in error. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17624) (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17624?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17624: -------------------------------- Labels: early-access (was: ) > (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException > --------------------------------------------------------------------------------------------- > > Key: JBIDE-17624 > URL: https://issues.jboss.org/browse/JBIDE-17624 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Fred Bricon > Assignee: Snjezana Peco > Priority: Minor > Labels: early-access > Fix For: 4.2.0.Beta3 > > > In Central > Software/Update page, (un)checking Early Access while refreshing the connector logs the following exception : > {noformat} > org.eclipse.swt.SWTException: Graphic is disposed > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.SWT.error(SWT.java:4327) > at org.eclipse.swt.graphics.Image.getBounds(Image.java:1164) > at org.eclipse.swt.widgets.Label.computeSize(Label.java:149) > at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491) > at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221) > at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164) > at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234) > at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491) > at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221) > at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164) > at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234) > at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491) > at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221) > at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164) > at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234) > at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491) > at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221) > at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197) > at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1290) > at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1276) > at org.eclipse.swt.widgets.Composite.layout(Composite.java:665) > at org.jboss.tools.central.editors.xpl.DiscoveryViewer.updateFilters(DiscoveryViewer.java:628) > at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:536) > at org.jboss.tools.central.editors.SoftwarePage.access$8(SoftwarePage.java:486) > at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:229) > {noformat} > scrolledContents is checked for disposed state, but the error occurs within layout() > {code} > if (this.scrolledContents != null && !this.scrolledContents.isDisposed()) { > this.scrolledContents.layout(true, true); //crashes here > ... > } > {code} > I don't know how we can prevent that -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17625) Checking an installed/up-to-date feature enables update anyway

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17625?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-17625: ------------------------------------- Count is still incorrect after selecting some installed connectors and then unchecking "show installed" : http://www.screencast.com/users/fbricon/folders/Jing/media/59d339d3-37ba-... > Checking an installed/up-to-date feature enables update anyway > -------------------------------------------------------------- > > Key: JBIDE-17625 > URL: https://issues.jboss.org/browse/JBIDE-17625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Beta3 > > > When selecting a connector that is already installed and up to date, this one shouldn't increment the number of item to install or update. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-15332: ----------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Fix For: 4.2.0.CR1 > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17527) revise Early Access disclaimer copy

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17527?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17527: ----------------------------------- Assignee: Michelle Murray (was: Mickael Istria) > revise Early Access disclaimer copy > ----------------------------------- > > Key: JBIDE-17527 > URL: https://issues.jboss.org/browse/JBIDE-17527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Michelle Murray > Labels: early-access > Fix For: 4.2.0.Beta3 > > > Copy needs a bit of a rewrite. > Old: > {quote} > *Early Access Features* > Early Access features contains new functionality and fixes that are under development. You are encouraged to use these and give feedback but be aware: They are NOT officially supported, and NOT guaranteed to work correctly in your installation nor is it guaranteed it will end up in the final version. Use them at your own risk! > [ ] I understand those conditions, and I still want to access Early Access features. > {quote} > Proposed: > {quote} > *Early Access features* > Early Access features contain new functionality and/or fixes that are under development. You are encouraged to use these features and to give feedback but be aware that these features are NOT officially supported, NOT guaranteed to work correctly, and subject to removal from JBoss Central at any time, for any reason. Use them at your own risk! > [ ] I understand these conditions, and still want to enable Early Access features. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2965) Mylyn Jenkins/Hudson Connector - Issues seen with different versions of Jenkins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2965?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2965: -------------------------------------- Could this blog post be related? https://www.eclipse.org/forums/index.php/t/545761/ If so, it seems to be an issue on server-side for some Jenkins instance. You should ask ci-issues(a)jboss.org to get access to the logs and see whether some errors happen on the server when trying to use the Mylyn/Jenkins connector. Is this issue really Criticat if it works in most cases? Can it be delayed to CR1? > Mylyn Jenkins/Hudson Connector - Issues seen with different versions of Jenkins > ------------------------------------------------------------------------------- > > Key: JBDS-2965 > URL: https://issues.jboss.org/browse/JBDS-2965 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.1.1.CR1 > Environment: JBDS 7.1.1.CR1 > Reporter: Len DiMaggio > Priority: Critical > Fix For: 8.0.0.Beta3 > > Attachments: Screenshot-2.png > > > See attached screenshot - the server validation feature fails - this error is returned to the user: > Server validation failed: Unexpected error: Unexpected response from Hudson server for '/api/xml': Internal Server Error -- 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