January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBIDE-8137) org.jboss.ide.eclipse.as.core requires jbt.bpel.facet.core facet

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8137?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-8137: --------------------------------- Attachment: screenshot47.png > org.jboss.ide.eclipse.as.core requires jbt.bpel.facet.core facet > ---------------------------------------------------------------- > > Key: JBIDE-8137 > URL: https://issues.jboss.org/browse/JBIDE-8137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS > Affects Versions: 3.2.0.CR1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Attachments: screenshot47.png > > > JBoss AS adapter installed without bpel leads to error message from org.eclipse.wst.common.project.facet.core -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-6368) Should nest categories in update site

by John Verhaeg (JIRA)

Should nest categories in update site ------------------------------------- Key: JBIDE-6368 URL: https://jira.jboss.org/browse/JBIDE-6368 Project: Tools (JBoss Tools) Issue Type: Task Components: updatesite Affects Versions: 3.2.next Reporter: John Verhaeg Assignee: Nick Boldt As discussed somewhat in JBIDE-4859, it seems like we should nest our categories in our update site. So, instead of having lots of sibling categories for the various tools in JBT alongside a sibling "All JBoss Tools" category, the latter should be promoted to a parent category for the others (dropping the "All" prefix). For example: - JBoss Tools - SOA Development - JBoss ESB Tools - Drools Core ... - Data Services - Hibernate - ModeShape - Smooks - Teiid Data Tools Connectivity - Teiid Designer Design-Time - Teiid Designer Runtime BTW, IMO having features in multiple categories blows. I don't like seeing this with other Eclipse projects either. Just my 2 cents. -- 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

15 years, 2 months

5
17
0 / 0

[JBoss JIRA] Created: (JBDS-1481) Create source archive as a composite of sources for jbosstools and jbds update sites

by Denis Golovin (JIRA)

Create source archive as a composite of sources for jbosstools and jbds update sites ------------------------------------------------------------------------------------ Key: JBDS-1481 URL: https://issues.jboss.org/browse/JBDS-1481 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build, P2 Enabled Product Affects Versions: 4.0.0.CR1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.0.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7736) Verify pi4soa jobs

by Nick Boldt (JIRA)

Verify pi4soa jobs ------------------ Key: JBIDE-7736 URL: https://jira.jboss.org/browse/JBIDE-7736 Project: Tools (JBoss Tools) Issue Type: Bug Components: pi4soa Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt Assignee: Max Andersen Priority: Trivial I have two builds for pi4soa right now. One pulls from trunk and builds towards a 3.1 release (JBoss Tools CR1 from trunk): http://hudson.qa.jboss.com/hudson/job/jbosstools-pi4soa-3.1_trunk/configure https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/trunk http://anonsvn.jboss.org/repos/jbosstools/trunk/build The other pulls from a stable branch and builds toward a 3.1 release (JBoss Tools 3.2.0.Beta2 from branch): http://hudson.qa.jboss.com/hudson/job/jbosstools-pi4soa-3.1_stable_branch... https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/branches/pi4soa-3.1.x http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.0.Beta2... My questions: Should there be a pi4soa 3.2 trunk build too, like Teiid has with 7.1/7.2 builds? If so, we need to clarify which branches should be used for JBT Beta2 and CR1 builds. If not, nothing to do. Is trunk toward 3.1 or 3.2? If the former, you're fine. If the latter, you need to update your poms and manifests - I didn't see any that were on version 3.2 (or even 3.1.1). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-1446) Referenced file error after opening JBDS 1.0.0 artifacts in JBDS 4.0.0 Beta2

by Pavol Srna (JIRA)

Referenced file error after opening JBDS 1.0.0 artifacts in JBDS 4.0.0 Beta2 ---------------------------------------------------------------------------- Key: JBDS-1446 URL: https://jira.jboss.org/browse/JBDS-1446 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: seam Affects Versions: 4.0.0.Beta2 Environment: JBDS 1.0.0.GA, JBDS 4.0.0.Beta2 (jbdevstudio-eap-linux-gtk-4.0.0.v201012050623R-H30-Beta2), linux 32bit Reporter: Pavol Srna Attachments: screenshot.png See attached screenshot. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1363) JBDS 4 upon applying updates loses the JBDS Splash

by Rajagopal Ramamoorthy (JIRA)

JBDS 4 upon applying updates loses the JBDS Splash -------------------------------------------------- Key: JBDS-1363 URL: https://jira.jboss.org/browse/JBDS-1363 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: ui/branding Affects Versions: 4.0.0.M2 Environment: RHEL 6 64bit Reporter: Rajagopal Ramamoorthy I am using JBDS 4 early release. Did a check for update and applied all updates. The JBDS red color splash screen has been replaced by Eclipse Helios blue screen which is their default. Should we loose our branding if someone updates JBDS via Eclipse ? -- 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

15 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBDS-1480) Welcom Screen loses all images after update

by Denis Golovin (JIRA)

Welcom Screen loses all images after update ------------------------------------------- Key: JBDS-1480 URL: https://issues.jboss.org/browse/JBDS-1480 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: P2 Enabled Product, Upstream Affects Versions: 4.0.0.CR1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.0.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1249) Remove version number from splash and use the "show version on splash" feature for specifics

by Max Rydahl Andersen (JIRA)

Remove version number from splash and use the "show version on splash" feature for specifics -------------------------------------------------------------------------------------------- Key: JBDS-1249 URL: https://jira.jboss.org/browse/JBDS-1249 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Reporter: Max Rydahl Andersen Fix For: 3.0.2.GA, 4.0.x we keep bumping into JBDS-973 or similar so lets remove the etched in full version from splash. -- 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

15 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBDS-1414) Improve design of JBDS version displayed on Splash Screen for each supported OS

by Vlado Pakan (JIRA)

Improve design of JBDS version displayed on Splash Screen for each supported OS ------------------------------------------------------------------------------- Key: JBDS-1414 URL: https://jira.jboss.org/browse/JBDS-1414 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: ui/branding Affects Versions: 4.0.0.Beta2 Environment: JBDS jbdevstudio-eap-linux-gtk-4.0.0.v201011250001R-H1-Beta2 Reporter: Vlado Pakan Assignee: Max Andersen Version of JBDS displayed on Splash Screen doesn't look so nice on some OS. It needs some design improvement. See attached files. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
23
0 / 0

[JBoss JIRA] Created: (JBDS-1393) Remove JBoss Generic Adapter using packaging instead of xsl transformation plugin

by Denis Golovin (JIRA)

Remove JBoss Generic Adapter using packaging instead of xsl transformation plugin --------------------------------------------------------------------------------- Key: JBDS-1393 URL: https://jira.jboss.org/browse/JBDS-1393 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 4.0.0.Beta1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.0.0.Beta2 -- 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

15 years, 2 months

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