[JBoss JIRA] (JBDS-3271) Cordova App Splash Screen Support
by Rodney Russ (JIRA)
[ https://issues.jboss.org/browse/JBDS-3271?page=com.atlassian.jira.plugin.... ]
Rodney Russ commented on JBDS-3271:
-----------------------------------
@burrsutter are you saying that this Jira should be done in conjunction with (or after FH-53)? Or are you just thanking [~gercan] for getting FH-53 put in so both tools stay consistent? Just asking as the former would indicate that we should defer this while the later would have us include it now.
> Cordova App Splash Screen Support
> ---------------------------------
>
> Key: JBDS-3271
> URL: https://issues.jboss.org/browse/JBDS-3271
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aerogear-hybrid, requirements
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Fix For: 9.0.0.CR1
>
>
> As a HTML5+Cordova mobile app developer, I need to change the splash screen associated with the application launch.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19343) integration tests fetch their required runtimes if not present in the cache folder?
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19343:
-----------------------------------
Fix Version/s: 4.3.0.Alpha2
> integration tests fetch their required runtimes if not present in the cache folder?
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19343
> URL: https://issues.jboss.org/browse/JBIDE-19343
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server, testing-tools
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Fix For: 4.3.0.Alpha2
>
>
> There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html )
> Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests.
> There are a number of such phase bindings in this test:
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/...
> And I think this step can be skipped w/ *-DskipTests*.
> But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder?
> Here are some console log snipped from builds 119 - 123:
> {code}
> 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1]
> 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1]
> 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1]
> {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4....
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration
by Rodney Russ (JIRA)
[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ]
Rodney Russ commented on JBDS-3273:
-----------------------------------
[~fbricon] do you have what you need to be able to devel_ack this requirement?
> JBoss Central: Automatic upstream quickstart integration
> ---------------------------------------------------------
>
> Key: JBDS-3273
> URL: https://issues.jboss.org/browse/JBDS-3273
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 9.0.0.Alpha2
>
>
> Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19184:
---------------------------------------
We mirror only angularjs-eclipse feature without tern, so if there were no changes in angularjs-eclipse itself, we are fine then.
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Victor Rubezhny
> Priority: Blocker
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JS projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3285) Git: Easy Import
by Rodney Russ (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Rodney Russ commented on JBDS-3285:
-----------------------------------
[~burrsutter] (and [~maxandersen]) should we give Easyimport a go in JBDS/JBoss Tools? Is this sufficient for you Burr, or are you looking for more?
> Git: Easy Import
> ----------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Burr Sutter
> Labels: usability
> Fix For: 9.0.x
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively):
> {quote}
> Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace".
> We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough.
> There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport.
> There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point.
> I invite you to give it a try, and to report issues here.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19343) integration tests fetch their required runtimes if not present in the cache folder?
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19343:
----------------------------------
Summary: integration tests fetch their required runtimes if not present in the cache folder?
Key: JBIDE-19343
URL: https://issues.jboss.org/browse/JBIDE-19343
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, server, testing-tools
Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
Reporter: Nick Boldt
There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html )
Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests.
There are a number of such phase bindings in this test:
https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/...
And I think this step can be skipped w/ *-DskipTests*.
But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder?
Here are some console log snipped from builds 119 - 123:
{code}
11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1]
13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1]
16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1]
{code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4....
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-19342:
-----------------------------------
Summary: Update code to cope with generics added to org.eclipse.core.runtime package API
Key: JBIDE-19342
URL: https://issues.jboss.org/browse/JBIDE-19342
Project: Tools (JBoss Tools)
Issue Type: Task
Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, build, cdi, cdi-extensions, central, common/jst/core, cordovasim, discovery, forge, freemarker, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing
Affects Versions: 4.3.0.Alpha2
Reporter: Fred Bricon
We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API.
>From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html :
{quote}
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021
Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25
Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common:
1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)"
2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented.
3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All)
4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature.
Typical change:
Old:
{code}
public Object getAdapter(Class adapter) {
if (ICompilationUnit.class.equals(adapter))
return getCompilationUnit();
return null;
}
{code}
New:
{code}
public <T> T getAdapter(Class<T> adapter) {
if (ICompilationUnit.class.equals(adapter))
return adapter.cast(getCompilationUnit());
return null;
}
{code}
5. Update implementations of IAdapterFactory
Hint for 4. & 5.:
- Open Type Hierarchy on IAdaptable, etc.
- In the view menu, select a working set that contains your projects
- In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy)
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months