August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-141: ---------------------------------- PRs processed. > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1, 4.1.1 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15317) LiveReload script injection corrupted html encoding

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15317: --------------------------------------- Hello [~tangtheone], first, thanks for your feedback and thanks for reporting the invalid content-length header value that I returning in my code ! I pushed an update of the PR in which the return content uses the same charset as the one given in the request, or it falls back the "Default Charset" that can be configured at the server level. Thus, if you set "UTF-8" at the LiveReload server level (this is the default value anyway), you should have the expected content in response. Let me know if this works for you. Thanks. Best regards, > LiveReload script injection corrupted html encoding > --------------------------------------------------- > > Key: JBIDE-15317 > URL: https://issues.jboss.org/browse/JBIDE-15317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Pei-Tang Huang > Assignee: Max Rydahl Andersen > Priority: Critical > Labels: encoding, livereload > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > Attachments: chinese.html > > Original Estimate: 1 day > Remaining Estimate: 1 day > > LiveReload script injection dissmisses the encoding of the original HTML content, my page contains CJK character in UTF-8 all became "?" character. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-147) Cannot build BPMN2 bot tests

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-147: --------------------------------------- Summary: Cannot build BPMN2 bot tests Key: JBTIS-147 URL: https://issues.jboss.org/browse/JBTIS-147 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: QE Affects Versions: 4.1.1 Reporter: Andrej Podhradsky Assignee: Marek Baluch Fix For: 4.1.1 Cannot build BPMN2 bot tests using 'mvn package', the following error occurs [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.18.0:package-plugin (default-package-plugin) on project org.jboss.tools.bpmn2.itests: Error assembling JAR: /home/apodhrad/Projects/jbosstools-integration-tests/tests/org.jboss.tools.bpmn2.itests/build.properties: bin.includes value(s) [lib/antlr.jar, lib/stringtemplate.jar] do not match any files. -> [Help 1] -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-146) Update all jbtis bot tests to 4.1.1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-146?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-146. ----------------------------------- > Update all jbtis bot tests to 4.1.1 > ------------------------------------ > > Key: JBTIS-146 > URL: https://issues.jboss.org/browse/JBTIS-146 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.1.1 > > > The following error occurs when JBTIS 4.1.0 is used > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.0-SNAPSHOT/target-platform-4.1.0-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.CR2-v20130719-1328-B29" in the repositories of the current location -> [Help 1] > This is due to mising plugin in locus. Fixed in JBTIS 4.1.1 target platform, so update all jbtis bot tests to use 4.1.1 TP and update site. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project with Seam 2.3.Final

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14629: --------------------------------------------- I've opened https://issues.jboss.org/browse/JBMETA-367 since it looks like the right place. [~dlmiles] please add/comments suggestion on that. > Errors when creating and deploying seam2 project with Seam 2.3.Final > --------------------------------------------------------------------- > > 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.1.Final > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15340) Remove site references from Locus site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15340?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-15340: ------------------------------------------- Assignee: Max Rydahl Andersen > Remove site references from Locus site > -------------------------------------- > > Key: JBIDE-15340 > URL: https://issues.jboss.org/browse/JBIDE-15340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Reporter: Rob Cernich > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 1.1.0-LOCUS > > > The Locus p2 repo/update site should not include references to other update sites. Currently it includes references to other sites, e.g. http://download.jboss.org/jbosstools/updates/development/juno/ -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15340) Remove site references from Locus site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15340?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15340: ---------------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) > Remove site references from Locus site > -------------------------------------- > > Key: JBIDE-15340 > URL: https://issues.jboss.org/browse/JBIDE-15340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Reporter: Rob Cernich > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.1.0-LOCUS > > > The Locus p2 repo/update site should not include references to other update sites. Currently it includes references to other sites, e.g. http://download.jboss.org/jbosstools/updates/development/juno/ -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15340) Remove site references from Locus site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15340?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15340: --------------------------------------------- [~nickboldt] we should fix this ASAP. Any idea why these were added ? > Remove site references from Locus site > -------------------------------------- > > Key: JBIDE-15340 > URL: https://issues.jboss.org/browse/JBIDE-15340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Reporter: Rob Cernich > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.1.0-LOCUS > > > The Locus p2 repo/update site should not include references to other update sites. Currently it includes references to other sites, e.g. http://download.jboss.org/jbosstools/updates/development/juno/ -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15340) Remove site references from Locus site

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15340?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15340: --------------------------------------------- Apparently my grep fu was failing on me. yes - that looks extremely wrong and defeats the whole point of locus and creates a cyclic dependency. Actually seems like this was in very early on in commit https://github.com/jbosstools/jbosstools-locus/commit/114433e0828498caebe... :( > Remove site references from Locus site > -------------------------------------- > > Key: JBIDE-15340 > URL: https://issues.jboss.org/browse/JBIDE-15340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: locus > Reporter: Rob Cernich > Priority: Blocker > Fix For: 1.1.0-LOCUS > > > The Locus p2 repo/update site should not include references to other update sites. Currently it includes references to other sites, e.g. http://download.jboss.org/jbosstools/updates/development/juno/ -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-146) Update all jbtis bot tests to 4.1.1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-146?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-146: ------------------------------------ Description: The following error occurs when JBTIS 4.1.0 is used [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.0-SNAPSHOT/target-platform-4.1.0-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.CR2-v20130719-1328-B29" in the repositories of the current location -> [Help 1] This is due to mising plugin in locus. Fixed in JBTIS 4.1.1 target platform, so update all jbtis bot tests to use 4.1.1 TP and update site. > Update all jbtis bot tests to 4.1.1 > ------------------------------------ > > Key: JBTIS-146 > URL: https://issues.jboss.org/browse/JBTIS-146 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Final > Reporter: Andrej Podhradsky > Fix For: 4.1.1 > > > The following error occurs when JBTIS 4.1.0 is used > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.0-SNAPSHOT/target-platform-4.1.0-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.CR2-v20130719-1328-B29" in the repositories of the current location -> [Help 1] > This is due to mising plugin in locus. Fixed in JBTIS 4.1.1 target platform, so update all jbtis bot tests to use 4.1.1 TP and update site. -- 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, 7 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 August 2013