[JBoss JIRA] Created: (JBDS-1715) JBossAS Tools has changed EAP default deploy to 'server', JBDS needs to set property for metadata deployment
by Rob Stryker (JIRA)
JBossAS Tools has changed EAP default deploy to 'server', JBDS needs to set property for metadata deployment
-------------------------------------------------------------------------------------------------------------
Key: JBDS-1715
URL: https://issues.jboss.org/browse/JBDS-1715
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Reporter: Rob Stryker
Assignee: Rob Stryker
Because JBossAS Tools has found most people using EAP are using their own downloaded versions of EAP, these versions are secured. Therefore for out-of-the-box experience, users must switch the deployment location to server-based, or unsecure their EAP, etc.
ASTools has switched to defaulting EAP to server-based, and so a solution needs to be provided to allow JBDS to auto-configure the bundled EAP and created server to default to metadata deployment
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9316) Missing Java Runtime selector in AS7 runtime definition
by Fred Bricon (JIRA)
Missing Java Runtime selector in AS7 runtime definition
-------------------------------------------------------
Key: JBIDE-9316
URL: https://issues.jboss.org/browse/JBIDE-9316
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M2
Environment: JBT AS plugins from trunk
Reporter: Fred Bricon
Assignee: Rob Stryker
Attachments: java_runtime_selection_as6.jpg, missing_java_runtime_selection_as7.jpg
When creating or modifying an existing AS7 runtime, there is no way you can choose a Java Runtime Environment, like JBoss AS6 or Tomcat server adapters.
It bit me when I wanted to try AS7 with the new JDK7 CR1. It's a severly lacking feature IMHO.
So you need to :
- add the missing UI bits
- make sure AS7 is run using the selected JRE
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9394) BuilderOrderValidationTest.testWrongBuildOrderPreference() failure
by Alexey Kazakov (JIRA)
BuilderOrderValidationTest.testWrongBuildOrderPreference() failure
------------------------------------------------------------------
Key: JBIDE-9394
URL: https://issues.jboss.org/browse/JBIDE-9394
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M3
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.x
This test fails from time to time. I can say in my computer it happens ~ every 20th time ;)
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.cdi.core.test.CDICoreAllTests
Tests run: 350, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 509.015 sec <<< FAILURE!
testWrongBuildOrderPreference(org.jboss.tools.cdi.core.test.tck.validation.BuilderOrderValidationTest) Time elapsed: 0.748 sec <<< FAILURE!
junit.framework.AssertionFailedError: expected:<2> but was:<3>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at junit.framework.Assert.assertEquals(Assert.java:201)
at org.jboss.tools.cdi.core.test.tck.validation.BuilderOrderValidationTest.testWrongBuildOrderPreference(BuilderOrderValidationTest.java:82)
...
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9380) IncrementalValidationTest.testAlternativesInBeansXml() failure
by Alexey Kazakov (JIRA)
IncrementalValidationTest.testAlternativesInBeansXml() failure
--------------------------------------------------------------
Key: JBIDE-9380
URL: https://issues.jboss.org/browse/JBIDE-9380
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M3
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 3.3.0.M3
{code}
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 14.995 sec <<< FAILURE!
testAlternativesInBeansXml(org.jboss.tools.cdi.core.test.tck.validation.IncrementalValidationTest) Time elapsed: 2.338 sec <<< FAILURE!
junit.framework.AssertionFailedError: Marker matches the 'No bean is eligible for injection to the injection point \[JSR-299 §5.2.1\]' pattern was found
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertFalse(Assert.java:34)
at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsNotCreated(AbstractResourceMarkerTest.java:238)
at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsNotCreated(AbstractResourceMarkerTest.java:232)
at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsNotCreated(AbstractResourceMarkerTest.java:393)
at org.jboss.tools.cdi.core.test.tck.validation.IncrementalValidationTest.testAlternativesInBeansXml(IncrementalValidationTest.java:129)
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months