May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2122) Unable to install EGit from JBoss Central

by Radim Hopp (JIRA)

Radim Hopp created JBDS-2122: -------------------------------- Summary: Unable to install EGit from JBoss Central Key: JBDS-2122 URL: https://issues.jboss.org/browse/JBDS-2122 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification, central Affects Versions: 5.0.0.Beta3 Environment: JBDS 5.0.0.Beta3 Fedora 16 OpenJDK 1.6.0_24 64b Reporter: Radim Hopp Assignee: Snjezana Peco Fix For: 5.0.0.Beta3 Attachments: EgitInstall.png, EgitInstall1.png Installation of EGit through JBoss Central says "The following connectors are not available: Eclipse EGit" EGit isn't even on extras site. See attached screenshots. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] (JBIDE-10825) Move to Tycho 0.14

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-10825: -------------------------------------- Summary: Move to Tycho 0.14 Key: JBIDE-10825 URL: https://issues.jboss.org/browse/JBIDE-10825 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Mickael Istria Assignee: Mickael Istria -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-9686) Errors in Error Log after clean JBT M3a installatin

by Jiri Peterka (JIRA)

Errors in Error Log after clean JBT M3a installatin --------------------------------------------------- Key: JBIDE-9686 URL: https://issues.jboss.org/browse/JBIDE-9686 Project: Tools (JBoss Tools) Issue Type: Bug Components: UpStream Affects Versions: 3.3.0.M3 Environment: JBT 3.3.0.M3a/2011-09-07_05-39-13-H18, L64, Fedora 15 64 bit Reporter: Jiri Peterka Assignee: Max Rydahl Andersen Priority: Critical Fix For: 3.3.0.M3 Attachments: error-log.png After clean JBT installation http://download.jboss.org/jbosstools/builds/development/3.3.0.M3a/2011-09... See screenshot !ENTRY org.eclipse.ui 4 4 2011-09-09 09:50:20.626 !MESSAGE Referenced part does not exist yet: org.eclipse.jdt.ui.PackageExplorer. Application Started: 10543 !ENTRY org.eclipse.ui 4 4 2011-09-09 09:50:27.623 !MESSAGE Invalid preference page path: Web Toolkit !ENTRY org.eclipse.ui 4 4 2011-09-09 09:50:27.624 !MESSAGE Invalid preference page path: Speed Trac Clean Eclipse JEE - 0 error messages -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

11
42
0 / 0

[JBoss JIRA] (JBIDE-11166) Supporting multi-module projects in OpenShift Deployment

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11166: ------------------------------------------- Summary: Supporting multi-module projects in OpenShift Deployment Key: JBIDE-11166 URL: https://issues.jboss.org/browse/JBIDE-11166 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift, JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.0.Beta1, 3.3.0.Beta2 POH5 archetype recently got updated and became the first project layout that requires support for multimodule project layouts. What they have is the following: Aggregator Project "AP" includes two child projects "A" and "B". This is the simplest case - but you could also easily have more complex layouts, i.e. AP includes another aggregatorproject QAP which nest other child projects. But the key point is that the "root" in OpenShift is considered the Aggegator project. And this is the kind of layout we would need to support, and I see the following things we need to check/implement to make it happen: A) The "magic" project on our OpenShift server adapter should be allowed to be any kind of project as long as it has git enabled on it. B) OpenShift Server Adapter should *not* deploy any child of Aggregator as binary by default C) Import of OpenShift Application should be sure it will actually import a multimodule project. D) Import of OpenShift App when using existing App would need to do some validity checks *and* somehow ensure the child projects gets available if they aren't imported (maybe a warning is enough?) I belive A and C should be trivially implemented if not already. B should be as simple as checking the phyiscal location. i.e. if A is a subdir within AP then dont deploy. i.e. /Users/max/ap is parent for project A stored in /Users/max/ap/x/y/z/a D is the hard part. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

6
17
0 / 0

[JBoss JIRA] (JBDS-2128) RESTEasy example referred to in the Web Services Guide for JBDS is missing

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2128: ---------------------------------- Summary: RESTEasy example referred to in the Web Services Guide for JBDS is missing Key: JBDS-2128 URL: https://issues.jboss.org/browse/JBDS-2128 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.0.Beta1-SOA Environment: Version: 5.0.0.Beta3 Build id: v20120430-1703-H125-Beta3 Build date: 20120430-1703 Reporter: Len DiMaggio Assignee: Snjezana Peco Priority: Blocker Fix For: 5.0.0.GA-SOA This book: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Developer_Stud... Refers to this example: http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/resteasy-examp... But - the example is not included in the Help->Project Examples sets of examples (see screenshot) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9688) Add JBoss public repository to list of default repositories in Eclipse

by Rob Cernich (JIRA)

Add JBoss public repository to list of default repositories in Eclipse ---------------------------------------------------------------------- Key: JBIDE-9688 URL: https://issues.jboss.org/browse/JBIDE-9688 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: maven Reporter: Rob Cernich Assignee: Fred Bricon Priority: Minor M2e exposes an extension point, which allows plugins to contribute repositories to be indexed. Automatically registering the JBoss repository seems like a sensible thing for JBoss Tools. This would allow the user to access the JBoss public repository from the tooling (e.g. add dependency) without requiring them to add the JBoss public repository to their settings.xml file. Of course, the user would still need to ensure that the repository was correctly configured within their pom so the project will build correctly. The following is all that is required (in plugin.xml): <extension point="org.eclipse.m2e.core.indexes"> <index indexId="JBOSS_NEXUS" isShort="true" repositoryUrl="http://repository.jboss.org/nexus/content/groups/public"> </index> </extension> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

7
12
0 / 0

[JBoss JIRA] (JBDS-2030) Disabled modal usage dialogs from extras plugins by default

by Jiri Peterka (JIRA)

Jiri Peterka created JBDS-2030: ---------------------------------- Summary: Disabled modal usage dialogs from extras plugins by default Key: JBDS-2030 URL: https://issues.jboss.org/browse/JBDS-2030 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build, updatesite Affects Versions: 5.0.0.M5 Environment: JBDS 5.0.0.M5 Reporter: Jiri Peterka Assignee: Nick Boldt Fix For: 5.0.0.Beta1 Usage analysis modal dialogs from extras plugins are quire annoying. Mainly in situations when there is more then one and the one with focus is hidden behind the other. It would be nice if appearing of these dialogs could be disabled by default in JBDS. Namely these: * subclipse usage * atlasian connector -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
18
0 / 0

[JBoss JIRA] (JBIDE-11468) Set up Jenkins unstable/yellow builds

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11468: -------------------------------------- Summary: Set up Jenkins unstable/yellow builds Key: JBIDE-11468 URL: https://issues.jboss.org/browse/JBIDE-11468 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 3.3.0.Beta3 In order to have a better readability of build status, we should do the necessary stuff to introduce "unstable/yellow" builds. This build status shows that the only issue in build is failing tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-11877) Deleting jar archive from Project Explorer doesn't affect Project Archives explorer

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11877: ----------------------------------------- Summary: Deleting jar archive from Project Explorer doesn't affect Project Archives explorer Key: JBIDE-11877 URL: https://issues.jboss.org/browse/JBIDE-11877 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.3.0.Beta3 Reporter: Jaroslav Jankovič Assignee: Rob Stryker Fix For: 3.3.0.Beta3, 3.3.0.CR1 If I simply delete jar archive (not node within Project Archives explorer) from Project Explorer, this "change" in project doesn't affect archive node within Project Archives explorer in Project Explorer - archive is still there. Then when I clean build the project, jar archive reappears. This seems that only way to remove jar file permanently is using Project Archives explorer or view. I think that this shouldn't be the only way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8208) Improve how annotation processors are setup/detected via maven/m2eclipse

by Max Rydahl Andersen (JIRA)

Improve how annotation processors are setup/detected via maven/m2eclipse ------------------------------------------------------------------------ Key: JBIDE-8208 URL: https://issues.jboss.org/browse/JBIDE-8208 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Fix For: 3.2.1 Any way m2eclipse can setup and detect annotation processors ? Why isn't annotation processor not enabled by default when generating the .settings files for it ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

9
26
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 May 2012