Announcement Announcement Module
Collapse
No announcement yet.
Deployment Assembly going haywire Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Deployment Assembly going haywire

    First, this was all working a few days ago and then poof it stopped working. The only thing I did in the middle was an svn update and my sts settings are not in svn.

    That said, whenever I publish to vFabric tc or to Tomcat 7, the published directory seems to ignore what the Deployment Assembly screen says and puts all my classes in at the root, instead of WEB-INF/classes. I've tried editing the org.eclipse.wst.common.component file by hand but that doesn't help.

    org.eclipse.wst.common.component:
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <project-modules id="moduleCoreId" project-version="1.5.0">
        <wb-module deploy-name="dal-server">
            <wb-resource deploy-path="/" source-path="/src/webapp" tag="defaultRootSource"/>
            <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/resources"/>
            <wb-resource deploy-path="/WEB-INF/classes/com" source-path="/src/com"/>
            <property name="context-root" value="dal-server"/>
            <property name="java-output-path" value="/dal-server/WEB-INF/classes"/>
        </wb-module>
    </project-modules>
    Everything under /src/com ends up in the root. I've tried everything, including installing STS and tc from scratch and checking out a fresh copy of the code from svn.

    Anybody have any ideas?

  • #2
    Hey!

    Why do you have "/src/com" and "src/resources" there? This looks a bit strange... "com" sounds to me like the first level of the package. Are you sure that you don't have a subfolder under "src" to distinguish between resources and Java source code?

    -Martin

    Comment


    • #3
      Originally posted by Martin Lippert View Post
      Hey!

      Why do you have "/src/com" and "src/resources" there? This looks a bit strange... "com" sounds to me like the first level of the package. Are you sure that you don't have a subfolder under "src" to distinguish between resources and Java source code?

      -Martin
      I knew this would come up. :-)

      The directory structure is
      src
      com/domain/blah/blah
      resources/etc/etc

      Yes, it probably would have made more sense to use src/java/com/domain/blah/blah, but that's not how it was setup and it's not the issue. I've tried it with a subfolder and the behavior is the same regardless.

      Comment


      • #4
        Hey!

        I just stumbled across this, but if that doesn't help, I guess the best way would be to attach a sample project that reproduces the problem, so that we can take a look at it directly. Would that be possible in your case?

        -Martin

        Comment


        • #5
          I finally got a chance to try and create a small project to duplicate the issue.

          I'm using a vanilla STS 3.0 install. Java 1.6. And the IvyDe plugin.
          I created the project using the Dynamic Web Project wizard.

          It's available here and includes the /Servers directory (config files):
          https://www.dropbox.com/sh/ph8yrkg0z...XY/testWeb.zip

          Here's how it expands out on my system:
          TcNoInsight\wtpwebapps\testWeb\WEB-INF
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\env\dev
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\env\local
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\env\prod
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\env\tst
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\foo\
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\foo\web
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\foo\web\admin
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\resources
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\resources\env
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\resources\env\dev
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\resources\env\local
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\resources\env\prod
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\resources\env\tst
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\webapp
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\webapp\WEB-INF
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\webapp\WEB-INF\jsp
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\webapp\WEB-INF\jsp\admin
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\webapp\WEB-INF\lib
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\webapp\WEB-INF\spring
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\WEB-INF
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\WEB-INF\jsp
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\WEB-INF\jsp\admin
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\WEB-INF\lib
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\classes\WEB-INF\spring
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\jsp
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\jsp\admin
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\lib
          TcNoInsight\wtpwebapps\testWeb\WEB-INF\spring

          It seems pretty clear that at the very least it ignores the exclusion filters on the eclipse build path.

          Thanks.

          Comment

          Working...
          X