Issue Details (XML | Word | Printable)

Key: CACTUS-232
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Petar Tahchiev
Reporter: Felipe Leme
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Cactus

Create new property for Cactus classes destination

Created: 20/Oct/05 05:15 AM   Updated: 11/Apr/08 12:34 PM
Return to search
Component/s: Maven Integration
Affects Version/s: 1.7.1
Fix Version/s: 1.8

Time Tracking:
Not Specified

Resolution Date: 08/Mar/08 11:16 AM


 Description  « Hide
I had to customize the Eclipse plugin to create a special folder for the classes generated by Cactus, but the plugin does not supply that information, while the JUnit/Test plugin does. More specifically, the Eclipse plugin has the following entry:

<j:if test="${empty testOutputDir}">
    <maven:get var="testOutputDir" plugin='maven-test-plugin' property='maven.test.dest'/>
  </j:if>

Looking on the maven-test-plugin, we get:

maven.test.dest = ${maven.build.dir}/test-classes

But the Cactus plugin does not supply such properyl; instead, it defines it on plugin.jelly:

    <ant:property name="cactus.target.classes.dir"
        value="${maven.build.dir}/test-cactus-classes"/>

So, in order to be consistent, I propose we create the cactus.test.dest property (which in turn would receive the ${maven.build.dir}/test-cactus-classes. value).

-- Felipe




 

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Petar Tahchiev added a comment - 08/Mar/08 11:16 AM
Ok, I have added the cactus.test.dest property, so I will close this issue now.