January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10434) OpenShift description in N&N

by Andre Dietisheim (Created) (JIRA)

OpenShift description in N&N ---------------------------- Key: JBIDE-10434 URL: https://issues.jboss.org/browse/JBIDE-10434 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M5 -- 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, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9591) Openshift Express: create RHC alike tooling that is able to create domain/app etc.

by Andre Dietisheim (JIRA)

Openshift Express: create RHC alike tooling that is able to create domain/app etc. ---------------------------------------------------------------------------------- Key: JBIDE-9591 URL: https://issues.jboss.org/browse/JBIDE-9591 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 When you want to deploy an app to openshift, you currently have to use the rhc command line executables. Since we want to be able to deploy to openshift without leaving eclipse we have to provide this in eclipse. This will furhtermore also ease usage on windows a lot since the rhc-tooling is only usable by installing cygwin. Openshift is offering a simplistic REST interface that offers those operations (create domain, create app, get user info etc.). We'll implement our own REST client to offer these functionalities to our users: https://github.com/openshift/os-client-tools/blob/master/express/doc/API http://docs.redhat.com/docs/en-US/OpenShift_Express/1.0/pdf/API_Guide/Ope... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
18
0 / 0

[JBoss JIRA] (JBIDE-10011) N&N for OpenShift

by Andre Dietisheim (Created) (JIRA)

N&N for OpenShift ----------------- Key: JBIDE-10011 URL: https://issues.jboss.org/browse/JBIDE-10011 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 project = "Tools (JBoss Tools)" AND component = "openshift" AND fixVersion = 3.3.0.M4" -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBDS-1839) JAX-RS maven integration plugin is missing in extra site

by Libor Zoubek (JIRA)

JAX-RS maven integration plugin is missing in extra site -------------------------------------------------------- Key: JBDS-1839 URL: https://issues.jboss.org/browse/JBDS-1839 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification, maven Affects Versions: 5.0.0.M3 Reporter: Libor Zoubek Fix For: 5.0.0.M4 I was verifying JBIDE-9290 on JBDS with m2e. JAX-RS configurator is missing there. It will definitely make sence to include this plugin when jax-rs tooling becomes part of JBDS. But it might make sense to include it before. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

7
12
0 / 0

[JBoss JIRA] (JBIDE-10243) Improve cheatsheets

by Snjezana Peco (Created) (JIRA)

Improve cheatsheets ------------------- Key: JBIDE-10243 URL: https://issues.jboss.org/browse/JBIDE-10243 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.3.0.M4 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M5 If a created project contains the cheatsheet.xml file, the Project Example engine should run the cheat sheet using that file. If a created project contains readme.html, the Project Example engine should open it in a browser. -- 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, 9 months

5
7
0 / 0

[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

13 years, 9 months

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

13 years, 10 months

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

13 years, 10 months

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

13 years, 10 months

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

13 years, 10 months

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