March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13611) forge failing to compile due to two poms w/ the same GAV

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13611?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13611. ------------------------------- Resolution: Done > forge failing to compile due to two poms w/ the same GAV > -------------------------------------------------------- > > Key: JBIDE-13611 > URL: https://issues.jboss.org/browse/JBIDE-13611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.1.0.Alpha2 > > > {code} > [ERROR] Two or more projects in the reactor have the same identifier, please make sure that <groupId>:<artifactId>:<version> is unique for each project: > {org.jboss.tools.forge.features:org.jboss.tools.forge.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.feature/pom.xml], > org.jboss.tools.forge.features:org.jboss.tools.forge.test.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.test.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.test.feature/pom.xml]} -> [Help 1] > {code} -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13707) "Mylyn Issue Tracker connector" cannot be installed from Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13707?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13707: ----------------------------------- Description: When trying to install Maven connectors from Central, one can read: "The following connectors are not available: Mylyn Issue Tracker Connector" https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Log doesn't tell more, excet {code} org.eclipse.core.runtime.CoreException: The following connectors are not available: Mylyn Issue Tracker Connectors (id=org.jboss.tools.common.mylyn.feature.feature.group, site=http://download.jboss.org/jbosstools/updates/development/kepler/cent...) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.checkForUnavailable(PrepareInstallProfileJob_e_3_6.java:300) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.computeInstallableUnits(PrepareInstallProfileJob_e_3_6.java:210) at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.run(PrepareInstallProfileJob_e_3_6.java:95) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code} was: When trying to install Maven connectors from Central, one can read: "The following connectors are not available: Mylyn Issue Tracker Connector" https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Log doesn't tell more. > "Mylyn Issue Tracker connector" cannot be installed from Central > ---------------------------------------------------------------- > > Key: JBIDE-13707 > URL: https://issues.jboss.org/browse/JBIDE-13707 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Mickael Istria > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > When trying to install Maven connectors from Central, one can read: > "The following connectors are not available: Mylyn Issue Tracker Connector" > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Log doesn't tell more, excet > {code} > org.eclipse.core.runtime.CoreException: The following connectors are not available: Mylyn Issue Tracker Connectors (id=org.jboss.tools.common.mylyn.feature.feature.group, site=http://download.jboss.org/jbosstools/updates/development/kepler/cent...) > at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.checkForUnavailable(PrepareInstallProfileJob_e_3_6.java:300) > at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.computeInstallableUnits(PrepareInstallProfileJob_e_3_6.java:210) > at org.eclipse.mylyn.internal.discovery.ui.PrepareInstallProfileJob_e_3_6.run(PrepareInstallProfileJob_e_3_6.java:95) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > {code} -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13707) "Mylyn Issue Tracker connector" cannot be installed from Central

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-13707: -------------------------------------- Summary: "Mylyn Issue Tracker connector" cannot be installed from Central Key: JBIDE-13707 URL: https://issues.jboss.org/browse/JBIDE-13707 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.1.0.Alpha1 Reporter: Mickael Istria Assignee: Snjezana Peco Priority: Blocker Fix For: 4.1.0.Alpha1 When trying to install Maven connectors from Central, one can read: "The following connectors are not available: Mylyn Issue Tracker Connector" https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Log doesn't tell more. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13703) Team - Verify the workflow

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-13703: ------------------------------------- Thank you Guillaume, I am curious to know if this problem is within the Maven or CVS aspect of the IDE. Can you checkout the project from the command-line using CVS then in JBDS use File - Import - Maven - Existing Maven Projects? > Team - Verify the workflow > -------------------------- > > Key: JBIDE-13703 > URL: https://issues.jboss.org/browse/JBIDE-13703 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: JBDS-usability.pdf > > > The average end-user would like to: > 1) check out (clone) a project from CVS, SVN or Git > -- add repo, navigate repo, check out a project > -- project may or may not have .classpath, .project or .settings files > -- project may be Maven-based > and see if the following work > 2) Are the appropriate facets enabled? > 3) Does it build immediately? > 4) Can I immediately hit the run button to launch it on my app server? > 5) Can I immediately hit the debug button to debug it on my app server? > -- how do I step if there are no break points? > 6) Make a change to a file, re-run/debug again > 7) Run JUnit tests > 8) Check the change back into the repo with comments -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13706) Cannot install Google tools from Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13706?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-13706. ------------------------------------ Resolution: Done Site was updated and now includes missing Google tools feature. http://download.jboss.org/jbosstools/updates/requirements/gwt/3.2.0.v2013... > Cannot install Google tools from Central > ---------------------------------------- > > Key: JBIDE-13706 > URL: https://issues.jboss.org/browse/JBIDE-13706 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > Here is what log says: > {code} > Contains: Cannot complete the install because one or more required items could not be found. > Contains: Software being installed: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711) > Contains: Missing requirement: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919) requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found > Contains: Cannot satisfy dependency: > Contains: From: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711) > Contains: To: org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919 > {code} > Main message: *requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found* -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13702) ForgeCorePlugin could use an installed Forge 2 Runtime

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13702?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-13702: ----------------------------------------- Hi Max, Check this code: https://github.com/forge/jbosstools-forge/blob/master/plugins/org.jboss.t... Would an exploded distro would be the right solution in here, since we are creating a URLClassLoader based on some JARs inside the forge-se.jar ? My only concern is that a temporary folder is created every time the plugin is initialized. The idea from this issue is to save some disk space and have that already configured instead. > ForgeCorePlugin could use an installed Forge 2 Runtime > ------------------------------------------------------ > > Key: JBIDE-13702 > URL: https://issues.jboss.org/browse/JBIDE-13702 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: George Gastaldi > Assignee: Koen Aers > > In Forge 1, it is possible to configure external Forge runtimes. In Forge 2 it would be nice to allow configuration of that, but also avoid the need to unzip the files in the startup. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13703) Team - Verify the workflow

by Guillaume Radde (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ] Guillaume Radde updated JBIDE-13703: ------------------------------------ Attachment: JBDS-usability.pdf The attached pdf shows a sequence of steps that led to an unusable Maven project. > Team - Verify the workflow > -------------------------- > > Key: JBIDE-13703 > URL: https://issues.jboss.org/browse/JBIDE-13703 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: JBDS-usability.pdf > > > The average end-user would like to: > 1) check out (clone) a project from CVS, SVN or Git > -- add repo, navigate repo, check out a project > -- project may or may not have .classpath, .project or .settings files > -- project may be Maven-based > and see if the following work > 2) Are the appropriate facets enabled? > 3) Does it build immediately? > 4) Can I immediately hit the run button to launch it on my app server? > 5) Can I immediately hit the debug button to debug it on my app server? > -- how do I step if there are no break points? > 6) Make a change to a file, re-run/debug again > 7) Run JUnit tests > 8) Check the change back into the repo with comments -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip (or at least document the limitations)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2456: ------------------------------------------- This requires much more work than just add a few bits and pieces into the current zip. Should get our builds to not depend on snapshots nor moving target platforms before being able to reliably build this from the zip. > JBDS should be buildable from source zip (or at least document the limitations) > ------------------------------------------------------------------------------- > > Key: JBDS-2456 > URL: https://issues.jboss.org/browse/JBDS-2456 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.0.GA, 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 7.0.0.Alpha2 > > > As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing: > {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote} > It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either). > Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3 -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13662) Unhandled event loop exception when closing Fileset dialog FAST

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13662?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13662. --------------------------------- Resolution: Done validateAndUpdateWidgets(etc) is called from the UI thread, so a simple check to isDisposed() fixes this. > Unhandled event loop exception when closing Fileset dialog FAST > --------------------------------------------------------------- > > Key: JBIDE-13662 > URL: https://issues.jboss.org/browse/JBIDE-13662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Archives > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-13335. ------------------------------ Verified in JBDS 6.0.1.CR1. Closing > remove Juno SR1+ performance fix from Central > ---------------------------------------------- > > Key: JBIDE-13335 > URL: https://issues.jboss.org/browse/JBIDE-13335 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 4.0.1.Final > > Attachments: JBIDE13335.patch.JBDS6.0.1.txt > > > For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars. > Need to therefore, for JBT 4.0.1 and JBDS 6.0.1: > a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places) > b) remove the connector from discovery plugins' plugin.xml (2 files) -- 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

13 years, 4 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 March 2013