[jbosstools-issues] [JBoss JIRA] Created: (JBIDE-3369) jboss server runtime build in jboss tools hasnt tracked late shift in JBOSS AS5 GA move of libraries to /common/lib

[William Woodman (JIRA)]

jboss server runtime build in jboss tools hasnt tracked late shift in JBOSS AS5 GA move of libraries to /common/lib
-------------------------------------------------------------------------------------------------------------------

                 Key: JBIDE-3369
                 URL: https://jira.jboss.org/jira/browse/JBIDE-3369
             Project: Tools (JBoss Tools)
          Issue Type: Task
          Components: JBossAS
         Environment: JBOSS AS 5 GA and JBOSS tools CR1 - JBossTools-3.0.0.CR1-N200812051203-ALL-win32.zip
            Reporter: William Woodman
            Priority: Minor


download eclipse, and install latest nightly build of jboss tools.  download latest new jboss AS5.0.0.GA  server from download site

download SEAM 2.1.1CR1 (not required to show the problem really but is part of my code base).

start eclipse and create a new jboss 5 server runtime and point at the jboss 5 AS install directories (in passing my pristine copies of jboss as5/server/default has no /lib directory which casues this to fail.  You have to create an empty /lib under the server/default and then it works)

howevver, what used to happen is that various hibernate jars would be included in the runtime library lists as well as <home>/client and <home>/lib directories.

with the shift in AS5.0.0 GA to the use of the <home>/common/lib model, this doesnt seem to be tracked in the server runtime library lookups.

Code used to work in JBOSS AS5.0.0CR2 and below which picked up the hibernate jars for validation etc, now dont compile under server runtime pointed at new jboss As5.0.0.GA build

work around.  Manually create a new user library - add the <home>/common/lib jars to that and include into the seam ejb project as an extra user library to get compiliation to complete properly.

 
 

-- 
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