[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-951) Seam Web Project in war configuration has an error '' right after creating under linux
Denis Golovin (JIRA)
jira-events at lists.jboss.org
Wed Sep 26 15:53:41 EDT 2007
[ http://jira.jboss.com/jira/browse/JBIDE-951?page=all ]
Denis Golovin resolved JBIDE-951.
---------------------------------
Resolution: Done
I force WTP IVirtualComponent update during creating Seam WEB Project
> Seam Web Project in war configuration has an error '' right after creating under linux
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-951
> URL: http://jira.jboss.com/jira/browse/JBIDE-951
> Project: JBoss Tools
> Issue Type: Bug
> Affects Versions: 2.0.0.Beta3
> Environment: FC6 Linux
> Reporter: Denis Golovin
> Assigned To: Denis Golovin
> Fix For: 2.0.0.Beta4
>
>
> that's happend because WTP doesn't update org.eclipse.wst.common.component file in .settings on Linux.
> Under windows it looks like
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
> <wb-module deploy-name="s1"><?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
> <wb-module deploy-name="s3">
> <wb-resource deploy-path="/" source-path="/WebContent"/>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/>
> <property name="context-root" value="s3"/>
> <property name="java-output-path" value="build/classes"/>
> <property name="web_app_libraries_processed" value="true"/>
> <property name="ear_libraries_processed" value="true"/>
> </wb-module>
> </project-modules>
> <wb-resource deploy-path="/" source-path="/WebContent"/>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/action"/>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/model"/><?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
> <wb-module deploy-name="s3">
> <wb-resource deploy-path="/" source-path="/WebContent"/>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/>
> <property name="context-root" value="s3"/>
> <property name="java-output-path" value="build/classes"/>
> <property name="web_app_libraries_processed" value="true"/><?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
> <wb-module deploy-name="s3">
> <wb-resource deploy-path="/" source-path="/WebContent"/>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/>
> <property name="context-root" value="s3"/>
> <property name="java-output-path" value="build/classes"/>
> <property name="web_app_libraries_processed" value="true"/>
> <property name="ear_libraries_processed" value="true"/>
> </wb-module>
> </project-modules>
> <property name="ear_libraries_processed" value="true"/>
> </wb-module>
> </project-modules>
> <property name="context-root" value="s1"/>
> <property name="java-output-path" value="build/classes"/>
> <property name="web_app_libraries_processed" value="true"/>
> <property name="ear_libraries_processed" value="true"/>
> </wb-module>
> </project-modules>
> right after seam web project is created in WAR deployment configuration.
> Under linux it looks different:
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
> <wb-module deploy-name="s3">
> <wb-resource deploy-path="/" source-path="/WebContent"/>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/> <---- source folder is still the same
> <property name="context-root" value="s3"/>
> <property name="java-output-path" value="build/classes"/>
> <property name="web_app_libraries_processed" value="true"/>
> <property name="ear_libraries_processed" value="true"/>
> </wb-module>
> </project-modules>
--
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
More information about the jbosstools-issues
mailing list