May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5135) Support Resources Localization and Versioning in JSF 2

by Denis Golovin (JIRA)

Support Resources Localization and Versioning in JSF 2 ------------------------------------------------------ Key: JBIDE-5135 URL: https://jira.jboss.org/jira/browse/JBIDE-5135 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.1.0.M4 Reporter: Denis Golovin See JSF 2 Spec "2.6.1.4 Libraries of Localized and Versioned Resources" -- 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
17
0 / 0

[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] 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, 6 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, 6 months

3
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, 6 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, 6 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-8963) There is no possibility to drag-and-drop into the page with empty <body>

by Vitali Yemialyanchyk (JIRA)

There is no possibility to drag-and-drop into the page with empty <body> ------------------------------------------------------------------------ Key: JBIDE-8963 URL: https://issues.jboss.org/browse/JBIDE-8963 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.1.M1 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich Priority: Blocker here is example: === <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Template Page title</title> <link href="styles/some-style.css" media="screen" type="text/css" rel="stylesheet" /> </head> <body> </body> </html> === - there is no possibility to drag-and-drop <div> into the <body> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8866) Move all plugins up to baseline

by Rob Stryker (JIRA)

Move all plugins up to baseline ------------------------------- Key: JBIDE-8866 URL: https://issues.jboss.org/browse/JBIDE-8866 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.3.0.M2 Reporter: Rob Stryker Assignee: Nick Boldt Fix For: 3.3.0.M2 Not really sure who to assign this to, short of making three dozen separate jira issues ;) I have 33 patches, one for each module, which modify all manifest.mf version numbers (in plugins, not in tests) to be brought up to our current baseline. So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a dependency on this.specific.runtime into this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads this.specific.plugin;bundle-version="3.5.0", it will move it up to this.specific.runtime;bundle-version="3.6.200". Etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7472) ZipException occurs if I remove any JAR from WEB-INF/lib when the target server is running.

by Alexey Kazakov (JIRA)

ZipException occurs if I remove any JAR from WEB-INF/lib when the target server is running. ------------------------------------------------------------------------------------------- Key: JBIDE-7472 URL: https://jira.jboss.org/browse/JBIDE-7472 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Rob Stryker Fix For: 3.2.0.Beta2 1. Create JSF2 project (I guess it can be any dynamic web project) 2. Deploy it to AS6.M5 (haven't try on other servers) 3. Start the server 4. Remove any JAR from WEB-INF/lib folder 5. I get a lot of IOExceptions and the project is not built anymore 6. Stopping server/re-building project doesn't help. In debugger I see that all the threads which try to open any JAR in class path (at least from AS/common/lib folder) fail with ZipException 7. Only restarting Eclipse can help. Here are the exceptions (a lot of them): org.eclipse.core.runtime.CoreException: I/O exception at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2524) at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getJar(JarPackageFragmentRoot.java:152) at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.computeChildren(JarPackageFragmentRoot.java:78) at org.eclipse.jdt.internal.core.JavaProjectElementInfo.initializePackageNames(JavaProjectElementInfo.java:252) at org.eclipse.jdt.internal.core.JavaProjectElementInfo.getProjectCache(JavaProjectElementInfo.java:225) at org.eclipse.jdt.internal.core.JavaProjectElementInfo.newNameLookup(JavaProjectElementInfo.java:290) at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2282) at org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:57) at org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:64) at org.eclipse.jdt.internal.core.CancelableNameEnvironment.<init>(CancelableNameEnvironment.java:26) at org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:162) at org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:255) at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.makeConsistent(ReconcileWorkingCopyOperation.java:190) at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:89) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1244) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178) at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114) at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:133) at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105) at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:398) at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173) Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:114) at java.util.zip.ZipFile.<init>(ZipFile.java:131) at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2518) ... 27 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

7
18
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 2011