Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2
    • Fix Version/s: 2.6
    • Component/s: AJDT support
    • Labels:
      None
    • Patch Submitted:
      Yes
    • Number of attachments :
      3

      Description

      Please add support for the AJDT plugin.

      I have modified the eclipse plugin for our site with the needed changes. I have attached the modifications that I made for someone to look at and incorporate into the plugin.

      1. ajdt.patch
        23 kB
        Carlos Sanchez

        Issue Links

          Activity

          Hide
          Eric Berry added a comment - - edited

          Alexander, In the configuration of the eclipse plugin add <ajdtVersion>none</ajdtVersion>. This should fix the problem.

          There is hidden documentation here http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html that describes how to use the ajdt plugin.

          Show
          Eric Berry added a comment - - edited Alexander, In the configuration of the eclipse plugin add <ajdtVersion>none</ajdtVersion>. This should fix the problem. There is hidden documentation here http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html that describes how to use the ajdt plugin.
          Hide
          Tan Quach added a comment -

          I agree with Alexander, and I've created a new issue: http://jira.codehaus.org/browse/MECLIPSE-547

          Show
          Tan Quach added a comment - I agree with Alexander, and I've created a new issue: http://jira.codehaus.org/browse/MECLIPSE-547
          Hide
          Eirik Rosvold Larsen added a comment -

          According to the comments on MECLIPSE-270, this jira task replaces/duplicates that task. MECLIPSE-270 is about adding attributes to classpathentries in .classpath.

          Can someone please elaborate how this can be accomplished in the pom.xml? This feature lacks documentation on the project website.

          Regards

          Show
          Eirik Rosvold Larsen added a comment - According to the comments on MECLIPSE-270 , this jira task replaces/duplicates that task. MECLIPSE-270 is about adding attributes to classpathentries in .classpath. Can someone please elaborate how this can be accomplished in the pom.xml? This feature lacks documentation on the project website. Regards
          Hide
          Arnaud Heritier added a comment -

          The documentation about ajdt is here : http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html
          You can find several exemples here : http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/test/resources/projects/
          If some docs are missing, do not hesitate to open an issue. We'll try to improve it.
          We know there are many lacks in it.

          Show
          Arnaud Heritier added a comment - The documentation about ajdt is here : http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html You can find several exemples here : http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/test/resources/projects/ If some docs are missing, do not hesitate to open an issue. We'll try to improve it. We know there are many lacks in it.
          Hide
          Eirik Rosvold Larsen added a comment -

          Arnaud: thanks for the link.

          After plundering around, I found that adding wtp version 2.0 to the pom automatically added the required attributes to the classpathentries like this:

          <classpathentry kind="var" path="M2_REPO/log4j/log4j/1.2.15/log4j-1.2.15.jar" sourcepath="M2_REPO/log4j/log4j/1.2.15/log4j-1.2.15-sources.jar">
          <attributes>
          <attribute value="/WEB-INF/lib" name="org.eclipse.jst.component.dependency"/>
          </attributes>
          </classpathentry>

          A nice feature was that the attribute was only added if the maven dependency scope was compile or runtime. Small question though: If the scope is provided, the maven eclipse plugin doesn't add any attribute to the corresponding classpathentry. The wtp plugin for eclipse seems to support the following attribute for entries that are not to be deployed:

          "org.eclipse.jst.component.nondependency"

          Maybe you should add this for scope provided? Just a thought..

          Thanks again!

          Show
          Eirik Rosvold Larsen added a comment - Arnaud: thanks for the link. After plundering around, I found that adding wtp version 2.0 to the pom automatically added the required attributes to the classpathentries like this: <classpathentry kind="var" path="M2_REPO/log4j/log4j/1.2.15/log4j-1.2.15.jar" sourcepath="M2_REPO/log4j/log4j/1.2.15/log4j-1.2.15-sources.jar"> <attributes> <attribute value="/WEB-INF/lib" name="org.eclipse.jst.component.dependency"/> </attributes> </classpathentry> A nice feature was that the attribute was only added if the maven dependency scope was compile or runtime. Small question though: If the scope is provided, the maven eclipse plugin doesn't add any attribute to the corresponding classpathentry. The wtp plugin for eclipse seems to support the following attribute for entries that are not to be deployed: "org.eclipse.jst.component.nondependency" Maybe you should add this for scope provided? Just a thought.. Thanks again!

            People

            • Assignee:
              Arnaud Heritier
              Reporter:
              Eric Berry
            • Votes:
              10 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: