[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2253: ----------------------------- Attachment: BYOE-Juno42-JBDS6Nightly-central1.png BYOE-Juno42-JBDS6Nightly-central2.png Here's what the resulting install looks like: !BYOE-Juno42-JBDS6Nightly-central1.png! !BYOE-Juno42-JBDS6Nightly-central2.png! Note that Central here is the JBT version, not the JBDS version, so there's no mention of SOA/BRMS tooling, and the eclipse.ini settings will be the Eclipse defaults, not the JBDS ones. {quote} Note: If you install JBoss Developer Studio updates into an existing Eclipse 3.7.2 (Indigo SR2) installation, you will most likely need to tweak your eclipse.ini file to give Eclipse more memory than is allocated by default. This should work for you but is currently Unsupported. Please see the following tips: Installing JBDS into Eclipse works, but runs out of memory: https://issues.jboss.org/browse/JBDS-1577#comment-12586050 How do I start Eclipse?: http://wiki.eclipse.org/IRC_FAQ#How_do_I_start_Eclipse.3F Using eclipse.ini, increasing heap & permgen memory: http://wiki.eclipse.org/Eclipse.ini#See_Also {quote} -- https://devstudio.jboss.com/updates/5.0/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2253: ----------------------------- Description: BYOE JBDS 6 Nightly 1. Launch clean Eclipse 4.2 2. Help > Install new 3. Add the following sites http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju... (target platform) http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk.... (extras) http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk.... (product) 4. Select all categorized features on the /product/ site. Click Next. Install. Restart when prompted. Once we have a first Early Access release of JBDS 6, the above process will change to: 1. Launch clean Eclipse 4.2 2. Help > Install new 3. Add the following site https://devstudio.jboss.com/updates/6.0-staging/central/core/ (target platform + product + extras) 4. Select all categorized features. Click Next. Install. Restart when prompted. was: BYOE JBDS 6 Nightly 1. Launch clean Eclipse 4.2 2. Help > Install new 3. Add the following sites http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju... (target platform) http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk.... (extras) http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk.... (product) 4. Select all categorized features on the /product/ site. Click Next. Install. Restart when prompted. Once we have a first Early Access release of JBDS 6, the above process will change to: 1. Launch clean Eclipse 4.2 2. Help > Install new 3. Add the following sites https://devstudio.jboss.com/updates/6.0-staging/central/core/ (target platform + product + extras) 4. Select all categorized features. Click Next. Install. Restart when prompted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2253: ---------------------------------- 1. Need a top-level restrictive "Product Feature" to control what can be installed and therefore how much QE has to test. (We already have this.) 2. Later might want to automate stuff like: * product customization * memory settings * osx launch settings * correct version of Central (JBDS vs. JBT - need to set correct URL!) * branding/skinning -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2253: ------------------------------------------- a) I don't think one giant feature is good here - a set of smaller parts would be interesting. b) what does "many footprints possible" mean here ? c) not relevant. JBT is not supposed to offer installation of something that has the potential to conflict with it. If you already got JBT, why would you install devstudio ? d) same as c e) not following what this means - the updatesite will need to be there no matter what and its what we would start with before pushing it into marketplace. Remember for 6 we said techpreview, thus it starts with an updatesite with the intended goal to make it available from eclipse marketplace once we are confident its sane/maintainable. -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2253: ---------------------------------- Working on a solution to the m2e restrictiveness. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_trunk.... >=2770 -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2253: ----------------------------- Attachment: JBDS2253-install-entire-JBDS-BrandedProduct-feature-to-EclipsePlatformRuntimeBinary4.2.1-note-changed-icons-and-About-screen.png JBDS2253-install-entire-JBDS-BrandedProduct-feature-to-EclipsePlatformRuntimeBinary4.2.1-uncheck-group-by-category.png JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1-About-after-with-Central.png JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1-available-sites.png JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1-About-before.png JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1.png 1. To build and test locally, I did this: a) download latest target platform site zip http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_4.0.ju... and unpack into some folder such as {code} /home/nboldt/JBDS_REPO_JunoSR0a {code} b) build JBDS product and extras sites in here (using `cd ~/devstudio_trunk/product; mvn install`). You could of course just download these as zips or point at the remote sites, but I wanted to tweak the "JBoss Developer Studio (Core Features)" feature. Resulting update sites are built under the devstudio SVN sources in a folder such as {code} /home/nboldt/devstudio_trunk/extras/site/target/site /home/nboldt/devstudio_trunk/product/site/target/site {code} 2. Then download Eclipse Platform Runtime Binary for linux x86_64 from http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/dro... 3. Unpack Eclipse, fire it up. !JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1-About-before.png! 4. Help > Install new ... > add these sites (in order): {code} /home/nboldt/tmp/JBDS_REPO_JunoSR0a /home/nboldt/devstudio_trunk/extras/site/target/site /home/nboldt/devstudio_trunk/product/site/target/site {code} You should then see these sites available and enabled (or similar): !JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1-available-sites.png! 4. Browse the site and select either everything or just the "JBoss Developer Studio (Core Features)" feature (com.jboss.jbds.product.feature). Click next. If you expand the sections you'll see something like this: !JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1.png! 5. After installation, Help > About and you'll see this: !JBDS2253-install-entire-JBDS-core-site-to-EclipsePlatformRuntimeBinary4.2.1-About-after-with-Central.png! 6. Should you want to add the "JBoss Developer Studio (Branded Product)" feature, you can Help > Install new > select the product site > uncheck the box for "Group by category", and then install the branded product feature: !JBDS2253-install-entire-JBDS-BrandedProduct-feature-to-EclipsePlatformRuntimeBinary4.2.1-uncheck-group-by-category.png! 7. After restarting you'll note the splash screen doesn't change, but the icon for Eclipse and Help > About is now the JBDS redball instead of the Eclipse logo. !JBDS2253-install-entire-JBDS-BrandedProduct-feature-to-EclipsePlatformRuntimeBinary4.2.1-note-changed-icons-and-About-screen.png! -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2253: ---------------------------------- Respinning in Jenkins: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_trunk.... >=2775 I'd be happy to commit this to Alpha2 branch if we need to do a respin-b anyway. -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2253: ------------------------------------------- Could you summarize what this does ? looking at the patch it seem to remove version constraints for some and add in version constraints for others (log4j callback?) ? is/was m2e the only thing that was "locked" down ? About the screenshots then we have zero interest in adding the product branding feature to users installs. I don't see the point of that since it is not jbds 6 the user is running. I couldn't spot which of the screenshots would be what the user sees and should install ? It looked like there were *alot* of choices making it not easy to choose ? I guess eclipse marketplace would be the best way to deliver this ? -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2253: ----------------------------- Attachment: core-site-option1.png techpreview-site-option2.png techpreview-site-option1.png Three possible ways to implement [~maxandersen]'s latest idea of simply putting the Core Features feature as a tech preview on an update site: a) on the core site: !core-site-option1.png! b) on the tech preview site, option1: !techpreview-site-option1.png! c) on the tech preview site, option2: !techpreview-site-option2.png! -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2253 at 9/28/12 1:44 PM: ----------------------------------------------------------- Three possible ways to implement [~maxandersen]'s latest idea of simply putting the Core Features feature as a tech preview on an update site: a) on the core site: !core-site-option1.png! b) on the tech preview site, option1: -{color:red} [^techpreview-site-option1.png] rejected- c) on the tech preview site, option2: -{color:red} [^techpreview-site-option2.png] rejected- was (Author: nickboldt): Three possible ways to implement [~maxandersen]'s latest idea of simply putting the Core Features feature as a tech preview on an update site: a) on the core site: !core-site-option1.png! b) on the tech preview site, option1: !techpreview-site-option1.png! c) on the tech preview site, option2: !techpreview-site-option2.png! -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2253 at 9/28/12 1:46 PM: ----------------------------------------------------------- Three possible ways to implement [~maxandersen]'s latest idea of simply putting the Core Features feature as a tech preview on an update site: a) on the core site: !core-site-option1.png! -{color:red}b) on the tech preview site, option1: [^techpreview-site-option1.png] c) on the tech preview site, option2: [^techpreview-site-option2.png] {color}- was (Author: nickboldt): Three possible ways to implement [~maxandersen]'s latest idea of simply putting the Core Features feature as a tech preview on an update site: a) on the core site: !core-site-option1.png! -{color:red}b) on the tech preview site, option1: [^techpreview-site-option1.png] c) on the tech preview site, option2: [^techpreview-site-option2.png] rejected {color}- -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2253 at 9/28/12 1:51 PM: ----------------------------------------------------------- 8. Now, to update to newer upstream Eclipse.org deps and thereby prove that JBDS BYOE no longer restricts the version of egit from being only 2.0 or the version of m2e being only 1.2... [^JBDS2253-egit2.0-installed.png] ... add 1 or more of these sites to JBDS via Help > Install new: http://download.eclipse.org/egit/updates-nightly http://download.eclipse.org/m2e-wtp/milestones/0.16.0/ http://download.eclipse.org/technology/m2e/milestones/1.2/ http://download.eclipse.org/technology/m2e/releases/ http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/ http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... https://repository.sonatype.org/content/repositories/forge-sites/m2e/1.3.... [^JBDS2253-add-update-sites-for-m2e-and-egit.png] 9. Install the updates [^JBDS2253-install-updates-to-egit2.2-and-m2e1.3.png] 10. On restart: [^JBDS2253-install-updated-to-egit2.2-and-m2e1.3.png] 11. Note that the splash screen mentioned above has the correct version of JBDS superimposed over it, but the wrong image - see JBDS-2294: [^JBDS2253-splash-screen-has-version-6.0.0-but-wrong-image.png] was (Author: nickboldt): 8. Now, to update to newer upstream Eclipse.org deps and thereby prove that JBDS BYOE no longer restricts the version of egit from being only 2.0 or the version of m2e being only 1.2... !JBDS2253-egit2.0-installed.png! ... add 1 or more of these sites to JBDS via Help > Install new: http://download.eclipse.org/egit/updates-nightly http://download.eclipse.org/m2e-wtp/milestones/0.16.0/ http://download.eclipse.org/technology/m2e/milestones/1.2/ http://download.eclipse.org/technology/m2e/releases/ http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/ http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-w... https://repository.sonatype.org/content/repositories/forge-sites/m2e/1.3.... !JBDS2253-add-update-sites-for-m2e-and-egit.png! 9. Install the updates !JBDS2253-install-updates-to-egit2.2-and-m2e1.3.png! 10. On restart: !JBDS2253-install-updated-to-egit2.2-and-m2e1.3.png! 11. Note that the splash screen mentioned above has the correct version of JBDS superimposed over it, but the wrong image: !JBDS2253-splash-screen-has-version-6.0.0-but-wrong-image.png! -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2253: ---------------------------------- New category in JBDS Core site added to 4.0.0.Alpha2 branch. Respin: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_stable... >=35 -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2253: ----------------------------- Labels: respin-b (was: ) -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2253 at 10/8/12 2:09 PM: ----------------------------------------------------------- Latest sites for testing this: == JBDS 6.0.0.Alpha2 == * Internal: http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.0.Alpha2d.c... * External: https://devstudio.jboss.com/updates/6.0-staging/ == JBDS 6.0.0.Beta1 == * Internal: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk.... was (Author: nickboldt): Latest site for testing JBDS 6.0.0.Alpha2: http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.0.Alpha2d.c... It's also in trunk: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-6.0_trunk.... -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2253: ---------------------------------- No. Because then we'd be changing Eclipse into JBDS. {quote} [~maxandersen]: About the screenshots then we have zero interest in adding the *product branding feature* to users installs. I don't see the point of that since it is not jbds 6 the user is running. {quote} -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2253: ------------------------------------------- Tried using the staging site on an eclipse with JBT Alpha2 installed - that should work should it not ? But i'm getting this funky error: Cannot complete the install because of a conflicting dependency. Software being installed: JBoss Developer Studio (Core Features) 6.0.0.Beta1-v20121015-0254-B45 (com.jboss.jbds.product.feature.feature.group 6.0.0.Beta1-v20121015-0254-B45) Software currently installed: JBoss Portlet 1.4.0.Alpha2-v20120922-1553-B34 (org.jboss.tools.portlet.feature.feature.group 1.4.0.Alpha2-v20120922-1553-B34) Only one of the following can be installed at once: JBoss Portlet 1.4.0.Beta1-v20121013-2108-B36 (org.jboss.tools.portlet.ui 1.4.0.Beta1-v20121013-2108-B36) JBoss Portlet 1.4.0.Alpha2-v20120922-1553-B34 (org.jboss.tools.portlet.ui 1.4.0.Alpha2-v20120922-1553-B34) Cannot satisfy dependency: From: JBoss Developer Studio (Core Features) 6.0.0.Beta1-v20121015-0254-B45 (com.jboss.jbds.product.feature.feature.group 6.0.0.Beta1-v20121015-0254-B45) To: org.jboss.tools.portlet.feature.feature.group [1.4.0.Beta1-v20121013-2108-B36] Cannot satisfy dependency: From: JBoss Portlet 1.4.0.Alpha2-v20120922-1553-B34 (org.jboss.tools.portlet.feature.feature.group 1.4.0.Alpha2-v20120922-1553-B34) To: org.jboss.tools.portlet.ui [1.4.0.Alpha2-v20120922-1553-B34] Cannot satisfy dependency: From: JBoss Portlet 1.4.0.Beta1-v20121013-2108-B36 (org.jboss.tools.portlet.feature.feature.group 1.4.0.Beta1-v20121013-2108-B36) To: org.jboss.tools.portlet.ui [1.4.0.Beta1-v20121013-2108-B36] -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2253: ---------------------------------- BYOE should require that none of JBT be pre-installed. Thought that was clear from the issue description: {quote} 1. Launch clean Eclipse 4.2 2. Help > Install new 3. Add the following site (will be public, no VPN required) https://devstudio.jboss.com/updates/6.0-staging/central/core/ (target platform + product + extras) 4. Select all categorized features (or the "BYOE" category). Click Next. Install. Restart when prompted. {quote} If you already have pieces of JBT installed, like JBoss Portlet 1.4.0.Alpha2-v20120922-1553-B34 (org.jboss.tools.portlet.ui 1.4.0.Alpha2-v20120922-1553-B34), it needs to be the SAME version as the pieces of JBDS you're about to install (JBoss Portlet 1.4.0.Beta1-v20121013-2108-B36 (org.jboss.tools.portlet.ui 1.4.0.Beta1-v20121013-2108-B36)). If it's not, uninstall the old stuff and then install JBDS BYOE instead. Whole point of JBDS BYOE is to control the versions being installed. If you want to freely upgrade piecemeal, then use the JBT or JBDS site and cherry pick features, rather than installing the "JBDS (Core Features)" feature. -- 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

[ https://issues.jboss.org/browse/JBDS-2253?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2253 at 10/26/12 1:24 PM: ------------------------------------------------------------ If anyone running on JDK 1.7 and running into issue of not being able to create any "new projects" from "JBoss Central", and if you see these errors in the log: {code} !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.086 !MESSAGE Permission denied: connect !STACK 0 java.net.SocketException: Permission denied: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) at java.net.Socket.connect(Socket.java:579) at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.132 !MESSAGE Permission denied: connect !STACK 0 java.net.SocketException: Permission denied: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) at java.net.Socket.connect(Socket.java:579) at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.jboss.tools.project.examples 4 0 2012-10-23 15:28:27.165 !MESSAGE Premature end of file. !STACK 0 org.xml.sax.SAXParseException; Premature end of file. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:205) at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:348) at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:305) at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:53) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} There's a possibility you're running into a JDK7 bug related to IPV6. A workaround is to add the following VM argument at the end of /studio/jbdevstudio.ini config file: -Djava.net.preferIPv4Stack=true And restart JBDS was (Author: dchia): If anyone running on JDK 1.7 and running into issue of not being able to create any "new projects" from "JBoss Central", and if you see these errors in the log: !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.086 !MESSAGE Permission denied: connect !STACK 0 java.net.SocketException: Permission denied: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) at java.net.Socket.connect(Socket.java:579) at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.jboss.tools.central 4 0 2012-10-23 15:28:27.132 !MESSAGE Permission denied: connect !STACK 0 java.net.SocketException: Permission denied: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:75) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) at java.net.Socket.connect(Socket.java:579) at org.eclipse.ecf.provider.filetransfer.events.socket.SocketEventCreateUtil.createSocket(SocketEventCreateUtil.java:43) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:81) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:73) at org.eclipse.ecf.internal.provider.filetransfer.httpclient.ECFHttpClientProtocolSocketFactory.createSocket(ECFHttpClientProtocolSocketFactory.java:65) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1142) at org.eclipse.ecf.provider.filetransfer.httpclient.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:710) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:889) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.transfer(ECFExamplesTransport.java:319) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.performDownload(ECFExamplesTransport.java:246) at org.jboss.tools.project.examples.filetransfer.ECFExamplesTransport.download(ECFExamplesTransport.java:206) at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:186) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !ENTRY org.jboss.tools.project.examples 4 0 2012-10-23 15:28:27.165 !MESSAGE Premature end of file. !STACK 0 org.xml.sax.SAXParseException; Premature end of file. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:205) at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:348) at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:305) at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:53) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) There's a possibility you're running into a JDK7 bug related to IPV6. A workaround is to add the following VM argument at the end of /studio/jbdevstudio.ini config file: -Djava.net.preferIPv4Stack=true And restart 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