[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ]
Jiri Peterka commented on JBDS-2847:
------------------------------------
[~maxandersen] there are some Java Problems, Maven Problems and XML Problems after import, most projects are without errors
Java Problems
{code}
Description Resource Path Location Type
EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem
EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem
EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 76 Java Problem
EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 85 Java Problem
EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem
EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 35 Java Problem
EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem
EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem
EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem
EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem
Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 32 Java Problem
Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 36 Java Problem
Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem
SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem
SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem
The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" Greeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem
The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" SimpleGreeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem
The declared package "org.javaee7.cdi.nobeans.xml" does not match the expected package "test.java.org.javaee7.cdi.nobeans.xml" GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 1 Java Problem
The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 3 Java Problem
The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 4 Java Problem
The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 12 Java Problem
The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 13 Java Problem
The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 14 Java Problem
{/code}
Maven Problems:
{code}
Description Resource Path Location Type
Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen (execution: default, phase: process-classes) pom.xml /jaxws-endpoint line 21 Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsimport (execution: default, phase: generate-sources) pom.xml /jaxws-client line 21 Maven Project Build Lifecycle Mapping Problem
{/code}
and xml problems
{code}
Description Resource Path Location Type
cvc-complex-type.2.1: Element 'jboss' must have no character or element information item [children], because the type's content type is empty. enforce-beans.xml /jax-rs-angularjs/src/test/resources line 4 XML Problem
cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem
cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem
cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem
cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem
cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem
cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 25 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 25 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 28 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jaxrs-endpoint/src/test/resources line 3 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-embedded line 5 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-remote line 5 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-jbosseap-remote line 5 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /send-receive/src/test/resources line 3 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /standalone/src/test/resources line 3 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /transactional/src/test/resources line 3 XML Problem
cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /user-transaction/src/test/resources line 3 XML Problem
cvc-pattern-valid: Value 'param1 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem
cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem
cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem
cvc-pattern-valid: Value 'param2 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem
cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem
cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem
{/code}
> Java EE 7 Tech Preview
> ----------------------
>
> Key: JBDS-2847
> URL: https://issues.jboss.org/browse/JBDS-2847
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly
> https://github.com/javaee-samples/javaee7-samples
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2847:
-------------------------------------------
[~jpeterka] okey - so you are seeing what I expect. Can you just to be 100% sure list the paths to the projects that *does* have problems for you ?
> Java EE 7 Tech Preview
> ----------------------
>
> Key: JBDS-2847
> URL: https://issues.jboss.org/browse/JBDS-2847
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly
> https://github.com/javaee-samples/javaee7-samples
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18095:
---------------------------------------------
marking as critical regression and for now targeted at CR1 but we'll need to investigate what options we got to know if doable.
> Server adapter fails to publish modules with non-ASCII class names
> ------------------------------------------------------------------
>
> Key: JBIDE-18095
> URL: https://issues.jboss.org/browse/JBIDE-18095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3, 4.2.0.CR1
> Environment: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140822-0028-B573 (nightly/luna repo), JBoss EAP 5.2.0 on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
> Priority: Critical
> Labels: regression
> Fix For: 4.2.0.CR1
>
>
> I have a 35 module war/ear project, where multiple plain jar modules are deployed as bundled libraries in the ear module. The problem is, two of these modules fail to deploy to the server deploy folder, and as a result, ClassNotFoundExceptions are thrown from the JBoss class loader. If I close the projects containing the two troublesome modules, they are deployed correctly and everything is fine (as with the Kepler version). The two modules show up in the "Bundled libraries" view in the ear project, and they show under the ear deployment in the server view. But, in the server view, the decoration on the server is always "Republish" after startup, even though the ear module is "Synchronized". The non-deployed modules have no decoration at all, while the other modules all show "Synchronized".
> The problem seems to be classes with non-ASCII class names. If I rename the classes, the modules are deployed correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18095:
----------------------------------------
Labels: regression (was: )
> Server adapter fails to publish modules with non-ASCII class names
> ------------------------------------------------------------------
>
> Key: JBIDE-18095
> URL: https://issues.jboss.org/browse/JBIDE-18095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3, 4.2.0.CR1
> Environment: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140822-0028-B573 (nightly/luna repo), JBoss EAP 5.2.0 on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
> Priority: Critical
> Labels: regression
>
> I have a 35 module war/ear project, where multiple plain jar modules are deployed as bundled libraries in the ear module. The problem is, two of these modules fail to deploy to the server deploy folder, and as a result, ClassNotFoundExceptions are thrown from the JBoss class loader. If I close the projects containing the two troublesome modules, they are deployed correctly and everything is fine (as with the Kepler version). The two modules show up in the "Bundled libraries" view in the ear project, and they show under the ear deployment in the server view. But, in the server view, the decoration on the server is always "Republish" after startup, even though the ear module is "Synchronized". The non-deployed modules have no decoration at all, while the other modules all show "Synchronized".
> The problem seems to be classes with non-ASCII class names. If I rename the classes, the modules are deployed correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18095:
----------------------------------------
Fix Version/s: 4.2.0.CR1
> Server adapter fails to publish modules with non-ASCII class names
> ------------------------------------------------------------------
>
> Key: JBIDE-18095
> URL: https://issues.jboss.org/browse/JBIDE-18095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3, 4.2.0.CR1
> Environment: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140822-0028-B573 (nightly/luna repo), JBoss EAP 5.2.0 on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
> Priority: Critical
> Labels: regression
> Fix For: 4.2.0.CR1
>
>
> I have a 35 module war/ear project, where multiple plain jar modules are deployed as bundled libraries in the ear module. The problem is, two of these modules fail to deploy to the server deploy folder, and as a result, ClassNotFoundExceptions are thrown from the JBoss class loader. If I close the projects containing the two troublesome modules, they are deployed correctly and everything is fine (as with the Kepler version). The two modules show up in the "Bundled libraries" view in the ear project, and they show under the ear deployment in the server view. But, in the server view, the decoration on the server is always "Republish" after startup, even though the ear module is "Synchronized". The non-deployed modules have no decoration at all, while the other modules all show "Synchronized".
> The problem seems to be classes with non-ASCII class names. If I rename the classes, the modules are deployed correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18095:
---------------------------------------------
thanks for the follow up [~AxelW]
I think [~rob.stryker] in the meantime managed to reproduce it and isolate it as an issue in TrueZip:
de.schlichtherle.io.ArchiveFileSystem$ArchiveFileSystemException: java.io.CharConversionException: pak/my/絁Claz.class
And yes, in past we did not use truezip for doing exploded deployments, but in luna we aligned and avoided having double the code to maintain but apparently we missed that truezip fails on non-US characters ;/
We'll investigate to see what can be done.
> Server adapter fails to publish modules with non-ASCII class names
> ------------------------------------------------------------------
>
> Key: JBIDE-18095
> URL: https://issues.jboss.org/browse/JBIDE-18095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3, 4.2.0.CR1
> Environment: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140822-0028-B573 (nightly/luna repo), JBoss EAP 5.2.0 on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
> Labels: regression
> Fix For: 4.2.0.CR1
>
>
> I have a 35 module war/ear project, where multiple plain jar modules are deployed as bundled libraries in the ear module. The problem is, two of these modules fail to deploy to the server deploy folder, and as a result, ClassNotFoundExceptions are thrown from the JBoss class loader. If I close the projects containing the two troublesome modules, they are deployed correctly and everything is fine (as with the Kepler version). The two modules show up in the "Bundled libraries" view in the ear project, and they show under the ear deployment in the server view. But, in the server view, the decoration on the server is always "Republish" after startup, even though the ear module is "Synchronized". The non-deployed modules have no decoration at all, while the other modules all show "Synchronized".
> The problem seems to be classes with non-ASCII class names. If I rename the classes, the modules are deployed correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18095:
----------------------------------------
Priority: Critical (was: Major)
> Server adapter fails to publish modules with non-ASCII class names
> ------------------------------------------------------------------
>
> Key: JBIDE-18095
> URL: https://issues.jboss.org/browse/JBIDE-18095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3, 4.2.0.CR1
> Environment: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140822-0028-B573 (nightly/luna repo), JBoss EAP 5.2.0 on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
> Priority: Critical
> Labels: regression
>
> I have a 35 module war/ear project, where multiple plain jar modules are deployed as bundled libraries in the ear module. The problem is, two of these modules fail to deploy to the server deploy folder, and as a result, ClassNotFoundExceptions are thrown from the JBoss class loader. If I close the projects containing the two troublesome modules, they are deployed correctly and everything is fine (as with the Kepler version). The two modules show up in the "Bundled libraries" view in the ear project, and they show under the ear deployment in the server view. But, in the server view, the decoration on the server is always "Republish" after startup, even though the ear module is "Synchronized". The non-deployed modules have no decoration at all, while the other modules all show "Synchronized".
> The problem seems to be classes with non-ASCII class names. If I rename the classes, the modules are deployed correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names
by Axel Wathne (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ]
Axel Wathne commented on JBIDE-18095:
-------------------------------------
- Yes, this works fine in Kepler
- By closing the project I mean Project -> Close Project in Eclipse. This changes the dependency from the ear project from a workspace project dependency to a jar file dependency like any other third party dependency (configured through Maven, maybe M2E changes the project automatically, not sure)
- I will try to make a minimal project to reproduce it, maybe tomorrow
> Server adapter fails to publish modules with non-ASCII class names
> ------------------------------------------------------------------
>
> Key: JBIDE-18095
> URL: https://issues.jboss.org/browse/JBIDE-18095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3, 4.2.0.CR1
> Environment: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140822-0028-B573 (nightly/luna repo), JBoss EAP 5.2.0 on Oracle Java 1.7.0_45
> Reporter: Axel Wathne
>
> I have a 35 module war/ear project, where multiple plain jar modules are deployed as bundled libraries in the ear module. The problem is, two of these modules fail to deploy to the server deploy folder, and as a result, ClassNotFoundExceptions are thrown from the JBoss class loader. If I close the projects containing the two troublesome modules, they are deployed correctly and everything is fine (as with the Kepler version). The two modules show up in the "Bundled libraries" view in the ear project, and they show under the ear deployment in the server view. But, in the server view, the decoration on the server is always "Republish" after startup, even though the ear module is "Synchronized". The non-deployed modules have no decoration at all, while the other modules all show "Synchronized".
> The problem seems to be classes with non-ASCII class names. If I rename the classes, the modules are deployed correctly.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17990:
---------------------------------------------
[~hwellmann] [~hwellmann.de] can you provide more info ?
i.e. do you have an error log where we can see what is failing ?
Any exceptions ?
And can you say if running eclipse with -clean fixes this or at least some of it ?
And what is "some technical identifier" exactly ?
All this would be helpful for us to diagnose the issue.
> Organize imports does not work for Maven dependencies
> -----------------------------------------------------
>
> Key: JBIDE-17990
> URL: https://issues.jboss.org/browse/JBIDE-17990
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta3
> Environment: Oracle JDK 1.8.0_05, Eclipse Luna
> Reporter: Harald Wellmann
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
>
> After upgrading from 4.2.0.Beta2 to Beta3 to test the fix for JBIDE-17724, Organize Imports is broken in my workspace. More precisely, I'm referring to the capability of finding the package a class lives in and generating the {{import}} directive with the FQCN.
> The corresponding Quick Fix is also broken.
> It only works for class names from sources in the workspace, it no longer works for class names from a Maven dependency in the local repository.
> This is even worse than JBIDE-17724, I'll have to revert to Beta2.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18123) Embed wizard: Deselecting embeddable cartridge does not trigger "possible data loss" dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18123?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18123:
-------------------------------------
Steps to Reproduce:
# ASSERT: have an application with at least 1 cartridge embedded (ex. mysql)
# EXEC: in OpenShift Explorer: Pick "Edit embedded cartridges" for your applicaiton in the context menu
# EXEC: in Embed wizard: uncheck your embedded cartridge (ex. mysql)
Result:
The cartridge is unchecked and removed once you hit "Finish"
Expected:
You should get warned and required to confirm the removal (as it was implemented in JBIDE-13961)
Assignee: Andre Dietisheim
> Embed wizard: Deselecting embeddable cartridge does not trigger "possible data loss" dialog
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-18123
> URL: https://issues.jboss.org/browse/JBIDE-18123
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: embed_wizard
> Fix For: 4.2.0.CR1
>
>
> In JBIDE-13961 we implemented showing a dialog informing about possible data loss after removing an embeddable cartridge. Nowadays this dialog is not shown anymore after unselecting embedded cartridge in Edit Embedded Cartridges shell (opened via context menu of an application).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months