July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17492) Forge2: CLI appears to stall when project has errors

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17492?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17492: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Forge2: CLI appears to stall when project has errors > ---------------------------------------------------- > > Key: JBIDE-17492 > URL: https://issues.jboss.org/browse/JBIDE-17492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta2 > Environment: Fedora 19, OpenJDK 7 > Reporter: Michelle Murray > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.2.0.CR1 > > > I have a project with errors. When in that project on the CLI and press tab for list of available commands, the CLI of forge1 and 2 act differently. > On forge1 CLI, CLI pauses momentarily and then sticks out a list of issues with the project: > {noformat} > [no project] workspace $ cd jboss-javaee6-webapp/ > ***ERROR*** Exception encountered: 14 problems were encountered while building the effective model for org.jboss.tools.examples:jboss-javaee6-webapp:0.0.1-SNAPSHOT > [FATAL] Non-resolvable parent POM: Could not find artifact org.jboss.bom:jboss-bom-parent:pom:1.0.4.Final-redhat-4 in jboss-wfk-2-5-0-maven-repository (file:/home/applications/jboss-wfk/jboss-wfk-2.5.0-maven-repository/) @ org.jboss.bom:jboss-javaee-6.0-with-tools:1.0.4.Final-redhat-4 > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.bom:jboss-javaee-6.0-with-hibernate:pom:1.0.4.Final-redhat-4 in jboss-wfk-2-5-0-maven-repository (file:/home/applications/jboss-wfk/jboss-wfk-2.5.0-maven-repository/) @ line 83, column 25 > [ERROR] 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. @ line 100, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing. @ line 108, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing. @ line 116, column 21 > [ERROR] 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar is missing. @ line 124, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:jar is missing. @ line 132, column 21 > [ERROR] 'dependencies.dependency.version' for org.hibernate:hibernate-validator:jar is missing. @ line 141, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec:jar is missing. @ line 155, column 21 > [ERROR] 'dependencies.dependency.version' for org.hibernate:hibernate-jpamodelgen:jar is missing. @ line 165, column 21 > [ERROR] 'dependencies.dependency.version' for org.hibernate:hibernate-validator-annotation-processor:jar is missing. @ line 173, column 21 > [ERROR] 'dependencies.dependency.version' for junit:junit:jar is missing. @ line 180, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 189, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.protocol:arquillian-protocol-servlet:jar is missing. @ line 195, column 21 > (type "set VERBOSE true" to enable stack traces) > [no project] workspace $ > {noformat} > But on forge2 CLI, the same project causes the CLI to appear to freeze. On the CLI where I started JBDS, output is streaming: > {noformat} > Jun 01, 2014 6:26:49 PM org.jboss.forge.addon.maven.projects.MavenFacetImpl getProperties > WARNING: Failed to resolve properties in [/home/applications/workspace/jboss-javaee6-webapp/pom.xml]. > Jun 01, 2014 6:26:50 PM org.jboss.forge.addon.maven.projects.MavenFacetImpl getProperties > WARNING: Failed to resolve properties in [/home/applications/workspace/jboss-javaee6-webapp/pom.xml]. > Jun 01, 2014 6:26:51 PM org.jboss.forge.addon.maven.projects.MavenFacetImpl resolveProperties > WARNING: Failed to resolve properties in [/home/applications/workspace/jboss-javaee6-webapp/pom.xml] for input value [org.jboss.spec.javax.servlet]. > Jun 01, 2014 6:26:52 PM org.jboss.forge.addon.maven.projects.MavenFacetImpl resolveProperties > WARNING: Failed to resolve properties in [/home/applications/workspace/jboss-javaee6-webapp/pom.xml] for input value [jboss-servlet-api_3.0_spec]. > Jun 01, 2014 6:26:54 PM org.jboss.forge.addon.maven.projects.MavenFacetImpl resolveProperties > WARNING: Failed to resolve properties in [/home/applications/workspace/jboss-javaee6-webapp/pom.xml] for input value [provided]. > Jun 01, 2014 6:26:55 PM org.jboss.forge.addon.maven.projects.facets.MavenDependencyFacet getEffectiveDependencies > SEVERE: Could not resolve managed dependencies in project [/home/applications/workspace/jboss-javaee6-webapp/pom.xml]. > java.lang.RuntimeException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: > [FATAL] Non-resolvable parent POM: Could not find artifact org.jboss.bom:jboss-bom-parent:pom:1.0.4.Final-redhat-4 in jboss-wfk-2-5-0-maven-repository (file:/home/applications/jboss-wfk/jboss-wfk-2.5.0-maven-repository/) @ org.jboss.bom:jboss-javaee-6.0-with-tools:1.0.4.Final-redhat-4, /home/mmurray/.m2/repository/org/jboss/bom/jboss-javaee-6.0-with-tools/1.0.4.Final-redhat-4/jboss-javaee-6.0-with-tools-1.0.4.Final-redhat-4.pom, line 7, column 13 > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.bom:jboss-javaee-6.0-with-hibernate:pom:1.0.4.Final-redhat-4 in jboss-wfk-2-5-0-maven-repository (file:/home/applications/jboss-wfk/jboss-wfk-2.5.0-maven-repository/) @ line 83, column 25 > [ERROR] 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. @ line 100, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing. @ line 108, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing. @ line 116, column 21 > [ERROR] 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar is missing. @ line 124, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:jar is missing. @ line 132, column 21 > [ERROR] 'dependencies.dependency.version' for org.hibernate:hibernate-validator:jar is missing. @ line 141, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec:jar is missing. @ line 155, column 21 > [ERROR] 'dependencies.dependency.version' for org.hibernate:hibernate-jpamodelgen:jar is missing. @ line 165, column 21 > [ERROR] 'dependencies.dependency.version' for org.hibernate:hibernate-validator-annotation-processor:jar is missing. @ line 173, column 21 > [ERROR] 'dependencies.dependency.version' for junit:junit:jar is missing. @ line 180, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 189, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.protocol:arquillian-protocol-servlet:jar is missing. @ line 195, column 21 > at org.jboss.forge.addon.maven.projects.MavenBuildManager.getProjectBuildingResult(MavenBuildManager.java:99) > at org.jboss.forge.addon.maven.projects.MavenFacetImpl.getProjectBuildingResult(MavenFacetImpl.java:143) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81) > at org.jboss.forge.addon.maven.projects.MavenFacetImpl_$$_javassist_ffe99930-1b28-45db-85dc-fc7e03d14343.getProjectBuildingResult(MavenFacetImpl_$$_javassist_ffe99930-1b28-45db-85dc-fc7e03d14343.java) > at org.jboss.forge.addon.maven.projects.facets.MavenDependencyFacet.getEffectiveDependencies(MavenDependencyFacet.java:174) > at org.jboss.forge.addon.maven.projects.facets.MavenDependencyFacet.getEffectiveDependency(MavenDependencyFacet.java:156) > at org.jboss.forge.addon.maven.projects.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:150) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81) > at org.jboss.forge.addon.maven.projects.facets.MavenDependencyFacet_$$_javassist_a3cab0e2-fcad-460c-9669-88a997fb437b.hasEffectiveDependency(MavenDependencyFacet_$$_javassist_a3cab0e2-fcad-460c-9669-88a997fb437b.java) > ... > ... > ... > {noformat} > Eventually, forge2 CLI outputs list of commands but with no error messages. > The long (minutes) pause isn't helpful to users. How can this be improved? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17628) Ctrl+4 does not open the default Forge runtime, but always 2.6.0

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17628?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17628: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Ctrl+4 does not open the default Forge runtime, but always 2.6.0 > ---------------------------------------------------------------- > > Key: JBIDE-17628 > URL: https://issues.jboss.org/browse/JBIDE-17628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > According to JBDS 8.0.0 Beta2 release notes: > {quote} > The default Forge runtime starts on pressing Ctrl+4. To change the default runtime, click Window→Preferences, expand Forge→Installed Forge Runtimes and select the check box of the runtime that you want to be default. > {quote} > This is not true. I changed the default to 1.x, started Forge using Ctrl+4, and it still starts 2.6.0. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17650) Find better way to enable Tern cordova module for cordova projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17650?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17650: ------------------------------------ New mirror pulled: http://download.jboss.org/jbosstools/updates/requirements/tern/0.4.0.2014... (Note that it's a NEWER build than the one you requested. Hope that's OK.) > Find better way to enable Tern cordova module for cordova projects > ------------------------------------------------------------------ > > Key: JBIDE-17650 > URL: https://issues.jboss.org/browse/JBIDE-17650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Victor Rubezhny > Fix For: 4.2.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17674) Remove 'wrong Node.js install' workaround

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17674?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-17674: ----------------------------------------- Fix is stored in the branch https://github.com/vrubezhny/jbosstools-jst/tree/jbide17674 The issue requires to have Tern.java v.0.4.0.201407021311 in TP > Remove 'wrong Node.js install' workaround > ------------------------------------------ > > Key: JBIDE-17674 > URL: https://issues.jboss.org/browse/JBIDE-17674 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta3 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.2.0.Beta3 > > > Since the 'Node.js install' is fixed in Tern.java we need to remove the workaround regarding the Node.js embedded install set up > - https://github.com/angelozerr/tern.java/pull/80 - An embedded install of Node.js should be used by default -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17697) Implement Browse button for 'JDBC Driver' in JPA: Setup wizard

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17697?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17697: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Implement Browse button for 'JDBC Driver' in JPA: Setup wizard > -------------------------------------------------------------- > > Key: JBIDE-17697 > URL: https://issues.jboss.org/browse/JBIDE-17697 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta2 > Reporter: Pavol Srna > Fix For: 4.2.0.CR1 > > Attachments: jpa-setup-FR.png > > > From usability point of view it would be more convenient for the user to enter the JDBC Driver with browse button. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17749) Update AngularJS-eclipse in Central Early Access to version 0.4.0.201407021517

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17749?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17749: ------------------------------------ Mirror pulled: http://download.jboss.org/jbosstools/updates/requirements/angularjs/0.4.0... This will be added to the appropriate target platforms shortly. > Update AngularJS-eclipse in Central Early Access to version 0.4.0.201407021517 > ------------------------------------------------------------------------------ > > Key: JBIDE-17749 > URL: https://issues.jboss.org/browse/JBIDE-17749 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Victor Rubezhny > Assignee: Nick Boldt > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta3 > > Attachments: AngularJS16x16.png, AngularJS32x32.png > > > We should provide an ability to install latest AngularJS-eclipse v.0.4.0.201407021517 through Central > There is no released or latest stable version, so we should take a copy from http://oss.opensagres.fr/angularjs-eclipse/0.4.0-SNAPSHOT/ Update Site. > [~nickboldt], please let me know if you need something more that just a link to Update Site. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17699) Browse for Driver in 'JPA: Generate Entities from Tables' is way too slow (~40s)

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17699?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17699: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Browse for Driver in 'JPA: Generate Entities from Tables' is way too slow (~40s) > -------------------------------------------------------------------------------- > > Key: JBIDE-17699 > URL: https://issues.jboss.org/browse/JBIDE-17699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta2 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > > screencast here: http://youtu.be/f3kSPjWxIGA -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17008) Changing Forge runtimes is broken

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17008?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17008: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Changing Forge runtimes is broken > --------------------------------- > > Key: JBIDE-17008 > URL: https://issues.jboss.org/browse/JBIDE-17008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Critical > Labels: regression > Fix For: 4.2.0.CR1 > > > If there is currently running the embedded instance of forge runtime and an user attempts to add a new runtime and attempts to use it right away -- then he is blocked and cannot run any commands in the console. > He would need to change the runtime back to the embedded one (in preferences) - stop it (in console view) and select the new one (in preferences) -- But even by doing that - the start/stop buttons are not working properly. > Expected is that after changing the runtime it automatically restarts forge and uses the new one. This is how it worked until Beta. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17704) JPA: Generate Entities From Tables wizard should tell people when something has gone wrong

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17704?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17704: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > JPA: Generate Entities From Tables wizard should tell people when something has gone wrong > ------------------------------------------------------------------------------------------- > > Key: JBIDE-17704 > URL: https://issues.jboss.org/browse/JBIDE-17704 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Pavol Srna > Priority: Critical > Fix For: 4.2.0.CR1 > > > I'm opening this jira based on experience from https://issues.jboss.org/browse/JBIDE-17702 > As you can see in the screencast here: http://youtu.be/BPagtMpfZM0, the user has no idea why the operation has failed. The error log is empty. The UI was frozen for several seconds. > UI wizard should be enhanced to tell the error on wizard page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16653) Forge integration should be able to take proxy info from eclipse

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16653?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-16653: ------------------------------ Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Forge integration should be able to take proxy info from eclipse > ---------------------------------------------------------------- > > Key: JBIDE-16653 > URL: https://issues.jboss.org/browse/JBIDE-16653 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014