[JBoss JIRA] Created: (JBIDE-6918) seam.ui.test failures: Content Assistant returned no proposals OR Settings page is not valid: Model source folder "/TestSeamSettingsPreferencesPage" does not exist.
by Nick Boldt (JIRA)
seam.ui.test failures: Content Assistant returned no proposals OR Settings page is not valid: Model source folder "/TestSeamSettingsPreferencesPage" does not exist.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6918
URL: https://jira.jboss.org/browse/JBIDE-6918
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.Beta
Reporter: Nick Boldt
Assignee: Alexey Kazakov
These tests have been failing consistently for the past 12 builds:
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.Seam Project New Wizard Tests
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testFrameworkComponents
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testMessages
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testVarAttributes
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testInterface
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testSeamELContentAssist
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testSeamELContentAssistJbide1645
>>><<< org.jboss.tools.seam.ui.test.SeamUiAllTests.testSettingsPage
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBDS-982) Request adding a Server during the installation wizard
by Jim Tyrrell (JIRA)
Request adding a Server during the installation wizard
------------------------------------------------------
Key: JBDS-982
URL: https://jira.jboss.org/jira/browse/JBDS-982
Project: JBoss Developer Studio
Issue Type: Feature Request
Environment: JBDS 3.0 M4 on Linux JDK 6
Reporter: Jim Tyrrell
It would be nice when selecting for example an existing SOA-P install to have available in the server view, a way to validate what I have selected is correct. For example I was selecting /jboss-soa-p.4.3.0/jboss-as and it should have been /jboss-soa-p.4.3.0 instead. It would be nice if some validation could be done and the next button would be greyed out not active unless the expected correct path was selected. I am not sure if the path should be /jboss-soa-p.4.3.0/jboss-as or /jboss-soa-p.4.3.0 but part of me thinks this should be /jboss-soa-p.4.3.0/jboss-as and not the way it is today.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-7474) Usage reporting exception - in case no internet connection
by Vitali Yemialyanchyk (JIRA)
Usage reporting exception - in case no internet connection
----------------------------------------------------------
Key: JBIDE-7474
URL: https://jira.jboss.org/browse/JBIDE-7474
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: usage
Affects Versions: 3.2.0.Beta2
Reporter: Vitali Yemialyanchyk
HTTP GET to "http://anonsvn.jboss.org/repos/jbosstools/workspace/usage/usage.properties" failed, response code received "{1}"
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)
at java.net.Socket.connect(Socket.java:475)
at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:233)
at sun.net.www.http.HttpClient.New(HttpClient.java:306)
at sun.net.www.http.HttpClient.New(HttpClient.java:323)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:860)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:801)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:726)
at org.jboss.tools.usage.http.HttpRemotePropertiesProvider.request(HttpRemotePropertiesProvider.java:86)
at org.jboss.tools.usage.http.HttpRemotePropertiesProvider.getMap(HttpRemotePropertiesProvider.java:65)
at org.jboss.tools.usage.internal.preferences.GlobalUsageSettings.isAllInstancesReportingEnabled(GlobalUsageSettings.java:80)
at org.jboss.tools.usage.internal.preferences.GlobalUsageSettings.isReportingEnabled(GlobalUsageSettings.java:64)
at org.jboss.tools.usage.internal.reporting.UsageReport$ReportingJob.run(UsageReport.java:114)
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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBDS-1346) New Server Runtime for SOA Platform 5.2 needed
by Gary Lamperillo (JIRA)
New Server Runtime for SOA Platform 5.2 needed
----------------------------------------------
Key: JBDS-1346
URL: https://jira.jboss.org/browse/JBDS-1346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 4.0.0.M2
Environment: SOA-P 5.2 and JBDS 4 M2
Reporter: Gary Lamperillo
In the ESB Project creation , We need a EAP 5.1 or SOA-P 5.2. I prefer a SOA-P 5.2 in the runtime list, the advantage of a SOA-P 5.2 is that all of the ESB Project specific internals are known and the wizard would not need to have the subsequent screens if SOA-P 5.2 is selected instead of the community release.
Without a EAP 5.1 or SOA-P 5.2, the following warning appears :
This server type expects a version of 5.0 but the server directory is of version 5.1.0.
see screen attachments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months