January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13437) bpel won't build in 40x branch

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13437: ---------------------------------- Summary: bpel won't build in 40x branch Key: JBIDE-13437 URL: https://issues.jboss.org/browse/JBIDE-13437 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL, updatesite, UpStream Affects Versions: 4.0.0.Alpha1-SOA Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.0.0.Alpha1-SOA BPEL builds are broken in 40x branch due to missing Eclipse.org bpel feature that is trying to be aggregated into the bpel site: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl... Solution: remove the feature (and ask upstream why it vanished). -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13437) bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13437?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13437: ------------------------------- Summary: bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature (was: bpel won't build in 40x branch) > bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature > -------------------------------------------------------------------------------------------- > > Key: JBIDE-13437 > URL: https://issues.jboss.org/browse/JBIDE-13437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL, updatesite, UpStream > Affects Versions: 4.0.0.Alpha1-SOA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.0.Alpha1-SOA > > > BPEL builds are broken in 40x branch due to missing Eclipse.org bpel feature that is trying to be aggregated into the bpel site: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stabl... > Solution: remove the feature (and ask upstream why it vanished). -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13436) jQuery Mobile: Code completion for all the available IDs for <a href="#...">

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13436?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13436: ----------------------------------- Summary: jQuery Mobile: Code completion for all the available IDs for <a href="#..."> (was: jQuery Mobile: Code completion for all the available page IDs for <a href="#...">) Description: Suppose we have a multi-page document: {code} <body> <div data-role="page" id="foo"> ... <a href="#bar">bar</a>  ... </div> <div data-role="page" id="bar"> ... <a href="#foo">Back to foo</a>  ... </div> </body> {code} Another example: {code} <a href="#popupBasic" data-rel="popup">Open Popup</a>  <div data-role="popup" id="popupBasic"> ... </div> {code} was: Suppose we have a multi-page document: {code} <body> <div data-role="page" id="foo"> ... <a href="#bar">bar</a>  ... </div> <div data-role="page" id="bar"> ... <a href="#foo">Back to foo</a>  ... </div> </body> {code} > jQuery Mobile: Code completion for all the available IDs for <a href="#..."> > ---------------------------------------------------------------------------- > > Key: JBIDE-13436 > URL: https://issues.jboss.org/browse/JBIDE-13436 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > > Suppose we have a multi-page document: > {code} > <body> > <div data-role="page" id="foo"> > ... > <a href="#bar">bar</a>  > ... > </div> > <div data-role="page" id="bar"> > ... > <a href="#foo">Back to foo</a>  > ... > </div> > </body> > {code} > Another example: > {code} > <a href="#popupBasic" data-rel="popup">Open Popup</a>  > <div data-role="popup" id="popupBasic"> > ... > </div> > {code} -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13436) jQuery Mobile: Code completion for all the available page IDs for <a href="#...">

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13436?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13436: ----------------------------------- Description: Suppose we have a multi-page document: {code} <body> <div data-role="page" id="foo"> ... <a href="#bar">bar</a>  ... </div> <div data-role="page" id="bar"> ... <a href="#foo">Back to foo</a>  ... </div> </body> {code} was: Suppose we have a multi-page document: {code} <body> <div data-role="page" id="foo"> ... <a href="#bar">bar</a>  ... </div> <div data-role="page" id="bar"> ... <a href="#foo">Back to foo</a>  ... </div> </body> {code} > jQuery Mobile: Code completion for all the available page IDs for <a href="#..."> > --------------------------------------------------------------------------------- > > Key: JBIDE-13436 > URL: https://issues.jboss.org/browse/JBIDE-13436 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > > Suppose we have a multi-page document: > {code} > <body> > <div data-role="page" id="foo"> > ... > <a href="#bar">bar</a>  > ... > </div> > <div data-role="page" id="bar"> > ... > <a href="#foo">Back to foo</a>  > ... > </div> > </body> > {code} -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13436) jQuery Mobile: Code completion for all the available page IDs for <a href="#...">

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13436?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13436: ----------------------------------- Description: Suppose we have a multi-page document: {code} <body> <div data-role="page" id="foo"> ... <a href="#bar">bar</a>  ... </div> <div data-role="page" id="bar"> ... <a href="#foo">Back to foo</a>  ... </div> {code} was: Suppose we have a multi-page document: {code} <div data-role="page" id="foo"> ... <a href="#bar">bar</a>  ... </div> ... <div data-role="page" id="bar"> ... <a href="#foo">Back to foo</a>  ... </div> {code} > jQuery Mobile: Code completion for all the available page IDs for <a href="#..."> > --------------------------------------------------------------------------------- > > Key: JBIDE-13436 > URL: https://issues.jboss.org/browse/JBIDE-13436 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > > Suppose we have a multi-page document: > {code} > <body> > <div data-role="page" id="foo"> > ... > <a href="#bar">bar</a>  > ... > </div> > <div data-role="page" id="bar"> > ... > <a href="#foo">Back to foo</a>  > ... > </div> > {code} -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13436) jQuery Mobile: Code completion for all the available page IDs for <a href="#...">

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-13436: -------------------------------------- Summary: jQuery Mobile: Code completion for all the available page IDs for <a href="#..."> Key: JBIDE-13436 URL: https://issues.jboss.org/browse/JBIDE-13436 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml/html source editing Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.1.x Suppose we have a multi-page document: {code} <div data-role="page" id="foo"> ... <a href="#bar">bar</a>  ... </div> ... <div data-role="page" id="bar"> ... <a href="#foo">Back to foo</a>  ... </div> {code} -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13436) jQuery Mobile: Code completion for all the available page IDs for <a href="#...">

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13436?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13436: ----------------------------------- Description: Suppose we have a multi-page document: {code} <body> <div data-role="page" id="foo"> ... <a href="#bar">bar</a>  ... </div> <div data-role="page" id="bar"> ... <a href="#foo">Back to foo</a>  ... </div> </body> {code} was: Suppose we have a multi-page document: {code} <body> <div data-role="page" id="foo"> ... <a href="#bar">bar</a>  ... </div> <div data-role="page" id="bar"> ... <a href="#foo">Back to foo</a>  ... </div> {code} > jQuery Mobile: Code completion for all the available page IDs for <a href="#..."> > --------------------------------------------------------------------------------- > > Key: JBIDE-13436 > URL: https://issues.jboss.org/browse/JBIDE-13436 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > > Suppose we have a multi-page document: > {code} > <body> > <div data-role="page" id="foo"> > ... > <a href="#bar">bar</a>  > ... > </div> > <div data-role="page" id="bar"> > ... > <a href="#foo">Back to foo</a>  > ... > </div> > </body> > {code} -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1?page=com.atlassian.jira.plugin.sy... ] Paul Leacu commented on JBTIS-1: -------------------------------- Remaining download.eclipse.org dependency references have been modified to reflect jboss.org mirrors by @nboldt : https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/pleacu-jbosstools-in... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/pleacu-jbosstools-in... --paull > Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone > --------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-1 > URL: https://issues.jboss.org/browse/JBTIS-1 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Paul Leacu > Labels: f2f2012 > Attachments: JBIDE-11121.tweak.txt, ModeShapeToolsBuildLog.txt > > > Generate target platforms for JBT/JBDS SOA Tooling which include: > 1. JBT Core TP + last stable JBT Core milestone. > 2. JBDS Core TP + last stable JBDS Core milestone. > Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones. > This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti). -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13435) remove uml2, zest & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13435?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13435: ------------------------------- Summary: remove uml2, zest & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s) (was: remove uml2 & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s)) > remove uml2, zest & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s) > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13435 > URL: https://issues.jboss.org/browse/JBIDE-13435 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > > {quote} > UML2 4.0 is not in your TP, though if I recall correctly (and they haven't removed the requirement) Teiid Designer requires UML2. Should it be added to your TP? I suspect you're resolving that dependency because it's already included in the JBT target platform [5] ? If that's the case then I believe it should be removed from ours and added to yours instead. > Graphiti 0.9 is in both your TP and the JBT one [5], yet I don't think anything in JBT requires it. It was most likely added to support something in the SOA-P/BRMS tooling space before you started having your own TP. It too should probably be removed from ours in favour of it being in yours - no need to be in both. > {quote} > -- [~nickboldt] > {quote} > You're correct about uml2 and teiid - we're currently loading that directly from our aggregate site.xml (along with zest needed by esb). I would assume those two would be better served in the base tp as well - I'll let Rob comment. {quote} > -- [~pleacu] -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13435) remove uml2 & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13435: ---------------------------------- Summary: remove uml2 & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s) Key: JBIDE-13435 URL: https://issues.jboss.org/browse/JBIDE-13435 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.0.0.Final Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.0.1.Final, 4.1.0.Alpha1 {quote} UML2 4.0 is not in your TP, though if I recall correctly (and they haven't removed the requirement) Teiid Designer requires UML2. Should it be added to your TP? I suspect you're resolving that dependency because it's already included in the JBT target platform [5] ? If that's the case then I believe it should be removed from ours and added to yours instead. Graphiti 0.9 is in both your TP and the JBT one [5], yet I don't think anything in JBT requires it. It was most likely added to support something in the SOA-P/BRMS tooling space before you started having your own TP. It too should probably be removed from ours in favour of it being in yours - no need to be in both. {quote} -- [~nickboldt] {quote} You're correct about uml2 and teiid - we're currently loading that directly from our aggregate site.xml (along with zest needed by esb). I would assume those two would be better served in the base tp as well - I'll let Rob comment. {quote} -- [~pleacu] -- 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

13 years, 2 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 January 2013