[INFO] Coping files with filtering to temporary directory.
"Copying" misses "y"

Hi
I'm getting (templating-maven-plugin-1.0.0):
[INFO] Building: MOJO-2014/pom.xml
[INFO] run script verify.groovy
[INFO] ..FAILED (5.6 s)
[INFO] The post-build script did not succeed. assert javaClass.text.contains('public static final String FIRST_COLOR = "red"')
| | |
| | false
| package org.codehaus.mojo.templating.it;
|
| public class Colors {
|
| public static final String FIRST_COLOR = "${first-color}";
| public static final String SECOND_COLOR = "${second-color}";
| public static final String THIRD_COLOR = "${third-color}";
| }
/home/gil/rpmbuild/BUILD/templating-maven-plugin-1.0.0/target/it/MOJO-2014/target/generated-sources/java-templates/org/codehaus/mojo/templating/it/Colors.java

Environment:
Apache Maven 3.3.3 (NON-CANONICAL_2015-07-10T12:37:52_mockbuild; 2015-07-10T14:37:52+02:00)
Maven home: /usr/share/maven
Java version: 1.8.0_71, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.71-1.b15.fc23.i386/jre
Default locale: it_IT, platform encoding: UTF-8
OS name: "linux", version: "4.3.5-300.fc23.i686", arch: "i386", family: "unix"

Any ideas as to why?
Thanks in advance
Regards

unfortunately easytesting is not maintained anymore

The problem here is that the whole documentation is duplicated by the README.md file. The same documentation is generated from sources and from site content src/site/apt/* during the site generation and release process. So best is to keep a single source of the truth instead of two locations which needed to be maintained.

Make a release to official Maven central repository with actual code, version 1.0.0.

As a bonus a shield with Maven repo would be nice in README.md, like this (dynamic one):

BTW. About shield, goto: http://shields.io/

Replace with github actions.

Provide optional mechanism to declare target package for generated class(es)

The plexs-build-api is not maintained anymore.

Hello.

In my project we have the next configuration:

<properties>
    <myProperty>defaultValue</myProperty>
</properties>
<profiles>
    <profile>
        <id>pre</id>
        <properties>
             <myProperty>valuePre</myProperty>
        </properties>
    </profile>
    <profile>
         <id>pro</id>
         <properties>
              <myProperty>valuePro</myProperty>
        </properties>
    </profile>
</profiles>

We use the default configuration of the plugin, and the goal "filter-sources".

We have a file where we are replacing the property ${myProperty} and the pluging works as intended, generating the java file with the value "defaultValue". However, if I try to compile the project with another profile, it is ignored, and the default value is taken.

Example:

mvn clean install -Ppre

The result is a .class file with the value "defaultValue".

Is there something I'm doing wrong or the plugin is not taking into account profiles?

Thanks.

Is this project abandoned, or are there plans to update and release new versions?
The latest 3.9.2 Maven release generates the following warnings with the last published version (1.0.0, from 2015):

[WARNING]   Plugin issue(s):
[WARNING]    * Plugin is a Maven 2.x plugin, which will be not supported in Maven 4.x
[WARNING]    * Plugin depends on plexus-container-default, which is EOL