[JBoss JIRA] (JBIDE-18083) Issues in the new "Edit server runtime environment" window
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-18083:
----------------------------------
Attachment: InstalledJREs2.png
InstalledJREs.png
If you press button "Environments..." then you will see:
!InstalledJREs.png!
instead Installed JREs
> Issues in the new "Edit server runtime environment" window
> ----------------------------------------------------------
>
> Key: JBIDE-18083
> URL: https://issues.jboss.org/browse/JBIDE-18083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7x6, Eclipse 64 bit version, java 1.7, Ubuntu 14.04, Eclipse 64 bit, Java 1.7
> Reporter: Wolfgang Knauf
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.CR1
>
> Attachments: InstalledJREs.png, InstalledJREs2.png, server_runtime.png
>
>
> See attached screenshot: there are three problems in the "Edit Server runtime environment" window.
> a) clicking the button "Environments" opens the "Execution Environments" preference window behind the current window, it cannot be focused
> b) same for the button "Installed JREs"
> c) the "Configuration base directory" is defaulted to "C:standalone". This does probably not make sense ;-). For WildFly7 server types, it is "standalone".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18209) Autoapply new default JS/CSS library preferences
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18209?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18209:
-----------------------------------
Labels: respin-b (was: )
> Autoapply new default JS/CSS library preferences
> ------------------------------------------------
>
> Key: JBIDE-18209
> URL: https://issues.jboss.org/browse/JBIDE-18209
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: respin-b
> Fix For: 4.2.0.CR1
>
>
> Preferences JBossTools->Web->JS/CSS are initially set to default versions declared in extension point org.jboss.tools.jst.web.ui.jscssLibs. User can change some of them and leave some default libraries. New version of JBossTools may change some default libraries and add new.
> With current implementation, user would have to go to preferences and use 'Restore Defaults' to get new default libraries. That is not good, new default libraries should replace old default libraries automatically.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18209) Autoapply new default JS/CSS library preferences
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18209?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18209:
-----------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.3.0.Alpha1)
> Autoapply new default JS/CSS library preferences
> ------------------------------------------------
>
> Key: JBIDE-18209
> URL: https://issues.jboss.org/browse/JBIDE-18209
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.CR1
>
>
> Preferences JBossTools->Web->JS/CSS are initially set to default versions declared in extension point org.jboss.tools.jst.web.ui.jscssLibs. User can change some of them and leave some default libraries. New version of JBossTools may change some default libraries and add new.
> With current implementation, user would have to go to preferences and use 'Restore Defaults' to get new default libraries. That is not good, new default libraries should replace old default libraries automatically.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3115) Include Ionic Palette in Central
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBDS-3115?page=com.atlassian.jira.plugin.... ]
Gorkem Ercan commented on JBDS-3115:
------------------------------------
Also noticed that everything included on the AngularJS connector that appears under Mobile Development with a description that mentions ionic is also included on the Hybrid Mobile tools connector. I am not sure if we need another package other than Hybrid Mobile tools in this case.
> Include Ionic Palette in Central
> --------------------------------
>
> Key: JBDS-3115
> URL: https://issues.jboss.org/browse/JBDS-3115
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: p2-product
> Affects Versions: 8.0.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 8.0.0.CR1
>
> Attachments: 3115-jbds-vs-jbt-connector.differences.central.png, 3115-jbds-vs-jbt-connector.differences.png, central after early access.png, central before early access.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18148) problem with Hibernate package-info.java TypeDefs
by Jeffrey Simpson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18148?page=com.atlassian.jira.plugi... ]
Jeffrey Simpson commented on JBIDE-18148:
-----------------------------------------
I downloaded Luna and installed the JBoss Tools/ I did not get any errors related to the Types/ I only got one about a Console configuration not being there.
> problem with Hibernate package-info.java TypeDefs
> -------------------------------------------------
>
> Key: JBIDE-18148
> URL: https://issues.jboss.org/browse/JBIDE-18148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Environment: OSX 10.9.4
> Reporter: Jeffrey Simpson
> Assignee: Koen Aers
> Fix For: 4.2.0.CR1
>
> Attachments: eclipseErrors.log, TypeDefError.png, TypeDefError.zip
>
>
> I just tried out JBoss Developer Studio 8.0.0.Beta3 and it reports all of my Hibernate types that are defined in a package-info as not being found. I get "Type "common-big-decimal" could not be found" where I use it to define an attribute on an entity.
> Here is my Package-info.java
>
> @org.hibernate.annotations.TypeDefs (
>
> {
> @org.hibernate.annotations.TypeDef(name="yfu_boolean", typeClass=org.yfu.util.hibernate.TrueFalseBooleanUserType.class),
> @org.hibernate.annotations.TypeDef(name="integer_date", typeClass=org.yfu.util.hibernate.IntegerDateUserType.class),
> @org.hibernate.annotations.TypeDef(name="integer_local_date", typeClass=org.yfu.util.hibernate.IntegerLocalDateUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_big_decimal", typeClass=org.yfu.util.hibernate.NullableBigDecimalUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_long", typeClass=org.yfu.util.hibernate.NullableLongUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_integer", typeClass=org.yfu.util.hibernate.NullableIntegerUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_string", typeClass=org.yfu.util.hibernate.NullableStringUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_tf_boolean", typeClass=org.yfu.util.hibernate.NullableTFBooleanUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_yn_boolean", typeClass=org.yfu.util.hibernate.NullableYNBoolenaUserType.class),
> @org.hibernate.annotations.TypeDef(name="yfu_boolean_integer", typeClass=org.yfu.util.hibernate.YFUBooleanIntegerUserType.class),
>
> }
> )
> package org.yfu.util.hibernate;
--
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 commented on JBIDE-17492:
-----------------------------------------
The CLI no longer stalls, however the errors are not displayed in the output. Looking at it
> 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] (JBDS-3002) JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3002?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3002:
-------------------------------------
Why are you using 8.0.0.beta3 or 7.1.1.GA to verify this, if it is targeted 8.0.0.CR1 release?
{quote}I'm just pointing out that it's an easily reproducible issue requiring zero config.{quote}
How about testing it under Windows or Ubuntu?
This issues is about installing JBDS with content signed by untrusted certificate. If you are testing it under fedora 20, you have all ready for the test. But under Windows and Ubuntu you have to remove mentioned certificate for store before testing.
> JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3002
> URL: https://issues.jboss.org/browse/JBDS-3002
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, updatesite
> Affects Versions: 7.1.1.GA
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: respin-a
> Fix For: 8.0.0.CR1
>
>
> We have jars in JBDS 7.1.1.GA which were signed using GTECyberTrust. Some linux installs do not include this root cert, so when installing, p2 rejects the cert:
> {code}One or more certificates rejected. Cannot proceed with installation.{code}
> Full details: https://community.jboss.org/message/866868
> *Platform details:*
> {code}
> Debian Jessie 64 bit
> $ uname -a:
> Linux Name 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux
> $ java -version
> java version "1.7.0_51"
> OpenJDK Runtime Environment (IcedTea 2.4.5) (7u51-2.4.5-2)
> OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
> {code}
> Note that Debian 8.0 "Jessie" is not yet released nor has a date for release been announced [0]. The latest stable Debian [1] is 7.4 "Wheezy", released on Feb 8, 2014. [2] The description for "testing" releases like Jessie is "Security updates are irregular and unreliable." [3] So... I don't think we support this OS yet. :)
> [0] http://www.debian.org/releases/jessie/
> [1] http://www.debian.org/releases/
> [2] http://www.debian.org/releases/wheezy/
> [3] https://release.debian.org/
> *Steps to repro on the above platform:*
> 1. Downloaded jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar
> 2. Ran java -jar jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar stuck to the defaults and clicked thru
> 3. Install failed with an error re certificates not being trusted
> 4. Log message in ~/jbdevstudio/studio/p2/director/configuration/1396752621141.log as follows:
> !ENTRY org.eclipse.equinox.p2.engine 8 0 2014-04-06 08:21:42.061
> !MESSAGE One or more certificates rejected. Cannot proceed with installation.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months