Closed GoogleCodeExporter closed 8 years ago
Thanks Sujay, I will look into this soon.
Original comment by baker.st...@gmail.com
on 30 Nov 2011 at 4:10
For now I'm using a simple workaround.
My build config is below.
But here I didn't have to use includes which does not seem to work with this
workaround.
{{
<build>
<plugins>
<plugin>
<groupId>com.google.code.maven-replacer-plugin</groupId>
<artifactId>maven-replacer-plugin</artifactId>
<version>1.4.0</version>
<executions>
<execution>
<phase>process-sources</phase>
<goals>
<goal>replace</goal>
</goals>
</execution>
</executions>
<configuration>
<file>${basedir}/relative/path/to/file</file>
<basedir>
/
</basedir> <tokenValueMap>absolute/path/to/token/value/map</tokenValueMap>
</configuration>
</plugin>
</plugins>
</build>
}}
Original comment by sujay.co...@gmail.com
on 30 Nov 2011 at 6:03
Code changes complete.
I have made tokenValueMap able to fall back to an absolute file in case it
cannot be found by a relative path.
This means you can remove the basedir argument and simply insert an absolute
path in your tokenValueMap.
However, I could not replicate a problem with includes not working for your
workaround. Perhaps this fix will cover your problem with includes as well.
This has not been released yet but exists on the trunk. You can either wait for
the next release which is going to happen soon (due to another outstanding
issue making it a priority for me) or build off trunk and install this plugin
into your local repository (as a snapshot). Check the InstallationGuide for
more information with that.
I hope this resolves the issue for you and I am sorry this has taken me so long
to get around to doing.
Steven
Original comment by baker.st...@gmail.com
on 12 Mar 2012 at 5:59
Thanks for the fix. I will wait for the release.
Original comment by sujay.co...@gmail.com
on 12 Mar 2012 at 7:16
Released as part of 1.5.0. This is being migrated through the central maven
repo and will take a few hours.
Note: the artifactId was changed to "replacer" from "maven-replacer-plugin"
(Issue 62) so you will need to change that too.
Original comment by baker.st...@gmail.com
on 13 Mar 2012 at 12:13
Just issue clean up.
Original comment by baker.st...@gmail.com
on 17 Sep 2012 at 12:44
Original issue reported on code.google.com by
sujay.co...@gmail.com
on 29 Nov 2011 at 8:22