May 2012 - jbosstools-issues - Jboss List Archives

[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, 10 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, 10 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, 10 months

2
13
0 / 0

[JBoss JIRA] (JBIDE-11840) Connectors are not available: SOA-P Tooling

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-11840: ---------------------------------- Summary: Connectors are not available: SOA-P Tooling Key: JBIDE-11840 URL: https://issues.jboss.org/browse/JBIDE-11840 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, SOA Tooling Affects Versions: 3.3.0.Beta3 Reporter: Pavol Srna Assignee: Snjezana Peco Fix For: 3.3.0.Beta3 Attachments: Screenshot-2.png I tried to install SOA-P Tooling using the JBoss Central and after I clicked on install button the following dialog appeared (see screenshot attached). Why is it saying that the SOA-P Tooling connectors are not available? However I could complete the install. -- 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
9
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, 10 months

4
14
0 / 0

[JBoss JIRA] (JBDS-2134) Extras site contains JBDS feature

by Vlado Pakan (JIRA)

Vlado Pakan created JBDS-2134: --------------------------------- Summary: Extras site contains JBDS feature Key: JBDS-2134 URL: https://issues.jboss.org/browse/JBDS-2134 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: updatesite Affects Versions: 5.0.0.Beta3 Environment: http://devstudio.jboss.com/updates/5.0/staging/extras/ Reporter: Vlado Pakan Fix For: 5.0.0.CR1 Attachments: installdialog.png Update site http://devstudio.jboss.com/updates/5.0/staging/extras/ contains also JBDS feature. !installdialog.png! -- 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
16
0 / 0

[JBoss JIRA] (JBDS-2116) jbds product build failing: Package uses conflict: Import-Package: org.mortbay.jetty; version="[6.1.0,7.0.0)"

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2116: -------------------------------- Summary: jbds product build failing: Package uses conflict: Import-Package: org.mortbay.jetty; version="[6.1.0,7.0.0)" Key: JBDS-2116 URL: https://issues.jboss.org/browse/JBDS-2116 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.Beta3 Reporter: Nick Boldt Assignee: Denis Golovin Priority: Blocker Fix For: 5.0.0.Beta3 {code} /mnt/hudson_workspace/workspace/devstudio-5.0_trunk.product/jbds-build/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.6.1.R36x_v20100823/scripts/genericTargets.xml:107: Processing inclusion from feature org.eclipse.help: Bundle org.eclipse.equinox.http.jetty_2.0.100.v20110502 failed to resolve.: Package uses conflict: Import-Package: org.mortbay.jetty; version="[6.1.0,7.0.0)" {code} https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.product/1260/c... -- 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

1
2
0 / 0

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

by Nick Boldt (Created) (JIRA)

build problems in Beta1 ----------------------- Key: JBIDE-10415 URL: https://issues.jboss.org/browse/JBIDE-10415 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.0.M5 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 3.3.0.M5 Container issue for build problems w/ M5. Check subtasks for component-specific issues. -- 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
5
0 / 0

[JBoss JIRA] (JBDS-1956) get m2eclipse logging under control in JBDS

by Max Rydahl Andersen (Created) (JIRA)

get m2eclipse logging under control in JBDS -------------------------------------------- Key: JBDS-1956 URL: https://issues.jboss.org/browse/JBDS-1956 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: maven Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Critical Fix For: 5.0.0.Beta1 When starting default JBDS installation the console gets *spewed* over with debug info. We should get that under control. What are our options? log to a file ? disable/reduce default log level? missing a plugin to control it or ? something ? -- 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] (JBIDE-11170) Forge: resource is not picked-up after creation on windows

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-11170: ---------------------------------- Summary: Forge: resource is not picked-up after creation on windows Key: JBIDE-11170 URL: https://issues.jboss.org/browse/JBIDE-11170 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 3.3.0.Beta1 Environment: jbdevstudio-product-universal-5.0.0.v201203010100M-H88-Beta1, winXP Reporter: Pavol Srna Assignee: Koen Aers Priority: Critical Fix For: 3.3.0.Beta1 Path, or quotation marks issues? Forge console output: [test] test $ entity --named customer ? In which package you'd like to create this @Entity, or enter for default [com.test.model] Created @Entity [com.test.model.customer] ***INFO*** The command [pick-up] takes [1] unnamed argument(s), but found [2]. ***INFO*** Swallowed unknown token [and] for command [pick-up]. ***INFO*** Swallowed unknown token [Settings/Pali/workspace/test/src/main/java/com/test/model/customer.java] for command [pick-up]. Picked up type <UnknownFileResource>: Documents Wrote C:\/Documents and Settings/Pali/workspace/test/src/main/java/com/test/model/customer.java -- 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
6
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 2012