Just committed this change to the 1.10 branch, it should get merged to
master soon. I diff'd the target directory of opennms-base-assembly with
both versions of the plugin and found no differences, in addition to
grepping through the code for escaped tokens like \${something}. I
didn't see any occurrences in our configs or script code.

-- Seth


On 07/05/2011 11:45 AM, Roskens, Ronald wrote:
> I'm fairly certain you can also bump maven-resources-plugin from 2.3 to 2.5 
> even though the comments in opennms/pom.xml say there's major escaping issues 
> beyond 2.3. As best I can tell all the filtered files now using the ${...} 
> syntax instead of @...@ like they used to so the comment doesn't seem to 
> apply any more. This will get rid of the builds errors about m2e needing a 
> newer version of maven-resources-plugin.
>   


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this 
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel

Reply via email to