July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17393) Show on main Central page the "Early Access" status

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17393?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-17393: ----------------------------------------- Wow! You guys don't make things simple do you :) I suggest the 'labels' should be: * Nothing when nothing installed and not enabled * 'Early Access enabled' for when EA is enabled, regardless of whether things are installed * 'Early Access features installed but disabled' - this is the one that users need to know, they've installed something and can't see changes to examples or updates and need to know it's because they don't have EA enabled > Show on main Central page the "Early Access" status > --------------------------------------------------- > > Key: JBIDE-17393 > URL: https://issues.jboss.org/browse/JBIDE-17393 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: early-access > Fix For: 4.2.0.Beta3 > > > The main Central page (not Software one) should show the "Early Access" status. It can be one of > * No Early Access component installed, no Early Access enabled (shows nothing) > * No Early Access component installed, Early Access enabled (shows Early Access enabled) > * at least 1 Early Access component installed, Early Access Enabled > * at least 1 Early Access component installed, Early Access not Enabled -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17562) Wrong schema location in beans.xml

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17562?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-17562. ------------------------------------ Verified in JBDS 8.0.0.Beta3-v20140706-0939-B172 > Wrong schema location in beans.xml > ---------------------------------- > > Key: JBIDE-17562 > URL: https://issues.jboss.org/browse/JBIDE-17562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Beta2 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17761) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [OpenShift]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17761?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17761: ------------------------------------------ bumped pom in master branch to 4.2.0.CR1-SNAPSHOT > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [OpenShift] > ------------------------------------------------------- > > Key: JBIDE-17761 > URL: https://issues.jboss.org/browse/JBIDE-17761 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta3 > > > For JBIDE 4.2.0.Beta3 [OpenShift]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3 > [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Beta3x > git push origin jbosstools-4.2.0.Beta3x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and > * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17729) compile failure in Seam (JavaEE)

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17729?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-17729. -------------------------------- > compile failure in Seam (JavaEE) > -------------------------------- > > Key: JBIDE-17729 > URL: https://issues.jboss.org/browse/JBIDE-17729 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, seam2 > Affects Versions: 4.2.0.Beta3 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Blocker > Fix For: 4.2.0.Beta3 > > > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.jboss.tools.seam.ui: Compilation failure: Compilation failure: > [ERROR] /home/daniel/git/jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/DBTablesViewer.java:[247] > [ERROR] Settings newSettings = cfg.buildSettings(); > [ERROR] ^^^^^^^^^^^^^^^^^^^ > [ERROR] Type mismatch: cannot convert from ISettings to Settings > [ERROR] 1 problem (1 error) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3033) Missing RichFaces maven archetypes

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3033?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3033: ----------------------------- CDW devel_ack: ? (was: +) CDW release: ? (was: +) > Missing RichFaces maven archetypes > ---------------------------------- > > Key: JBDS-3033 > URL: https://issues.jboss.org/browse/JBDS-3033 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: maven > Affects Versions: 8.0.0.Beta1 > Reporter: Juraj Húska > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 8.0.0.Beta3 > > > There is no RichFaces archetype available for selection, when trying to create a maven project. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3033) Missing RichFaces maven archetypes

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3033?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3033: ------------------------------ Component/s: (was: central) > Missing RichFaces maven archetypes > ---------------------------------- > > Key: JBDS-3033 > URL: https://issues.jboss.org/browse/JBDS-3033 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: maven > Affects Versions: 8.0.0.Beta1 > Reporter: Juraj Húska > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 8.0.0.Beta3 > > > There is no RichFaces archetype available for selection, when trying to create a maven project. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17404) CordovaSim cannot be launched on RHEL7

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17404?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-17404: ------------------------------------- < Konstantin Marmalyukov is there a reason why GTK3 (contains /usr/lib64/libwebkitgtk-3.0.so.0) could not be the default? [~kpiwko], due to JavaFx web-engine, which is not available if running against GTK 3 - http://stackoverflow.com/questions/21093723/how-to-run-javafx-application.... Here is the related JavaFx jira - https://javafx-jira.kenai.com/browse/RT-35264 < If using EPEL depedency is fine, I believe that RPM distros should use yum provide yum install combo in instructions as this is the most flexible. What combo do you mean? could you possibly insert commands here? > CordovaSim cannot be launched on RHEL7 > -------------------------------------- > > Key: JBIDE-17404 > URL: https://issues.jboss.org/browse/JBIDE-17404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Environment: RHEL7 latest, 64bit > Installed webkitgtk3-devel 0:2.0.4-6-el7 > TicketMonster Cordava example from latest WFK > JBDS 8.0.0.Beta1 > OpenJDK 7 > Reporter: Karel Piwko > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > Attachments: CordovaSimFailure.png, libwebkit2gtk.content, snapshot1.png, webkitgtk.content, webkitgtk3.content > > > Launching BrowserSim fails with NPE, adding information from workspace log > Before webkitgtk3-devel is installed > {code} > !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 13:03:54.128 > !MESSAGE org.jboss.tools.aerogear.hybrid.core > !ENTRY org.jboss.tools.vpe.browsersim 4 0 2014-05-23 13:03:56.162 > !MESSAGE BrowserSim is failed to start with the following error: > "No more handles" > Please note that WebKitGTK 1.2.0 or newer must be installed and available in the library load path. > If not, use your package manager to install libwebkitgtk. > Also see <a href="https://community.jboss.org/docs/DOC-18100">BrowserSim FAQ</a>. > Stack trace: > org.eclipse.swt.SWTError: No more handles > at org.eclipse.swt.SWT.error(SWT.java:4467) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.SWT.error(SWT.java:4327) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:103) > at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:36) > at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:25) > at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:37) > at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:39) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:189) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:90) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:84) > {code} > After: > {code} > !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380 > !MESSAGE org.jboss.tools.aerogear.hybrid.core > !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380 > !MESSAGE org.jboss.tools.aerogear.hybrid.core > !ENTRY org.eclipse.core.jobs 4 2 2014-05-23 14:03:57.395 > !MESSAGE An internal error occurred during: "Launching TicketMonster-Cordova". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:157) > at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:115) > at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:24) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17582) Classes with same name screw up code coverage

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17582?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-17582. -------------------------------- > Classes with same name screw up code coverage > --------------------------------------------- > > Key: JBIDE-17582 > URL: https://issues.jboss.org/browse/JBIDE-17582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, hibernate > Affects Versions: 4.2.0.Beta3 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.Beta3 > > > Several bundles contain class with same name: org/jboss/tools/hibernate/proxy/ConfigurationProxy . Classes with same name are confusing, so that for example, it causes code coverage analysis to fail. > When copying a class, it's recommended to at least change the package. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-14305: ------------------------------ Fix Version/s: 4.2.0.CR1 > Error popup when runing schema ddl with Hibernate Configurations > ----------------------------------------------------------------- > > Key: JBIDE-14305 > URL: https://issues.jboss.org/browse/JBIDE-14305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: labdoui labdoui > Assignee: Koen Aers > Priority: Minor > Fix For: 4.1.0.Beta2, 4.2.0.CR1 > > > Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema > to reproduce the problem just explore the database from hibernate console > java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V > at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) > at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26) > at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) > at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17678) Country combo box has an empty space above the list of countries

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17678?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17678: -------------------------------- Priority: Minor (was: Major) > Country combo box has an empty space above the list of countries > ---------------------------------------------------------------- > > Key: JBIDE-17678 > URL: https://issues.jboss.org/browse/JBIDE-17678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, upstream > Affects Versions: 4.2.0.Beta2 > Environment: Ubuntu 12.04 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.x > > Attachments: jbossorg-TC-download-runtime-wizard.png, jpp 610 country combo 1.jpg, jpp 610 country combo 2.jpg, jpp 610 country combo 3.jpg > > > While selecting country in Terms and Conditions page of download runtime wizard, there is an empty space above the list of countries. The empty space grows when scrolling up. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014