[JBoss JIRA] (JBDS-2548) Add com.google.gdt.eclipse.suite.e42.feature to JBDS target platform to make building simpler
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2548?page=com.atlassian.jira.plugin.... ]
Vlado Pakan closed JBDS-2548.
-----------------------------
Verified on git
> Add com.google.gdt.eclipse.suite.e42.feature to JBDS target platform to make building simpler
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-2548
> URL: https://issues.jboss.org/browse/JBDS-2548
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Build, updatesite
> Affects Versions: 7.0.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> Discovered while documenting limitations & build instructions in JBDS-2456 that if we add com.google.gdt.eclipse.suite.e42.feature to the JBDS "multiple" target platform (or equivalently, if we we build using _mvn clean install -Punified.target -Dtpc.group=jbosstools_), we no longer need to include the *-Pjboss-requirements-composite-extras-mirror* profile to build JBDS, and can therefore build more simply like this:
> {code}mvn clean install -Pmaximum,multiple.target{code}
> So, I propose we add *com.google.gdt.eclipse.suite.e42.feature* to the JBDS TP so as to make building easier. The reason it's required is this dependency chain:
> *com.jboss.jbds.site.product* depends on *org.jboss.tools.maven.gwt* depends on bundle *com.google.gwt.eclipse.core* which is included in *com.google.gdt.eclipse.suite.e42.feature*.
> If you currently try to build using the JBDS TP and omit the *-Pjboss-requirements-composite-extras-mirror* profile flag, you get this:
> {code}
> [ERROR] Software being installed: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT
> [ERROR] Missing requirement: org.jboss.tools.maven.gwt 1.5.0.Alpha2-v20130412-2122-B29 requires 'bundle com.google.gwt.eclipse.core 2.5.0' but it could not be found
> {code}
> We could even go a step further and set multiple & maximum as defaults in the JBDS product root pom, so that a build need only be invoked with _mvn clean install_.
--
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
12 years, 10 months
[JBoss JIRA] (JBIDE-14722) Odd behavior out of eclipse browser & browsersim on Windows 7
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14722?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-14722:
-------------------------------------
[~burrsutter], I have followed your "step by step" demo video ( http://vimeo.com/67480300 ), and everything seems to work well. Here is my demo.html
{code}
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet"
href="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.css" />
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script
src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
<meta charset="UTF-8">
<title>Insert title here</title>
</head>
<body>
<div data-role="page" id="page-1" data-theme="b">
<div data-role="panel" id="panel-1">
<ul data-role="listview" id="listview-1" data-theme="b">
<li><a href="item1.html">Menu one</a></li>
<li><a href="#page-2">Menu two</a></li>
<li><a href="item3.html">Menu three</a></li>
</ul>
</div>
<div data-role="header" data-theme="b">
<a href="#panel-1" id="button-1" data-role="button" data-icon="bars" data-iconpos="notext" data-theme="b">Link button</a>
<h1>Contacts</h1>
<a href="#dialog-1" id="button-2" data-rel="dialog" data-role="button" data-icon="info" data-iconpos="notext">About</a>
</div>
<div data-role="content">
<p>Page content goes here.</p>
<div data-role="fieldcontain">
<label for="text-1">Name</label>
<input name="text-1" id="text-1" data-clear-btn="true" value="" placeholder="First name & Last Name" type="text"/>
</div>
<div data-role="fieldcontain">
<label for="email-1">Email</label>
<input name="email-1" id="email-1" data-clear-btn="true" value="" type="email"/>
</div>
<div data-role="fieldcontain">
<label for="tel-1">Phone</label>
<input name="tel-1" id="tel-1" data-clear-btn="true" value="" type="tel"/>
</div>
<div data-role="fieldcontain">
<label for="date-1">Birth Date</label>
<input name="date-1" id="date-1" data-clear-btn="true" value="" type="date"/>
</div>
</div>
<div data-role="footer" data-theme="b">
<h4>Contacts</h4>
</div>
</div>
<div data-role="dialog" id="dialog-1">
<div data-role="header">
<h1>About</h1>
</div>
<div data-role="content">
<h6>Dialog content.</h6>
About this application
<a href="#dialog-1" data-role="button" data-rel="back">OK</a>
</div>
</div>
<div data-role="page" id="page-2" data-theme="b">
<div data-role="header" data-theme="b">
<a href="#" data-role="button" data-rel="back" data-icon="back">Back</a>
<h1>Second page</h1>
</div>
<div data-role="content">
<p>Page content goes here.</p>
<div data-role="collapsible-set" id="collapsible-set-1" data-theme="b">
<div data-role="collapsible">
<h4>Orders</h4>
<p>Collapsible content.</p>
</div>
<div data-role="collapsible">
<h4>Key Contacts</h4>
<p>Collapsible content.</p>
</div>
<div data-role="collapsible">
<h4>Locations</h4>
<p>Collapsible content.</p>
</div>
</div>
</div>
</div>
<div data-role="footer" data-theme="b">
<h4>Second page</h4>
</div>
</div>
</body>
</html>
{code}
Screenshots:
!demo.png|thumbnail!
!internal.png|thumbnail!
Environment:
- Windows 7 64
- Beta1-v20130529-0631-B257
> Odd behavior out of eclipse browser & browsersim on Windows 7
> -------------------------------------------------------------
>
> Key: JBIDE-14722
> URL: https://issues.jboss.org/browse/JBIDE-14722
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Beta1
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Priority: Critical
> Attachments: demo.png, internal.png
>
>
> Version: 7.0.0.Beta1
> Build id: Beta1-v20130529-0631-B257
> Build date: 20130529-0631
> The internal Eclipse browser is not rendering the page correctly and browsersim is just blank.
> see screenshot - using Java 6 32-bit JDK
> http://screencast.com/t/jFYWPQYX
--
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
12 years, 10 months
[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
12 years, 10 months
[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
12 years, 10 months
[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
12 years, 10 months