You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2022/04/28 06:55:00 UTC

[jira] [Commented] (MCOMPILER-492) Dependent modules are always recompiled if we run the "package" goal

    [ https://issues.apache.org/jira/browse/MCOMPILER-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529231#comment-17529231 ] 

Slawomir Jaranowski commented on MCOMPILER-492:
-----------------------------------------------

There is my reason ... {{maven-ejb-plugin}} by default always build new jar.

With additional configuration to ejb plugin, problem is solved.
{code:java}
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-ejb-plugin</artifactId>
   <configuration>
     <archive>
       <forced>false</forced>
     </archive>
   </configuration>
</plugin>
{code}
 

> Dependent modules are always recompiled if we run the "package" goal
> --------------------------------------------------------------------
>
>                 Key: MCOMPILER-492
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-492
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.10.0, 3.10.1
>            Reporter: Slawomir Jaranowski
>            Priority: Major
>
> After MCOMPILER-474 we are checking if generated jar from dependent module has timestamp greater than Maven session start time.
> It is always true because new jar is always created even if no change in project.
> So now dependent module are always recompile.
> h3. workaround
> provide only "class" for configuration parameter {{fileExtensions}}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)