July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20084) Import of jboss-sandbox-quickstarts

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20084?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-20084: ----------------------------------------- Yes, the import is now very fast. > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-20070) Fix minor issues in RedDeer import

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20070?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-20070: ----------------------------------------- I tried the upstream changes and it seems that only the last issue is fixed. The plugins folder still has Java listed and the root folder still has Eclipse project. > Fix minor issues in RedDeer import > ---------------------------------- > > Key: JBIDE-20070 > URL: https://issues.jboss.org/browse/JBIDE-20070 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: dialog.png > > > When I try to import the whole RedDeer project (cloned from https://github.com/jboss-reddeer/reddeer.git) I can see that some folders have listed "Maven, Java" and some only "Maven" even though the directory structure seems the same to me (e.g. directory "plugins" and directory "features" contain only one pom file and set of other folders, but one has "Java" listed and one does not). > List of minor issues: > - the root folder (reddeer) has listed Maven, Eclipse project - I think the Eclipse project should not be there > - features has listed "Maven" but plugins and tests have "Maven, Java" > - all plugins in tests folder are correctly recognized as OSGI bundles except for the org.jboss.reddeer.workbench.test that has also "Java" nature -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20195) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Aerogear]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20195?page=com.atlassian.jira.plugi... ] Ilya Buziuk reassigned JBIDE-20195: ----------------------------------- Assignee: Konstantin Marmalyukov (was: Ilya Buziuk) > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Aerogear] > ------------------------------------------------------------------------------------ > > Key: JBIDE-20195 > URL: https://issues.jboss.org/browse/JBIDE-20195 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Aerogear]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20195) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Aerogear]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20195?page=com.atlassian.jira.plugi... ] Ilya Buziuk reassigned JBIDE-20195: ----------------------------------- Assignee: Ilya Buziuk > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Aerogear] > ------------------------------------------------------------------------------------ > > Key: JBIDE-20195 > URL: https://issues.jboss.org/browse/JBIDE-20195 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Aerogear]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20203) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [OpenShift]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20203?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20203: ---------------------------------------- Assignee: Andre Dietisheim > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [OpenShift] > ------------------------------------------------------------------------------------- > > Key: JBIDE-20203 > URL: https://issues.jboss.org/browse/JBIDE-20203 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [OpenShift]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20215) Version property is not replaced with a value defined in parent pom

by Matous Jobanek (JIRA)

Matous Jobanek created JBIDE-20215: -------------------------------------- Summary: Version property is not replaced with a value defined in parent pom Key: JBIDE-20215 URL: https://issues.jboss.org/browse/JBIDE-20215 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.3.0.Alpha1 Environment: JBDS 9.0.0.Alpha1 Reporter: Matous Jobanek Consider this situation: There is a parent pom where a version property is defined. {code:xml} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>jira</groupId> <artifactId>jira-reproducer-parent</artifactId> <version>1.0</version> <packaging>pom</packaging> <properties> <reproducer.child.version>1.1.Final</reproducer.child.version> </properties> </project> {code} Then there is a child pom and version of this pom is the property defined in the parent pom. {code:xml} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>jira</groupId> <artifactId>jira-reproducer-parent</artifactId> <version>1.0</version> <relativePath>../pom.xml</relativePath> </parent> <artifactId>jira-reproducer-child</artifactId> <version>${reproducer.child.version}</version> </project> {code} Then the generated pom at target/classes/META-INF/maven/jira/jira-reproducer-child/pom.xml doesn't contain the replaced value from the parent pom, but the original property: {code:xml} <version>${reproducer.child.version}</version> {code} should be: {code:xml} <version>1.1.Final</version> {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19992) Open Properties view on double click of elemet in batch diagram

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19992?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19992. ----------------------------------- Agreed, we do not need this feature. > Open Properties view on double click of elemet in batch diagram > --------------------------------------------------------------- > > Key: JBIDE-19992 > URL: https://issues.jboss.org/browse/JBIDE-19992 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > In batch editor diagram tab, it would be nice if after double click on some element (e.g. step) corrensponding Properties view would be open and activated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20214) Put entry to make a Cordova project Feedhenry-albe in Configure

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20214?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-20214: --------------------------------- Fix Version/s: 4.3.0.Beta2 > Put entry to make a Cordova project Feedhenry-albe in Configure > --------------------------------------------------------------- > > Key: JBIDE-20214 > URL: https://issues.jboss.org/browse/JBIDE-20214 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.3.0.Beta2 > Reporter: Mickael Istria > Assignee: Gorkem Ercan > Fix For: 4.3.0.Beta2 > > > I just saw https://www.youtube.com/watch?v=mpfKTe-Qb8k > As an addition to be able to connect to FeedHenry via the "New" wizard, I believe it would make sense to also add an entry in the "Configure" context menu to "Enable FeedHenry" on an existing Thym project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20214) Put entry to make a Cordova project Feedhenry-albe in Configure

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20214?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-20214: ------------------------------------ Assignee: Gorkem Ercan > Put entry to make a Cordova project Feedhenry-albe in Configure > --------------------------------------------------------------- > > Key: JBIDE-20214 > URL: https://issues.jboss.org/browse/JBIDE-20214 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.3.0.Beta2 > Reporter: Mickael Istria > Assignee: Gorkem Ercan > > I just saw https://www.youtube.com/watch?v=mpfKTe-Qb8k > As an addition to be able to connect to FeedHenry via the "New" wizard, I believe it would make sense to also add an entry in the "Configure" context menu to "Enable FeedHenry" on an existing Thym project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20185) create just one marketplace entry for jboss tools

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20185?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-20185: ------------------------------------------- [~jrichter1] could you have a look at this, please? > create just one marketplace entry for jboss tools > ------------------------------------------------- > > Key: JBIDE-20185 > URL: https://issues.jboss.org/browse/JBIDE-20185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > As discussed on JBIDE-20024 it now makes sense to have just one jboss tools entry on markteplace. > To avoid full loss of stats the entry to rename is JBoss Tools (Luna): http://marketplace.eclipse.org/content/jboss-tools-luna/metrics since it has the highest count by far currently. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2015