[JBoss JIRA] Created: (JBDS-230) there is no PDF version for Visual Web Tools Ref Guide in bundled book
by Anatoly Fedosik (JIRA)
there is no PDF version for Visual Web Tools Ref Guide in bundled book
----------------------------------------------------------------------
Key: JBDS-230
URL: http://jira.jboss.com/jira/browse/JBDS-230
Project: Developer Studio
Issue Type: Bug
Components: Doc - JSFTools
Affects Versions: 1.0.0.GA
Reporter: Anatoly Fedosik
Assigned To: Anatoly Fedosik
Fix For: 1.0.1
there is no PDF version for Visual Web Tools Ref Guide in bundled book.
lang.docpdf:
[copy] Copying 350 files to D:\SVNLocation\documentation\jboss-tools-docs\b
uild\jsf\en\pdf\images
[java] Making portrait pages on USletter paper (8.5inx11in)
[java] Buildfile: build.xml
[java]
[java] fork-fop-instance:
[java] [echo] D:\SVNLocation\jsf\docs\userguide/../build/userguide/en/
pdf
[java] [echo] D:\SVNLocation\jsf\docs\userguide/../build/userguide/en/
pdf/Visual_Web_Tools_Reference_Guide.pdf
[java] [echo] D:\SVNLocation\jsf\docs\userguide/../build/userguide/en/
pdf/docbook_fop.tmp
[java] [fop] No files processed. No files were selected by the filese
ts and no fofile was set.
[java]
[java] BUILD SUCCESSFUL
[java] Total time: 0 seconds
[delete] Deleting: D:\SVNLocation\documentation\jboss-tools-docs\build\jsf\en
\pdf\docbook_fop.tmp
[delete] Deleting directory D:\SVNLocation\documentation\jboss-tools-docs\bui
ld\jsf\en\pdf\images
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 10 months
[JBoss JIRA] Commented: (JBDS-84) VPE doesn't work on Windows
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBDS-84?page=comments#action_12392301 ]
Max Andersen commented on JBDS-84:
----------------------------------
open a seperate issue and attach the info and file there.
> VPE doesn't work on Windows
> ---------------------------
>
> Key: JBDS-84
> URL: http://jira.jboss.com/jira/browse/JBDS-84
> Project: Developer Studio
> Issue Type: Bug
> Environment: Windows 2000 professional. Eclipse v3.2.1. JRE 1.5.0.6.
> Reporter: Kent Tong
> Attachments: eclipse-configuration.txt
>
>
> 1) Install Eclipse platform v3.2.1 binary for Windows.
> 2) Install Eclipse JDT v3.2.1 binary for Windows.
> 3) Install Exadel Studio Pro 4.04a.
> 4) Create a JSF project using the default settings.
> 5) Create a JSP file using the default settings.
> 6) In the editor window, it says "The VPE editor can't be run because your system environment needs to be changed slightly".
> There is no log file found (workspace/.metadata/.log doesn't exist). Running Eclipse with -debug doesn't show anything related to Exadel or any exception trace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 10 months
[JBoss JIRA] Moved: (JBIDE-1497) Use single base class for EL parsing
by Denis Golovin (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-1497?page=all ]
Denis Golovin moved EXIN-473 to JBIDE-1497:
-------------------------------------------
Project: JBoss Tools (was: Exadel Integration)
Key: JBIDE-1497 (was: EXIN-473)
Component/s: Cleanup
(was: Cleanup)
Fix Version/s: 2.0.0.GA
Affects Version/s: (was: 1.0.0.GA)
> Use single base class for EL parsing
> ------------------------------------
>
> Key: JBIDE-1497
> URL: http://jira.jboss.com/jira/browse/JBIDE-1497
> Project: JBoss Tools
> Issue Type: Task
> Components: Cleanup
> Reporter: Alexey Kazakov
> Assigned To: Alexey Kazakov
> Fix For: 2.0.0.GA
>
>
> We use different classes to parce EL:
> org.jboss.tools.common.model.util.ELParser (Used by JSF Conten Assist and VPE bundle resolver)
> org.jboss.tools.seam.internal.core.el.SeamELTokenizer (Used by Seam Content Assist and Validator)
> org.jboss.tools.jsf.text.ext.hyperlink.JSPExprHyperlinkPartitioner (Used by JSF Hiperlinks)
> We have to refactor it to use one Basic Parcer for EL and maybe have some implementation for special cases if we need it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 11 months
[JBoss JIRA] Moved: (JBIDE-1498) XML/DTD issues
by Denis Golovin (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-1498?page=all ]
Denis Golovin moved EXIN-89 to JBIDE-1498:
------------------------------------------
Project: JBoss Tools (was: Exadel Integration)
Key: JBIDE-1498 (was: EXIN-89)
Component/s: Cleanup
(was: Cleanup)
Fix Version/s: 2.0.0.GA
(was: 1.0.0.beta2)
> XML/DTD issues
> --------------
>
> Key: JBIDE-1498
> URL: http://jira.jboss.com/jira/browse/JBIDE-1498
> Project: JBoss Tools
> Issue Type: Task
> Components: Cleanup
> Reporter: Max Andersen
> Assigned To: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 2.0.0.GA
>
>
> There seem to be a big mix of mixed and uppercase tag names and file names in xml and dtd's used by exadel.
> e.g. kb-schema_1.0.dtd has BodyContent, StartTag, EndTag, Boolean instead of body-content, start-tag and end-tag.
> Many xml files doesn't have a DTD/XSD reference hence is not validatable.
> setting files uses UPPERCASE in xml (e.g. old .exadelproject file)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 11 months
[JBoss JIRA] Moved: (JBIDE-1494) TextFomating tag should have default bexaviour, now it is used as copy everywhere
by Denis Golovin (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-1494?page=all ]
Denis Golovin moved EXIN-476 to JBIDE-1494:
-------------------------------------------
Project: JBoss Tools (was: Exadel Integration)
Key: JBIDE-1494 (was: EXIN-476)
Component/s: Cleanup
(was: Cleanup)
Fix Version/s: 2.0.0.GA
Affects Version/s: (was: 1.0.0.GA)
> TextFomating tag should have default bexaviour, now it is used as copy everywhere
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-1494
> URL: http://jira.jboss.com/jira/browse/JBIDE-1494
> Project: JBoss Tools
> Issue Type: Task
> Components: Cleanup
> Reporter: Denis Golovin
> Assigned To: Maxim Areshkau
> Fix For: 2.0.0.GA
>
>
> It should be renamed to vpe:textFormatting
> Now there ar ea lot of blocks like posted below:
> <vpe:textFormating>
> <vpe:format type="BlockFormat" addChildren="deny" />
> <vpe:format type="UnderlineFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="BoldFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="ItalicFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="FontNameFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="FontSizeFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="BackgroundColorFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="ForegroundColorFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> </vpe:textFormating>
> It should have default behavior that is defined by inserting just <vpe:textFormatting> tag inside template. If some behavior should be redefined use vpe:format tag for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 11 months