[JBoss JIRA] (JBIDE-17818) Visual Editor: Need to handle external html / htm files
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17818?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17818:
------------------------------------------------
https://github.com/jbosstools/jbosstools-vpe/pull/294 - pull request for respin. Waiting for +1.
> Visual Editor: Need to handle external html / htm files
> -------------------------------------------------------
>
> Key: JBIDE-17818
> URL: https://issues.jboss.org/browse/JBIDE-17818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Reporter: Ilya Buziuk
> Assignee: Konstantin Marmalyukov
> Labels: new_and_noteworthy, respin-a
> Fix For: 4.2.1.CR1
>
>
> Now VPE / HTML Preview can handle only workspace's files. Need to add external files support
> When I open html pages outside eclipse workspace I get an error stating VPE preview cannot open the file.
> That is not ok.
> preview should be able to just fine preview the html no matter where the content is from and if it is because some current limitation about preview then users should at least be able to edit files even if external to the workspace.
> by external to workspace I mean what is opened with File > Open File...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (JBDS-3240) Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3240?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3240:
-----------------------------
Fix Version/s: 8.0.1.GA
> Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central
> --------------------------------------------------------------------
>
> Key: JBDS-3240
> URL: https://issues.jboss.org/browse/JBDS-3240
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.GA
> Reporter: Marek Novotny
> Assignee: Fred Bricon
> Fix For: 8.0.1.GA
>
>
> JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default.
> For instance I click on HTML5 project in Start from Scratch in JBoss Central:
> it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (JBDS-3240) Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3240?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3240:
-----------------------------
Summary: Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central (was: JBDS 8 aka JBoss Central provide by default old EAP/WFK archetypes)
> Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central
> --------------------------------------------------------------------
>
> Key: JBDS-3240
> URL: https://issues.jboss.org/browse/JBDS-3240
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.GA
> Reporter: Marek Novotny
> Assignee: Fred Bricon
>
> JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default.
> For instance I click on HTML5 project in Start from Scratch in JBoss Central:
> it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months
[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18772:
------------------------------------
PR 116 is already merged. -1 for PR 117.
> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.x
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 6 months