November 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-13133) 'Import all existing projects after clone finishes' not working

by Galder Zamarreño (JIRA)

Galder Zamarreño created JBIDE-13133: ---------------------------------------- Summary: 'Import all existing projects after clone finishes' not working Key: JBIDE-13133 URL: https://issues.jboss.org/browse/JBIDE-13133 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Galder Zamarreño Not sure whose responsibility is this... I cloned a git repo via 'Git Repository Exploring' perspective, and in the last dialog screen I clicked on 'Import all existing projects after clone finishes', but when cloning finished, no project add been imported. This is in JBDS 5.0.1.GA. -- 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

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] (JBIDE-13098) 4 tests failing in org.jboss.tools.as.test.core.parametized.server

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13098: ---------------------------------- Summary: 4 tests failing in org.jboss.tools.as.test.core.parametized.server Key: JBIDE-13098 URL: https://issues.jboss.org/browse/JBIDE-13098 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.0.0.CR1 Reporter: Nick Boldt Assignee: Rob Stryker Priority: Blocker {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--server/22/testReport/} >>> org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest.testJBIDE6184_Odd_Republish_Error[0] 11 sec 1 >>> org.jboss.tools.as.test.core.parametized.server.ServerBeanLoader3Test.testServerBeanLoaderFromRuntimes[9] 11 ms 10 >>> org.jboss.tools.as.test.core.parametized.server.publishing.DeploymentAssemblyFilesetReferenceTest.testRootFolder 0.74 sec 10 >>> org.jboss.tools.as.test.core.parametized.server.publishing.DeploymentAssemblyFilesetReferenceTest.testRootFolderExcludeZ 0.75 sec 10 {code} -- 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

13 years, 4 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-13114) openshift-java-client: improve how userAgent is passed to UrlConnectionClient

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13114: ---------------------------------------- Summary: openshift-java-client: improve how userAgent is passed to UrlConnectionClient Key: JBIDE-13114 URL: https://issues.jboss.org/browse/JBIDE-13114 Project: Tools (JBoss Tools) Issue Type: Enhancement Affects Versions: 4.0.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.x clarify how the user-agent is set to the UrlConnectionHttpClient. You can actually set it to the constructor but also by a setter: {code:title=com.openshift.internal.client.httpclient.UrlConnectionHttpClient} public UrlConnectionHttpClient(String username, String password, String userAgent, boolean sslChecks, IMediaType requestMediaType, String acceptedMediaType, String version, String authKey, String authIV) { {code} {code:title=com.openshift.internal.client.httpclient.UrlConnectionHttpClient} public void setUserAgent(String userAgent) { this.userAgent = userAgent; } {code} Both variants are actually used in the library code: {code:title=com.openshift.internal.client.RestService} public RestService(String baseUrl, String clientId, IHttpClient client) { this.baseUrl = UrlUtils.ensureStartsWithHttps(baseUrl); this.client = client; client.setUserAgent(new RestServiceProperties().getUseragent(clientId)); {code} {code:title=com.openshift.client.OpenShiftConnectionFactory} public IOpenShiftConnection getConnection(final String clientId, final String login, final String password, final String authKey, final String authIV, final String serverUrl, final boolean proxySet, final String proxyHost, final String proxyPort) throws OpenShiftException { Assert.notNull(clientId); Assert.notNull(login); Assert.notNull(password); Assert.notNull(serverUrl); if (proxySet) { System.setProperty("proxyHost", proxyHost); System.setProperty("proxyPort", proxyPort); } try { final IHttpClient httpClient = new UrlConnectionHttpClientBuilder().setCredentials(login, password, authKey, authIV) .client(); final IRestService service = new RestService(serverUrl, clientId, httpClient); return getConnection(service, login, password); } catch (FileNotFoundException e) { throw new OpenShiftException(e, "Failed to establish connection for user ''{0}}''", login); } catch (IOException e) { throw new OpenShiftException(e, "Failed to establish connection for user ''{0}}''", login); } } {code} -- 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

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] (JBIDE-13096) Add Existing SSH key: automatically provide sensible default-name

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13096: ---------------------------------------- Summary: Add Existing SSH key: automatically provide sensible default-name Key: JBIDE-13096 URL: https://issues.jboss.org/browse/JBIDE-13096 Project: Tools (JBoss Tools) Issue Type: Enhancement Affects Versions: 4.0.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 4.1.x When adding an existing ssh key the user is required to provide a name for the key he's adding (uploading). To the newbie user it is not obvious what he shall provide as name. We should help here a provide some sensible default name. How to reproduce: # ASSERT: make sure you have an account on OpenShift and in the OpenShift Explorer # EXEC: in the OpenShift Explorer: pick "Manage SSH Keys..." from the context-menu of your user # EXEC: in the upcoming dialog: hit "Add" Result: You get a dialog that asks you to browse and select your key and provide a name for it. Expected: Automatically provide some meaningful default name so that the newbie user may just pick his key and upload. -- 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

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] (JBDS-2394) CLONE - ESB projects cannot be deployed using Server Add/Remove

by Rob Stryker (JIRA)

Rob Stryker created JBDS-2394: --------------------------------- Summary: CLONE - ESB projects cannot be deployed using Server Add/Remove Key: JBDS-2394 URL: https://issues.jboss.org/browse/JBDS-2394 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.0.GA-SOA Environment: Fedora, jdk7 Reporter: Rob Stryker Assignee: Rob Stryker Priority: Critical Fix For: 5.0.2.GA, 6.0.0.CR2, 6.0.x * Create a new server runtime for SOA-P 5.3 -- Preferences -> Server -> Runtime Environments * Create a new ESB project with the defaults * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification. The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove." -- 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

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] (JBIDE-12527) Improve maven conversion of lib jars

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12527: ----------------------------------- Summary: Improve maven conversion of lib jars Key: JBIDE-12527 URL: https://issues.jboss.org/browse/JBIDE-12527 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 4.0.0.Alpha1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Alpha2 As a follow up on JBIDE-8973, we should be able to also convert project dependencies that are not classpath entries. Use case : convert an EAR project to maven. All the jars in <earproject>/lib/ and all jars referenced as virtual components in .settings/org.eclipse.wst.common.component should be identified and converted -- 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

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-12530) Warn the user about unresolvable dependencies during maven conversion

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12530: ----------------------------------- Summary: Warn the user about unresolvable dependencies during maven conversion Key: JBIDE-12530 URL: https://issues.jboss.org/browse/JBIDE-12530 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 4.0.0.Alpha1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Alpha2 When identifying jars as maven dependencies, if dependencies are identified against some remote nexus repository, the maven dependency won't be resolvable if that repo was not added to the maven settings.xml We should display a warning image in that case. We could also provide a way to manage/add repositories from the conversion wizard. -- 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

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12166) Blank, no demo code in archetypes: Java EE 6 (WAR & EAR), HTML5, RichFaces, Spring, GWT

by Burr Sutter (JIRA)

13 years, 4 months

6
16
0 / 0

[JBoss JIRA] (JBIDE-12702) All groovy jars unidentified during project conversion

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12702: ----------------------------------- Summary: All groovy jars unidentified during project conversion Key: JBIDE-12702 URL: https://issues.jboss.org/browse/JBIDE-12702 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Alpha2 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Beta1 - Create a dynamic web project - Copy all jars from a groovy distro lib directory into <project>/WebContent/WEB-INF/lib - Right click on project > Configure > Convert to Maven... - Set GAV and packaging = war - The identification wizard tries to identify all the jars ASSERT : all jars are identified <- FAILS : all groovy jars are unidentified -- 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

13 years, 4 months

2
9
0 / 0

[JBoss JIRA] (JBIDE-12984) Hang Ups

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-12984: ----------------------------------- Summary: Hang Ups Key: JBIDE-12984 URL: https://issues.jboss.org/browse/JBIDE-12984 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter Lots of hang ups on a brand new install of JBDS6 - Java 7 32-bit (selected in the installer). http://screencast.com/t/TblKtYtfK EAP6 startup hangs (seemingly though the server does start) Use of the HTML5 Archetype hangs Quit, Force Quit - in order to get back into JBDS6 In some cases, I have reinstalled several times. -- 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

13 years, 4 months

5
31
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 November 2012