[JBoss JIRA] (JBIDE-14607) Forge Wizards Menu
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14607?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-14607:
-------------------------------------
New Entity/Generate Entities should also prompt for "Persistence Setup" if needed.
Scaffold Entities should also prompt for "Scaffold Setup" if needed.
REST endpoint-from-entity should also prompt for "REST Setup" if needed.
> Forge Wizards Menu
> ------------------
>
> Key: JBIDE-14607
> URL: https://issues.jboss.org/browse/JBIDE-14607
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: forge
> Reporter: Burr Sutter
> Assignee: Koen Aers
> Attachments: forge_wizards.png
>
>
> The Forge Wizards are currently "buried" under Command/Ctrl-N, under the JBoss Tools category, they have no icons.
> New Project
> Persistence Setup
> New Entity
> New Field
> Generate Entities
> Scaffold Setup
> Scaffold Entities
> I propose the following:
> These be pulled into a category called "JBoss Forge"and that category also be available on the right-click/context New menu for any Maven-based project.
> I normally will use either the HTML5, Java EE Web or RichFaces archetypes from JBoss Central as the starting point for a project - then add entities/scaffolding via Forge.
--
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
[JBoss JIRA] (JBIDE-14676) Preview in jQuery Mobile Palette wizards does not work on Mac OS
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14676?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-14676.
-------------------------------
Verified with JBDS 7.0.0 Beta1-v20130529-0631-B257
> Preview in jQuery Mobile Palette wizards does not work on Mac OS
> ----------------------------------------------------------------
>
> Key: JBIDE-14676
> URL: https://issues.jboss.org/browse/JBIDE-14676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Beta1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.0.Beta1
>
>
> In product, plugin org.jboss.tools.jst.web is deployed as a jar. HTML loaded to preview references js and css files using protocol "jar:". It turns out that some browsers do not support it. We have to unpack these files to plugin state location and reference them using protocol 'file:' supported by all browsers.
--
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
[JBoss JIRA] (JBIDE-14701) openshift-java-client: DomainResourceIntegrationTest#shouldContainErrorMessageAndContainErrorCode128 is failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14701?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14701:
------------------------------------------
pushed upstream
> openshift-java-client: DomainResourceIntegrationTest#shouldContainErrorMessageAndContainErrorCode128 is failing
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14701
> URL: https://issues.jboss.org/browse/JBIDE-14701
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
>
> The test makes sure that there's an application and then kills the domain without using "force" which is supposed the fail. The exception that's being thrown then is asserted for the Messages it is supposed contain.
> The test fails in the following assertion:
> {code}
> assertThat(e.getRestResponse().getMessages().get(0)).isNotNull();
> {code}
> The assertion fails with the following error:
> {code}
> java.lang.AssertionError: expecting actual value not to be null
> at org.fest.assertions.Fail.failure(Fail.java:228)
> at org.fest.assertions.Fail.fail(Fail.java:167)
> at org.fest.assertions.Fail.failIfActualIsNull(Fail.java:100)
> at org.fest.assertions.GenericAssert.isNotNull(GenericAssert.java:238)
> at com.openshift.internal.client.DomainResourceIntegrationTest.shouldContainErrorMessageAndContainErrorCode128(DomainResourceIntegrationTest.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> {code}
> This is a regression that was most likely introduced when resolving JBIDE-14509
--
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
[JBoss JIRA] (JBIDE-14701) openshift-java-client: DomainResourceIntegrationTest#shouldContainErrorMessageAndContainErrorCode128 is failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14701?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14701:
------------------------------------------
I kept the *null* key to closely match what OpenShift returns to me. I simply added an additional key in Message#FIELD_DEFAULT to access this message in a more readable way.
> openshift-java-client: DomainResourceIntegrationTest#shouldContainErrorMessageAndContainErrorCode128 is failing
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14701
> URL: https://issues.jboss.org/browse/JBIDE-14701
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
>
> The test makes sure that there's an application and then kills the domain without using "force" which is supposed the fail. The exception that's being thrown then is asserted for the Messages it is supposed contain.
> The test fails in the following assertion:
> {code}
> assertThat(e.getRestResponse().getMessages().get(0)).isNotNull();
> {code}
> The assertion fails with the following error:
> {code}
> java.lang.AssertionError: expecting actual value not to be null
> at org.fest.assertions.Fail.failure(Fail.java:228)
> at org.fest.assertions.Fail.fail(Fail.java:167)
> at org.fest.assertions.Fail.failIfActualIsNull(Fail.java:100)
> at org.fest.assertions.GenericAssert.isNotNull(GenericAssert.java:238)
> at com.openshift.internal.client.DomainResourceIntegrationTest.shouldContainErrorMessageAndContainErrorCode128(DomainResourceIntegrationTest.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> {code}
> This is a regression that was most likely introduced when resolving JBIDE-14509
--
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
[JBoss JIRA] (JBIDE-14701) openshift-java-client: DomainResourceIntegrationTest#shouldContainErrorMessageAndContainErrorCode128 is failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14701?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-14701 at 6/3/13 7:59 AM:
------------------------------------------------------------------
*e.getRestresponse().getMessages()* returns a map with the following content:
{code}
{null=Operation failed with exit code "128".Reason given: "Domain contains applications. Delete applications first or set force to true."}
{code}
Notice the erroneous "null" key and erroneous way accessing the messages via an integer *getMessages().get(0)*
was (Author: adietish):
*e.getRestresponse().getMessages()* returns a map with the following content:
{code}
{null=Operation failed with exit code "128".Reason given: "Domain contains applications. Delete applications first or set force to true."}
{code}
Notice the erroneous "null" key and erroneous accessing scheme as if it was a list *getMessages().get(0)*
> openshift-java-client: DomainResourceIntegrationTest#shouldContainErrorMessageAndContainErrorCode128 is failing
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14701
> URL: https://issues.jboss.org/browse/JBIDE-14701
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
>
> The test makes sure that there's an application and then kills the domain without using "force" which is supposed the fail. The exception that's being thrown then is asserted for the Messages it is supposed contain.
> The test fails in the following assertion:
> {code}
> assertThat(e.getRestResponse().getMessages().get(0)).isNotNull();
> {code}
> The assertion fails with the following error:
> {code}
> java.lang.AssertionError: expecting actual value not to be null
> at org.fest.assertions.Fail.failure(Fail.java:228)
> at org.fest.assertions.Fail.fail(Fail.java:167)
> at org.fest.assertions.Fail.failIfActualIsNull(Fail.java:100)
> at org.fest.assertions.GenericAssert.isNotNull(GenericAssert.java:238)
> at com.openshift.internal.client.DomainResourceIntegrationTest.shouldContainErrorMessageAndContainErrorCode128(DomainResourceIntegrationTest.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> {code}
> This is a regression that was most likely introduced when resolving JBIDE-14509
--
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
[JBoss JIRA] (JBIDE-14727) SeamRuntimeDetectionTest test failure
by Victor Rubezhny (JIRA)
Victor Rubezhny created JBIDE-14727:
---------------------------------------
Summary: SeamRuntimeDetectionTest test failure
Key: JBIDE-14727
URL: https://issues.jboss.org/browse/JBIDE-14727
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.1.0.Beta1
Environment: RHEL 5 x86_64 Oracle JDK 1.7
Reporter: Victor Rubezhny
Fix For: 4.1.0.Beta2
Issue is reproducible not only on RHEL 6 x86, Oracle JDK 1.6 configuration as well.
{code}org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice (from org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests)
Failing for the past 15 builds (Since #381 )
Took 1.3 sec.
add description
Error Message
expected:<1> but was:<2>
Stacktrace
java.lang.AssertionError: expected:<1> but was:<2>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice(SeamRuntimeDetectionTest.java:368)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
{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
11 years
[JBoss JIRA] (JBIDE-13645) Run on iOS simulator
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13645?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-13645.
----------------------------------
Verified in JBoss Tools 4.1.0.Beta1b
> Run on iOS simulator
> --------------------
>
> Key: JBIDE-13645
> URL: https://issues.jboss.org/browse/JBIDE-13645
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Labels: noteworthy
> Fix For: 4.1.0.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> This is needed to provide "Run on iOS Simulator" functionality. Ideally the solution should be able to change the different types of iOS devices that are started through a Launch Configuration dialog.
--
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