May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11734) Create TP site using an "eclipse-repository", <repositories> and category.xml

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11734: -------------------------------------- Summary: Create TP site using an "eclipse-repository", <repositories> and category.xml Key: JBIDE-11734 URL: https://issues.jboss.org/browse/JBIDE-11734 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: target-platform Reporter: Mickael Istria Assignee: Nick Boldt Fix For: 3.3.0.CR1 Instead of parsing and tweaking a .target file to generate the "requirement" repository, we could make it a normal "eclipse-repository" artifact. We would manage versions in it. Then we know the versions of deps in that site, and we can create target platform using 0.0.0 for versions since we are sure they are resolved against our site. -- 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, 11 months

2
18
0 / 0

[JBoss JIRA] (JBIDE-11729) problem with AS installation since declarative services are not installed automagically

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11729: ------------------------------------------- Summary: problem with AS installation since declarative services are not installed automagically Key: JBIDE-11729 URL: https://issues.jboss.org/browse/JBIDE-11729 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.CR1 need to investigate the root cause of JBIDE-11645 and JBIDE-10803 Is the solution just that central and jaxrs feature depends on the AS feature? But doesn't that limit the general p2 installation/configuration? -- 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, 11 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-10115) Replacing the jaxrs-api.jar by the Orbit JAX-RS API plugin

by Xavier Coulon (Created) (JIRA)

Replacing the jaxrs-api.jar by the Orbit JAX-RS API plugin ---------------------------------------------------------- Key: JBIDE-10115 URL: https://issues.jboss.org/browse/JBIDE-10115 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Webservices Affects Versions: 3.3.0.M3 Reporter: Xavier Coulon Assignee: Xavier Coulon Priority: Minor The Eclipse Orbit repository (http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/r...) contains the JAX-RS API bundled as a plugin, so we could probably remove the jars I've put in the org.jboss.tools.ws.jaxrs projects' /lib folder and just add a dependency on that plugin, which would reduce the SVN size. On the other side, it would add an external dependency that devs should grab to avoid compilation errors, and it may have an impact on the build chain (have to confirm that with Nick Boldt) WDYT ? -- 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, 11 months

7
22
0 / 0

[JBoss JIRA] (JBIDE-10118) new key is added with its full path, it should get added with its name only, if the patch matches the key directory

by Andre Dietisheim (Created) (JIRA)

new key is added with its full path, it should get added with its name only, if the patch matches the key directory ------------------------------------------------------------------------------------------------------------------- Key: JBIDE-10118 URL: https://issues.jboss.org/browse/JBIDE-10118 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- 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, 11 months

5
8
0 / 0

[JBoss JIRA] (JBIDE-11524) Rename jobs, sites, profiles, variables... to clearer names (remove reference to nightly)

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11524: -------------------------------------- Summary: Rename jobs, sites, profiles, variables... to clearer names (remove reference to nightly) Key: JBIDE-11524 URL: https://issues.jboss.org/browse/JBIDE-11524 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Nick Boldt Priority: Minor nightly is a very confusing name, that does not reflect at all what really happens. We should prefer using "staging" in variable, profiles, jobs, url... to make it clearer For instance, * jbosstools-nightly-staging-composite -> jbosstools-staging-composite * jboostools-nightly -> jbosstools-staging-aggregate -- 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, 11 months

3
30
0 / 0

[JBoss JIRA] Created: (JBDS-1863) mirror a copy of SpringIDE 2.7.2 onto download.jboss.org

by Nick Boldt (JIRA)

mirror a copy of SpringIDE 2.7.2 onto download.jboss.org -------------------------------------------------------- Key: JBDS-1863 URL: https://issues.jboss.org/browse/JBDS-1863 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, updatesite Affects Versions: 5.0.0.M4 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.M4 Current versions of SpringIDE included in JBDS are: JBDS 4.x :: SpringIDE 2.5 JBDS 5.0 :: SpringIDE 2.6 The purpose of this mirror is to determine if we'd be better off using 2.7 instead of 2.6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
16
0 / 0

[JBoss JIRA] Created: (JBIDE-8863) Error deploying EAR with a module having a sub-module in its component descriptor.

by Philippe Guinot (JIRA)

Error deploying EAR with a module having a sub-module in its component descriptor. ---------------------------------------------------------------------------------- Key: JBIDE-8863 URL: https://issues.jboss.org/browse/JBIDE-8863 Project: Tools (JBoss Tools) Issue Type: Bug Components: core Affects Versions: 3.2.0.Final Environment: Tested with Eclipse Indigo Release 20110319-2305 with latest nightly build trunk of JBoss Tools. Deploying on a JBoss 4.2 server. Reporter: Philippe Guinot Assignee: Max Rydahl Andersen h3.Context: For some reasons I have to deploy an EAR webapp with (in its libs) a jar containing itself another jar. h3.Environment: For this I have a first Java project with the following component descriptor: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="project1"> <wb-resource deploy-path="/" source-path="/src/main/java"/> </wb-module> </project-modules> {code} Then, the second Java project has the component descriptor: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="project2"> <wb-resource deploy-path="/" source-path="/src/main/java"/> <dependent-module archiveName="project1.jar" deploy-path="/lib" handle="module:/resource/project1/project1"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {code} Then, in Eclipse when exporting the *project2* as a *Module Archive*, I obtain a .jar file featuring both classes from *project2* and a *lib* folder with the project1 compiled jar. Now, in the ear project I have the following lines in the component descriptor: {code:xml} <dependent-module archiveName=" project1.jar" deploy-path="/lib" handle="module:/resource/ project1/ project1"> <dependency-type>uses</dependency-type> </dependent-module> <dependent-module archiveName=" project2.jar" deploy-path="/lib" handle="module:/resource/ project2/ project2"> <dependency-type>uses</dependency-type> </dependent-module> {code} (The EAR needs the 2 jars as well) h3.Problem: Then, when deployed into my *JBoss 4.2 Runtime* server in Eclipse, I got the following error: {code}Error renaming C:\DEV\jboss\server\default\tmp\jbosstoolsTemp\tmp7021855122707247750.jar to C:\DEV\jboss\server\default\deploy\EAR_Project.ear\lib\project2.jar\lib\project1.jar{code} After some research, I think an exception is thrown at *org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil.LocalCopyCallback.moveTempFile(File, File)* during the safe rename. However, when I look to the error message I got the feeling that the publishing process want to copy the tmp jar file into a folder called "*C:\DEV\jboss\server\default\deploy\EAR_Project.ear\lib\project2.jar\lib\*" which can not work because "*C:\DEV\jboss\server\default\deploy\EAR_Project.ear\lib\project2.jar*" is a file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

8
30
0 / 0

[JBoss JIRA] (JBIDE-11912) Improve SSH key management

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-11912: ---------------------------------------- Summary: Improve SSH key management Key: JBIDE-11912 URL: https://issues.jboss.org/browse/JBIDE-11912 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.x Initially OpenShift was only able to handle a single unique SSH (rsa) key. A user also had to provide his key when creating the domain. Things evolved a lot since then. The current OpenShift release supports - multiple keys - rsa and dsa keys - keys are not required when creating a domain Our tooling still offers what we implemented when OpenShift required one to provide his single key when creating the domain. We require the user to create/provide his key when he wants to create his domain. !create-domain.png! Furthermore we also force the key-name to libra_id_rsa. We did that to avoid conflicts with the config (<home>/.ssh/config) that the rhc CLI tools create. -- 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, 11 months

4
21
0 / 0

[JBoss JIRA] (JBIDE-12049) Disable program arguments change in launch config unless you uncheck Always update arguments

by Martin Malina (JIRA)

Martin Malina created JBIDE-12049: ------------------------------------- Summary: Disable program arguments change in launch config unless you uncheck Always update arguments Key: JBIDE-12049 URL: https://issues.jboss.org/browse/JBIDE-12049 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.1 Similarly to how the launch configuration works for remote servers, the Program arguments for a local server should be greyed and disabled unless you uncheck "Always update arguments...". Currently, if the checkbox is checked, the changes you make in the text field are not reflected anyway - the arguments are calculated at each launch of the server. -- 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, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6116) Would be very nice if JBoss Tools would download and install JBoss AS into a local directory so that manual configuration can be avoided.

by Lincoln Baxter III (JIRA)

Would be very nice if JBoss Tools would download and install JBoss AS into a local directory so that manual configuration can be avoided. ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6116 URL: https://jira.jboss.org/jira/browse/JBIDE-6116 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.1.0.GA Reporter: Lincoln Baxter III When using the GlassFish eclipse plug-in, if the Server Runtime is not currently installed or configured, the plug-in will give you a chance to configure the Runtime, or click a button/link to have the plugin go out to the internet, download, and configure the application server for you. I think it would be great for new users/usability if JBoss Tools could provide a similar convenience. The latest plugin-compatible version of the AS should probably be the target of the download. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

6
19
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