[JBoss JIRA] Created: (JBIDE-5020) XML complains when Tag Library is created
by Jiri Peterka (JIRA)
XML complains when Tag Library is created
-----------------------------------------
Key: JBIDE-5020
URL: https://jira.jboss.org/jira/browse/JBIDE-5020
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.1.0.M4
Environment: Linux 32,64 and probably others, OpenJDK 1.6
Reporter: Jiri Peterka
Priority: Minor
Fix For: 3.1.0.CR1
There are XML complains after Tag library is created:
Tag library version:
- 1.2 - ERROR
The content of element type "taglib" is incomplete, it must match "(tlib-version,jsp-version,short-name,uri?,display-name?,small-icon?,large-icon?,description?,validator?,listener*,tag+)".
( Simply there is no tag "tag" defined in the default template and when first is created then error is gone )
- 2.0 and 2.1 - WARNING
No grammar constraints (DTD or XML schema) detected for the document.
Expected state: No error messages / warnings present after using standard creation process.
Steps to reproduce:
Create JSF Project "JSFTest"
In "Web Project" view select "JSFTest" -> "WebContent" -> Create Tag Library
Open Tag Library XML file
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-4741) Installation of JBT 3.1 failed on Eclipse 3.5 (Galileo)
by Jiri Peterka (JIRA)
Installation of JBT 3.1 failed on Eclipse 3.5 (Galileo)
-------------------------------------------------------
Key: JBIDE-4741
URL: https://jira.jboss.org/jira/browse/JBIDE-4741
Project: JBoss Tools
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.1.0.M2
Environment: GNU/Linux - Fedora 11 (64-bit)
Eclipse 3.5 64bit (Linux - GTK) (JEE bundle with dependencies)
Java: Sun JDK 1.5.19 or 1.6.13 (x64)
Reporter: Jiri Peterka
An error occurred while installing the items
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Install, operand=null --> [R]org.eclipse.tptp.platform.ac.linux_em64t 4.4.200.v200906121434, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.ChmodAction).
The action chmod failed - file /opt/app/ide/e35ee-2/plugins/org.eclipse.tptp.platform.ac.linux_em64t_4.4.200.v200906121434/agent_controller/bin/ACVersion.sh does not exist.
Steps to reproduce:
1. Download Eclipse package
http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo...
2. Install dependecies for JBT
3. Install JBT from update site ( development or nightly updates)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-5110) Original JSF project isn't working when imported
by Jiri Peterka (JIRA)
Original JSF project isn't working when imported
------------------------------------------------
Key: JBIDE-5110
URL: https://jira.jboss.org/jira/browse/JBIDE-5110
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.1.0.M4
Environment: JBT 2.1.0.v200910281724M-H247-M4, Linux 64,32
Reporter: Jiri Peterka
Steps to reproduce:
1. Create default JSF Project test_jsf0 in workspace1
2. Switch to workspace2
3. Import test_jsf0
4. Switch to workspace1
5. Work with project test_jsf1
FAILURE: Project is closed, when opened, there is error message: The project description file (.project) for 'test_jsf1' is missing. This file contains important information about the project. The project will not function properly until this file is restored.
ASSERT: Original project should be working
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-5049) Specifying Server JRE via Open Launch Configuration is confusing
by Vlado pakan (JIRA)
Specifying Server JRE via Open Launch Configuration is confusing
----------------------------------------------------------------
Key: JBIDE-5049
URL: https://jira.jboss.org/jira/browse/JBIDE-5049
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Environment: JBoss Tools 3.1 M4
JDK Sun 1.5.0_14
JBoss AS 4.3
Reporter: Vlado pakan
Assignee: Rob Stryker
Selecting JRE for server defined within Eclipse server view is confusing. Check these two scenarios:
1. Define new server with Runtime using JRE 1.5.0
2. Open Launch Configuration of this server, select JRE tab, select JRE 1.6.0 choose apply and OK.
3. Reopen Open Launch Configuration dialog and JRE 1.5.0 is selected instead JRE 1.6.0
Looks like JRE is always inhereted from Server Runtime settings and not using "Open Launch Configuration" settings and it's confusing.
1. Define new JBoss EAP 5.0 Runtime. This Runtime needs JRE 1.6 and this JRE is automatically selected during creation of Runtime as Runtime JRE. There is no possibility to select JRE 1.5 for JBoss EAP 5.0 Runtime.
2. Select JRE 1.5 as default workspace JRE Windows > Preferences > Java > Installed JRE's
3. Open Launch Configuration and JRE 1.5 is selected and is also used when server is started. It brings many errors because JBoss 5.0 runs only with 1.6 JRE
4. Change JRE via OPen Launch Configuration dialog to JRE 1.6 choose Apply and OK.
5. Reopen Open Launch Configuration dialog and JRE was not change it's still JRE 1.5. It's again quite confusing
6. Change workspace default JRE to JRE 1.6
7. Open Launch Configuration is now using JRE 1.6 and server starts correctly
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months