May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14653) Feature and plugins info is incorrect for Aerogear plugins

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14653?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-14653: --------------------------------- Labels: respin-b (was: ) > Feature and plugins info is incorrect for Aerogear plugins > ---------------------------------------------------------- > > Key: JBIDE-14653 > URL: https://issues.jboss.org/browse/JBIDE-14653 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.0.Beta1 > Environment: JBT 4.1.0.Beta1-v20130526-0812-B258 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Priority: Critical > Labels: respin-b > Fix For: 4.1.0.Beta1 > > Attachments: aerogearfeature.png, aerogearplugins.png > > > 1. Open Help > About Eclipse > Installation Details > 2. Select Installed Software tab > 3. Select either org.jboss.tools.aerogear.hybrid.feature.feature.group or org.jboss.tools.aerogear.hybrid.feature.source.feature.group > ERROR: Feature description should contain "based mobile" instead "basedmobile" > !aerogearfeature.png! > 4. Select Plug-ins tab > 5. Type aerogear ni filter > ERROR: Aerogear plugins has neither provider or Plug-in name. Version of org.jboss.tools.aerogear.hybrid.cordova is 2.7.0 all the others plug-ins has version 1.0.0.Beta1... I don't know if this is correct > !aerogearplugins.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14555) Wrong warning "Could not initialize class my.pkg.ArchiveBuilder" by Arquillian

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14555?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14555: --------------------------------------- Aggressively logging messages is fixed within JBIDE-14523. I will check the "Could not initialize class my.pkg.ArchiveBuilder" warning. > Wrong warning "Could not initialize class my.pkg.ArchiveBuilder" by Arquillian > ------------------------------------------------------------------------------ > > Key: JBIDE-14555 > URL: https://issues.jboss.org/browse/JBIDE-14555 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.0.Beta1 > Reporter: Juergen Zimmermann > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.0.Beta1, 4.1.0.Beta2 > > > I'm using JBoss Tools 41-Update-2013-05-19_01-13-51-B207 having the new Arquillian component. > I'm getting a warning "Could not initialize class my.pkg.ArchiveBuilder" in all Arquillian-based test classes. > In fact my ArchiveBuilder isn't a regular class, but it's an enum: > public enum ArchiveBuilder { > INSTANCE; > private final WebArchive archive = ShrinkWrap.create(WebArchive.class, "shop.war"); > private ArchiveBuilder() {...} > public static ArchiveBuilder getInstance() { return INSTANCE; } > public Archive<? extends Archive<?>> getArchive() { return archive; } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14703) MavenArchetypeWizardParameterPage never shows error in case of loadArchetypeDescriptor() method caught InvocationTargetException

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14703?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-14703: ---------------------------------- Attachment: stack-download-failed.png Wizard allows to finish and error reported in the end. > MavenArchetypeWizardParameterPage never shows error in case of loadArchetypeDescriptor() method caught InvocationTargetException > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14703 > URL: https://issues.jboss.org/browse/JBIDE-14703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Attachments: stack-download-failed.png > > > In case there is a problem with downloading a stack descriptor file InvocationTargetException caught in loadArchetypeDescriptor method. It sets error message which is never visible trough the wizard page, because it gets cleared in validation method when page become visible -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14703) MavenArchetypeWizardParameterPage never shows error in case of loadArchetypeDescriptor() method caught InvocationTargetException

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-14703: ------------------------------------- Summary: MavenArchetypeWizardParameterPage never shows error in case of loadArchetypeDescriptor() method caught InvocationTargetException Key: JBIDE-14703 URL: https://issues.jboss.org/browse/JBIDE-14703 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, project-examples Affects Versions: 4.1.0.Beta1 Reporter: Denis Golovin In case there is a problem with downloading a stack descriptor file InvocationTargetException caught in loadArchetypeDescriptor method. It sets error message which is never visible trough the wizard page, because it gets cleared in validation method when page become visible -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14702) Maven Archetype is downloaded twice when archetype based project example selected in Project Examples wizard

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14702?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-14702: ---------------------------------- Description: (was: ) Priority: Minor (was: Major) marked as minor, because it works just fine, but slows wizard selection just a little. > Maven Archetype is downloaded twice when archetype based project example selected in Project Examples wizard > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-14702 > URL: https://issues.jboss.org/browse/JBIDE-14702 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14702) Maven Archetype is downloaded twice when archetype based project example selected in Project Examples wizard

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14702?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-14702: --------------------------------------- first is happening in onWizardContextChange(), second in selectionChange() both call ArchetypeExamplesWizardPage.initializeArchetype() which in turn calls Properties ArchetypeExamplesWizardPage.getRequiredProperties(Archetype archetype, final String archetypeRepositoryUrl). > Maven Archetype is downloaded twice when archetype based project example selected in Project Examples wizard > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-14702 > URL: https://issues.jboss.org/browse/JBIDE-14702 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-14629: ---------------------------------------- BTW I checked a few online xml/schema validators and they show the same error. > Errors when creating and deploying seam2 project > ------------------------------------------------ > > Key: JBIDE-14629 > URL: https://issues.jboss.org/browse/JBIDE-14629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1 > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta2 > > Attachments: seamerror.png > > > ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB. > 1. Fix DefaultDS Database connection definition > ASSERT: It's possible to connect to DefaultDS > 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final > ERROR: There is error in Problems view: > !seamerror.png! > 3. Start seam project on server > ERROR: This error appear in Server log. Application is not deployed: > {noformat} > 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found. > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml") > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war") > 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar") > 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource] > {noformat} > Is this supported scenario? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14485) Webservices and Rest New and Noteworthy for 4.1.0.Beta1

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14485?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-14485: -------------------------------------- Assignee: Brian Fitzpatrick > Webservices and Rest New and Noteworthy for 4.1.0.Beta1 > ------------------------------------------------------- > > Key: JBIDE-14485 > URL: https://issues.jboss.org/browse/JBIDE-14485 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Webservices > Reporter: Max Rydahl Andersen > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.1.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Webservices and Rest is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Webservices and Rest by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-14629: ---------------------------------------- [~maxandersen] we are not experts in xml but if we understand xsd spec. correctly then there is an error in jboss-deployment-structure-1_0.xsd (not in the actual XML file). We may be wrong but if we "fix" this .xsd file then XML validation stops complaining. > Errors when creating and deploying seam2 project > ------------------------------------------------ > > Key: JBIDE-14629 > URL: https://issues.jboss.org/browse/JBIDE-14629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1 > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta2 > > Attachments: seamerror.png > > > ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB. > 1. Fix DefaultDS Database connection definition > ASSERT: It's possible to connect to DefaultDS > 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final > ERROR: There is error in Problems view: > !seamerror.png! > 3. Start seam project on server > ERROR: This error appear in Server log. Application is not deployed: > {noformat} > 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found. > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml") > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war") > 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar") > 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource] > {noformat} > Is this supported scenario? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13407 at 5/30/13 4:23 PM: ------------------------------------------------------------- Signed all of JBDS via Jenkins job which runs maven [0] to call out to rpm-sign via a shell script [1], using jbosscodesign2009 certificate: Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.signed.pro... Update site: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.signed.pro... Installer/update site jar: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.signed.pro... [~maxandersen], [~dgolovin], [~mickael_istria], [~ldimaggio], [~burrsutter] care to take a look at the above and see if it works, performs the same, etc.? [0] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... [1] https://svn.jboss.org/repos/devstudio/trunk/hudson-jobs/bin/jarsign.sh was (Author: nickboldt): Signed all of JBDS via Jenkins job, using jbosscodesign2009 certificate: Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.signed.pro... Update site: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.signed.pro... Installer/update site jar: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.signed.pro... [~maxandersen], [~dgolovin], [~mickael_istria], [~ldimaggio], [~burrsutter] care to take a look at the above and see if it works, performs the same, etc.? > Jar signing for JBT plugins/features > ------------------------------------ > > Key: JBIDE-13407 > URL: https://issues.jboss.org/browse/JBIDE-13407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Beta2 > > Attachments: dialog_do-you-trust-these-certs.png, JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > > > Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product. > Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
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 2013