[JBoss JIRA] (JBIDE-17492) Forge2: CLI appears to stall when project has errors
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17492?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-17492:
------------------------------------
Summary: Forge2: CLI appears to stall when project has errors (was: Forge2: CLI stalls when project has errors)
> 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
>
> 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.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17492) Forge2: CLI stalls when project has errors
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17492?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-17492:
------------------------------------
Description:
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?
was:
I have a project with errors.
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}
> Forge2: CLI stalls 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
>
> 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.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2734:
---------------------------------------
Thanks [~koen.aers].
I've documented some bugs in JBIDE-17488, JBIDE-17489, JBIDE-17490, JBIDE-17491, JBIDE-17492.
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: forge, requirements
> Reporter: Burr Sutter
> Assignee: Koen Aers
> Priority: Blocker
> Labels: QE_JBDS80_needinfo
> Fix For: 8.0.0.Beta2
>
>
> Is Forge 2 ready to be included in JBDS ?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17492) Forge2: CLI stalls when project has errors
by Michelle Murray (JIRA)
Michelle Murray created JBIDE-17492:
---------------------------------------
Summary: Forge2: CLI stalls 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
I have a project with errors.
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}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17491) Forge2: CLI won't autocomplete workspace project names unless list them first
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17491?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-17491:
------------------------------------
Description:
On forge2 start, on CLI type 'cd ' and beginning of workspace project name and press tab key for CLI to autocomplete project name.
But tab doesn't do anything.
To work around this, on CLI first enter 'ls' to list the projects in the workspace. Then type 'cd ' and beginning of workspace project name and press tab key and this time the autocomplete works.
This issues does not occur for forge1 CLI in same version of JBDS.
was:
On forge2 start, on CLI type 'cd ' and beginning of workspace project name and press tab key for CLI to autocomplete project name.
But tab doesn't do anything.
To work around this, on CLI first enter 'ls' to list the projects in the workspace. Then type 'cd ' and beginning of workspace project name and press tab key and this time the autocomplete works.
> Forge2: CLI won't autocomplete workspace project names unless list them first
> -----------------------------------------------------------------------------
>
> Key: JBIDE-17491
> URL: https://issues.jboss.org/browse/JBIDE-17491
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta2
> Environment: Fedora 19, OpenJDK 7
> Reporter: Michelle Murray
>
> On forge2 start, on CLI type 'cd ' and beginning of workspace project name and press tab key for CLI to autocomplete project name.
> But tab doesn't do anything.
> To work around this, on CLI first enter 'ls' to list the projects in the workspace. Then type 'cd ' and beginning of workspace project name and press tab key and this time the autocomplete works.
> This issues does not occur for forge1 CLI in same version of JBDS.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17489) Forge2: Character appears on CLI on tab and backspace
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17489?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-17489:
------------------------------------
Description:
With Forge2 started:
* tab to complete a dir adds a character to the end of the line
* backspace when there is nothing left to delete adds a character
Extra character doesn't seem to have an effect.
This issue does not appear for forge1 CLI in same version of JBDS.
!Forge_extrachar.png!
was:
With Forge2 started:
* tab to complete a dir adds a character to the end of the line
* backspace when there is nothing left to delete adds a character
Extra character doesn't seem to have an effect.
!Forge_extrachar.png!
> Forge2: Character appears on CLI on tab and backspace
> -----------------------------------------------------
>
> Key: JBIDE-17489
> URL: https://issues.jboss.org/browse/JBIDE-17489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta2
> Environment: Fedora 19, GTK 2 + GTK 3, OpenJDK 7
> Reporter: Michelle Murray
> Attachments: Forge_extrachar.png
>
>
> With Forge2 started:
> * tab to complete a dir adds a character to the end of the line
> * backspace when there is nothing left to delete adds a character
> Extra character doesn't seem to have an effect.
> This issue does not appear for forge1 CLI in same version of JBDS.
> !Forge_extrachar.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17491) Forge2: CLI won't autocomplete workspace project names unless list them first
by Michelle Murray (JIRA)
Michelle Murray created JBIDE-17491:
---------------------------------------
Summary: Forge2: CLI won't autocomplete workspace project names unless list them first
Key: JBIDE-17491
URL: https://issues.jboss.org/browse/JBIDE-17491
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.0.Beta2
Environment: Fedora 19, OpenJDK 7
Reporter: Michelle Murray
On forge2 start, on CLI type 'cd ' and beginning of workspace project name and press tab key for CLI to autocomplete project name.
But tab doesn't do anything.
To work around this, on CLI first enter 'ls' to list the projects in the workspace. Then type 'cd ' and beginning of workspace project name and press tab key and this time the autocomplete works.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17000) Show in -> Forge Console option disappeared
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17000?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-17000:
-----------------------------------------
Previously Show In > Forge Console executed the pick-up command on the Forge1 CLI.
In the Forge 2 Console view, the pick-up button is now gone and pick-up doesn't seem to be an available command.
How do users now efficiently navigate within their project source code?
> Show in -> Forge Console option disappeared
> -------------------------------------------
>
> Key: JBIDE-17000
> URL: https://issues.jboss.org/browse/JBIDE-17000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta1
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 4.2.0.Beta3
>
>
> Show in -> Forge Console option disappeared
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17488) Forge2: project-specific wizards are not visible on Ctrl+4
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17488?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-17488:
------------------------------------
Description:
JBDS-2734 states the following:
{quote}
* The availability of the wizards is depending on the initial selection when hitting the above key combo.
=> with nothing selected there are wizards for managing connection profiles and Forge addons and for creating new projects.
=> with e.g. a project selected there will be wizards for setting up support for JPA, JSF, and so on as well as for creating classes, generating entities, scaffolding a user interface, etc.
{quote}
After starting forge2, I navigate to my project
{noformat}
[workspace]$ cd my-mobile-app
[my-mobile-app]$
{noformat}
Tab (eventually) provides a list of forge2 possible commands, of which jpa-new-entity is one.
Ctrl+4 opens the forge2 wizards list window but only the wizards for connections, addons and new project are displayed.
Navigating down to scr/com/company/example/mymobileapp/model again only shows the wizards for connections, addons and new project.
was:
JBDS-2734 states the following:
{quote}
* The availability of the wizards is depending on the initial selection when hitting the above key combo.
=> with nothing selected there are wizards for managing connection profiles and Forge addons and for creating new projects.
=> with e.g. a project selected there will be wizards for setting up support for JPA, JSF, and so on as well as for creating classes, generating entities, scaffolding a user interface, etc.
{quote}
After starting forge2, I navigate to my project
{noformat}
[workspace]$ cd my-mobile-app
[my-mobile-app]$
{noformat}
Tab (eventually) provides a list of forge2 possible commands, of which jpa-new-entity is one.
Ctrl+4 opens the forge2 wizards list window but only the wizards for connections, addons and new project are displayed.
> Forge2: project-specific wizards are not visible on Ctrl+4
> ----------------------------------------------------------
>
> Key: JBIDE-17488
> URL: https://issues.jboss.org/browse/JBIDE-17488
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta2
> Environment: Fedora19, GTK2 + GTK3, OpenJDK7
> Reporter: Michelle Murray
> Priority: Blocker
>
> JBDS-2734 states the following:
> {quote}
> * The availability of the wizards is depending on the initial selection when hitting the above key combo.
> => with nothing selected there are wizards for managing connection profiles and Forge addons and for creating new projects.
> => with e.g. a project selected there will be wizards for setting up support for JPA, JSF, and so on as well as for creating classes, generating entities, scaffolding a user interface, etc.
> {quote}
> After starting forge2, I navigate to my project
> {noformat}
> [workspace]$ cd my-mobile-app
> [my-mobile-app]$
> {noformat}
> Tab (eventually) provides a list of forge2 possible commands, of which jpa-new-entity is one.
> Ctrl+4 opens the forge2 wizards list window but only the wizards for connections, addons and new project are displayed.
> Navigating down to scr/com/company/example/mymobileapp/model again only shows the wizards for connections, addons and new project.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17490) Forge2: CLI is slow to list forge commands on first use inside project
by Michelle Murray (JIRA)
Michelle Murray created JBIDE-17490:
---------------------------------------
Summary: Forge2: CLI is slow to list forge commands on first use inside project
Key: JBIDE-17490
URL: https://issues.jboss.org/browse/JBIDE-17490
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.0.Beta2
Environment: Fedora 19, OpenJDK 7, GTK2 and GTK3
Reporter: Michelle Murray
The forge2 cli is slow to list commands on first use inside a project.
So on starting forge2, move to project dir and press tab. It takes 5+ seconds to display the list of available forge commands.
This speed should be improved.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months