October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18312) CordovaSim struggles with POST

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18312?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-18312: ------------------------------------- I reimported project and now POST works no error in debugger console. Only issue left is that new contact is ot displayed within Enterprise Contact list I have to refresh manually index.html page and then new added contact is displayed. Is this new issue or is it part of this one? > CordovaSim struggles with POST > ------------------------------ > > Key: JBIDE-18312 > URL: https://issues.jboss.org/browse/JBIDE-18312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.2.0.CR2 > > Attachments: hybrid1001.zip, post_error.png > > > I will attach the project. > The $.ajax post does not fire correctly from inside of CordovaSim - but it does via the iOS Simulator and from a real Android Device. Nothing in the error message on the client-side. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18506) Usage plugin sometimes locks JBT/JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18506?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18506: --------------------------------------------- should we not be waiting until eclipse is fully started to send the events that would gather these ui sizes ? > Usage plugin sometimes locks JBT/JBDS > ------------------------------------- > > Key: JBIDE-18506 > URL: https://issues.jboss.org/browse/JBIDE-18506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.2.0.CR1 > Reporter: Snjezana Peco > Assignee: Alexey Kazakov > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.CR2 > > Attachments: usagestacktrace.out > > > JBossToolsUsageActivator initializes settings when starting and calls > AbstractEclipseEnvironment.initScreenSettings() > that uses the Display.syncExec method > which causes JBT/JBDS to freeze. The issue isn't always reproducible, but it often happens when starting JBDS/JBT in a new workspace. > While I was testing JBIDE-16379, I reproduced it each time when I started Eclipse 4.4.1/JBT 4.2.0.CR1 in a new workspace. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18416) Forge New Project wizard - field names should have the same case

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18416?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-18416. ------------------------------ Verified in JBT 4.2.0.CR2 build. > Forge New Project wizard - field names should have the same case > ---------------------------------------------------------------- > > Key: JBIDE-18416 > URL: https://issues.jboss.org/browse/JBIDE-18416 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Michelle Murray > Assignee: George Gastaldi > Fix For: 4.2.0.CR2 > > > Forge 2 New Project wizard field names should have consistent sentence case - see Guideline 1.6 http://wiki.eclipse.org/User_Interface_Guidelines#Capitalization. > * Ctrl+4 + New Project > * Final Name > Final name > * Project Type > Project type > * Build System > Build system > For 'From Archetype' window: > * Archetype Repository > Archetype repository << would it be clearer if were 'Archetype repository URL'? > * Enter a maven archetype coordinate > Enter a Maven archetype coordinate > For 'From Archetype Catalog' window: > * Choose a maven archetype for your project > Choose a Maven archetype for your project -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-534) Forge How To: Generate a Basic UI for Your Application Data

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-534?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-534: -------------------------------------------- Hi [~sdorfiel], I have completed the peer review for this article. Please let me know in case you want to discuss any of the comments. As always, these are suggestions only :) Thanks, Supriya > Forge How To: Generate a Basic UI for Your Application Data > ----------------------------------------------------------- > > Key: TOOLSDOC-534 > URL: https://issues.jboss.org/browse/TOOLSDOC-534 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - Forge Tools > Reporter: Michelle Murray > Assignee: Suz Dorfield > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18413) CheckboxTableControlBuilder is never refreshed when value choices change

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18413?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-18413. ------------------------------ Verified in JBT 4.2.0.CR2 build. > CheckboxTableControlBuilder is never refreshed when value choices change > ------------------------------------------------------------------------ > > Key: JBIDE-18413 > URL: https://issues.jboss.org/browse/JBIDE-18413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.2.0.CR2 > > > When I change the combo in {{Java: Generate Equals and Hashcode}}, checkbox table below does not refresh the items -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18359) REGRESSION: Changed files are not being opened in Eclipse

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18359?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-18359. ------------------------------ Verified in JBT 4.2.0.CR2 build. > REGRESSION: Changed files are not being opened in Eclipse > --------------------------------------------------------- > > Key: JBIDE-18359 > URL: https://issues.jboss.org/browse/JBIDE-18359 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.2.0.CR2 > > > When a command changes the selected resource, it is no longer opened in Eclipse after execution (Eg: JPA: New Entity) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18353) Selecting (DTP Connection Profile) in Generate Entities wizard takes ages

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18353?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-18353. ------------------------------ Verified in JBT 4.2.0.CR2 build. > Selecting (DTP Connection Profile) in Generate Entities wizard takes ages > ------------------------------------------------------------------------- > > Key: JBIDE-18353 > URL: https://issues.jboss.org/browse/JBIDE-18353 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Critical > Labels: regression > Fix For: 4.2.0.CR2 > > Attachments: forge-db.png, forge-stack.txt > > > I believe this is a regression. It used to work as far as I remember. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18386) Stale table data shown when switching form working to invalid connection profiles in jpa-generate-entities-from-tables

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18386?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-18386. ------------------------------ Verified in JBT 4.2.0.CR2 build. > Stale table data shown when switching form working to invalid connection profiles in jpa-generate-entities-from-tables > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18386 > URL: https://issues.jboss.org/browse/JBIDE-18386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 4.2.0.CR2 > > > 1. Run JPA: Generate Entities From Tables > 2. Select a valid connection profile > 3. Click Next > 4. Click back > 5. Select a connection profile that fails to connect > 6. Click next > 7. Tables from first connection profile are still displayed -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17492?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-17492. ------------------------------ The project doesn't stall and the error is correctly shown in the tooling. Verified in JBT 4.2.0.CR2 build. > 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.CR2 > > > 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.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16379) Using symbolic links in the workspace path causes an infinite loop for m2e builder

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16379?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16379: --------------------------------------------- auto share egit is really a big usability improvement so I would really not like having to recommend disabling it. What goes on in that which causes slowness? if it is just about detecting cycles in the traverse we should be able to fix that I Reckon? > Using symbolic links in the workspace path causes an infinite loop for m2e builder > ---------------------------------------------------------------------------------- > > Key: JBIDE-16379 > URL: https://issues.jboss.org/browse/JBIDE-16379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.3.x > > > See JBIDE-16286 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014