[JBoss JIRA] (JBIDE-17994) HTML preview should support projects with no webroot defined (i.e. non-wtp projects)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17994?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-17994:
----------------------------------------
Cordova projects may have either *org.eclipse.thym.core.HybridAppNature* or *org.jboss.tools.aerogear.hybrid.core.HybridAppNature* nature. So for such projects we can use "www" folder (if it exists) as a webroot. I guess we can't depend on Thym plugins so we have to hardcode these nature IDs in common (the util class which searches for webroot is placed in common module).
But what about projects w/o cordova natures? Users may import cordova projects as a plain eclipse project. Should we look for config.xml in the project root and "www" folder (if exists) for such projects?
[~maxandersen], [~gercan], what do you think?
> HTML preview should support projects with no webroot defined (i.e. non-wtp projects)
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-17994
> URL: https://issues.jboss.org/browse/JBIDE-17994
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: visual-page-editor-core
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.CR1
>
>
> 1. We should support cordova projects (www folder) automatically
> 2. Understand VPE properties for defining/override web root
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17993) Default ionic js/css references for ionic palette components
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-17993:
--------------------------------------
Summary: Default ionic js/css references for ionic palette components
Key: JBIDE-17993
URL: https://issues.jboss.org/browse/JBIDE-17993
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.2.0.CR1
Let's add the following default references to the JS/CSS palette:
{code}
<link href="lib/ionic/css/ionic.css" rel="stylesheet">
<!-- ionic/angularjs js -->
<script src="lib/ionic/js/ionic.bundle.js"></script>
{code}
so these links will be inserted into the page when dropping an ionic component from the Palette with the "add js/css references" checkbox checked.
But I'm not sure we can add the comment <!-- ionic/angularjs js --> in our preferences too.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17944) BrowserSim: Use http: protocol instead of file: for accessing local files
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17944?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-17944 at 7/29/14 2:28 PM:
-----------------------------------------------------------------
ionic projects yes, they are for CodovaSim, right. But in general for plain HTML projects it could be useful.
Ionic (cordova) example: https://github.com/driftyco/ionic-demo
was (Author: akazakov):
ionic projects yes, they are for CodovaSim, right. But in general for plain HTML projects it could be useful.
Ionic (cordova) examples: http://ionicframework.com/examples/
> BrowserSim: Use http: protocol instead of file: for accessing local files
> -------------------------------------------------------------------------
>
> Key: JBIDE-17944
> URL: https://issues.jboss.org/browse/JBIDE-17944
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
>
> Currently, BrowserSim works through file: protocol but this protocol doesn't work well with paths relative to the webroot (which start with "/").
> So if a local file contains any links to local resources (css, js, ...) via relative paths then these resources are not available in BrowserSim.
> For example all official ionic example projects use such paths. It makes "open with BrowserSim" feature useless for those projects.
> It would be great if BrowserSim uses http: as our HTML5 preview does.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR
by Patrick Decat (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ]
Patrick Decat commented on JBIDE-17724:
---------------------------------------
Hi [~maxandersen], here is a test case to reproduce the issue:
# Unzip the attached project structure (stripped down from an existing project)
# Run 'mvn clean install eclipse:clean eclipse:eclipse' at the root
# Import existing projects into eclipse luna with JBoss Tools
# Deploy to a "JBoss Enterprise Application Platform 5.x" runtime
# Make a change to {{MyController.java}} inside the project-war webapp => the change is hot deployed
# Make a change to {{MySecondController.java}} inside the project-module dependency => the full WAR is undeployed then redeployed
> Changes cause full redeployment of exploded WAR
> -----------------------------------------------
>
> Key: JBIDE-17724
> URL: https://issues.jboss.org/browse/JBIDE-17724
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Environment: Windows 8.1 x64
> Java 7u51 x64
> Luna x64
> Reporter: Cody Lerum
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.2.0.Beta3, 4.2.0.CR1
>
> Attachments: JBIDE-17724-JBossEAP5-testcase.tar.bz2, workspace.zip
>
>
> After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final
> This prevents any updating of JSF resources or debugging java code.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month