[
https://issues.apache.org/jira/browse/AXIS2-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694592#action_12694592
]
Jason Fager commented on AXIS2-4295:
------------------------------------
Just for discussion's sake, why not set the targetPath to '.'?
Pegging the build to a particular version of a Maven plugin, maybe that is the
right way to get a repeatable build. I've never done it, though, and I kind of
get a headache thinking about managing that... if you're doing it for one
plugin, shouldn't you be doing it for all?
But even if it is the 'right' thing, planning ahead a bit, when the time comes
to bump up to the next Maven version, this change would need to be made
anyways. If it works with the earlier plugin as expected, then may as well do
it now, right?
> saaj testResource has empy targetPath
> -------------------------------------
>
> Key: AXIS2-4295
> URL: https://issues.apache.org/jira/browse/AXIS2-4295
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: saaj
> Affects Versions: nightly
> Reporter: Jason Fager
>
> In saaj's pom.xml, the targetPath that the *.properties are being copied to
> is empty. This results in the build attempting to copy the file into '/'
> <testResource>
> <targetPath></targetPath> <!-- Not good. -->
> <directory>test-resources</directory>
> <includes>
> <include>**/*.properties</include>
> </includes>
> </testResource>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
