[JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19568:
-----------------------------------
Fix Version/s: 4.3.x
> Disable the "Check for update" button while a check for update is in progress
> -----------------------------------------------------------------------------
>
> Key: JBIDE-19568
> URL: https://issues.jboss.org/browse/JBIDE-19568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.x
>
>
> while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog.
> In error log it was reporting this:
> org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/.
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116)
> at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284)
> at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191)
> at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
> at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
> at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
> at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> would have expected we told the user about this error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3199:
-----------------------------------
[~ldimaggio] re re ping?
> Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3199
> URL: https://issues.jboss.org/browse/JBDS-3199
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
>
> These "kitchensink" strings are retained:
> grep -ir kitchen *
> main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source>
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS"
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true"
> test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS"
> test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBDS-3207) Importing of Seam 2 Remoting Helloworld example shows errors in JBDS 8
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3207?page=com.atlassian.jira.plugin.... ]
Fred Bricon closed JBDS-3207.
-----------------------------
Fix Version/s: 9.0.0.Beta1
(was: 9.0.x)
Resolution: Cannot Reproduce Bug
> Importing of Seam 2 Remoting Helloworld example shows errors in JBDS 8
> ----------------------------------------------------------------------
>
> Key: JBDS-3207
> URL: https://issues.jboss.org/browse/JBDS-3207
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 8.0.0.GA
> Environment: JBoss Developer Studio
> Version: 8.0.0.GA
> Build id: GA-v20141020-1042-B317
> Build date: 20141020-1042
> Reporter: Marek Novotny
> Assignee: Fred Bricon
> Fix For: 9.0.0.Beta1
>
>
> The import of Seam Remoting Helloword example results with 2 errors on helloworld-ejb project:
> {code}
> Cannot change version of project facet EJB Module to 2.1. helloworld-ejb line 1 Maven Java EE Configuration Problem
> One or more constraints have not been satisfied. helloworld-ejb line 1 Maven Java EE Configuration Problem
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-18459) MacBook Pro Retina Display Font
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18459?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-18459.
---------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.2.x)
(was: 4.3.x)
Resolution: Out of Date
Font issue not a problem in HTML-based central in beta1. Resolving as out-of-date.
> MacBook Pro Retina Display Font
> -------------------------------
>
> Key: JBIDE-18459
> URL: https://issues.jboss.org/browse/JBIDE-18459
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, central, forge, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.CR1
> Environment: MacBook Pro 15" mid-2014 Retina set at "Best for Display" (default)
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta1
>
> Attachments: Screenshot 2014-09-30 13.58.59.png, Screenshot 2014-09-30 14.04.34.png, Screenshot 2014-10-03 16.44.07.png
>
>
> Some fonts are "fuzzy".
> Screenshot 1
> - under "JBoss Buzz"
> - under "Start from a sample" and Portal Applications
> - the open cheatsheet.xml (AngularJS Forge)
> Screenshot 2
> - jQuery Mobile and Ionic Palettes
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19248) Import examples from git repo
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19248?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19248:
--------------------------------
Fix Version/s: LATER
(was: 4.3.0.Beta1)
> Import examples from git repo
> -----------------------------
>
> Key: JBIDE-19248
> URL: https://issues.jboss.org/browse/JBIDE-19248
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: project-examples
> Affects Versions: 4.2.2.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: LATER
>
>
> Currently, project examples for wfk and eap needs to be assembled individually into zip files and downloaded separately.
> It'd be easier, from a "go offline" scenario and also in general maintenance context, to be able to import the examples from git
> Project examples descriptor (or another mechanism) could define :
> - git repo url
> - sha1/tag
> - example folder
> The import process would then :
> - clone the repo to a user defined location (~/.jbosstools/offline) by default if it doesn't exist, or update the repo if it exists
> - traverse the sha1/tag tree to extract the chosen examples and copy them to another user defined location.
> Once the repo has been cloned, every project creation would likely be very, very fast
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19753) Investigate if Arquillian works fine with Sapphire 9.0.0
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19753?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19753:
----------------------------------------
This in just a question of compatibility. Eclipse Mars update site contains Sapphire 9. If a user installs Spphire from Eclipse Mars using default update site he/she won't able to install/use JBT plugins which requires Sapphire 8.
> Investigate if Arquillian works fine with Sapphire 9.0.0
> --------------------------------------------------------
>
> Key: JBIDE-19753
> URL: https://issues.jboss.org/browse/JBIDE-19753
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: arquillian
> Reporter: Alexey Kazakov
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> Currently JBT TP includes Sapphire 9.0.0.201408261741 (available in Eclipse Mars M6 update site).
> I just checked the latest nightly build from https://hudson.eclipse.org/sapphire/job/9.0.x/ and I see that some Sapphire API has been changed. We have compilation problems in Batch because of it.
> Sapphire is gonna be updated in Mars M7 - https://www.eclipse.org/forums/index.php/t/1066214/
> And we have to switch to the new API in Batch in JBT 4.3.0.Beta1 and update Sapphire in our TP.
> So, we also should make sure that Arquillian supports the latest Sapphire 9.0.0.x. Otherwise we will get a problem with two components (Batch and Arquillian) which depends on two incompatible versions of Sapphire.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19753) Investigate if Arquillian works fine with Sapphire 9.0.0
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19753?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-19753:
---------------------------------------
In https://www.eclipse.org/forums/index.php/t/890531/ Konstantin claims that Sapphire 8 will be compatible with Mars.
{quote}
Based on the feedback received, the minimum Java version for Sapphire 9 and beyond has been changed to Java 8. As a consequence of this change, support for Indigo, Juno and Kepler was dropped (Eclipse added Java 8 support in Luna). Sapphire 8.x will continue to support Java 6 and all Eclipse releases going back to Indigo.
{quote}
> Investigate if Arquillian works fine with Sapphire 9.0.0
> --------------------------------------------------------
>
> Key: JBIDE-19753
> URL: https://issues.jboss.org/browse/JBIDE-19753
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: arquillian
> Reporter: Alexey Kazakov
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> Currently JBT TP includes Sapphire 9.0.0.201408261741 (available in Eclipse Mars M6 update site).
> I just checked the latest nightly build from https://hudson.eclipse.org/sapphire/job/9.0.x/ and I see that some Sapphire API has been changed. We have compilation problems in Batch because of it.
> Sapphire is gonna be updated in Mars M7 - https://www.eclipse.org/forums/index.php/t/1066214/
> And we have to switch to the new API in Batch in JBT 4.3.0.Beta1 and update Sapphire in our TP.
> So, we also should make sure that Arquillian supports the latest Sapphire 9.0.0.x. Otherwise we will get a problem with two components (Batch and Arquillian) which depends on two incompatible versions of Sapphire.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19753) Investigate if Arquillian works fine with Sapphire 9.0.0
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19753?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19753:
----------------------------------------
Sapphire 9 is targeted for Mars. I'm not sure we can safely stick with Sapphire 8 for JBT 4.3.0.
> Investigate if Arquillian works fine with Sapphire 9.0.0
> --------------------------------------------------------
>
> Key: JBIDE-19753
> URL: https://issues.jboss.org/browse/JBIDE-19753
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: arquillian
> Reporter: Alexey Kazakov
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> Currently JBT TP includes Sapphire 9.0.0.201408261741 (available in Eclipse Mars M6 update site).
> I just checked the latest nightly build from https://hudson.eclipse.org/sapphire/job/9.0.x/ and I see that some Sapphire API has been changed. We have compilation problems in Batch because of it.
> Sapphire is gonna be updated in Mars M7 - https://www.eclipse.org/forums/index.php/t/1066214/
> And we have to switch to the new API in Batch in JBT 4.3.0.Beta1 and update Sapphire in our TP.
> So, we also should make sure that Arquillian supports the latest Sapphire 9.0.0.x. Otherwise we will get a problem with two components (Batch and Arquillian) which depends on two incompatible versions of Sapphire.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years