[jira] (MASSEMBLY-603) ${maven.build.timestamp} placeholder is not filtered
[
https://jira.codehaus.org/browse/MASSEMBLY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=362903#comment-362903
]
Mike Duigou commented on MASSEMBLY-603:
---
The workaround produces ${maven.build.timestamp} in the output for me and in
some contexts (NetBeans) the following error message:
[ERROR] Resolving expression: '${maven.build.timestamp}': Detected the
following recursive expression cycle in 'maven.build.timestamp':
[maven.build.timestamp]
This and http://jira.codehaus.org/browse/MRESOURCES-99 both deserve to be fixed.
${maven.build.timestamp} placeholder is not filtered
Key: MASSEMBLY-603
URL: https://jira.codehaus.org/browse/MASSEMBLY-603
Project: Maven Assembly Plugin
Issue Type: Bug
Components: filtering
Affects Versions: 2.3, 2.4
Reporter: Igor Bljahhin
Priority: Minor
Attachments: assembly-issue.zip
When filtering files in assembly plugin most of placeholders are replaced
with values,
but Maven's property maven.build.timestamp (described here
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html in
Special Variables section) is not substituted with value.
Run mvn clean package in the test project and you will get
target/assembly-issue-0.0.1-SNAPSHOT-dist.zip archive. Open index.html from
archive and you will see that property project.version was replaced during
assembly, but maven.build.timestamp was left untouched.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-603) ${maven.build.timestamp} placeholder is not filtered
[
https://jira.codehaus.org/browse/MASSEMBLY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=356881#comment-356881
]
Kristian Rosenvold commented on MASSEMBLY-603:
--
This is an interesting issue because the interpolation context created in maven
core is not used inside the assembly plugin, which is basically the root cause
of this problem.
Since the context setup is duplicated (and slightly different!) inside assembly
plugin, we run into problems like this.
The good solution to this would of course be to somehow inherit the
interpolator from maven core. The bad would be to simply expand the duplication
to include the missing values. The suggested workaround causes maven core to
interpolate the expression into a value that is used by the plugin, which also
works :)
${maven.build.timestamp} placeholder is not filtered
Key: MASSEMBLY-603
URL: https://jira.codehaus.org/browse/MASSEMBLY-603
Project: Maven Assembly Plugin
Issue Type: Bug
Components: filtering
Affects Versions: 2.3, 2.4
Reporter: Igor Bljahhin
Priority: Minor
Attachments: assembly-issue.zip
When filtering files in assembly plugin most of placeholders are replaced
with values,
but Maven's property maven.build.timestamp (described here
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html in
Special Variables section) is not substituted with value.
Run mvn clean package in the test project and you will get
target/assembly-issue-0.0.1-SNAPSHOT-dist.zip archive. Open index.html from
archive and you will see that property project.version was replaced during
assembly, but maven.build.timestamp was left untouched.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-603) ${maven.build.timestamp} placeholder is not filtered
[
https://jira.codehaus.org/browse/MASSEMBLY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MASSEMBLY-603:
--
Affects Version/s: 2.4
${maven.build.timestamp} placeholder is not filtered
Key: MASSEMBLY-603
URL: https://jira.codehaus.org/browse/MASSEMBLY-603
Project: Maven Assembly Plugin
Issue Type: Bug
Components: filtering
Affects Versions: 2.3, 2.4
Reporter: Igor Bljahhin
Priority: Minor
Attachments: assembly-issue.zip
When filtering files in assembly plugin most of placeholders are replaced
with values,
but Maven's property maven.build.timestamp (described here
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html in
Special Variables section) is not substituted with value.
Run mvn clean package in the test project and you will get
target/assembly-issue-0.0.1-SNAPSHOT-dist.zip archive. Open index.html from
archive and you will see that property project.version was replaced during
assembly, but maven.build.timestamp was left untouched.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-603) ${maven.build.timestamp} placeholder is not filtered
[
https://jira.codehaus.org/browse/MASSEMBLY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314542#comment-314542
]
Anton Koscejev commented on MASSEMBLY-603:
--
Currently a workaround that works for me:
{code}
properties
!-- workaround for http://jira.codehaus.org/browse/MASSEMBLY-603 --
maven.build.timestamp${maven.build.timestamp}/maven.build.timestamp
/properties
{code}
${maven.build.timestamp} placeholder is not filtered
Key: MASSEMBLY-603
URL: https://jira.codehaus.org/browse/MASSEMBLY-603
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Components: filtering
Affects Versions: 2.3
Reporter: Igor Bljahhin
Priority: Minor
Attachments: assembly-issue.zip
When filtering files in assembly plugin most of placeholders are replaced
with values,
but Maven's property maven.build.timestamp (described here
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html in
Special Variables section) is not substituted with value.
Run mvn clean package in the test project and you will get
target/assembly-issue-0.0.1-SNAPSHOT-dist.zip archive. Open index.html from
archive and you will see that property project.version was replaced during
assembly, but maven.build.timestamp was left untouched.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-603) ${maven.build.timestamp} placeholder is not filtered
[
https://jira.codehaus.org/browse/MASSEMBLY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-603:
--
Component/s: filtering
${maven.build.timestamp} placeholder is not filtered
Key: MASSEMBLY-603
URL: https://jira.codehaus.org/browse/MASSEMBLY-603
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Components: filtering
Affects Versions: 2.3
Reporter: Igor Bljahhin
Priority: Minor
Attachments: assembly-issue.zip
When filtering files in assembly plugin most of placeholders are replaced
with values,
but Maven's property maven.build.timestamp (described here
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html in
Special Variables section) is not substituted with value.
Run mvn clean package in the test project and you will get
target/assembly-issue-0.0.1-SNAPSHOT-dist.zip archive. Open index.html from
archive and you will see that property project.version was replaced during
assembly, but maven.build.timestamp was left untouched.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-603) ${maven.build.timestamp} placeholder is not filtered
Igor Bljahhin created MASSEMBLY-603:
---
Summary: ${maven.build.timestamp} placeholder is not filtered
Key: MASSEMBLY-603
URL: https://jira.codehaus.org/browse/MASSEMBLY-603
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Igor Bljahhin
Priority: Minor
Attachments: assembly-issue.zip
When filtering files in assembly plugin most of placeholders are replaced with
values,
but Maven's property maven.build.timestamp (described here
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html in
Special Variables section) is not substituted with value.
Run mvn clean package in the test project and you will get
target/assembly-issue-0.0.1-SNAPSHOT-dist.zip archive. Open index.html from
archive and you will see that property project.version was replaced during
assembly, but maven.build.timestamp was left untouched.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
