maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Closed] (MNG-6661) Override via user property
Date Mon, 27 May 2019 21:37:00 GMT


Robert Scholte closed MNG-6661.
    Resolution: Won't Fix
      Assignee: Robert Scholte

All properties that start with $\{project. are readonly/immutable by design; you could say
it reflects the xpath of the pom.xml.

None of these will ever be settable via commandline or property. 

So as you already discovered you should be using <build><directory> to solve this,
all maven-plugins will understand this.

> Override via user property
> --------------------------------------------------
>                 Key: MNG-6661
>                 URL:
>             Project: Maven
>          Issue Type: Improvement
>          Components: core
>            Reporter: Sergey Ponomarev
>            Assignee: Robert Scholte
>            Priority: Minor
> I would like to improve a build speed of a big project. The project uses a lot of IO
operation during a build. So I decided to put all /target directories into RAM disk while
keeping sources on a hard drive.
> I mounted a RAM disk to /mnt/ramdisk and created a profile:
> {code:xml}
>     <profile>
>       <activation>
>         <activeByDefault>true</activeByDefault>
>       </activation>
>       <id>ramDisk</id>
>       <properties>
>        <>/mnt/ramdisk/${project.groupId}/${project.artifactId}/target</>
>       </properties>
>     </profile>
> {code}
> In fact this is an equivalent of specifying
> But unfortunately this doesn't work because the property here (i.e. "user property")
is ignored.
> To make it working I should add into pom.xml this:
> {code}
>   <build>
>     <directory>${}</directory>
> {code}
> I.e. explicitly reuse the user property as configuration.
> Don't be confused, we can call the user property anyhow e.g. ${ram_dir} but I just wan't
to reuse existing property.
> I found a ticket that looks similar but
this is another story.
> So could we implement this?

This message was sent by Atlassian JIRA

View raw message