January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9003) Background image path not calculated when using image dialog from css property view

by Maxim Areshkau (JIRA)

Background image path not calculated when using image dialog from css property view ----------------------------------------------------------------------------------- Key: JBIDE-9003 URL: https://issues.jboss.org/browse/JBIDE-9003 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.3.0.M1 Reporter: Maxim Areshkau Assignee: Denis Golovin Fix For: 3.3.0.M2 Attachments: relative-path-fix.diff #1 Open html file with div element #2 Open CSS Properties VIew #3 Select div on html file #4 Try to set background image using CSS Properties View->Background Tab->Background Image, When you select image, path calculated incorrectly. Used absolute path, but should be relative. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-8840) Support EL susbstitution for collections

by Denis Golovin (JIRA)

Support EL susbstitution for collections ---------------------------------------- Key: JBIDE-8840 URL: https://issues.jboss.org/browse/JBIDE-8840 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common Affects Versions: 3.3.0.M1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.3.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] (JBIDE-10197) Deployment assembly missbehaves - workaround with fileset

by Dirk Dollar (Created) (JIRA)

Deployment assembly missbehaves - workaround with fileset --------------------------------------------------------- Key: JBIDE-10197 URL: https://issues.jboss.org/browse/JBIDE-10197 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.2.0.Final Environment: Eclipse helios 3.6.2 Reporter: Dirk Dollar Assignee: Rob Stryker Priority: Minor This is my first bugreport... if I'm doing something wrong or chose the wrong component (something) - please be forgiving :-) so I had a couple days to figure this one out - the deployment assembly is misbehaving similarly (but differnt) to older versions when it was used under a different name (J2EE module dependencies i think). So when I add a folder e.g. WebContent and want it to deploy to / it will not work or more accurately - under certain circumstances it will stop working. E.g. I think after adding some additional libraries to deploy to webcontent/lib. I suspect the problem is that it gets deleted before deploying. The workaround for me was to use a fileset of the <projectname>/WebContent folder and to point it to an empty deploy path - and to scream in rage at everyone who dared to touch any settings in there. -- 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, 5 months

10
23
0 / 0

[JBoss JIRA] Created: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs

by Nick Boldt (JIRA)

improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs ----------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8667 URL: https://issues.jboss.org/browse/JBIDE-8667 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Nick Boldt (2011-04-01 10:11:04) nickboldt: and while I'd love to do: (2011-04-01 10:11:12) nickboldt: mkdir whatever-new (2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new (2011-04-01 10:11:25) nickboldt: rm -fr whatever (2011-04-01 10:11:29) nickboldt: mv whatever-new whatever (2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and "it's there and updated" is less (2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have (2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the same folder on top (2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of whack w.r.t the site content (2011-04-01 10:12:17) maxandersen: hmmm (2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then rename" instead of "push into existing and clean out cruft" (2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm all ears (2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply connect over ssh and run a script directly (2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete the existing one.. (2011-04-01 10:14:10) maxandersen: sftp rm should work? (2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete (2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont need to rename anything (2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know "locally" (2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in the composite*.xml files (2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site (2011-04-01 10:15:17) nickboldt: and then delete the old one 1. generate composite metadata files on the fly 2. publish that into root dir, all/repo/ 3. purge previous build's folder over scripted sftp? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

7
44
0 / 0

[JBoss JIRA] Created: (JBIDE-4810) Create JUnit Test Suite for every component in repository

by Denis Golovin (JIRA)

Create JUnit Test Suite for every component in repository --------------------------------------------------------- Key: JBIDE-4810 URL: https://jira.jboss.org/jira/browse/JBIDE-4810 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Denis Golovin Assignee: Denis Golovin -- 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, 5 months

3
16
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, 5 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, 5 months

5
8
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, 5 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, 5 months

8
30
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, 5 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 January 2012