[JBoss JIRA] (JBIDE-18217) Central editor asynchrnously call InstallationChecker
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18217?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-18217.
------------------------------
> Central editor asynchrnously call InstallationChecker
> -----------------------------------------------------
>
> Key: JBIDE-18217
> URL: https://issues.jboss.org/browse/JBIDE-18217
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> Currently, Central editor calls directly InstallationChecker, which depending on the connection speed and reliability, can take some time. If connection is slow, then the UI is frozen until the request is either rejected or accepted.
> Instead, Central Editor should invoke InstallationChecker asynchronously to open faster.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18639) For JBIDE 4.2.0.Final: Prepare for Final/GA release [OpenShift]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18639?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18639:
------------------------------------------
{code}
[INFO] openshift.all ..................................... SUCCESS [0.400s]
[INFO] openshift.plugins ................................. SUCCESS [0.007s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [2.021s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [1.343s]
[INFO] org.jboss.tools.openshift.express.core ............ SUCCESS [4.305s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.554s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [2.641s]
[INFO] openshift.tests ................................... SUCCESS [0.007s]
[INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [13.061s]
[INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [27.592s]
[INFO] openshift.features ................................ SUCCESS [0.006s]
[INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.137s]
[INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.154s]
[INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.096s]
[INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.108s]
[INFO] openshift.site .................................... SUCCESS [25.407s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7:01.619s
[INFO] Finished at: Thu Oct 16 15:05:02 CEST 2014
[INFO] Final Memory: 100M/1416M
[INFO] ------------------------------------------------------------------------
{code}
> For JBIDE 4.2.0.Final: Prepare for Final/GA release [OpenShift]
> ---------------------------------------------------------------
>
> Key: JBIDE-18639
> URL: https://issues.jboss.org/browse/JBIDE-18639
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Final
>
>
> For JBIDE 4.2.0.Final [OpenShift]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA.
> [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT
> mvn clean verify -Dtpc.version=4.41.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18623) Examples are not working in offline mode
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18623?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18623:
--------------------------------
Labels: respin-b (was: respin-a)
> 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
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.2.0.CR2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-18623) Examples are not working in offline mode
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18623?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18623:
----------------------------------------
Labels: respin-a (was: )
> 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
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-18623) Examples are not working in offline mode
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18623?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18623:
----------------------------------------
Priority: Blocker (was: Major)
> 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
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-18623) Examples are not working in offline mode
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18623?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18623:
----------------------------------------
Fix Version/s: 4.2.0.CR2
> 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
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> 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, 6 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 closed JBIDE-18594.
------------------------------
Closing, nothing to QE here.
> 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, respin-b
> 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, 6 months