April 2012 - jbosstools-issues - Jboss List Archives

[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-11324) Features are missing Description

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-11324: ----------------------------------- Summary: Features are missing Description Key: JBIDE-11324 URL: https://issues.jboss.org/browse/JBIDE-11324 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.Beta1 Reporter: Vlado Pakan Fix For: 3.3.0.Beta2 Features with Description containing only feature name: JBoss ESB Tools JBoss BPEL Editor JBoss Maven CDI Configurator JBoss Maven Hibernate Configurator JBoss Maven JPA Configurator JBoss Maven Project Examples JBoss Runtime Drools Detector JBoss Runtime ESB Detector JBoss Runtime ESB Detector The JBoss Tools for Savara. JBoss Tools Common JBoss Tools Common Text editing extensions JBoss Tools Common UI JBoss Tools Usage Reporting JBoss Tools Verification Smooks Tools Feature JBoss Tools RichFaces has poor description "Visual editing" -- 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
12
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] (JBIDE-11495) Improve ability to configure dependent hudson jobs and provide accessable documentation

by Barry LaFond (JIRA)

Barry LaFond created JBIDE-11495: ------------------------------------ Summary: Improve ability to configure dependent hudson jobs and provide accessable documentation Key: JBIDE-11495 URL: https://issues.jboss.org/browse/JBIDE-11495 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Barry LaFond SOA decoupling has elevated the need to have more configurable control over upstream and downstream dependencies. Notes from Nick: * a number of jobs are now set to build only when triggered by upstream, but SOA stuff is not as well handled * ideally you'd want: a) check svn every N hours (usually 6) and b) upstream should use Parameterized Trigger to cause downstream to fire * you can also ensure that you're building against a stable aggregate using an override like the one I've set up for SOA Tooling aggregate... * in your maven invocation, under Properties, you can do this: # use latest upstream nightly Core update site instead of "wild components" in the composite staging site jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools... * that way you pull from the aggregate (updates weekly) instead of the composite (updates every time a component respins) * means if you depended on something like tests/common/jst/vpe/jsf/seam/maven/central/usage stack, you wouldn't need to worry about getting incompatible pieces -- 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] (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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2012