March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-245) Please update JBTIS TP dependencies to Luna Alpha1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-245?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-245: ------------------------------------------- [~rcernich] what are the issues Teiid has with changes to JBT servers ? We (Rob Stryker) asked for feedback on jbosstools-dev early on but I haven't seen any reports/complaints. It is that kind of feedback we are looking for. Part of the changes we are doing in servers are to allow Teiid to create runtime-less servers so if Teiid is having problems that should be raised so we can see if we can avoid breaking them or if they by any chance used things that is considered private impl details. In any case - please let us/me know whats hurting :) About Graphiti - sounds fine to require 0.10 initially. [~kconner] the whole presumption/agreement on doing the tooling split was that we were okey doing the split if we could still get feedback and have alphas of the Integration stack on our tools. I repeat that every time. Please don't keep forgetting that in your planning :) If you need help doing migration I've always said that if it is done early rather than later I can gather resources to help where/if needed. > Please update JBTIS TP dependencies to Luna Alpha1 > -------------------------------------------------- > > Key: JBTIS-245 > URL: https://issues.jboss.org/browse/JBTIS-245 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, savara, switchyard, teiid > Affects Versions: 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > > Greetings - welcome to Luna! > An Alpha1 version of the Eclipse Luna based JBTIS TP is now available in nexus [1]. It's also available here [2] and an integration build of the current Luna JBTIS is available here [3]. > I'm still working on dates but if we could get a first cut at the scope involved with upgrading that would help planning this thing immensely. There is SpringIDE and graphiti changes among others. > Thanks! > [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > [2] http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Al... > [3] http://download.jboss.org/jbosstools/updates/integration/luna/integration... -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2864: --------------------------------------- Docs Q: what will this look like from a user's perspective? will users need to change the way they deploy apps to OpenShift or set any special settings? > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2745: ---------------------------------- Comment: was deleted (was: Docs Q: I am lost with all of the comments in this jira. Please can someone provide a clear bullet point list of what is being implemented for JBDS 8.0.0.) > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > Fix For: 8.0.0.Beta1 > > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2734: --------------------------------------- Docs Q: I am lost with all of the comments in this jira. Please can someone provide a clear bullet point list of what is being implemented for JBDS 8.0.0. > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > Assignee: Koen Aers > Labels: QE_JBDS80_needinfo > Fix For: 8.0.0.Beta1 > > > Is Forge 2 ready to be included in JBDS ? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2734: ------------------------------- Labels: QE_JBDS80_needinfo (was: ) > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > Assignee: Koen Aers > Labels: QE_JBDS80_needinfo > Fix For: 8.0.0.Beta1 > > > Is Forge 2 ready to be included in JBDS ? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2745: --------------------------------------- Docs Q: I am lost with all of the comments in this jira. Please can someone provide a clear bullet point list of what is being implemented for JBDS 8.0.0. > Support installation of Early Access / Experimental / Incubating plugins > ------------------------------------------------------------------------ > > Key: JBDS-2745 > URL: https://issues.jboss.org/browse/JBDS-2745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Burr Sutter > Fix For: 8.0.0.Beta1 > > > It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear? > [~burrsutter], [~maxandersen], are we talking about: > * an additional dialog warning users about untested content? (that might be ignored / blindclicked) > * an additional tab in Central for this type of content (what label would you use?) > * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored) > * some other workflow? > See also JBDS-2068. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-2734: ------------------------------------ Not sure how/when this received a QE ack - question - are we building new wizards for this? > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > Assignee: Koen Aers > Fix For: 8.0.0.Beta1 > > > Is Forge 2 ready to be included in JBDS ? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2734: ------------------------------- CDW qa_ack: ? (was: +) > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge, requirements > Reporter: Burr Sutter > Assignee: Koen Aers > Fix For: 8.0.0.Beta1 > > > Is Forge 2 ready to be included in JBDS ? -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2932) Verify VJET/0.10.0.201309201624 with JBDS 8.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2932?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2932: ---------------------------------- See also JBIDE-16164 > Verify VJET/0.10.0.201309201624 with JBDS 8.0 > --------------------------------------------- > > Key: JBDS-2932 > URL: https://issues.jboss.org/browse/JBDS-2932 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Marián Labuda > Fix For: 8.0.0.Beta1 > > > See: https://issues.jboss.org/browse/JBIDE-15677 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16657) handle the case where development = stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16657?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16657: ------------------------------------ In this scenario, the same metadata exists in BOTH sites. So... what's the problem if you hit http://download.jboss.org/jbosstools/updates/development/kepler/ or http://download.jboss.org/jbosstools/updates/stable/kepler/ and get the same 4.1.1.Final release bits? > handle the case where development = stable > ------------------------------------------- > > Key: JBIDE-16657 > URL: https://issues.jboss.org/browse/JBIDE-16657 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Reporter: Max Rydahl Andersen > Fix For: 4.2.0.Beta1 > > > once we release Final, the development updatesite actually contains final and not the latest CR1 so there is a mismatch between website and reality ;) > Suggestion: > Add "marker" to latest_development in products.yml that will add an alert > to the latest active development download that the updatesite actually has stable. > actualcontent: 4.1.0.Final > Would give something like: > Info: 4.1.0.Final have been released and is what you will get when installing from the development 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, 1 month

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 March 2014