Maven 1.x JXR Plugin
  1. Maven 1.x JXR Plugin
  2. MPJXR-3

Uses pom.build.sourceDirectory instead of maven.compile.src.set

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5
    • Labels:
      None
    • Number of attachments :
      0

      Description

      I believe this is also true for several other plugins (javadoc, etc). This means that if you use something like:

      <path id="maven.j2ee.compile.src.set" location="$

      {pom.build.sourceDirectory}

      /../j2ee$

      {cactus.j2ee.version}

      "/>
      <maven:addPath id="maven.compile.src.set" refid="maven.j2ee.compile.src.set"/>

      it won't work with several plugins...

      I'm starting to think that allowing multiple source directories in project.xml wouldn't be so bad at all and that there are valid cases (I believe Cactus is one - I'm happy to discuss that though).

      Thanks
      -Vincent

        Activity

        Hide
        Achim Westermann added a comment -

        Jason did a good job for a similar request:

        http://jira.codehaus.org/browse/MAVEN-130

        This would be good for jxr too. I am voting +1!

        Additionally I think configuration of multiple source folders
        in the project.xml might really clean up the hacking in maven.xml.

        I am bored of all this "re-think why you need several source folders...".
        Explanation why it's bad may be easy but explanation how to do without
        it for a mature project that uses it for reasonable purposes is harder.

        Show
        Achim Westermann added a comment - Jason did a good job for a similar request: http://jira.codehaus.org/browse/MAVEN-130 This would be good for jxr too. I am voting +1! Additionally I think configuration of multiple source folders in the project.xml might really clean up the hacking in maven.xml. I am bored of all this "re-think why you need several source folders...". Explanation why it's bad may be easy but explanation how to do without it for a mature project that uses it for reasonable purposes is harder.

          People

          • Assignee:
            Unassigned
            Reporter:
            Vincent Massol
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: