[JBoss JIRA] (JBIDE-18623) Examples are not working in offline mode
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18623?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-18623:
--------------------------------------
So - the issue here is:
1) The re-use of a beta3 workspace - we do not support users re-using Beta3 workspaces
and
2) Errors in the quickstarts - these are to be fixed upstream
Is that all?
> Examples are not working in offline mode
> ----------------------------------------
>
> Key: JBIDE-18623
> URL: https://issues.jboss.org/browse/JBIDE-18623
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.2.0.CR2
> Environment: JBT 4.2.0.CR2a, JBDS 8.0.0.CR2a
> Reporter: Radim Hopp
> Assignee: Fred Bricon
>
> After executing offline groovy script and configuring JBT/JBDS to use generated examples and maven repository, project examples are not shown in JBoss Central.
> Warning is logged, when user tries to refresh "Start from sample" section (this one is from JBDS):
> {noformat}Invalid URL: http://download.jboss.org/jbosstools/examples/project-examples-jbds80.Bet...
> Groovy script has errors generating few examples (JBIDE-18582), but I think this is not relevant to this issue. What can be relevant is PR from JBIDE-18589 - switching descriptors from Beta3 to GA.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18594) Create a consistent /staging/ URL for JBT
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18594?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18594:
------------------------------------
Old way was to run a script to regen those two files. Your new approach requires manually updating this file, so we can just update this section of the rel guide:
{code:title=https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_guide/8.0/JBT_4.2.0_Staging_For_QE.adoc#regenerate-composite-site-metadata-for-staged-updates}
=== Regenerate composite site metadata for staged updates
Update files __http://download.jboss.org/jbosstools/updates/staging/luna/composite*.xml__ , with SFTP/SCP via command-line or your
favourite SFTP GUI client (such as Eclipse RSE).
Optionally, run this script, then verify the resulting composite site:
[source,bash]
----
~/tru/buildci/util/cleanup/jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --dirs-to-scan updates/staging/luna
firefox "view-source:http://download.jboss.org/jbosstools/updates/staging/luna/com..."
----
{code}
> Create a consistent /staging/ URL for JBT
> -----------------------------------------
>
> Key: JBIDE-18594
> URL: https://issues.jboss.org/browse/JBIDE-18594
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.CR2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> Currently, the site we use for staging are organized much differently from what will be shipped to end-users. This results in making tests against staging behaving differently to how release will believe, so making tests confusing, error-prone and useless.
> We need to rework the staging process so that its output is similar to what will be the output of a release:
> * updates/staging/luna , compositing
> ** target-platform
> ** JBT core
> ** Central TP
> * earlyaccess site (location still to be decided?), currently 'http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget...
> Those sites are the one that need to be used respectively for jboss.discovery.site.ul and jboss.discovery.earlyaccess.site.url in ide-config.properties
> Then the process of releasing to development isn't much more than a _cp -r_ and some _sed /staging/development/_
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18628) NPE when creating Connection Profile using forge wizard
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18628?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-18628:
------------------------------------
Here is my screencast: http://youtu.be/8JGk7HjXM0M
> NPE when creating Connection Profile using forge wizard
> -------------------------------------------------------
>
> Key: JBIDE-18628
> URL: https://issues.jboss.org/browse/JBIDE-18628
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR2
> Reporter: Pavol Srna
> Priority: Blocker
> Labels: regression
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:459)
> at java.util.Properties.setProperty(Properties.java:166)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.createProperties(ConnectionProfileManagerImpl.java:172)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveExistingProfile(ConnectionProfileManagerImpl.java:82)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfile(ConnectionProfileManagerImpl.java:73)
> at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfiles(ConnectionProfileManagerImpl.java:142)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.database.tools.connections.ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.saveConnectionProfiles(ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.java)
> at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl.execute(CreateConnectionProfileCommandImpl.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.execute(CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.java)
> at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.execute(CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.java)
> at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:113)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18594) Create a consistent /staging/ URL for JBT
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18594?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-18594 at 10/15/14 9:28 AM:
------------------------------------------------------------------
1. Let just stop generating them if they generale wrong content
2. oops, sorry. I'm updating it. => I just looked at it and it seems ok. Did you already fix it?
was (Author: mickael_istria):
1. Let just stop generating them if they generale wrong content
2. oops, sorry. I'm updating it.
> Create a consistent /staging/ URL for JBT
> -----------------------------------------
>
> Key: JBIDE-18594
> URL: https://issues.jboss.org/browse/JBIDE-18594
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.CR2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> Currently, the site we use for staging are organized much differently from what will be shipped to end-users. This results in making tests against staging behaving differently to how release will believe, so making tests confusing, error-prone and useless.
> We need to rework the staging process so that its output is similar to what will be the output of a release:
> * updates/staging/luna , compositing
> ** target-platform
> ** JBT core
> ** Central TP
> * earlyaccess site (location still to be decided?), currently 'http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget...
> Those sites are the one that need to be used respectively for jboss.discovery.site.ul and jboss.discovery.earlyaccess.site.url in ide-config.properties
> Then the process of releasing to development isn't much more than a _cp -r_ and some _sed /staging/development/_
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18247) Eclipse is blocked for several minutes on startup when HTTP/80 is firewalled
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18247?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18247:
----------------------------------------
Labels: respin-b (was: )
> Eclipse is blocked for several minutes on startup when HTTP/80 is firewalled
> ----------------------------------------------------------------------------
>
> Key: JBIDE-18247
> URL: https://issues.jboss.org/browse/JBIDE-18247
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Reporter: Pavol Srna
> Assignee: Fred Bricon
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.CR2
>
> Attachments: console-log.txt, eclipse-firewalled-jstack.txt, stack-cr1a.txt
>
>
> Imagine a situation where you are behind firewall which blocks HTTP/80.
> You unpack fresh eclipse and install jbosstools. After installation you are prompted to restart eclipse. But eclipse is blocked at startup for several minutes - there is blocking central thread which cannot access web because of firewall.
> If you don't forget to setup proxy in eclipse you won't experience this. But otherwise you will be stucked on eclipse startup. And that is bad user experience.
> I would suggest to fix it so, that eclipse can at least start - just central content is not loaded when http is blocked.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18247) Eclipse is blocked for several minutes on startup when HTTP/80 is firewalled
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18247?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18247:
----------------------------------------
Priority: Critical (was: Major)
> Eclipse is blocked for several minutes on startup when HTTP/80 is firewalled
> ----------------------------------------------------------------------------
>
> Key: JBIDE-18247
> URL: https://issues.jboss.org/browse/JBIDE-18247
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Reporter: Pavol Srna
> Assignee: Fred Bricon
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.CR2
>
> Attachments: console-log.txt, eclipse-firewalled-jstack.txt, stack-cr1a.txt
>
>
> Imagine a situation where you are behind firewall which blocks HTTP/80.
> You unpack fresh eclipse and install jbosstools. After installation you are prompted to restart eclipse. But eclipse is blocked at startup for several minutes - there is blocking central thread which cannot access web because of firewall.
> If you don't forget to setup proxy in eclipse you won't experience this. But otherwise you will be stucked on eclipse startup. And that is bad user experience.
> I would suggest to fix it so, that eclipse can at least start - just central content is not loaded when http is blocked.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18594) Create a consistent /staging/ URL for JBT
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18594?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18594:
----------------------------------------
1. Let just stop generating them if they generale wrong content
2. oops, sorry. I'm updating it.
> Create a consistent /staging/ URL for JBT
> -----------------------------------------
>
> Key: JBIDE-18594
> URL: https://issues.jboss.org/browse/JBIDE-18594
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.CR2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> Currently, the site we use for staging are organized much differently from what will be shipped to end-users. This results in making tests against staging behaving differently to how release will believe, so making tests confusing, error-prone and useless.
> We need to rework the staging process so that its output is similar to what will be the output of a release:
> * updates/staging/luna , compositing
> ** target-platform
> ** JBT core
> ** Central TP
> * earlyaccess site (location still to be decided?), currently 'http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget...
> Those sites are the one that need to be used respectively for jboss.discovery.site.ul and jboss.discovery.earlyaccess.site.url in ide-config.properties
> Then the process of releasing to development isn't much more than a _cp -r_ and some _sed /staging/development/_
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18594) Create a consistent /staging/ URL for JBT
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18594?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18594:
------------------------------------
[~mickael_istria] 2 problems with PR 421/422:
1. jbosstools/updates/staging/luna/composite*.xml are *generated* files, so your manual changes will be overwritten.
2. you forgot to update BOTH composite*.xml files - you only did compositeContent.xml :(
Changes to jbosstools/configuration/ide-config.properties look good provided that you copied/moved content to the new paths.
https://github.com/jbdevstudio/jbdevstudio-devdoc/pull/113 looks OK but only skimmed it - need to actually test it when we do the next release. :)
> Create a consistent /staging/ URL for JBT
> -----------------------------------------
>
> Key: JBIDE-18594
> URL: https://issues.jboss.org/browse/JBIDE-18594
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.CR2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> Currently, the site we use for staging are organized much differently from what will be shipped to end-users. This results in making tests against staging behaving differently to how release will believe, so making tests confusing, error-prone and useless.
> We need to rework the staging process so that its output is similar to what will be the output of a release:
> * updates/staging/luna , compositing
> ** target-platform
> ** JBT core
> ** Central TP
> * earlyaccess site (location still to be decided?), currently 'http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget...
> Those sites are the one that need to be used respectively for jboss.discovery.site.ul and jboss.discovery.earlyaccess.site.url in ide-config.properties
> Then the process of releasing to development isn't much more than a _cp -r_ and some _sed /staging/development/_
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months