April 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11236) gwt-kitchensink not working when deployed from within JBT

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-11236: ---------------------------------- Summary: gwt-kitchensink not working when deployed from within JBT Key: JBIDE-11236 URL: https://issues.jboss.org/browse/JBIDE-11236 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.3.0.Beta1 Environment: JBT 3.3.0.Beta1e on eclipseEE indigo SR2 Fedora 16 Oracle java 1.7.0_02-b13 64b Reporter: Radim Hopp Assignee: Snjezana Peco Fix For: 3.3.0.Beta1 Attachments: gwt-kitchensink.png GWT Web Project is not working, when deployed from within JBDS or JBT (using steps described in README.md). When deployed, only header, footed and the right "Find out more" panel is shown. When deployed from command line using `mvn package` -> `mvn jboss-as:deploy` everything is working as expected. -- 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, 11 months

6
15
0 / 0

[JBoss JIRA] (JBIDE-11327) Wrong feature copyright information

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-11327: ----------------------------------- Summary: Wrong feature copyright information Key: JBIDE-11327 URL: https://issues.jboss.org/browse/JBIDE-11327 Project: Tools (JBoss Tools) Issue Type: Bug Components: Legal Affects Versions: 3.3.0.Beta1 Environment: JBT 3.3.0.v20120308-1736-H123-Beta1 Reporter: Vlado Pakan Assignee: Max Rydahl Andersen Fix For: 3.3.0.Beta2 These features doesn't have year 2012 in copyright info: org.jboss.tools.maven.jaxrs.feature org.jboss.tools.maven.jbosspackaging.feature org.jboss.tools.maven.profiles.feature org.jboss.tools.modeshape.rest.feature This feature doesn't have any copyright info: org.jboss.tools.openshift.express.feature -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-11692) build problems in Beta1-SOA

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11692: ---------------------------------- Summary: build problems in Beta1-SOA Key: JBIDE-11692 URL: https://issues.jboss.org/browse/JBIDE-11692 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, SOA Tooling, updatesite Affects Versions: 3.3.0.Beta1-SOA Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 3.3.0.Beta1-SOA Tracker issue for all the problems getting JBT SOA 3.3.0.Beta1 and JBDS SOA 5.0.0.Beta1 out the door. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] (JBDS-2098) Can we provide the jira/bugzilla defaults in JBDS

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-2098: ----------------------------------------- Summary: Can we provide the jira/bugzilla defaults in JBDS Key: JBDS-2098 URL: https://issues.jboss.org/browse/JBDS-2098 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Max Rydahl Andersen related to JBIDE-9351 -- 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, 11 months

2
16
0 / 0

[JBoss JIRA] (JBIDE-11694) Teiid 7.7.x uses wrong version of upstream parent pom

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11694: ---------------------------------- Summary: Teiid 7.7.x uses wrong version of upstream parent pom Key: JBIDE-11694 URL: https://issues.jboss.org/browse/JBIDE-11694 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng, SOA Tooling, teiid Affects Versions: 3.3.0.Beta1-SOA Reporter: Nick Boldt Assignee: Barry LaFond Fix For: 3.3.0.Beta1-SOA [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.jboss.tools:teiid:0.0.3-SNAPSHOT (/mnt/hudson_workspace/workspace/soatools-3.3.0.Beta1--teiid-designer/sources/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.jboss.tools:org.jboss.tools.parent.pom:pom:0.0.3-SNAPSHOT in jboss-developer-repository-group (https://repository.jboss.org/nexus/content/groups/developer/) and 'parent.relativePath' points at wrong local POM @ line 5, column 10 -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Build step 'Invoke top-level Maven targets' marked build as failure https://hudson.qa.jboss.com/hudson/view/SOA-Team/view/SOATools-3.3.0.Beta... -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-11693) deprecate old jbosstools-3.3_stable_branch component jobs for SOA components

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11693: ---------------------------------- Summary: deprecate old jbosstools-3.3_stable_branch component jobs for SOA components Key: JBIDE-11693 URL: https://issues.jboss.org/browse/JBIDE-11693 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng, SOA Tooling Affects Versions: 3.3.0.Beta1-SOA Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 3.3.0.Beta1-SOA Since these are now deprecated, identify them as such and ensure that the new jobs are properly enabled and linked to upstream/downstream jobs. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11700) Please add m2e-apt from [build #7] to JBT Composite Reqs Mirror (Indigo Extras Site) and to JBDS Extras site

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-11700: ----------------------------------- Summary: Please add m2e-apt from [build #7] to JBT Composite Reqs Mirror (Indigo Extras Site) and to JBDS Extras site Key: JBIDE-11700 URL: https://issues.jboss.org/browse/JBIDE-11700 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng Affects Versions: 3.3.0.Beta3 Reporter: Fred Bricon Assignee: Nick Boldt Fix For: 3.3.0.Beta3 m2e-apt needs to be a first class citizen of JBT / JBDS For JBT : needs to be available from the sowftare install tab in JBoss Central For JBDS : needs to be included in the installer {quote} rather it goes into Indigo core reqs site, product build, and installer http://download.jboss.org/jbosstools/updates/indigo/SR2/ and http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... {quote} Waiting for the jenkins build #7 (triggered in release mode) to finish : https://hudson.qa.jboss.com/hudson/view/DevStudio/view/m2eclipse-wtp/job/... -- 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, 11 months

2
29
0 / 0

[JBoss JIRA] (JBIDE-11299) Central should install Project Examples otherwise the Project Examples area on Getting Started tab says "No Entries Found" instead of showing JBoss Quickstarts

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11299: ---------------------------------- Summary: Central should install Project Examples otherwise the Project Examples area on Getting Started tab says "No Entries Found" instead of showing JBoss Quickstarts Key: JBIDE-11299 URL: https://issues.jboss.org/browse/JBIDE-11299 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta2 Attachments: eclipse372platform+JBTAbridged=ProjectExamplesFound.png, IndigoSR1-JEE+Central+all-of-central=noProjectExamplesFound.png Steps to repro: 1. unpack eclipse-platform-3.7.2-linux-gtk-x86_64.tar.gz 2. install JBoss Tools 3.3.0.Beta1 (whole Abridged category) from http://download.jboss.org/jbosstools/updates/development/indigo/ 3. restart when prompted, and look at Central: !eclipse372platform+JBTAbridged=ProjectExamplesFound! Now, try again but only install Central (to save time, use JEE bundle): 1. unpack eclipse-jee-indigo-SR1-linux-gtk-x86_64.tar.gz 2. install JBoss Central 3.3.0.Beta1 (whole Abridged category) from http://download.jboss.org/jbosstools/updates/development/indigo/ 3. restart when prompted, and look at Central: !IndigoSR1-JEE+Central+all-of-central=noProjectExamplesFound! ---- When installing org.jboss.tools.central.feature_1.0.0.v20120307-1926-H67-Beta1, the following features should also be included: org.jboss.tools.project.examples.feature_1.2.1.v20120305-1726-H75-Beta1 org.jboss.tools.community.project.examples.feature_1.2.1.v20120305-1726-H75-Beta1 ...? What feature provides the quickstarts? -- 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, 11 months

4
50
0 / 0

[JBoss JIRA] (JBDS-2087) move all features from com.jboss.jbds.all (generated top-level product feature) to com.jboss.jbds.product.feature so that all of JBDS can be installed into Eclipse via a single feature

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2087: -------------------------------- Summary: move all features from com.jboss.jbds.all (generated top-level product feature) to com.jboss.jbds.product.feature so that all of JBDS can be installed into Eclipse via a single feature Key: JBDS-2087 URL: https://issues.jboss.org/browse/JBDS-2087 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Build, installer, updatesite, Upstream Affects Versions: 5.0.0.Beta3 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 5.0.0.Beta3 A few milestones ago, I moved much of the content of com.jboss.jbds.product.feature into com.jboss.jbds.all to expose it more obviously when a user looks into Help > About > Installation details in JBDS. However, this means that the single point of entry to installing all of JBDS is now com.jboss.jbds.all, which, because it's a PRODUCT, can't be installed into something like Eclipse JEE Indigo SR2. Solution is to move all the contents of com.jboss.jbds.all into its child feature, com.jboss.jbds.product.feature, and have the .all include ONLY the single .product.feature. Any objections to this plan? Denis? Mickael? Max? -- 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, 11 months

2
13
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-189) modify ws user guide documents

by Feng Qian (JIRA)

modify ws user guide documents ------------------------------ Key: TOOLSDOC-189 URL: https://issues.jboss.org/browse/TOOLSDOC-189 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Feng Qian Assignee: Isaac Rooskov After fix the issue: JBIDE-8490,need to modify the ws docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
14
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