September 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3122) Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3122?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3122: -------------------------------------- Fix Version/s: 8.0.1.GA > Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin > ------------------------------------------------------------------------------------------ > > Key: JBDS-3122 > URL: https://issues.jboss.org/browse/JBDS-3122 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: ui/branding > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Labels: f2f2014 > Fix For: 8.0.1.GA > > Attachments: fc20-mate-result.png > > > Based on stats and general crazy interests dark themes like provided by http://marketplace.eclipse.org/content/eclipse-moonrise-ui-theme and basic Eclipse Luna dark theme we should check if we have some obvious glitches when eclipse is switched to dark theme. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3122) Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3122?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3122: -------------------------------------- Labels: f2f2014 (was: ) > Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin > ------------------------------------------------------------------------------------------ > > Key: JBDS-3122 > URL: https://issues.jboss.org/browse/JBDS-3122 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: ui/branding > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Labels: f2f2014 > Fix For: 8.0.1.GA > > Attachments: fc20-mate-result.png > > > Based on stats and general crazy interests dark themes like provided by http://marketplace.eclipse.org/content/eclipse-moonrise-ui-theme and basic Eclipse Luna dark theme we should check if we have some obvious glitches when eclipse is switched to dark theme. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3122) Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3122?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3122: ----------------------------- CDW pm_ack: ? > Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin > ------------------------------------------------------------------------------------------ > > Key: JBDS-3122 > URL: https://issues.jboss.org/browse/JBDS-3122 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: ui/branding > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Labels: f2f2014 > Attachments: fc20-mate-result.png > > > Based on stats and general crazy interests dark themes like provided by http://marketplace.eclipse.org/content/eclipse-moonrise-ui-theme and basic Eclipse Luna dark theme we should check if we have some obvious glitches when eclipse is switched to dark theme. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3122) Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3122?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3122: -------------------------------------- CDW release: ? Status: New (was: New) Target Release: 8.0.1.GA > Test/ensure devstudio works with dark themes as built into eclipse luna or moonrise plugin > ------------------------------------------------------------------------------------------ > > Key: JBDS-3122 > URL: https://issues.jboss.org/browse/JBDS-3122 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: ui/branding > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Labels: f2f2014 > Attachments: fc20-mate-result.png > > > Based on stats and general crazy interests dark themes like provided by http://marketplace.eclipse.org/content/eclipse-moonrise-ui-theme and basic Eclipse Luna dark theme we should check if we have some obvious glitches when eclipse is switched to dark theme. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18096) could not complete update project configuration - illegalargumentexception

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18096?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18096: ---------------------------------------- Labels: f2f2014 (was: ) > could not complete update project configuration - illegalargumentexception > -------------------------------------------------------------------------- > > Key: JBIDE-18096 > URL: https://issues.jboss.org/browse/JBIDE-18096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Labels: f2f2014 > > while trying to fix import of javaee-samples I bumped into this happening when running update project configuration. > java.lang.IllegalArgumentException > at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.removeProjectFacet(FacetedProjectWorkingCopy.java:876) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:309) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) > at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configure(WebProjectConfiguratorDelegate.java:150) > at org.eclipse.m2e.wtp.AbstractProjectConfiguratorDelegate.configureProject(AbstractProjectConfiguratorDelegate.java:93) > at org.eclipse.m2e.wtp.WTPProjectConfigurator.configure(WTPProjectConfigurator.java:70) > at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318) > at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > It happened on ~100 projects so was quite invasive ;/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3141: ------------------------------------------- for QE to test and open issues if anything or resolve if all just works. > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > Assignee: Len DiMaggio > Fix For: 8.0.0.CR2 > > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3141: -------------------------------------- Fix Version/s: 8.0.0.CR2 > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > Assignee: Len DiMaggio > Fix For: 8.0.0.CR2 > > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3141: -------------------------------------- Assignee: Len DiMaggio > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > Assignee: Len DiMaggio > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18323) JBoss Maven Repository not recognized

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18323?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18323: ---------------------------------------- Priority: Minor (was: Major) > JBoss Maven Repository not recognized > ------------------------------------- > > Key: JBIDE-18323 > URL: https://issues.jboss.org/browse/JBIDE-18323 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Andrea Vibelli > Assignee: Fred Bricon > Priority: Minor > > I am using JBoss Developer Studio Version: 8.0.0.Beta3, and trying to import my Maven Repository, but it doesn't get recognized. Does the Maven repository have to contain specific metadata / pom f/ GAVs in order to be recognized? > JBoss Maven Integration has version: 1.6.0.Beta3-v20140718-1719-B77 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18323) JBoss Maven Repository not recognized

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18323?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18323: ---------------------------------------- Fix Version/s: 4.2.0.CR2 4.2.1.Final > JBoss Maven Repository not recognized > ------------------------------------- > > Key: JBIDE-18323 > URL: https://issues.jboss.org/browse/JBIDE-18323 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Andrea Vibelli > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.CR2, 4.2.1.Final > > > I am using JBoss Developer Studio Version: 8.0.0.Beta3, and trying to import my Maven Repository, but it doesn't get recognized. Does the Maven repository have to contain specific metadata / pom f/ GAVs in order to be recognized? > JBoss Maven Integration has version: 1.6.0.Beta3-v20140718-1719-B77 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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