February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10201) associate sites not being loaded correctly into JBT SOA site; duplicate references node in content.xml

by Nick Boldt (Created) (JIRA)

associate sites not being loaded correctly into JBT SOA site; duplicate references node in content.xml ------------------------------------------------------------------------------------------------------ Key: JBIDE-10201 URL: https://issues.jboss.org/browse/JBIDE-10201 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.0.M5 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M5 1. Start Eclipse 3.7.1 JEE bundle. 2. Add this site: http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/ 3. Search for updates {code} !MESSAGE Error in file:/home/nboldt/eclipse/37clean/eclipse/p2/org.eclipse.equinox.p2.repository/cache/content1375829237.jar at line 11628, column 24: Duplicate singleton element in element "repository": <references size="4"> {code} 4. If you then check for the list of available update sites, you'll see that the ones listed in the SOA site's associate site list are not shown. So, two problems: a) content.xml contains TWO <references> sections b) second section of references is not loaded when the site is read -- 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, 10 months

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4442) Improve branding/skinning of What's New / N&N pages

by Nick Boldt (JIRA)

Improve branding/skinning of What's New / N&N pages --------------------------------------------------- Key: JBIDE-4442 URL: https://jira.jboss.org/jira/browse/JBIDE-4442 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Nick Boldt Assignee: Max Rydahl Andersen The N&N pages (http://docs.jboss.org/tools/whatsnew/)are very plain. At the very least, we could introduce some colour (as used on www.jboss.org/tools/ or http://download.jboss.org/jbosstools/updates/nightly/trunk/ ?) and perhaps use this banner: http://www.jboss.org/theme/images/banners/tools-banner.png Beyond that, we ought to have persistent navigation for downloads, update sites, browsing/reporting JIRAs, movies, docs, etc. so people can more easily find other useful resources. I'd be happy to take a crack at editing these pages if you let me know where they live in SVN. Are they generated by template? Seam? XSLT? -- 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, 10 months

6
19
0 / 0

[JBoss JIRA] (JBIDE-11096) setup test runs that use p2director to verify update site install

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11096: ------------------------------------------- Summary: setup test runs that use p2director to verify update site install Key: JBIDE-11096 URL: https://issues.jboss.org/browse/JBIDE-11096 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Reporter: Max Rydahl Andersen Assignee: Nick Boldt Fix For: 3.3.0.CR1 idea is to have a separate hudson job that runs p2director for each top level feature/category. Generate junit.xml which has a failure/success for each main feature + "all", especially "abridged" Should test source features too. But first one would be "everything" -- 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, 10 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-9980) build problems in M4

by Nick Boldt (Created) (JIRA)

build problems in M4 -------------------- Key: JBIDE-9980 URL: https://issues.jboss.org/browse/JBIDE-9980 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M4 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M4 track problems building M4. see subtasks. -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBDS-1594) Detail what 3rd party projects should be included in JBDS 5.x

by Nick Boldt (JIRA)

Detail what 3rd party projects should be included in JBDS 5.x ------------------------------------------------------------- Key: JBDS-1594 URL: https://issues.jboss.org/browse/JBDS-1594 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Reporter: Nick Boldt Assignee: Burr Sutter JBDS 4.0.0 contains: * SpringIDE 2.5.1.201011101000-RELEASE * TestNG 5.14.6.20110119_1050 (Hosted here: http://reports.qa.atl.jboss.com/binaries/RHDS/requirements/helios/) ---- What should the next two releases contain? JBDS 4.x should contain: * SpringIDE 2.5.1.201011101000-RELEASE * TestNG 5.14.6.20110119_1050 * ...? JBDS 5.x should contain: * SpringIDE 2.6? * TestNG 5.? * ...? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
24
0 / 0

[JBoss JIRA] (JBIDE-9926) Importing some of the BPEL Examples results in log error

by Pavol Srna (Created) (JIRA)

Importing some of the BPEL Examples results in log error -------------------------------------------------------- Key: JBIDE-9926 URL: https://issues.jboss.org/browse/JBIDE-9926 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Affects Versions: 3.2.2.M2 Reporter: Pavol Srna Assignee: Robert (Bob) Brodt Fix For: 3.2.2.Final Try to import ODE BPEL Example and see error log. -- 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, 10 months

7
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8054) Text selection in VPE source pane is not synchronized with selection in Visual Pane

by Vlado Pakan (JIRA)

Text selection in VPE source pane is not synchronized with selection in Visual Pane ----------------------------------------------------------------------------------- Key: JBIDE-8054 URL: https://issues.jboss.org/browse/JBIDE-8054 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.CR1 Environment: Linux 32bit JBDS 4.0.0.v201012161657N-H584-CR1 Reporter: Vlado Pakan Assignee: Maxim Areshkau Attachments: selectionError.swf Steps to reproduce: 1. Open any jsp page in VPE editor and select some text in VPE source pane. The same text is selected in visual pane. 2. Make mouse left click somewhere in visual pane. There should be no selected text. 3. Select the same text in step 1. via source pane 4. No text is selected in visual pane but the same text selected in source pane has to be selected in visual pane. After reopening jsp page it's working again as mentioned above. Selection is synchronized only first time. See attached screencast. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] (JBDS-1992) Migrate "JBDS Build Results" Web site ant build script to maven

by Denis Golovin (JIRA)

Denis Golovin created JBDS-1992: ----------------------------------- Summary: Migrate "JBDS Build Results" Web site ant build script to maven Key: JBDS-1992 URL: https://issues.jboss.org/browse/JBDS-1992 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Build Affects Versions: 5.0.0.Beta1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 5.0.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, 10 months

3
20
0 / 0

[JBoss JIRA] (JBDS-1990) Build JBDS product w/ Tycho?

by Nick Boldt (JIRA)

Nick Boldt created JBDS-1990: -------------------------------- Summary: Build JBDS product w/ Tycho? Key: JBDS-1990 URL: https://issues.jboss.org/browse/JBDS-1990 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build, P2 Enabled Product Affects Versions: 5.0.0.Beta1 Reporter: Nick Boldt Assignee: Denis Golovin Fix For: 5.0.0.Beta1 I've managed to get Tycho to build the p2 product using a new pom file [1] (which first regenerates the update site locally THEN builds the products for 4 or the 6 supported platforms (suspect I have to just add more platforms to the parent pom to get win64 and carbon64 in there) and a couple minor tweaks to product/features/com.jboss.jbds/pom.xml file. However, while building, I get some errors: {code} java.io.FileNotFoundException: /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/features/com.jboss.jbds/target/products/com.jboss.jbds.all/macosx/JBDevStudio.icns (No such file or directory) Error - 7 icon(s) not replaced in /tmp/p2.brandingIron9043279577960813921/launcher.exe using /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/features/com.jboss.jbds/target/products/com.jboss.jbds.all/jbds.ico {code} And, the resulting product can't launch (I only tried the lin64 one): {code} !ENTRY org.eclipse.osgi 4 0 2012-01-11 13:46:58.598 !MESSAGE Application error !STACK 1 java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini). at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code} Any idea what's wrong here? -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-10495) Define how BPEL users handle JBoss BPEL migration

by Max Rydahl Andersen (Created) (JIRA)

Define how BPEL users handle JBoss BPEL migration ------------------------------------------------- Key: JBIDE-10495 URL: https://issues.jboss.org/browse/JBIDE-10495 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Reporter: Max Rydahl Andersen Assignee: Robert (Bob) Brodt Priority: Blocker Fix For: 3.3.0.Beta1 JBDS-1909 is talking about keeping the old way of creating JBoss Legacy BPEL projects without outlining how migration works and which packaging approach is used. I want to be aligned on what this migration means: It seems we will have: 2 different facets old jboss and new bpel 2 different packaging - one using WTP style packaging that is compatible with JBoss AS adapters (old jboss) and one using non-WTP style packing which is not compatible with anything but specific tomcat server adapter (new jboss) 2 different wizards for creating projects And could we please not keep old packaging styles around if we could just migrate them over one way or the other. And please let us not make *another* deployment/packaging approach. I hope i'm wrong in the above observations so please let us once and for all document what the migration plan is and what reality we have ;) -- 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, 10 months

6
9
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 February 2012