[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-14610:
----------------------------------
Fix Version/s: 4.3.x
(was: 4.2.x)
> Design http://download.jboss.org/jbosstools structure
> -----------------------------------------------------
>
> Key: JBIDE-14610
> URL: https://issues.jboss.org/browse/JBIDE-14610
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, updatesite
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.3.x
>
>
> We have several types of objects which names should be presented in site stucture:
> # Project: jbosstools
> # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final
> # Subproject: core, soatools
> # Module: base, javaee, central, freemarker and etc.
> # Distribution Type: updates|builds
> # Bits Type: stable|development|nightly
> # Targeted Eclipse: indigo|juno|kepler
> # You name it ...
> Now we mostly use following patterns to publish nightly bits, but not always and not for every project:
> # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\}
> # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure
> # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18355) Unexpected chars in freemarker editor
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18355?page=com.atlassian.jira.plugi... ]
Peter Palaga commented on JBIDE-18355:
--------------------------------------
Huh, sorry for commenting into Release Notes Text. Once again at the proper location:
I'd say that what we see here is Quick Diff, an old feature of the platform. It should disappear when you press {code}CTRL+SHIFT+Q{code} or if you disable it in the context menu of the left editor margin.
> have it disabled by default
You surely do not propose to disable it for all text editors?
I am not sure if I can disable it for FreeMarker editor only, but I can investigate if this is what you want?
> Unexpected chars in freemarker editor
> -------------------------------------
>
> Key: JBIDE-18355
> URL: https://issues.jboss.org/browse/JBIDE-18355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1b, L64
> Reporter: Jiri Peterka
> Assignee: Peter Palaga
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: freemarker-strange-char.ogv, html-template.ftl
>
>
> Strange characters occurs when editing ftl file (check the screencast)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18355) Unexpected chars in freemarker editor
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18355?page=com.atlassian.jira.plugi... ]
Peter Palaga updated JBIDE-18355:
---------------------------------
Release Notes Text: (was: Gentlemen, I'd say that what we see here is Quick Diff, an old feature of the platform. It should disappear when you press {code}CTRL+SHIFT+Q{code} or if you disable it in the context menu of the left editor margin.)
> Unexpected chars in freemarker editor
> -------------------------------------
>
> Key: JBIDE-18355
> URL: https://issues.jboss.org/browse/JBIDE-18355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1b, L64
> Reporter: Jiri Peterka
> Assignee: Peter Palaga
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: freemarker-strange-char.ogv, html-template.ftl
>
>
> Strange characters occurs when editing ftl file (check the screencast)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months