river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Reedy <dennis.re...@gmail.com>
Subject Re: [jira] Commented: (RIVER-300) introduce maven to the river build process
Date Thu, 20 Jan 2011 03:00:15 GMT

On Jan 19, 2011, at 955PM, Patricia Shanahan wrote:

> Peter Firmstone (JIRA) wrote:
> ...
>> Sometimes change is an opportunity to consider other changes, such as
>> the namespace change from com.sun.jini to org.apache.river, this is
>> currently in the experimental stages and we're not certain if this
>> should be done at the same time, but I'd like to keep the option open
>> for now.
> ...
> 
> Given the number of package changes, is there any opportunity to prepare a program or
script that would automate the import statement changes? That could save users a lot of time.

I used the following ant file (convert.xml)

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<project name="Converter" default="convert" basedir=".">
    <property environment="env."/>
    <property name="src" value="."/>

    <target name="convert">
            <replace dir="${src}" summary="yes">
            <replacefilter token="com.sun.jini" value="org.apache.river"/>
            <replacefilter token="com/sun/jini" value="org/apache/river"/>
            <include name="**/*.html" />
            <include name="**/*.xml" />
            <include name="**/*.java" />
            <include name="**/*.config" />
            <include name="**/*.mf" />
            <include name="**/*.sh" />
            <include name="**/*.bat" />
            <exclude name="**/convert.xml" />
        </replace>
    </target>
 </project>


Mime
View raw message