[ 
http://issues.apache.org/jira/browse/JELLY-194?page=comments#action_12368040 ] 

Felipe Leme commented on JELLY-194:
-----------------------------------

Any clue when/if these issues (JELLY-194, JELLY-203, JELLY-204 and JELLY-205) 
will make it to the codebase? 

In particular, I think this feature is very useful - everytime I start a 
project in a new company, I need to create a small project only to provide such 
tag...

 

> New tag that copy text files replacing Jelly properties
> -------------------------------------------------------
>
>          Key: JELLY-194
>          URL: http://issues.apache.org/jira/browse/JELLY-194
>      Project: jelly
>         Type: New Feature
>   Components: taglib.util
>     Versions: 1.0
>     Reporter: Felipe Leme
>  Attachments: JELLY-194.patch1, JELLY-194.patch2
>
> Hi,
> It would be nice if there was a Jelly tag similar to <ant:copy> that would 
> copy text files replacing the Jelly properties.
> For instance, I need to copy a datasource XML definition to JBoss before 
> running Cactus (on maven), but each developer in my project has its own 
> database schema. So, I could have a XML file like this:
>  
> <datasource>
>       <username>${ds.username}</username>
>       <password>${ds.password}</password>
> </datasource>
> And then something like this on maven.xml:
> <preGoal name="cactus:test">
>    <util:copyAndReplace file="datasource.xml" 
>          toFile="${env.JBOSS_HOME}/server/default/deploy"/> 
> </preGoal>
> If you think such tag is useful (and hence would be incorporated on Jelly), I 
> could write the tag and test cases and then submit a patch (I'm just not sure 
> what's the best name for it).
> -- Felipe

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to