[JBoss JIRA] Created: (JBIDE-1841) Error #1 while performing SchemaExport if server isn't started.
by Anton Klimkovich (JIRA)
Error #1 while performing SchemaExport if server isn't started.
---------------------------------------------------------------
Key: JBIDE-1841
URL: http://jira.jboss.com/jira/browse/JBIDE-1841
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 2.0.1
Reporter: Anton Klimkovich
Priority: Minor
Attachments: exception.txt, TestHib.zip
EXECUTE: Import attached java project.
EXECUTE: Open Hibernate Configuration View
EXECUTE: Right mouse click and select Add Configuration from context menu
EXECUTE: On Main tab select imported project and path to cfg.xml
EXECUTE: On Clathpath tab set path to hsqldb.jar
EXECUTE: On Mappings tab add path to mapping file.
EXECUTE: Press Apply button and Ok button
ASSERT: Hibernate configuration appear in Hibernate Configuration View
EXECUTE: Right mouse click on configeration in Hibernate Configuration View and select Run SchemaExport
FAILURE: java.sql.SQLException: socket creation error
Log attached.
--
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
12 years, 3 months
[JBoss JIRA] Created: (JBIDE-2764) Split up build(s) in smaller pieces
by Max Rydahl Andersen (JIRA)
Split up build(s) in smaller pieces
-----------------------------------
Key: JBIDE-2764
URL: https://jira.jboss.org/jira/browse/JBIDE-2764
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Reporter: Max Rydahl Andersen
Fix For: LATER
Currently our build is very monolithic (for no real good reason) and that results in the build being very slow, not easy to see which component cause a failure since all dependents will also fail, respins takes alot of time ;(
We should split up the build in smaller parts (not necessarily all the way down to modules) which makes it possible to build the various part more or less independently by just being able to take the generated artifacts from dependent builds.
It would also be beneficial if the compile, test and upload parts gets separated so e.g. tests can be executed on separate platforms without having a full rebuild.
--
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
12 years, 3 months
[JBoss JIRA] Created: (JBIDE-830) JSF support: linked folders
by Petr Lindovsky (JIRA)
JSF support: linked folders
---------------------------
Key: JBIDE-830
URL: http://jira.jboss.com/jira/browse/JBIDE-830
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 2.0.0.Beta3
Environment: Windows XP
Reporter: Petr Lindovsky
I have a Web project (originally developed in another IDE) where the META-INF and WEB-INF directories are located directly under the root of the project (e.g. next to src).
So I can't take the project root as the web content directory. To make this work with Europa, I created a new WebConent directory under the root and added folder links there pointing to the existing META-INF and WEB-INF. This now works in Europa.
Is it possible to add RedHat JSF support to this? This wizard doesn't seem to take this into account.
I created a project where you can see the problem: It works in Europa (you can use Export > WAR file and Run As > Run On Server) but I don't know hat to make it work with the RedHat JSF support.
(Note: I used absolute paths in the links in the project; in reality we used path variables to enable sharing.)
--
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
12 years, 8 months