May 2013 - jbosstools-issues - Jboss List Archives

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-14629: ------------------------------------------- Assignee: Alexey Kazakov (was: Max Rydahl Andersen) you mean it is the .xsd that is wrong and not the actual file ? .xsd errors would be on wildfly mailing list/jira. > 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-14381) Verify that p2.statsURI appears in artifacts.xml for Beta1 stable branch update site builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14381?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-14381. ------------------------------ Resolution: Done Latest apache log dump contains both "_41/Beta1" and "_master/Beta2" data, suggesting that both stable branch (_41) and master branch (_master) are working. > Verify that p2.statsURI appears in artifacts.xml for Beta1 stable branch update site builds > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14381 > URL: https://issues.jboss.org/browse/JBIDE-14381 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Looking for this to appear in the Beta1 stable branch builds: > {code} <property name="p2.statsURI" > value="http://download.jboss.org/jbosstools/usage/installs/jbosstools-build-site..."/> > {code} > If it's not there, then there's a problem w/ the mojo NOT generating content for the stable branch. Today we only see download stat data for Beta1 from master/trunk, but nothing from the Alpha2x branch so I've opened this to make sure we audit that this requirement is actually working. -- 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 commented on JBIDE-13407: ------------------------------------ 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

[JBoss JIRA] (JBIDE-13527) [tester] freeze parsing wsdl

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13527?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-13527: -------------------------------------- Labels: new_and_noteworthy (was: ) > [tester] freeze parsing wsdl > ---------------------------- > > Key: JBIDE-13527 > URL: https://issues.jboss.org/browse/JBIDE-13527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.2.Final > Reporter: Alessio Soldano > Assignee: Brian Fitzpatrick > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: jaxws-complex.war, threaddump.txt > > > JBT freezes when the ws tester is used to consume the wsdl contract for the jaxws-complex.war test deployment of JBossWS testsuite. -- 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-14507) arquillian excessive dependencies includes jsf, seam, project examples and portlets

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14507?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-14507: ------------------------------------- Assignee: Max Rydahl Andersen (was: Snjezana Peco) > arquillian excessive dependencies includes jsf, seam,project examples and portlets > ----------------------------------------------------------------------------------- > > Key: JBIDE-14507 > URL: https://issues.jboss.org/browse/JBIDE-14507 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Affects Versions: 4.1.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta2 > > > When [~aslak] installed arquillian he noticed an excessively long list of dependencies: > Warning: You are installing software that contains unsigned content. The authenticity or validity of this software cannot be established. Do you want to continue with the installation? > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.archives.core_3.4.100.Alpha2-v20130424-2035-B57 > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.archives.ui_3.4.100.Alpha2-v20130424-2035-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.archives.webtools_2.4.100.Alpha2-v20130424-2035-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.as.classpath.core_2.4.100.Alpha2-v20130424-2035-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.as.ui_2.4.100.Alpha2-v20130424-2035-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.arquillian.core_1.0.4.Beta1-v20130516-1548-B9.jar > /home/aslak/dev/tools/eclipse-4.3/features/org.jboss.tools.arquillian.feature_1.0.4.Beta1-v20130516-1548-B9 > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.arquillian.ui_1.0.4.Beta1-v20130516-1548-B9.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.el.core_3.5.0.Alpha2-v20130415-2228-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.el.ui_3.5.0.Alpha2-v20130415-2228-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.model_3.5.0.Alpha2-v20130415-2228-B57 > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.model.ui_3.5.0.Alpha2-v20130415-2228-B57 > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.projecttemplates_3.5.0.Alpha2-v20130415-2228-B57 > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.resref.core_3.5.0.Alpha2-v20130415-2228-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.text.ext_3.5.0.Alpha2-v20130415-2228-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.text.xml_3.5.0.Alpha2-v20130415-2228-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.ui_3.5.0.Alpha2-v20130415-2228-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.validation_3.5.0.Alpha2-v20130415-2228-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jmx.core_1.4.0.Alpha2-v20130424-2035-B57.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jsf_3.5.0.Alpha2-v20130420-0455-B56.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jst.jsp_3.5.0.Alpha2-v20130420-0309-B33.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jst.web_3.5.0.Alpha2-v20130420-0309-B33.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jst.web.kb_3.5.0.Alpha2-v20130420-0309-B33 > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.portlet.core_1.5.0.Alpha2-v20130405-1819-B10.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.project.examples_1.5.0.Alpha2-v20130419-1334-B34.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.seam.core_3.5.0.Alpha2-v20130420-0455-B56.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.seam.pages.xml_3.5.0.Alpha2-v20130420-0455-B56.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.seam.xml_3.5.0.Alpha2-v20130420-0455-B56.jar > /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.usage_1.2.0.Alpha2-v20130415-2228-B57.jar > Why is seam, portlet, jsf and others required ? -- 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 Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14702?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14702: ------------------------------------- IIRC that was a hack in m2e to prevent some resolution errors. Needs more investigation. > 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] (JBTIS-90) JBDSIS - create 6.0.0 for SOA-5.3.x Juno support

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-90?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-90: --------------------------------- site support: https://github.com/jbosstools/jbosstools-integration-stack/commit/2ce88b3... > JBDSIS - create 6.0.0 for SOA-5.3.x Juno support > ------------------------------------------------ > > Key: JBTIS-90 > URL: https://issues.jboss.org/browse/JBTIS-90 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 6.0.0 > > -- 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)

Denis Golovin created JBIDE-14702: ------------------------------------- Summary: 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-14519) Arquillian Validation validating missing Class in @Deployment method?

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14519?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-14519: ------------------------------------- Assignee: Max Rydahl Andersen (was: Snjezana Peco) > Arquillian Validation validating missing Class in @Deployment method? > --------------------------------------------------------------------- > > Key: JBIDE-14519 > URL: https://issues.jboss.org/browse/JBIDE-14519 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta2 > > Attachments: Screenshot.png > > > Not quite sure what is going on here, but it shows Validation error on the Injection point and in the Deployment definition. > Both show the warning > Arquillian: the SuperTestHandler type is not included in the deployment -- 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-14429) arquillian tab in junit has no Arquillian logo

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14429?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-14429: ------------------------------------- Assignee: Max Rydahl Andersen (was: Snjezana Peco) > arquillian tab in junit has no Arquillian logo > ---------------------------------------------- > > Key: JBIDE-14429 > URL: https://issues.jboss.org/browse/JBIDE-14429 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta2 > > -- 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