Maven
  1. Maven
  2. MNG-2979

Cross module dependencies for multi-module site

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.0.5
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Linux 2.6.18-gentoo-r6 #2 SMP PREEMPT Wed Feb 28 10:25:50 CET 2007 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
    • Complexity:
      Intermediate
    • Number of attachments :
      9

      Description

      Considering a multi-module project A which declares two sub-projects (modules) B and C. Having module C indicating in its POM a dependency against module B. Compilation and packaging work great without having to install module B in maven local repository, it locate module B for module C using declared aggregation at top level project A.

      But for site goals it does not work, that is to say when maven try to generate site for module C it tells that module B artifact cannot be found. So we have to install module B to be able to generate module C site, whereas it is not necessary for compile or package goals.

      I think it would be great if site goals behaves like compile and package with aggregation. It would be more coherent, and avoid to have to run install just for site goals.

      1. build.log
        12 kB
        John Casey
      2. maven.diff
        1 kB
        Tiago Bruno Pires Gomes
      3. maven.diff
        0.5 kB
        Tiago Bruno Pires Gomes
      4. mng-2979-testcase.tar.gz
        2 kB
        Oran Kelly
      5. package.txt
        6 kB
        Mat Gessel
      6. site.txt
        8 kB
        Mat Gessel
      7. to-package.log
        10 kB
        John Casey

        Activity

        Hide
        Paul Benedict added a comment -

        Reopening based on the feedback of two users who apparently verified it isn't fixed. John, just close this again if confirmations turn out to be false.

        Show
        Paul Benedict added a comment - Reopening based on the feedback of two users who apparently verified it isn't fixed. John, just close this again if confirmations turn out to be false.
        Hide
        Guillaume Barry added a comment -

        Hi,
        I got the problem with maven 2.0.9
        mvn site or mvn clean install site doesn't work.

        mvn clean install is working and of course after that mvn site works (using local repository)

        is there a workaround with a single command line build ?

        Show
        Guillaume Barry added a comment - Hi, I got the problem with maven 2.0.9 mvn site or mvn clean install site doesn't work. mvn clean install is working and of course after that mvn site works (using local repository) is there a workaround with a single command line build ?
        Hide
        Shriniwas Joshi added a comment - - edited

        Do we have any workaround for this problem please?

        As Barry mentioned above we need a way to do this in single line as thats what we need to provide in Hudson config.

        Please leave us some comments.

        Shrini

        Show
        Shriniwas Joshi added a comment - - edited Do we have any workaround for this problem please? As Barry mentioned above we need a way to do this in single line as thats what we need to provide in Hudson config. Please leave us some comments. Shrini
        Hide
        René Zanner added a comment -

        A work-around is to configure two separate jobs in Hudson: one for building (clean install), the other for generating and deploying the site ("site site:deploy" or directly "site-deploy").

        We do it in our project: the normal build job is based on checking Subversion, the site build is time-based.

        Show
        René Zanner added a comment - A work-around is to configure two separate jobs in Hudson: one for building (clean install), the other for generating and deploying the site ("site site:deploy" or directly "site-deploy"). We do it in our project: the normal build job is based on checking Subversion, the site build is time-based.
        Hide
        Brett Porter added a comment -

        this is resolved in 3.0-alpha-5. mvn clean package site or mvn clean install site both work. mvn clean site works up until the point that the site report requires the module A dependency which was never built.

        Show
        Brett Porter added a comment - this is resolved in 3.0-alpha-5. mvn clean package site or mvn clean install site both work. mvn clean site works up until the point that the site report requires the module A dependency which was never built.

          People

          • Assignee:
            John Casey
            Reporter:
            Wally Wallou
          • Votes:
            14 Vote for this issue
            Watchers:
            16 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: