[JBoss JIRA] (JBIDE-18578) Additional javaee7-samples import issues
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18578?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-18578:
------------------------------------------
Maven problems are gone with jax-ws configurator installed.
Problems which I see now and are not mentioned in Jirka's post are:
JPA Problems
{code}
Duplicate entity name "Child" found in the persistence unit. Entity names must be unique. Child.java /jpa-ordercolumn/src/main/java/org/javaee7/jpa/ordercolumn/entity/bidirectionaljoin line 11 JPA Problem
Duplicate entity name "Child" found in the persistence unit. Entity names must be unique. Child.java /jpa-rdercolumn/src/main/java/org/javaee7/jpa/ordercolumn/entity/bidirectionalmappedby line 10 JPA Problem
Duplicate entity name "Child" found in the persistence unit. Entity names must be unique. Child.java /jpa-ordercolumn/src/main/java/org/javaee7/jpa/ordercolumn/entity/unidirectional line 9 JPA Problem
Duplicate entity name "Parent" found in the persistence unit. Entity names must be unique. Parent.java /jpa-ordercolumn/src/main/java/org/javaee7/jpa/ordercolumn/entity/bidirectionaljoin line 17 JPA Problem
Duplicate entity name "Parent" found in the persistence unit. Entity names must be unique. Parent.java /jpa-ordercolumn/src/main/java/org/javaee7/jpa/ordercolumn/entity/bidirectionalmappedby line 16 JPA Problem
Duplicate entity name "Parent" found in the persistence unit. Entity names must be unique. Parent.java /jpa-ordercolumn/src/main/java/org/javaee7/jpa/ordercolumn/entity/unidirectional line 17 JPA Problem
{code}
and two JAX-RS problems
{code}
Multiple JAX-RS Activators are defined for the project. MyAnnotatedApplication.java /jaxrs-singleton/src/main/java/org/javaee7/jaxrs/singleton line 10 JAX-RS Problem
Multiple JAX-RS Activators are defined for the project. MyApplication.java /jaxrs-singleton/src/main/java/org/javaee7/jaxrs/singleton line 11 JAX-RS Problem
{code}
> Additional javaee7-samples import issues
> ----------------------------------------
>
> Key: JBIDE-18578
> URL: https://issues.jboss.org/browse/JBIDE-18578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.CR2
> Environment: JBDS 8.0.0.CR2
> Reporter: Jiri Peterka
> Assignee: Rastislav Wagner
> Fix For: 4.3.0.Beta2
>
>
> Additional javaee7-samples import issues
> Clone and import https://github.com/javaee-samples/javaee7-samples as maven projects
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
> There are still some Java Problems, Maven Problems and XML Problems after import, most projects are without errors. Project should be imported 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}
> Additional issues:
> https://issues.jboss.org/browse/JBIDE-18352
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20084) Import of jboss-sandbox-quickstarts
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20084?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-20084.
------------------------------------
Resolution: Done
I believe that with latest version from upstream, this is now resolved and those quickstart import correctly within a few seconds.
> Import of jboss-sandbox-quickstarts
> -----------------------------------
>
> Key: JBIDE-20084
> URL: https://issues.jboss.org/browse/JBIDE-20084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta2
>
>
> I tried to import jboss-sandbox-quickstarts (from https://github.com/jboss-developer/jboss-sandbox-quickstarts.git) and I found following issues with it
> - it takes quite a long time (app 3 and a half minutes to import 9 projects
> - during import it seems to be "stuck" for a while and the following exception is logged
> {code}
> org.eclipse.core.runtime.CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:410)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:950)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:76)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:97)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$4.run(ProjectConfigurationManager.java:521)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.java:26)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.enableMavenNature(ProjectConfigurationManager.java:518)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator.configure(MavenProjectConfigurator.java:44)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:236)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.run(EasymportJob.java:93)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> ... 35 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 41 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 44 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 47 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19771) Improve Available detectors dialog
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19771?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-19771.
------------------------------------
Resolution: Done
The related commit was re-pushed (with all the necessary things) last week, and JBT/JBDS now include a version of the importer with this fixed.
> Improve Available detectors dialog
> ----------------------------------
>
> Key: JBIDE-19771
> URL: https://issues.jboss.org/browse/JBIDE-19771
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: easymport
> Affects Versions: 4.3.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
> Attachments: available-detectors.png
>
>
> At the moment, the dialog looks a bit untidy - there is no description what the detectors mean, they are not alphabetically ordered (or does the order mean something?) and they even seem not to be aligned.
> Also, the link that opens the dialog is too long - Show available detectors would be enough and the description about what detectors are could go to the dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months