[JBoss JIRA] (JBIDE-18771) BrowserSim: Create new navigation bar and buttons for iphone 6 / 6+ skins
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18771?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-18771:
-------------------------------------
< Ilya Buziuk this just reuses existing iphone 4 resources we got and setup the right dimensions, correct ? (since still waiting for legal for approving the more realistic skins, right?).
[~maxandersen], PRs for this issue could be treated as a dead code - it doesn't used anywhere and can't break anything (including API). I have tested this IOS 8 navigation bar using iphone 4 !sample.png|thumbnail! and verify that everything works fine but I didn't apply it for that skin. This navbar will be used *only* for iphone 6 / iphone 6+ skin.
< (it does not change api's, just add a new setup to already dynamic list does it not ?)
precisely^
> BrowserSim: Create new navigation bar and buttons for iphone 6 / 6+ skins
> -------------------------------------------------------------------------
>
> Key: JBIDE-18771
> URL: https://issues.jboss.org/browse/JBIDE-18771
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim, cordovasim
> Affects Versions: 4.2.0.Final
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: nav-mockup.png, sample.png
>
>
> Navigation bar and buttons will be created from iphone 6 IOS 8 screenshots
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18812) Unable to build Web Services
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18812?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18812:
----------------------------------------
Seems like you're not using the latest version of the parent pom. Can you try a local build with the "-U" option to make sure you get it? CI job seems to be working fine...
> Unable to build Web Services
> ----------------------------
>
> Key: JBIDE-18812
> URL: https://issues.jboss.org/browse/JBIDE-18812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
> Priority: Blocker
> Fix For: 4.3.0.Alpha1
>
>
> When running a {{mvn clean verify}} on MacOSX, I get the following errors:
> {code}
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> [INFO] Scanning for projects...
> [WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
> [WARNING] Could not transfer metadata org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-server (${jbosstools-server-site}): No connector available to access repository jbosstools-server (${jbosstools-server-site}) of type p2 using the available factories WagonRepositoryConnectorFactory
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
> [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_maste...
> [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas...
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.core/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.ui/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
> [INFO] Resolving class path of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.ui:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.ui/pom.xml
> [INFO] Computing target platform for MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.jaxrs.core:1.8.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.jaxrs.core/pom.xml
> [ERROR] Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86} -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.RuntimeException: Could not determine SWT implementation fragment bundle for environment {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86}
> at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.fixSWT(ProjectorResolutionStrategy.java:155)
> at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:95)
> at org.eclipse.tycho.p2.util.resolution.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:166)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:103)
> at org.eclipse.tycho.p2.resolver.P2DependencyResolver.doResolveDependencies(P2DependencyResolver.java:352)
> at org.eclipse.tycho.p2.resolver.P2DependencyResolver.resolveDependencies(P2DependencyResolver.java:325)
> at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:107)
> at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> ... 11 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3191:
--------------------------------------
{code}How does the code that builds the p2.inf or feature.xml or .product file know to insert ONE or TWO URLs in there? How are you going to programmatically toggle the inclusion of the 8.0-development site based on BUILD_ALIAS=GA ?{code}
This is indeed tricky to implement as build configuration/build steps/p2 inf directive.
What I have in mind is that this become controlled via a plugin directly, such as com.jboss.devstudio.core. This plugin would have an IStartup extension that would start a background job when starting the product, and that would run some basic checks by introspecting the runtime directly.
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Fix For: 8.0.1.GA
>
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associate.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (TOOLSDOC-556) MobileDev How To: Create Your First Mobile Web App
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-556?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-556:
-------------------------------------
Sprint: 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov) (was: 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov), 2014/S22 (24-Nov > 7-Dec))
> MobileDev How To: Create Your First Mobile Web App
> --------------------------------------------------
>
> Key: TOOLSDOC-556
> URL: https://issues.jboss.org/browse/TOOLSDOC-556
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Reporter: Michelle Murray
> Assignee: Aakanksha Singh
> Fix For: 4.2.0.Final
>
>
> Instructions to cover in this How To:
> 1. Create a HTML5 Project
> 2. Build and Deploy the Application
> 3. View the Application with BrowserSim
> 4. Enable LiveReload for BrowserSim
> 5. Change the Application
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (TOOLSDOC-482) Add info on new download feature for enterprise servers
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-482?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-482:
-------------------------------------
Sprint: 2014/S5 (31-Mar > 13-Apr), 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov) (was: 2014/S5 (31-Mar > 13-Apr), 2014/S20 (27-Oct > 9-Nov), 2014/S21 (10-Nov > 23-Nov), 2014/S22 (24-Nov > 7-Dec))
> Add info on new download feature for enterprise servers
> -------------------------------------------------------
>
> Key: TOOLSDOC-482
> URL: https://issues.jboss.org/browse/TOOLSDOC-482
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: User Guide - JBoss Server Tools
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Aakanksha Singh
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Within IDE could always download JBoss AS servers. That functionality has now been extended to downloading JBoss EAP servers.
> Writer task: Edit topic 23487, which was previously solely for JBT. Add conditions as necessary to the intro, steps and note so that they accommodate the JBDS/EAP workflow. Make two new screen caps for JBDS/EAP and use conditions to add then to the existing <imageobject> tags. Add this topic to the JBDS User Guide content spec after Features Overview [22815].
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18806) When discovery URL is not set, "Software/Updates" page is silently hidden
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18806?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-18806.
------------------------------
Assignee: Nick Boldt (was: Max Rydahl Andersen)
Resolution: Done
The missing tab is fixed as of 8.0.1.CR1-v20141121-2335-B332: [^JBIDE18806-fixed-jbds.png]
As to the hardcoded jbosstools.version and devstudio.version variables, they can either be set in plugins or they can be set in the parent pom used to build the aggregates and JBDS. My vote is for the parent pom since they're needed globally, and that way won't be forgotten (or half-forgotten) when we move up a version... like we did for 4.2.1.CR1 (but not 8.0.1.CR1).
> When discovery URL is not set, "Software/Updates" page is silently hidden
> -------------------------------------------------------------------------
>
> Key: JBIDE-18806
> URL: https://issues.jboss.org/browse/JBIDE-18806
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
> Attachments: JBDS801-central-no-software-update-tab.png, JBIDE18806-fixed-jbds.png
>
>
> With latest CI build (in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... ), Central editor seems to miss the "Software/Updates" tab.
> Log mentions an error, which doesn't seem related at first sight:
> {code:none}
> !SESSION 2014-11-21 15:51:47.555 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.8.0_11
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.jboss.tools.project.examples 4 0 2014-11-21 15:53:24.762
> !MESSAGE All attempts to discover connectors have failed
> !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2014-11-21 15:53:24.762
> !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> !STACK 0
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
