December 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-2258) Provide a plugin for JAX-RS resp. Resteasy

by Juergen Zimmermann (JIRA)

Provide a plugin for JAX-RS resp. Resteasy ------------------------------------------ Key: JBIDE-2258 URL: http://jira.jboss.com/jira/browse/JBIDE-2258 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1.0.CR1 Reporter: Juergen Zimmermann NetBeans 6.1 provides a plugin for Sun's Jersey being the reference implementation of JAX-RS (= Java API for RESTful Web Services): https://jersey.dev.java.net/servlets/ReadMsg?list=users&msgNo=1293 Resteasy is the upcoming implementation of JAX-RS for JBoss -- see http://wiki.jboss.org/wiki/RESTeasyJAXRS It would be nice to also have a JAX-RS plugin for Resteasy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8838) add source feature to JBT components; generate source plugins w/ Tycho

by Nick Boldt (JIRA)

add source feature to JBT components; generate source plugins w/ Tycho ---------------------------------------------------------------------- Key: JBIDE-8838 URL: https://issues.jboss.org/browse/JBIDE-8838 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M2 As per example done in https://bugs.eclipse.org/bugs/show_bug.cgi?id=344515 and http://wiki.eclipse.org/Minerva#Source, the rest of JBT needs source features/plugins. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

8
63
0 / 0

[JBoss JIRA] Created: (JBIDE-9309) Easily adding full JBoss AS source

by arjan tijms (JIRA)

Easily adding full JBoss AS source ---------------------------------- Key: JBIDE-9309 URL: https://issues.jboss.org/browse/JBIDE-9309 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: arjan tijms Assignee: Rob Stryker The JBoss AS server runtime from JBoss tools adds a library container to the classpath of an Eclipse project. This container provides a large amount of jar files that make up JBoss AS itself and the Java EE services it offers. Attaching the source code for this is notoriously difficult. Because it concerns a large amount of jar files, attaching source code for each jar is a rather tedious job. For JBoss AS 5, the fact that the location of jars in the source archive was completely different from the structure exposed in Eclipse or the binary build of JBoss AS, made it very hard to actually locate the correct source jar. Sometimes even names were different, making it even harder. For JBoss AS 6, the source archive does not even contain the source for the majority of the JBoss AS artifacts. Source for 'core functionality' (from the point of view of the Java EE developer), like Servlet and JSF is missing. The user has to hunt the Internet to find the correct source for the correct version that JBoss AS 6 uses. This makes an already tedious job even more tedious. I would like to request functionality where the user can point to a single _jboss-src.xyz_ file that contains all sources. JBoss tools should then automatically attach the right source from the archive to the right jar from the library container. Alternatively the user could point to a maven repository (but this should not make the Eclipse project dependent on maven). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

10
30
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

14 years, 1 month

11
42
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

14 years, 1 month

7
12
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

14 years, 1 month

9
26
0 / 0

[JBoss JIRA] (JBDS-1954) license text not aligned in JBDS features

by Max Rydahl Andersen (Created) (JIRA)

license text not aligned in JBDS features ----------------------------------------- Key: JBDS-1954 URL: https://issues.jboss.org/browse/JBDS-1954 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: updatesite Reporter: Max Rydahl Andersen Priority: Minor Fix For: 5.0.0.Beta1 noticed that licensetext are not same for JBDS features. see screenshot from p2 update manager. -- 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

14 years, 1 month

5
8
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-189) modify ws user guide documents

by Feng Qian (JIRA)

modify ws user guide documents ------------------------------ Key: TOOLSDOC-189 URL: https://issues.jboss.org/browse/TOOLSDOC-189 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Feng Qian Assignee: Isaac Rooskov After fix the issue: JBIDE-8490,need to modify the ws docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
14
0 / 0

[JBoss JIRA] (JBIDE-10415) build problems in Beta1

by Nick Boldt (Created) (JIRA)

build problems in Beta1 ----------------------- Key: JBIDE-10415 URL: https://issues.jboss.org/browse/JBIDE-10415 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.0.M5 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 3.3.0.M5 Container issue for build problems w/ M5. Check subtasks for component-specific issues. -- 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

14 years, 1 month

3
5
0 / 0

[JBoss JIRA] (JBDS-1956) get m2eclipse logging under control in JBDS

by Max Rydahl Andersen (Created) (JIRA)

get m2eclipse logging under control in JBDS -------------------------------------------- Key: JBDS-1956 URL: https://issues.jboss.org/browse/JBDS-1956 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: maven Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Critical Fix For: 5.0.0.Beta1 When starting default JBDS installation the console gets *spewed* over with debug info. We should get that under control. What are our options? log to a file ? disable/reduce default log level? missing a plugin to control it or ? something ? -- 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

14 years, 1 month

3
2
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 December 2011