July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17241) Forge should use the m2e settings.xml during Maven artifact resolution

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17241?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-17241. ------------------------------ Verified in jbt 4.2.0.Beta3 respin-c. > Forge should use the m2e settings.xml during Maven artifact resolution > ---------------------------------------------------------------------- > > Key: JBIDE-17241 > URL: https://issues.jboss.org/browse/JBIDE-17241 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Labels: respin-b > Fix For: 4.2.0.Beta3 > > > When I have a project like TicketMonster or any of the WFK examples in my workspace, I configure m2e to use a separate settings.xml file (say ~/.m2/contributor-settings.xml or ~/.m2/redhat-repos.xml) which point to the RedHat enterprise repositories or other repos. My usual settings.xml file lacks this. > Forge uses the ~/.m2/settings.xml file by default, even though the Eclipse workspace uses a different one. From the point of view of end-users this results in weird behavior in Forge. For example, Forge facets are not activated correctly because the Maven artifacts in the Red Hat enterprise repo could not be found. > It requires the user to modify the content of ~/.m2/settings.xml instead of just pointing to a different one, which is a bit unreasonable of Forge, given the current capabilites of m2e. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17536: --------------------------------------------- btw. where is the content for /updates/staging moving ? dont we technically just need a staging/luna composite ? > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15842) JPA Hibernate validation rules are too strict by default

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15842?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBIDE-15842: --------------------------------------- Are you gonna fix this? if you look at http://docs.oracle.com/javaee/6/api/javax/persistence/ManyToOne.html there is clearly written targetEntity - (Optional) The entity class that is the target of the association. > JPA Hibernate validation rules are too strict by default > -------------------------------------------------------- > > Key: JBIDE-15842 > URL: https://issues.jboss.org/browse/JBIDE-15842 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: hibernate > Reporter: Tomas Remes > Assignee: Koen Aers > Fix For: 4.2.x > > > When you for example import Seam UI example (https://github.com/seam2/jboss-seam/tree/Seam_2_3/examples/ui) to JBDS, you will face a lot of IMO unnecessary errors, which are fired by JPA validator. E.g: > "Target entity is not defined" > These rules are in most cases defined as optional attributes of JPA annotations, therefore I think the validation rules are too strict - many of them have error level by default. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17822) Launch shortcut enablement expression caused exception

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17822?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-17822: ------------------------------------- Assignee: Xavier Coulon > Launch shortcut enablement expression caused exception > ------------------------------------------------------ > > Key: JBIDE-17822 > URL: https://issues.jboss.org/browse/JBIDE-17822 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > Attachments: error1, error2, error3, error4, error5 > > > Sometimes when expanding JAX-RS Explorer, a bunch of errors appears in Error Log. > There are 5 similar errors: > {code} > Launch shortcut 'org.testng.eclipse.shortcut' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.testng.eclipse.shortcut.testngSuite' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.jboss.tools.maven.actions.LifeCycleCleanVerify' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.jboss.tools.maven.ui.isCleanVerifyMenuEnabled to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.eclipse.ant.ui.antShortcutWithDialog' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} > {code} > Launch shortcut 'org.eclipse.ant.ui.antShortcut' enablement expression caused exception. Shortcut was removed. > org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17826) Unable to run Aerogear Cordova project with CordovaSim

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17826?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17826. --------------------------------- Closing really. > Unable to run Aerogear Cordova project with CordovaSim > ------------------------------------------------------ > > Key: JBIDE-17826 > URL: https://issues.jboss.org/browse/JBIDE-17826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Affects Versions: 4.2.0.Beta3 > Environment: Fedora 18 KDE 64bit > JBDS 8.0.0.Beta3-v20140706-0939-B172 (jboss-devstudio-8.0.0.Beta3-v20140706-0939-B172-installer-eap.jar) > Oracle JDK 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.2.0.Beta3 > > Attachments: central-respinB.png, central.png > > > 1. Import Hybrid Mobile Project from JBoss Central > 2. Run it with CordovaSim > ERROR: > {noformat} > no protocol: /home/vpakan/jbds800Beta3/studio/configuration > Stack trace: > java.net.MalformedURLException: no protocol: /home/vpakan/jbds800Beta3/studio/configuration > at java.net.URL.<init>(URL.java:586) > at java.net.URL.<init>(URL.java:483) > at java.net.URL.<init>(URL.java:432) > at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.getPortFromURL(CordovaSimArgs.java:100) > at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.parseArgs(CordovaSimArgs.java:51) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:88) > org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object; > Stack trace: > java.lang.NoSuchMethodError: org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object; > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.loadPreferences(CordovaSimRunner.java:165) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:179) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:110) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:89) > org.jboss.tools.vpe.cordavasim.command.stop.server: Server on port 0 was stopped > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-17960 at 7/24/14 5:53 AM: -------------------------------------------------------------- hi Karl: Can you verify for me that you do mean the affected version is 3.0.0.GA ? There are no further maintenance releases planned for that release train. We're currently working on 4.2.0, and I don't believe we even have any releases planned for 4.1.x anymore. If you mean 4.2.0 or 4.1.x, please let me know. Otherwise I might have to close this issue as wont-fix. Edited typos: 3.x -> 4.x. was (Author: rob.stryker): hi Karl: Can you verify for me that you do mean the affected version is 3.0.0.GA ? There are no further maintenance releases planned for that release train. We're currently working on 3.2.0, and I don't believe we even have any releases planned for 3.1.x anymore. If you mean 3.2.0 or 3.1.x, please let me know. Otherwise I might have to close this issue as wont-fix. > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.0.0.GA > Reporter: Karl Pietrzak > Priority: Minor > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17960: --------------------------------------- I am unable to replicate this in JBoss Tools 4.2.0.Beta3. [~the_alchemist] what version of JBoss Tools are you using? 3.0.0 is very very old so I don't think that's the one you're using. In the screencast I can see that once you changed the JRE in the runtime config to something reasonable, the server start worked. In Beta3, I am unable to get to the state that you had in the Launch config where the Classpath tab contained the strange/broken item. > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.0.0.GA > Reporter: Karl Pietrzak > Priority: Minor > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3107) Create domain dialog - edit domain members error

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3107?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-3107: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Create domain dialog - edit domain members error > ------------------------------------------------ > > Key: JBDS-3107 > URL: https://issues.jboss.org/browse/JBDS-3107 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: uxtest > Attachments: OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png > > > When creating a new OpenShift domain, if I click "Edit domain members" with the domain name left blank, I get the following error: > https://www.evernote.com/shard/s230/sh/ce9003cb-7988-4cdd-a4bc-52b04b9123... > This error is not helpful - and it appears the real problem is that to edit domain members I must create the domain first. > Suggest that we change the create domain dialog to do the following: > 1. Enter domain name (this is all that is shown on the dialog. (Mockup attached ) > 2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached) > Not sure if there was a reason we didn't add ability to edit the domain members directly here rather than kicking the user back into the openshift web console. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3103) Provide more info during OpenShift application creation

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3103?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-3103: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Provide more info during OpenShift application creation > ------------------------------------------------------- > > Key: JBDS-3103 > URL: https://issues.jboss.org/browse/JBDS-3103 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: uxtest > > During the project setup on OpenShift from the create new application wizard, the user is not provided much information about what is happening. This process does take a little while, and users would be more comfortable if they could see into what is happening for a better idea of if the process is failing or still working. A "more info" dropdown could be used on the modal to show log file information during this process. > https://www.evernote.com/shard/s230/sh/a750beed-4fc9-43d0-90a6-495573f09a... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3106) OpenShift create application wizard to take up less screen height

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3106?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-3106: -------------------------------- Issue Type: Enhancement (was: Feature Request) > OpenShift create application wizard to take up less screen height > ----------------------------------------------------------------- > > Key: JBDS-3106 > URL: https://issues.jboss.org/browse/JBDS-3106 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Environment: Fedora, 1440x900 resolution screen > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: uxtest > > For users with small screen sizes, the OpenShift create application wizard is very tall and might overflow their screen real-estate. Many of the dialogs in this wizard have lots of wasted space, so we should see if we can reduce the size of these dialogs as much as possible. > The height of the dialog is ~870px high. The most common resolution people run these days is 1366x768 - meaning we're already too high for people's viewable screen. > ---------------- > Screen by screen analysis > ---------------- > Sign in dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/baf765b4-cee1-470c-88a0-1afd237868... > Existing or new application dialog - ~145px wasted height: https://www.evernote.com/shard/s230/sh/d76f10b6-fb40-455d-bef6-d1b1ea44b0... > Name, domain, and embedded cartridges dialog - ~200px wasted height: https://www.evernote.com/shard/s230/sh/04381c6a-e9d7-4c6a-bd47-15b5b83a8e... > Configure project dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/4932fd92-12b3-456f-8f9c-a25548f4f6... > Clone settings, processing dialog - ~480px wasted height: https://www.evernote.com/shard/s230/sh/0d921581-6d12-4ba0-8c99-dc4c904e90... -- 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