[JBoss JIRA] (JBIDE-19039) Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19039?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-19039:
---------------------------------------
The forge component doesn't compute wizard window size. It is calculated from upstream in the Window class. Since all wizards work in this way, I think we shouldn't change that behaviour.
Besides, I can't reproduce the issue. On my monitor, the forge wizards look the same in the portrait and landscape mode.
Could you describe what some standard Eclipse wizard looks like on your monitor?
> Window size shouldn't be computed proportionally to 'display' size but rather aligned with the components
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19039
> URL: https://issues.jboss.org/browse/JBIDE-19039
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.2.Final
> Reporter: Pavol Srna
> Assignee: Snjezana Peco
> Attachments: forge-scaffold-window.png, other-wizard.png
>
>
> Wizard window size shouldn't be computed proportionally to 'display' size. But instead it should be aligned with the components that are in the wizard.
> You can see on the screenshots how it looks when you have your monitor in portrait orientation.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19056:
----------------------------------------
I gave a first shot to such mojo, which is accessible in https://github.com/mickaelistria/jbosstools-maven-plugins/tree/JBIDE-19056
Then it can be set on any module producing p2 installable unit to compare versions with baseline.
{code:xml}
<plugin>
<groupId>org.jboss.tools.tycho-plugins</groupId>
<artifactId>repository-utils</artifactId>
<version>0.22.1-SNAPSHOT</version>
<executions>
<execution>
<goals>
<goal>compare-version-with-baselines</goal>
</goals>
<phase>verify</phase>
<configuration>
<baselines>
<repo>http://download.jboss.org/jbosstools/updates/stable/luna</repo>
</baselines>
</configuration>
</execution>
</executions>
</plugin>
{code}
For example, when this is set and we're trying to build org.jboss.tools.usage bundle from master, build fails with
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) on project org.jboss.tools.usage: Version of 'org.jboss.tools.usage/2.0.0.Alpha1-v20150123-1146) must be bigger than baseline one (2.0.1.Final-v20141209-0333-B84) -> [Help 1]
{code}
I believe this should definitely make us less error-prone with version management.
CC [~nickboldt] [~jpeterka] [~mmalina] [~maxandersen] [~fbricon]
> A Mojo to validate a version (compared to baseline)
> ---------------------------------------------------
>
> Key: JBIDE-19056
> URL: https://issues.jboss.org/browse/JBIDE-19056
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released.
> Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-12274) BrowserSim borks on jquery mobile (RHEL 6.1)
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12274?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-12274:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.0.0.Alpha1)
(was: 4.3.x)
> BrowserSim borks on jquery mobile (RHEL 6.1)
> --------------------------------------------
>
> Key: JBIDE-12274
> URL: https://issues.jboss.org/browse/JBIDE-12274
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 3.3.0.CR1
> Environment: RHEL 6.1
> JBoss Developer Studio 5.0.0.CR1
> Reporter: Gabriel De Repentigny
> Assignee: Konstantin Marmalyukov
> Labels: upstream
> Fix For: 4.3.0.Alpha1
>
> Attachments: jQMrefsRemoved.png, midori-browsersim.png, midori-browsersim.png, python-tabbed-browser.png, Screenshot-BrowserSim .png, windows-7_Safari-5.1.2-7534.52.7.png
>
>
> I'm walking through the JBoss Way Ticket Monster lab. JDS's BrowserSim borks while trying to render mobile.html (pasted below) which is part of the tutorial.
> The problem seems to be with the jquery mobile js file. If you take that include out, it renders (sans-mobile styling).
> {code:xml}
> <!DOCTYPE html>
> <html>
> <head>
> <title>jQuery Mobile Template</title>
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
> <meta name="viewport" content="width=device-width, initial-scale=1" />
> <link rel="stylesheet"
> href="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.css" />
> <script type="text/javascript"
> src="http://code.jquery.com/jquery-1.7.1.min.js"></script>
> <script type="text/javascript"
> src="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.js"></script>
> <script type="text/javascript">
> $(document).on("pageinit", "#page1", function(event){
> alert("Ready To Go");
> });
> $.getJSON("rest/events", function(events) {
> // console.log("returned are " + results);
> var listOfEvents = $("#listOfItems");
> listOfEvents.empty();
> $.each(events, function(index, event) {
> // console.log(event.name);
> listOfEvents.append("<li><a href=’#’>" + event.name + "</a>");
> });
> listOfEvents.listview("refresh");
> });
> </script>
> </head>
> <body>
> <div data-role="page" id="page1">
> <div data-role="header">
> <h1>jQuery Mobile</h1>
> </div>
> <div data-role="content">
> <ul id="listOfItems" data-role="listview" data-inset="true"
> data-filter="true">
> <li><a href="">One</a></li>
> <li><a href="">Two</a></li>
> <li><a href="">Three</a></li>
> </ul>
> </div>
> <div data-role="footer">
> <h4>www.jboss.org/developer</h4>
> </div>
> </div>
> </body>
> </html>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-17632) Support rendering of JSF widgets in preview mode of VPE editor
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17632?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-17632.
--------------------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.3.x)
Resolution: Rejected
> Support rendering of JSF widgets in preview mode of VPE editor
> --------------------------------------------------------------
>
> Key: JBIDE-17632
> URL: https://issues.jboss.org/browse/JBIDE-17632
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks, Oracle JDK 7u60, Oracle JDK 8u5
> Reporter: Vineet Reynolds
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha1
>
> Attachments: PreviewMode-JBDS8.jpg, visual_page_editor.png
>
>
> JSF input widgets in XHTML files are rendered as plain text, when viewed in Visual mode of the JBoss Tools HTML editor.
> This is a side-effect of using tha WebKit engine in Mac, to perform the rendering:
> {noformat}
> kmarmaliykov: vineetr: Now everything is rendered using modern webkit engine. It works perfect for HTML5 pages but hasn't support jsf tags
> {noformat}
> This is being raised as a tracker issue for JBDS 8, since:
> {noformat}
> kmarmaliykov: vineetr: For JBDS8 the main goal was to provide good preview for html5 pages
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBTIS-322) Missing dependency for teiid JBDSIS 8.0.0
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-322?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-322.
-----------------------------------
Verified with JBDS-IS 8.0.0.CR1
> Missing dependency for teiid JBDSIS 8.0.0
> -----------------------------------------
>
> Key: JBTIS-322
> URL: https://issues.jboss.org/browse/JBTIS-322
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform, teiid
> Affects Versions: 4.2.0.Alpha2
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.2.0.Beta1a-TP, 8.0.0.Beta1, 4.2.0.Beta1
>
>
> Running the JBoss Central installer with JBDSIS 8.0.0.Alpha2 like this:
> ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.0.Alpha2/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.0.Alpha2
> And selecting all components causes teiid only to fail with:
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Teiid Designer 8.6.1.Alpha1-v20140916-1443-B176 (org.teiid.designer.feature.feature.group 8.6.1.Alpha1-v20140916-1443-B176)
> Missing requirement: org.teiid.datatools.connectivity.ui 8.6.1.Alpha1-v20140916-1443-B176 (org.teiid.datatools.connectivity.ui 8.6.1.Alpha1-v20140916-1443-B176) requires 'bundle org.eclipse.birt.report.data.oda.hive.ui [4.3.2,5.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: Teiid Designer 8.6.1.Alpha1-v20140916-1443-B176 (org.teiid.designer.feature.feature.group 8.6.1.Alpha1-v20140916-1443-B176)
> To: org.teiid.datatools.connectivity.ui [8.1.0,9.0.0)
> Teiid does successfully install with the p2 installer.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBTIS-241) JBDSIS 7.0.0 fails to install Teiid, Designer, Client into JBDS 8.0.0.alpha
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-241?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-241.
-----------------------------------
Verified with
* JBDS 7.1.1.GA + JBDS-IS 7.0.3.GA
* JBDS 8.0.2.GA + JBDS-IS 8.0.0.CR1
> JBDSIS 7.0.0 fails to install Teiid, Designer, Client into JBDS 8.0.0.alpha
> ----------------------------------------------------------------------------
>
> Key: JBTIS-241
> URL: https://issues.jboss.org/browse/JBTIS-241
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: teiid
> Affects Versions: 4.0.1
> Reporter: Len DiMaggio
> Assignee: Barry LaFond
> Fix For: 8.0.0.Beta1
>
>
> With JBDS 8.0.0.alpha2:
> Version: 8.0.0.Alpha2
> Build id: Alpha2-v20140214-1707-B71
> Build date: 20140214-1707
> And JBDSIS 7.0.0:
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack
> These plugins fail to install:
> * Teiid Designer
> * Teiid Designer Runtime
> * Teiid Runtime Clients
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Teiid Designer 8.3.1.Final-v20140122-1920-B21 (org.teiid.designer.feature.feature.group 8.3.1.Final-v20140122-1920-B21)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.Alpha2-v20140214-1707-B71 (com.jboss.devstudio.core.package 8.0.0.Alpha2-v20140214-1707-B71)
> Only one of the following can be installed at once:
> Mbeans Plug-in 3.0.0.Alpha2-v20140212-1516-B15 (org.jboss.ide.eclipse.as.ui.mbeans 3.0.0.Alpha2-v20140212-1516-B15)
> Mbeans Plug-in 2.4.101.Final-v20131206-1843-B159 (org.jboss.ide.eclipse.as.ui.mbeans 2.4.101.Final-v20131206-1843-B159)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Alpha2-v20140214-1707-B71 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Alpha2-v20140214-1707-B71)
> To: org.jboss.ide.eclipse.as.feature.feature.group [3.0.0.Alpha2-v20140212-1516-B15]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.Alpha2-v20140214-1707-B71 (com.jboss.devstudio.core.package 8.0.0.Alpha2-v20140214-1707-B71)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.Alpha2-v20140214-1707-B71]
> Cannot satisfy dependency:
> From: JBossAS Tools 2.4.101.Final-v20131206-1843-B159 (org.jboss.ide.eclipse.as.feature.feature.group 2.4.101.Final-v20131206-1843-B159)
> To: org.jboss.ide.eclipse.as.ui.mbeans [2.4.101.Final-v20131206-1843-B159]
> Cannot satisfy dependency:
> From: JBossAS Tools 3.0.0.Alpha2-v20140212-1516-B15 (org.jboss.ide.eclipse.as.feature.feature.group 3.0.0.Alpha2-v20140212-1516-B15)
> To: org.jboss.ide.eclipse.as.ui.mbeans [3.0.0.Alpha2-v20140212-1516-B15]
> Cannot satisfy dependency:
> From: Teiid Designer 8.3.1.Final-v20140122-1920-B21 (org.teiid.designer.feature.feature.group 8.3.1.Final-v20140122-1920-B21)
> To: org.jboss.ide.eclipse.as.feature.feature.group [2.4.100,3.0.0)
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Teiid Runtime Clients 8.3.1.Final-v20140122-1920-B21 (org.teiid.designer.teiid.client.feature.feature.group 8.3.1.Final-v20140122-1920-B21)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.Alpha2-v20140214-1707-B71 (com.jboss.devstudio.core.package 8.0.0.Alpha2-v20140214-1707-B71)
> Only one of the following can be installed at once:
> Core Runtime 3.10.0.v20140123-0905 (org.eclipse.core.runtime 3.10.0.v20140123-0905)
> Core Runtime 3.9.0.v20130326-1255 (org.eclipse.core.runtime 3.9.0.v20130326-1255)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.Alpha2-v20140214-1707-B71 (com.jboss.devstudio.core.package 8.0.0.Alpha2-v20140214-1707-B71)
> To: toolingcom.jboss.devstudio.core.package.configuration [8.0.0.Alpha2-v20140214-1707-B71]
> Cannot satisfy dependency:
> From: JBoss AS Core Plug-in 2.4.101.Final-v20131206-1843-B159 (org.jboss.ide.eclipse.as.core 2.4.101.Final-v20131206-1843-B159)
> To: bundle org.eclipse.core.runtime [3.7.0,3.10.0)
> Cannot satisfy dependency:
> From: Teiid Runtime Clients 8.3.1.Final-v20140122-1920-B21 (org.teiid.designer.teiid.client.feature.feature.group 8.3.1.Final-v20140122-1920-B21)
> To: org.jboss.ide.eclipse.as.core [2.4.0,3.0.0)
> Cannot satisfy dependency:
> From: toolingcom.jboss.devstudio.core.package.configuration 8.0.0.Alpha2-v20140214-1707-B71
> To: toolinggtk.linux.x86_64org.eclipse.core.runtime [8.0.0.Alpha2-v20140214-1707-B71]
> Cannot satisfy dependency:
> From: toolinggtk.linux.x86_64org.eclipse.core.runtime 8.0.0.Alpha2-v20140214-1707-B71
> To: bundle org.eclipse.core.runtime 3.10.0.v20140123-0905
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Teiid Designer Runtime 8.3.1.Final-v20140122-1920-B21 (org.teiid.designer.runtime.feature.feature.group 8.3.1.Final-v20140122-1920-B21)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.Alpha2-v20140214-1707-B71 (com.jboss.devstudio.core.package 8.0.0.Alpha2-v20140214-1707-B71)
> Only one of the following can be installed at once:
> JBoss Server Tools - Runtimes Integration 3.0.0.Alpha2-v20140212-1516-B15 (org.jboss.tools.as.runtimes.integration 3.0.0.Alpha2-v20140212-1516-B15)
> JBoss Server Tools - Runtimes Integration 2.4.101.Final-v20131206-1843-B159 (org.jboss.tools.as.runtimes.integration 2.4.101.Final-v20131206-1843-B159)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Alpha2-v20140214-1707-B71 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Alpha2-v20140214-1707-B71)
> To: org.jboss.ide.eclipse.as.feature.feature.group [3.0.0.Alpha2-v20140212-1516-B15]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.Alpha2-v20140214-1707-B71 (com.jboss.devstudio.core.package 8.0.0.Alpha2-v20140214-1707-B71)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.Alpha2-v20140214-1707-B71]
> Cannot satisfy dependency:
> From: JBossAS Tools 3.0.0.Alpha2-v20140212-1516-B15 (org.jboss.ide.eclipse.as.feature.feature.group 3.0.0.Alpha2-v20140212-1516-B15)
> To: org.jboss.tools.as.runtimes.integration [3.0.0.Alpha2-v20140212-1516-B15]
> Cannot satisfy dependency:
> From: JBossAS Tools 2.4.101.Final-v20131206-1843-B159 (org.jboss.ide.eclipse.as.ui 2.4.101.Final-v20131206-1843-B159)
> To: bundle org.jboss.tools.as.runtimes.integration [2.4.0,3.0.0)
> Cannot satisfy dependency:
> From: Teiid Designer Runtime 8.3.1.Final-v20140122-1920-B21 (org.teiid.designer.runtime.feature.feature.group 8.3.1.Final-v20140122-1920-B21)
> To: org.jboss.ide.eclipse.as.ui [2.4.0,3.0.0)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19079) SWTException when creating JPA 2.0 project
by Koen Aers (JIRA)
Koen Aers created JBIDE-19079:
---------------------------------
Summary: SWTException when creating JPA 2.0 project
Key: JBIDE-19079
URL: https://issues.jboss.org/browse/JBIDE-19079
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Reporter: Koen Aers
Assignee: Koen Aers
Fix For: 4.3.0.Alpha1, 4.2.3.Beta1
This is the produced stacktrace:
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4441)
at org.eclipse.swt.SWT.error(SWT.java:4356)
at org.eclipse.swt.SWT.error(SWT.java:4327)
at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:903)
at org.hibernate.eclipse.console.views.KnownConfigurationsProvider.refreshTree(KnownConfigurationsProvider.java:91)
at org.hibernate.eclipse.console.views.KnownConfigurationsProvider.access$0(KnownConfigurationsProvider.java:85)
at org.hibernate.eclipse.console.views.KnownConfigurationsProvider$KnownConfigurationsVisitor.visit(KnownConfigurationsProvider.java:163)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
at org.hibernate.eclipse.console.views.KnownConfigurationsProvider.resourceChanged(KnownConfigurationsProvider.java:141)
at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months