Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Mon, 3 Jun 2013 18:00:03 -0500 (CDT)
From: "Bob Fields (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: 
 <JIRA.146502.1370300346647.370.1370300403337@codehaus01.managed.contegix.com>
In-Reply-To: <JIRA.146502.1370300346647@codehaus01.managed.contegix.com>
References: <JIRA.146502.1370300346647@codehaus01.managed.contegix.com>
Subject: [jira] (MCOMPILER-206) Buildhelper plugin (add source dir) ignored
 on compile in site phase
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Bob Fields created MCOMPILER-206:
------------------------------------

             Summary: Buildhelper plugin (add source dir) ignored on compil=
e in site phase
                 Key: MCOMPILER-206
                 URL: https://jira.codehaus.org/browse/MCOMPILER-206
             Project: Maven 2.x Compiler Plugin
          Issue Type: Bug
    Affects Versions: 3.1
         Environment: Java 1.6.0_43-b01 64 bit Windows7. maven 3.0.4.
            Reporter: Bob Fields
         Attachments: mvnsiteFailure.zip

mvn install recognizes additional directories from maven-buildhelper-plugin=
. Running mvn site afterwards does not recognize the additional src directo=
ries. This was not a problem until compiler 3.0 plugin changed the way comp=
ilation is done, it now recompiles the project every time even when no chan=
ges have been made, unfortunately it needs to recompile during the site pha=
se now. Multiple recompilations normally would not be a problem (though pre=
ferred not to have to do), if it found all the source directories. I tested=
 the old 2.5.1 plugin by deleting the target/classes files and then running=
 mvn site, and it fails the same way (additional buildhelper directories no=
t added to compilation path), so this issue also exists in the plugin v2.x.=
 Attached a debug log output, it shows that the buildhelper dirs were added=
 when that plugin was run under 'Source directories' but were not passed to=
 the javac command line when the compiler plugin was run. Running the same =
under mvn install shows both sourcepath values passed to the javac compiler=
. I'm hoping there's a simple solution to this, otherwise I'll build the SN=
APSHOT version of the compiler-plugin and attempt to troubleshoot (probably=
 easier than duplicating the problem in a very small project). Because it i=
s such a large project, I have to run the install phase separately from the=
 site phase (memory constraints).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira