November 2013 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-427) Generate Release Notes doc for JBDS 7.1.0.GA

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-427?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-427: ------------------------------------- Description: Holder JIRA for all of the elements that RNs for GA need to document. *CR1 N&N* * OpenShift Tools: time outs (JBIDE-16046) * JSF: hyperlink detector * Forge: updated runtime 1.4.3.Final (JBIDE-15859, JBIDE-16028) *CR1 Extras* * New and updated 3rd party plug-ins in JBoss Central (JBDS-2710) * Central TP zip (TOOLSDOC-426) * Support EAP 6.2 (JBDS-2784) *Maybe?* * Show a warning when enterprise maven repo is missing for enterprise quickstarts (JBIDE-15860) * Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install (JBIDE-15449) was: Holder JIRA for all of the elements that RNs for GA need to document. *CR1 N&N* * Show a warning when enterprise maven repo is missing for enterprise quickstarts (JBIDE-15860) * Update Forge Embedded Runtime to 1.4.3.Final (JBIDE-15859, JBIDE-16028) * Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install (JBIDE-15449) * Update to VJET 0.10.0.201309201624 in Central (for 4.1.1.CR1) (JBIDE-15677, JBDS-2710) * Support EAP 6.2 (JBDS-2784) * Central TP zip (TOOLSDOC-426) > Generate Release Notes doc for JBDS 7.1.0.GA > -------------------------------------------- > > Key: TOOLSDOC-427 > URL: https://issues.jboss.org/browse/TOOLSDOC-427 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.1.1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > > Holder JIRA for all of the elements that RNs for GA need to document. > *CR1 N&N* > * OpenShift Tools: time outs (JBIDE-16046) > * JSF: hyperlink detector > * Forge: updated runtime 1.4.3.Final (JBIDE-15859, JBIDE-16028) > *CR1 Extras* > * New and updated 3rd party plug-ins in JBoss Central (JBDS-2710) > * Central TP zip (TOOLSDOC-426) > * Support EAP 6.2 (JBDS-2784) > *Maybe?* > * Show a warning when enterprise maven repo is missing for enterprise quickstarts (JBIDE-15860) > * Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install (JBIDE-15449) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16100) OpenShift time out preference should show default 240 seconds and not 0

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16100?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16100: ------------------------------------ Environment: Version: 7.1.0.CR1 Build id: CR1-v20131124-0717-B560 Build date: 20131124-0717 > OpenShift time out preference should show default 240 seconds and not 0 > ----------------------------------------------------------------------- > > Key: JBIDE-16100 > URL: https://issues.jboss.org/browse/JBIDE-16100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Environment: Version: 7.1.0.CR1 > Build id: CR1-v20131124-0717-B560 > Build date: 20131124-0717 > Reporter: Michelle Murray > Attachments: OpenShift_deftimeout.png > > > Click Window > Preferences > JBoss Tools > OpenShift. > Remote requests time out field states '0'. > !OpenShift_deftimeout.png! > If the default time out is 240 seconds (as stated in N&N) and I haven't changed the default time out, then this should read 240 - right? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16100) OpenShift time out preference should show default 240 seconds and not 0

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16100?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16100: ------------------------------------ Attachment: OpenShift_deftimeout.png > OpenShift time out preference should show default 240 seconds and not 0 > ----------------------------------------------------------------------- > > Key: JBIDE-16100 > URL: https://issues.jboss.org/browse/JBIDE-16100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Attachments: OpenShift_deftimeout.png > > > Click Window > Preferences > JBoss Tools > OpenShift. > Remote requests time out field states '0'. > !OpenShift_deftimeout.png! > If the default time out is 240 seconds (as stated in N&N) and I haven't changed the default time out, then this should read 240 - right? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16100) OpenShift time out preference should show default 240 seconds and not 0

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16100?page=com.atlassian.jira.plugi... ] Michelle Murray updated JBIDE-16100: ------------------------------------ Affects: Documentation (Ref Guide, User Guide, etc.) > OpenShift time out preference should show default 240 seconds and not 0 > ----------------------------------------------------------------------- > > Key: JBIDE-16100 > URL: https://issues.jboss.org/browse/JBIDE-16100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Attachments: OpenShift_deftimeout.png > > > Click Window > Preferences > JBoss Tools > OpenShift. > Remote requests time out field states '0'. > !OpenShift_deftimeout.png! > If the default time out is 240 seconds (as stated in N&N) and I haven't changed the default time out, then this should read 240 - right? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16100) OpenShift time out preference should show default 240 seconds and not 0

by Michelle Murray (JIRA)

Michelle Murray created JBIDE-16100: --------------------------------------- Summary: OpenShift time out preference should show default 240 seconds and not 0 Key: JBIDE-16100 URL: https://issues.jboss.org/browse/JBIDE-16100 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.1.CR1 Reporter: Michelle Murray Click Window > Preferences > JBoss Tools > OpenShift. Remote requests time out field states '0'. !OpenShift_deftimeout.png! If the default time out is 240 seconds (as stated in N&N) and I haven't changed the default time out, then this should read 240 - right? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16056) CLONE - JSF Portlet deployment error on JPP 6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16056?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16056: ------------------------------------ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... shows build #44 contains this change, so it'll be in CR1 respin-a. > CLONE - JSF Portlet deployment error on JPP 6 > --------------------------------------------- > > Key: JBIDE-16056 > URL: https://issues.jboss.org/browse/JBIDE-16056 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Optional > Labels: respin-a > Fix For: 4.1.1.CR1 > > > Deploying of JSF Portal Project with JSF Portlet ends with error on JPP 6. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16056) CLONE - JSF Portlet deployment error on JPP 6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16056?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16056: --------------------------------------------- [~snjeza], see the comment above: > Snjezana Peco lets put this in just because it is now there because we have it and its "as bad/good" as we had before. Yes, please put in the PR. Below is me requesting to create jira to find ways we can either remove/lock down this portal integration or find a way so changes in the runtimes doesn't always break us: "But we should create a jira to start winding this feature down and not have to keep maintaining it because there is simple too many moving factors here and removing files in a facet without warnings is just a really bad thing to start doing." And then I ask if you have checked the latest WFK seam libraries are also incompatible and if they are that should be investigated since it does not make sense that we got incompatible conflicting richfaces libraries in these two frameworks: "Also are you sure the richfaces libraries are not compatible if you use the latest versions from WFK/Seam ? We really should reach out to wfk/richfaces team before doing such changes in tools if it is actually already handled on the runtime side....and if it is nothandled there that incompatbility sounds like a bug we should get reported." So in short - yes, apply this PR and then open jiras and reach out to seam/wfk team for the remaining issues. But that can be done next week. PR is the important part now. But probably too late if [~nickboldt] already started the respin. > CLONE - JSF Portlet deployment error on JPP 6 > --------------------------------------------- > > Key: JBIDE-16056 > URL: https://issues.jboss.org/browse/JBIDE-16056 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Optional > Labels: respin-a > Fix For: 4.1.1.CR1 > > > Deploying of JSF Portal Project with JSF Portlet ends with error on JPP 6. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15639) Support running on Eclipse Luna M3 (4.4.M3) platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15639?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15639: ------------------------------- Description: Luna -M2- M3 has been released, with already a few changes available. We should investigate the effort of moving current master from Kepler to Luna. As Target Platform 4.40.0.Alpha1-SNAPSHOT is now based on Luna, it is easy to try a build for a given component with {code}mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT{code} If you component has new compilation or test failure, you should report them as a Jira and make it a dependency of this Jira. WTP API Migration: http://wiki.eclipse.org/New_Help_for_Old_Friends_IX Eclipse core: Not published yet. was: Luna M2 has been released, with already a few changes available. We should investigate the effort of moving current master from Kepler to Luna. As Target Platform 4.40.0.Alpha1-SNAPSHOT is now based on Luna, it is easy to try a build for a given component with {code}mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT{code} If you component has new compilation or test failure, you should report them as a Jira and make it a dependency of this Jira. WTP API Migration: http://wiki.eclipse.org/New_Help_for_Old_Friends_IX Eclipse core: Not published yet. > Support running on Eclipse Luna M3 (4.4.M3) platform > ---------------------------------------------------- > > Key: JBIDE-15639 > URL: https://issues.jboss.org/browse/JBIDE-15639 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform, updatesite > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > > Luna -M2- M3 has been released, with already a few changes available. We should investigate the effort of moving current master from Kepler to Luna. > As Target Platform 4.40.0.Alpha1-SNAPSHOT is now based on Luna, it is easy to try a build for a given component with > {code}mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT{code} > If you component has new compilation or test failure, you should report them as a Jira and make it a dependency of this Jira. > WTP API Migration: http://wiki.eclipse.org/New_Help_for_Old_Friends_IX > Eclipse core: Not published yet. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16073) Create Luna M3 target-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16073?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16073: ------------------------------------ PR applied and building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >=183 > Create Luna M3 target-platform > ------------------------------ > > Key: JBIDE-16073 > URL: https://issues.jboss.org/browse/JBIDE-16073 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha1 > > > We plan to build 4.2.0.Alpha1 against Luna M3, so we need a target-platform -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16082) Prevent JBoss Tools 4.1 and JBDS 7.x from installing into Luna due to platform/API incompatibilities

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16082?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-16082. ------------------------------ Assignee: Nick Boldt Resolution: Done Child tasks are done, so closing this container. [~phantomjinx] if you want to open a new JIRA to track the ODA / Teiid issue, please do. > Prevent JBoss Tools 4.1 and JBDS 7.x from installing into Luna due to platform/API incompatibilities > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-16082 > URL: https://issues.jboss.org/browse/JBIDE-16082 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, forge, hibernate, server, testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.1.1.CR1 > > > We already know (from JBIDE-15639) that components like Arquillian, Forge, Server, and Hibernate will not compile with Luna dependencies due to the fact that the upstream projects on which they depend have changed in incompatible ways. > Therefore, JBT 4.2 / JBDS 8 is being built to *ONLY work with Luna*. > But the converse should be true, too: we don't want users installing JBT 4.1 / JBDS 7.x onto Luna and ending up with something that *doesn't work*, even if it can be installed that way. > *Solution:* > Update manifest.mf files to PREVENT installing key parts of JBT 4.1 / JBDS 7.x into Luna, so that no user will hit this problem. -- 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, 5 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 November 2013