April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17203) Cordova project requires user to recreate run configuration when iOS target sdk is changed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17203?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17203: ---------------------------------------- Assignee: Gorkem Ercan (was: Max Rydahl Andersen) > Cordova project requires user to recreate run configuration when iOS target sdk is changed > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17203 > URL: https://issues.jboss.org/browse/JBIDE-17203 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Tadeas Kriz > Assignee: Gorkem Ercan > > When cordova application is changed that way that it requires newer iOS target SDK (for example switching from iOS 6 to iOS 7) it will no longer compile unless the user deletes and then makes a new run configuration. It would be good if the user might select which target sdk will be used, this will probably mitigate this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11292) Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11292?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-11292: ------------------------------------- I have not noticed it recently but perhaps not running the same steps > Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-11292 > URL: https://issues.jboss.org/browse/JBIDE-11292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 3.3.x > > Attachments: project_configuration_is_not_up_to_date_0.png > > > "Project configuration is not up-to-date with pom.xml. Run project configuration update" > I have noticed, with beta1e and perhaps beta1d, that when I load up my workspace with projects - created via the archetypes, quickstarts and even File Import - perhaps, after a restart of the IDE - the next time I import (file-import or archetype) another maven project, the previous projects throw up the project configuration error msg. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17202) Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.7.0

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17202?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-17202: -------------------------------------- Nothing all that surprising: !ENTRY org.eclipse.jdt.core 4 4 2014-04-25 22:42:06.595 !MESSAGE Background Indexer Crash Recovery !STACK 0 java.lang.OutOfMemoryError: GC overhead limit exceeded at java.io.BufferedInputStream.<init>(BufferedInputStream.java:195) at java.io.BufferedInputStream.<init>(BufferedInputStream.java:175) at org.eclipse.jdt.internal.compiler.util.Util.getZipEntryByteContent(Util.java:689) at org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIndex.execute(AddJarFileToIndex.java:233) at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:405) at java.lang.Thread.run(Thread.java:724) !ENTRY org.eclipse.core.jobs 4 2 2014-04-25 22:57:03.564 !MESSAGE An internal error occurred during: "Updating Maven Dependencies". !STACK 0 java.lang.OutOfMemoryError: GC overhead limit exceeded at org.apache.maven.model.Dependency.setLocation(Dependency.java:474) at org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.parseDependency(MavenXpp3ReaderEx.java:1394) at org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.parseDependencyManagement(MavenXpp3ReaderEx.java:1527) at org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.parseModel(MavenXpp3ReaderEx.java:2460) at org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.read(MavenXpp3ReaderEx.java:4350) at org.apache.maven.model.io.xpp3.MavenXpp3ReaderEx.read(MavenXpp3ReaderEx.java:560) at org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:118) at org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:91) at org.apache.maven.model.building.DefaultModelProcessor.read(DefaultModelProcessor.java:77) at org.apache.maven.model.building.DefaultModelBuilder.readModel(DefaultModelBuilder.java:453) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:256) at org.apache.maven.model.building.DefaultModelBuilder.importDependencyManagement(DefaultModelBuilder.java:1001) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:397) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:368) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:359) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:145) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:105) at org.eclipse.m2e.core.internal.embedder.MavenImpl.readMavenProject(MavenImpl.java:625) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$4.call(ProjectRegistryManager.java:665) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$4.call(ProjectRegistryManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:165) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:141) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:95) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.execute(ProjectRegistryManager.java:913) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.readMavenProjectFacade(ProjectRegistryManager.java:660) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:377) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:336) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1$1.call(ProjectRegistryRefreshJob.java:95) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1$1.call(ProjectRegistryRefreshJob.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:165) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:141) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:95) > Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.7.0 > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-17202 > URL: https://issues.jboss.org/browse/JBIDE-17202 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: build > Affects Versions: 4.2.0.Beta1 > Environment: Linux 2.6.32-358.23.2.el6.x86_64 #1 SMP Sat Sep 14 05:32:37 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.7.0_25" > OpenJDK Runtime Environment (rhel-2.3.10.4.el6_4-x86_64) > OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) > Reporter: Len DiMaggio > Attachments: log, Screenshot-1.png, Screenshot-2.png, Screenshot.png > > > See attached logs and screenshots - building WildFly causes a GC failure -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3019) Cordova project requires user to recreate run configuration when iOS target sdk is changed

by Tadeas Kriz (JIRA)

Tadeas Kriz created JBDS-3019: --------------------------------- Summary: Cordova project requires user to recreate run configuration when iOS target sdk is changed Key: JBDS-3019 URL: https://issues.jboss.org/browse/JBDS-3019 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: aerogear-hybrid Affects Versions: 7.1.1.GA Reporter: Tadeas Kriz Assignee: Max Rydahl Andersen When cordova application is changed that way that it requires newer iOS target SDK (for example switching from iOS 6 to iOS 7) it will no longer compile unless the user deletes and then makes a new run configuration. It would be good if the user might select which target sdk will be used, this will probably mitigate this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14971) PMD4 - Generate Abstract Syntax Tree fails

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14971?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14971: ------------------------------------- We'll definitely needs a new version. We'll know which one once it's released :-) > PMD4 - Generate Abstract Syntax Tree fails > ------------------------------------------ > > Key: JBIDE-14971 > URL: https://issues.jboss.org/browse/JBIDE-14971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Affects Versions: 4.1.0.Beta2 > Environment: java version "1.7.0_09-icedtea" > OpenJDK Runtime Environment (rhel-2.3.3.2.el6_3-x86_64) > OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode) > RHEL6 > Version: 7.0.0.Beta2 > Build id: Beta2-v20130616-1738-B261 > Build date: 20130616-1738 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.2.0.Beta2 > > Attachments: log.1, Screenshot.png > > > Installed PMD4 from here: > PMD - http://download.jboss.org/jbosstools/updates/requirements/pmd/4.0.0.v2013... > Then selected source code and executed Generate Abstract Syntax Tree > And hit this error: > net.sourceforge.pmd.lang.java.ast.ParseException: Can't use static imports when running in JDK 1.4 mode! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11292) Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11292?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-11292: ------------------------------------- I don't remember experiencing this issue with m2e 1.5.0 (JBT 4.2/JBDS 8), have you? > Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-11292 > URL: https://issues.jboss.org/browse/JBIDE-11292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 3.3.x > > Attachments: project_configuration_is_not_up_to_date_0.png > > > "Project configuration is not up-to-date with pom.xml. Run project configuration update" > I have noticed, with beta1e and perhaps beta1d, that when I load up my workspace with projects - created via the archetypes, quickstarts and even File Import - perhaps, after a restart of the IDE - the next time I import (file-import or archetype) another maven project, the previous projects throw up the project configuration error msg. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16630) Table of seam runtimes is not updated after seam was added via runtime detection

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16630?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-16630. ----------------------------------- Verified in JBDS 8.0.0 Beta1-v20140408-2350-B93 > Table of seam runtimes is not updated after seam was added via runtime detection > -------------------------------------------------------------------------------- > > Key: JBIDE-16630 > URL: https://issues.jboss.org/browse/JBIDE-16630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.Alpha2 > Reporter: Radoslav Rábara > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta1 > > > The table Seam Runtime Environment in Preferences is not updated right after the runtime with seam was added via runtime detection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2978) Monitor WTP issue re: nested packed jars

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2978?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2978: ------------------------------------------- pinged on wtp-dev on this issuse. > Monitor WTP issue re: nested packed jars > ---------------------------------------- > > Key: JBDS-2978 > URL: https://issues.jboss.org/browse/JBDS-2978 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: build, requirements, upstream > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > Fix For: 8.0.0.GA > > > Adding this subtask as a reminder to myself to check in w/ WTP from time to time to see if https://bugs.eclipse.org/bugs/show_bug.cgi?id=430923 gets fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17002) Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17002: --------------------------------------------- [~nickboldt] could we please separate "fixing 4.1.2. final" from "releasing java 8 connector" ? especially since I dont recall there being a 4.1.2.Final release two weeks ago ? ...thus i'm confused by that statement. What we released last was 4.2.0.Beta1. > Add Java 8 connector (JDT/WTP/M2E) in Central for JBT 4.1.2 > ----------------------------------------------------------- > > Key: JBIDE-17002 > URL: https://issues.jboss.org/browse/JBIDE-17002 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.2.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.1.2.Final > > Attachments: jbide17002-3-4-features.png, jbide17002-6-7-features.png, jbide17002-patch-catg.png > > > We decided to provide an easy way for JBT users to install Java 8 support in Eclipse Kepler SR2 in 1 click, instead of have to chase the update sites for JDT, M2e and WTP. > * JDT Feature patch : http://download.eclipse.org/eclipse/updates/4.3-P-builds/ > * M2E 1.4.1 (org.eclipse.m2e.feature) http://download.eclipse.org/technology/m2e/releases/1.4/1.4.1.20140328-1905 > * WTP Feature Patch : http://download.eclipse.org/webtools/patches/drops/R3.5.2/P-3.5.2-2014032... > All 3 features should be available via a unique connector in JBoss Central > Software Updates -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17189) Application wizard: if launched from central "Use my existing OpenShift application" is preselected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17189?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17189: ------------------------------------- Summary: Application wizard: if launched from central "Use my existing OpenShift application" is preselected (was: Application wizard: if launched from central "Use my existing OpenShift applaiction" is preselected) > Application wizard: if launched from central "Use my existing OpenShift application" is preselected > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-17189 > URL: https://issues.jboss.org/browse/JBIDE-17189 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Fix For: 4.2.0.Beta2 > > > # EXEC: launch "New OpenShift Application" link > Result: > The new application wizard pops up but its preselected to "Use my existing OpenShift application" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 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 April 2014