January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2882) Spring installation was interrupted during first try

by Jiri Peterka (JIRA)

Jiri Peterka created JBDS-2882: ---------------------------------- Summary: Spring installation was interrupted during first try Key: JBDS-2882 URL: https://issues.jboss.org/browse/JBDS-2882 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rd-party-certification Affects Versions: 7.1.0.GA Environment: JBDS 7.1.0.GA L64 - Fedora 19_64, OpenJDK 1.7.0_45 Reporter: Jiri Peterka During installation on new JBDS 7.1.0.GA (new intallation, new workspace L64 - Fedora 19 L64) I've encountered problem during installatin. {code} An error occurred while collecting items to be installed session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... Premature end of Content-Length delimited message body (expected: 284559; received: 235439 Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... Premature end of Content-Length delimited message body (expected: 66424; received: 28048 Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... Premature end of Content-Length delimited message body (expected: 226131; received: 183796 Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... Premature end of Content-Length delimited message body (expected: 1644715; received: 114317 Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... Premature end of Content-Length delimited message body (expected: 4268797; received: 469464 Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... Premature end of Content-Length delimited message body (expected: 183813; received: 56354 {code} Stacktrace {code} org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 284559; received: 235439 at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:138) at java.io.FilterInputStream.read(FilterInputStream.java:133) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:172) at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {code} During second try everything went ok -- 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] (JBDS-2882) Spring installation was interrupted during first try

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2882?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2882: ----------------------------- CDW devel_ack: ? CDW pm_ack: ? CDW qa_ack: ? CDW release: ? > Spring installation was interrupted during first try > ---------------------------------------------------- > > Key: JBDS-2882 > URL: https://issues.jboss.org/browse/JBDS-2882 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 7.1.0.GA > Environment: JBDS 7.1.0.GA L64 - Fedora 19_64, OpenJDK 1.7.0_45 > Reporter: Jiri Peterka > > During installation on new JBDS 7.1.0.GA (new intallation, new workspace L64 - Fedora 19 L64) I've encountered problem during installatin. > {code} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... > Premature end of Content-Length delimited message body (expected: 284559; received: 235439 > Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... > Premature end of Content-Length delimited message body (expected: 66424; received: 28048 > Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... > Premature end of Content-Length delimited message body (expected: 226131; received: 183796 > Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... > Premature end of Content-Length delimited message body (expected: 1644715; received: 114317 > Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... > Premature end of Content-Length delimited message body (expected: 4268797; received: 469464 > Unable to read repository at http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3.... > Premature end of Content-Length delimited message body (expected: 183813; received: 56354 > {code} > Stacktrace > {code} > org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 284559; received: 235439 > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:138) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:172) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} > During second try everything went ok -- 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] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2745: ---------------------------------- * Controlling what gets in is a human thing (ie., PRD/ERD/Requirements JIRAs w/ ACKs). That won't change. * Being able to provide updates from [EA/Exp/Inc] to [Final/GA] has always been possible, though we never included the EA/Exp/Inc content before. Ability to update won't change. * Labelling how pre-GA content appears is simply a user interface thing (aka *eye candy*). That WILL change. * Providing automation & testing to verify content is properly labelled / versioned is new. Does that make it clear what we need to do? > 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 > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15848) JSF Portal Project XML Problem

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15848?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-15848. ----------------------------------- Verified in JBDS 8.0.0 Alpha1-v20131212-0740-B25 > JSF Portal Project XML Problem > ------------------------------ > > Key: JBIDE-15848 > URL: https://issues.jboss.org/browse/JBIDE-15848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, portal-gatein, upstream > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0 Beta1-v20131102-1529-B493 and JPP 6.1 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > Attachments: jsf - Error.jpg, jsf - show details.jpg > > > Creating JSF Portal Project ends with error: > Referenced file contains errors (jar:file:/home/rrabara/jbdevstudio7.1.0.Beta1b/studio/plugins/org.jboss.tools.jst.web_3.5.1.Alpha2-v20130927-0108-B90.jar!/catalog/web-facesconfig_2_2.xsd). > Type: XML Error, Resource: faces-config.xml -- 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] (JBDS-2862) During install, I should be able to create a new directory to install into

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2862: ---------------------------------- Lost these commits when I applied PR https://github.com/jbdevstudio/jbdevstudio-product/pull/124 (JBDS-2669) so I've reapplied them in master branch via new PR: https://github.com/jbdevstudio/jbdevstudio-product/pull/129 > During install, I should be able to create a new directory to install into > -------------------------------------------------------------------------- > > Key: JBDS-2862 > URL: https://issues.jboss.org/browse/JBDS-2862 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.CR1 > Environment: Mac OS X > Reporter: Jim Tyrrell > Assignee: Denis Golovin > Labels: jbds711 > Fix For: 7.1.1.GA, 8.0.0.Alpha2 > > Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png > > > See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2758) No repository found error message after installation Spring and Mylyn bugzilla connector

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-2758?page=com.atlassian.jira.plugin.... ] Jiri Peterka commented on JBDS-2758: ------------------------------------ Nick, sorry, missed this one: 1) Installer or BYOE? Installer 2) Existing or fresh workspace? Fresh 3) Java? OpenJDK 1.7.0_25 (now 45) 64 bit 4) L64 (as noted in environment - currently on Fedora 19) 5) Spring related? I'll do some investigation with 8.0 alpha1, stay tuned > No repository found error message after installation Spring and Mylyn bugzilla connector > ---------------------------------------------------------------------------------------- > > Key: JBDS-2758 > URL: https://issues.jboss.org/browse/JBDS-2758 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 7.1.0.Alpha1 > Environment: JBDS 7.1.0.Alpha1, L64 > Reporter: Jiri Peterka > Assignee: Jiri Peterka > Attachments: no-repository-found.png > > > No repository found at file:/home/jpeterka/ide/test/jbds71a1/studio/configuration/org.eclipse.osgi/bundles/308/data/listener_1925729951/ -- 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-15849) JSF Portlet deployment error on JPP 6

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15849?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-15849. ----------------------------------- Verified in JBDS 8.0.0 Alpha1-v20131212-0740-B25 > JSF Portlet deployment error on JPP 6 > ------------------------------------- > > Key: JBIDE-15849 > URL: https://issues.jboss.org/browse/JBIDE-15849 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > Attachments: server.log > > > 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] (JBDS-2842) Add UI for central connectors update

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2842?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2842: ------------------------------------------- I don't even think central normally shows when there is an update component - it only happened for GPE because they added a new plugin/feature afaik. We could add some indications that there are updates available - today that just shows up on startup provided by eclipse as a popup when starting. > Add UI for central connectors update > ------------------------------------ > > Key: JBDS-2842 > URL: https://issues.jboss.org/browse/JBDS-2842 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Affects Versions: 7.1.0.GA > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 8.0.0.Alpha2 > > > Provide UI to inform users that there is an updated connector in JBoss Central. > Currently, when a user has a connector installed (e.g. GPE) and this connector gets updated, the only indication of that is that the connector is visible in Central even though it has been installed (and therefore would not normally show up). > There should be some element telling users that a given installed connector can be updated, rather than it appearing as new. -- 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] (JBDS-2850) JavaScript Editing Support

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2850?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2850: ------------------------------------------- [~burrsutter] these last three is not editing javascript in traditional sense; those are visual editing of a html page + javascript. > JavaScript Editing Support > -------------------------- > > Key: JBDS-2850 > URL: https://issues.jboss.org/browse/JBDS-2850 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jsp/jsf/xml/html source editing, requirements > Reporter: Burr Sutter > > 1) Support for code assist/completion (ctrl-space) for AngularJS $scope. > 2) Support for code jQuery $('# -- 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] (JBDS-2881) Make clear the distinction between update.zip and central.zip on access.redhat

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2881?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2881: ---------------------------------- [~mmurray]: To request these changes, send an email to release-engineering(a)redhat.com with the instructions above. You can also cc: cobrien(a)redhat.com as he's likely the one who'll do the work. > Make clear the distinction between update.zip and central.zip on access.redhat > ------------------------------------------------------------------------------ > > Key: JBDS-2881 > URL: https://issues.jboss.org/browse/JBDS-2881 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build, updatesite > Affects Versions: 7.1.0.GA > Reporter: Michelle Murray > > [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > [2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip. > update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation." > Can the text [1] for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline." > Can the text [2] for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline." -- 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 January 2014