January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16409: ---------------------------------------- I believe we'll have to start the TP 4.32.x stream with this change. [~nickboldt] WDYT ? > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16343: ------------------------------------- Import is incorrect and it's too long for a menu anyway. Extraction location can be defined in wizard. See http://docs.jboss.org/tools/whatsnew/core/core-news-3.3.0.M5.html > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 4.2.x > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-16409: -------------------------------------- Assignee: Mickael Istria > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16403) Welcome page "Show on startup" option is grey

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16403?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16403: -------------------------------- Fix Version/s: 4.2.0.Beta1 > Welcome page "Show on startup" option is grey > --------------------------------------------- > > Key: JBIDE-16403 > URL: https://issues.jboss.org/browse/JBIDE-16403 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Final > Environment: Kubuntu 64 bits > Reporter: Emmanuel Hugonnet > Priority: Minor > Fix For: 4.2.0.Beta1 > > Attachments: jboss_central.png > > > The option "show on startup" is displayed with a grey background instead of the default one. Changing theme doesn't affect it. > See screenshot -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16409: ---------------------------------------- Should we use this repository? http://build.eclipse.org/webtools/committers/wtp4x-R3.5.2-M/2014013014523... Ideally, it would be cool if you could format your request as explained in https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... (that would prevent from some questions and save time). > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Priority: Blocker > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16343: ---------------------------------------- The issue with just "extract" is that it doesn't say where stuff is about to be extracted. What about "Import as Jars inside Project...". > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 4.2.x > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16343: ------------------------------------- How about "Extract jars from library"? [~burrsutter], [~maxandersen], [~mmurray] any suggestions? > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 4.2.x > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16402) A newly created project is not imported into Eclipse when the project location is non-existent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16402?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16402: -------------------------------- Fix Version/s: 4.1.2.CR1 4.2.0.Alpha2 > A newly created project is not imported into Eclipse when the project location is non-existent > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16402 > URL: https://issues.jboss.org/browse/JBIDE-16402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Vineet Reynolds > Assignee: Koen Aers > Fix For: 4.1.2.CR1, 4.2.0.Alpha2 > > > When a non-existent location is specified in Eclipse, Forge creates the project, but fails to import the project into the Eclipse workspace. > This also seems to be related to an issue where the Location field is not pre-filled (not sure why; I'm reporting this bug on behalf of a user, so I'm hoping to get more details). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16402) A newly created project is not imported into Eclipse when the project location is non-existent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16402?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16402: -------------------------------- Assignee: Koen Aers > A newly created project is not imported into Eclipse when the project location is non-existent > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16402 > URL: https://issues.jboss.org/browse/JBIDE-16402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Vineet Reynolds > Assignee: Koen Aers > > When a non-existent location is specified in Eclipse, Forge creates the project, but fails to import the project into the Eclipse workspace. > This also seems to be related to an issue where the Location field is not pre-filled (not sure why; I'm reporting this bug on behalf of a user, so I'm hoping to get more details). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2370) Bad/non-helping error message when central has no connection

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2370?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2370: ----------------------------------- You can't mention JBoss Central or a refresh button as the wizards can also be opened via the New Project... menu +1 for the link though. {quote} An error occurred while downloading Wizard metadata. Please check your Internet connection and your <a href="link/to/prefs">Proxy Settings</a>. {quote} I believe that, once the connection issue is solved, next attempt to open the wizard should succeed without having the need to refresh anything. Or am I wrong? > Bad/non-helping error message when central has no connection > ------------------------------------------------------------ > > Key: JBDS-2370 > URL: https://issues.jboss.org/browse/JBDS-2370 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: upstream > Affects Versions: 5.0.0.GA > Environment: JDK 1.7 32-bit, Windows > Reporter: David Chia > Assignee: Snjezana Peco > Priority: Critical > Labels: jbds711 > Fix For: 7.1.1.CR1, 8.0.0.Alpha2 > > > After a successful install, I tried to create a "Java EE Web Project" and run into an error dialog "Failed to load Wizard - Wizard metadata could not be loaded". I've also tried all other projects and result in the same error. The only project I could create is the "Dynamic Web Project". Looking at the error log, there are a lot of these "Connection errors" like below. > !SESSION 2012-10-23 15:28:07.909 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_07 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US > Framework arguments: -product com.jboss.jbds.product.product > Command-line arguments: -os win32 -ws win32 -arch x86 -product com.jboss.jbds.product.product > !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.086 > !MESSAGE Permission denied: connect > !STACK 0 > java.net.SocketException: Permission denied: connect > at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) > at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) > at java.net.Socket.connect(Socket.java:579) > at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) > at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) > at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) > at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) > at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) > at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) > at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.132 > !MESSAGE Permission denied: connect > !STACK 0 > java.net.SocketException: Permission denied: connect > at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) > at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) > at java.net.Socket.connect(Socket.java:579) > at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) > at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) > at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) > at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) > at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) > at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) > at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) > at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) > at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) > at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

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