[JBoss JIRA] (JBIDE-18294) In runtime detection of EAP 5, when you uncheck the EAP server in the results, the seam runtime is still added
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18294?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-18294:
----------------------------------
Comment: was deleted
(was: I think this feature works as expected.
If a runtime contains EAP and Seam, they can be disabled separately.
You have to expand the EAP entry to see that EAP includes Seam.
You have only disabled EAP. If you disable Seam, it won't be added.
If you disable EAP and Seam, the OK button will be disabled so you won't be able to add any runtimes.
)
> In runtime detection of EAP 5, when you uncheck the EAP server in the results, the seam runtime is still added
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18294
> URL: https://issues.jboss.org/browse/JBIDE-18294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection, seam2
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.2.1.Final
>
>
> This is a followup of JBIDE-17630 which contained two issues and one is still outstanding:
> When you search for runtimes and EAP 5.x (including seam) is found, by default the entry is collapsed and you can expand it to see the seam runtime included with the eap server.
> If you uncheck the eap server, the seam runtime beneath will still be checked. This can be confusing. I believe checking/unchecking the eap server should affect the seam runtime as well.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18301) configuring openshift application from Aerogear quickstart fails.
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBIDE-18301:
------------------------------------
Summary: configuring openshift application from Aerogear quickstart fails.
Key: JBIDE-18301
URL: https://issues.jboss.org/browse/JBIDE-18301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.CR1
Reporter: Gorkem Ercan
1. clone git@github.com:gorkem/aerogear-push-quickstarts.git
2. add aerogear-push-quickstarts/server/contacts-mobile-picketlink-secured from the repo as a maven project
3. Right click to select Configure> New Import Openshift application
Follow the steps. The wizard fails to complete because it complains about uncommitted changes.
I think this is probably happening because JGit sees symlinks as uncommitted changes.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18294) In runtime detection of EAP 5, when you uncheck the EAP server in the results, the seam runtime is still added
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18294?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-18294:
---------------------------------------
I think this feature works as expected.
If a runtime contains EAP and Seam, they can be disabled separately.
You have to expand the EAP entry to see that EAP includes Seam.
You have only disabled EAP. If you disable Seam, it won't be added.
If you disable EAP and Seam, the OK button will be disabled so you won't be able to add any runtimes.
> In runtime detection of EAP 5, when you uncheck the EAP server in the results, the seam runtime is still added
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18294
> URL: https://issues.jboss.org/browse/JBIDE-18294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection, seam2
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.2.1.Final
>
>
> This is a followup of JBIDE-17630 which contained two issues and one is still outstanding:
> When you search for runtimes and EAP 5.x (including seam) is found, by default the entry is collapsed and you can expand it to see the seam runtime included with the eap server.
> If you uncheck the eap server, the seam runtime beneath will still be checked. This can be confusing. I believe checking/unchecking the eap server should affect the seam runtime as well.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18294) In runtime detection of EAP 5, when you uncheck the EAP server in the results, the seam runtime is still added
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18294?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-18294:
---------------------------------------
I think this feature works as expected.
If a runtime contains EAP and Seam, they can be disabled separately.
You have to expand the EAP entry to see that EAP includes Seam.
You have only disabled EAP. If you disable Seam, it won't be added.
If you disable EAP and Seam, the OK button will be disabled so you won't be able to add any runtimes.
> In runtime detection of EAP 5, when you uncheck the EAP server in the results, the seam runtime is still added
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18294
> URL: https://issues.jboss.org/browse/JBIDE-18294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection, seam2
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.2.1.Final
>
>
> This is a followup of JBIDE-17630 which contained two issues and one is still outstanding:
> When you search for runtimes and EAP 5.x (including seam) is found, by default the entry is collapsed and you can expand it to see the seam runtime included with the eap server.
> If you uncheck the eap server, the seam runtime beneath will still be checked. This can be confusing. I believe checking/unchecking the eap server should affect the seam runtime as well.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18298) Text in OpenShift dialogs cannot be read
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18298?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18298:
------------------------------------------
[~dgolovin] Color Scheme? We dont use any special color scheme, what do I miss? The composites which are black on black in the screenshots are transparent. I achieved this by setting a transparent png to is background (it's a StyledText so that scrolling and wrapping works right. StyledText dont support transparency unless you use some background picture). I very astonished that there is any background color here.
> Text in OpenShift dialogs cannot be read
> ----------------------------------------
>
> Key: JBIDE-18298
> URL: https://issues.jboss.org/browse/JBIDE-18298
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Environment: RHEL 6
> Java 1.7
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.CR1
>
> Attachments: application-configuration-wizard-page.png, application-template-wizard-page.png, Screenshot-1.png, Screenshot.png
>
>
> See the attached screenshots - some text boxes cannot be read as the background and text are both dark.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17492) Forge2: CLI appears to stall when project has errors
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17492?page=com.atlassian.jira.plugi... ]
George Gastaldi updated JBIDE-17492:
------------------------------------
Labels: respin-b (was: )
> 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
> Labels: respin-b
> 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.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17492) Forge2: CLI appears to stall when project has errors
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17492?page=com.atlassian.jira.plugi... ]
George Gastaldi resolved JBIDE-17492.
-------------------------------------
Resolution: Done
Fixed in Forge
> 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.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18298) Text in OpenShift dialogs cannot be read
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18298?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18298:
---------------------------------------
Cannot replicate it on Ubuntu 14.04.1 LTS.
> Text in OpenShift dialogs cannot be read
> ----------------------------------------
>
> Key: JBIDE-18298
> URL: https://issues.jboss.org/browse/JBIDE-18298
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Environment: RHEL 6
> Java 1.7
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.CR1
>
> Attachments: application-configuration-wizard-page.png, application-template-wizard-page.png, Screenshot-1.png, Screenshot.png
>
>
> See the attached screenshots - some text boxes cannot be read as the background and text are both dark.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18298) Text in OpenShift dialogs cannot be read
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18298?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18298:
---------------------------------------
This could be related to color scheme used in OS.
> Text in OpenShift dialogs cannot be read
> ----------------------------------------
>
> Key: JBIDE-18298
> URL: https://issues.jboss.org/browse/JBIDE-18298
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Environment: RHEL 6
> Java 1.7
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.CR1
>
> Attachments: application-configuration-wizard-page.png, application-template-wizard-page.png, Screenshot-1.png, Screenshot.png
>
>
> See the attached screenshots - some text boxes cannot be read as the background and text are both dark.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months