Details
-
Type:
Wish
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Not A Bug
-
Affects Version/s: 1.0.2
-
Fix Version/s: 1.2
-
Component/s: jelly/ant integration
-
Labels:None
-
Environment:Maven 1.0.2 with plugins modifieds
Using JAVA 1.4 / 1.5 / 1.6
xdoclet-1.2-beta3
Ant 1.6.1 / 1.7.0 / 1.7.1
Clearcase 2002.05.00+
Cygwin (1.5.25-15 version)
Description
Hello,
I'm trying to delete view-private files on the clearcase in the CYGWIN with MAVEN by editing the maven.xml
Command that I use to delete view-private archives:
cleartool ls -recurse -view_only | xargs rm -rf
The maven.xml contains the follow project:
<project
xmlns:ant="jelly:ant"
xmlns:j="jelly:core"
xmlns:maven="jelly:maven"
xmlns:u="jelly:util"
>
Tries:
1 (executing in maven.xml with in the cmd executable using a .bat with the exclusion view-private command):
<goal name="blabla">
<exec dir="${basedir}" executable="cmd">
<arg value="/c"/>
<arg value="limpa_resources.bat"/>
</exec>
</goal>
ERROR:
[exec] cleartool: Error: Unable to access "|": Invalid argument.
[exec] cleartool: Error: Unable to access "xargs": No such file or directory.
[exec] cleartool: Error: Unable to access "rm": No such file or directory.
[exec] cleartool: Error: Unable to access "-rf": No such file or directory.
[exec] [ERROR] Result: 1
OBSERVATION: The "pipe" is not recognized by the maven exec.
2 (executing in maven.xml with the exclusion view-private command):
<goal name="blabla">
<exec dir="${basedir}" executable="cleartool">
<arg line="ls -recurse -view_only | xargs rm -rf"/>
</exec>
</goal>
ERROR:
[exec] 'limpa_resources.bat' não é reconhecido como um comando interno
[exec] ou externo, um programa operável ou um arquivo em lotes.
[exec] [ERROR] Result: 1
OBSERVATION: I don't know why this happens, I also tried to do this in the DOS.
Well,
I wish to know if is possible to use the "pipe" command in the tag execution or by using a .bat that execute this command.
And I want to know if is possible do DO or NOT.
I accept suggestions.
I aprecciate the attention,
Tks,
Timóteo Soutello, from Brazil
Please, ignore the fix version 1.2. I putted that version wrongly.
Tks,
Timoteo