[
http://jira.codehaus.org/browse/MOUNCE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189587#action_189587
]
Brian Fox commented on MOUNCE-2:
--------------------------------
I guess the real problem is those that do commit them. In that case though I
think the current location is as good as any other since:
1) the scm would know about them
2) they need to be inside the tree for them to be in scm
3) the standard release rules would apply where the files shouldn't have been
modified.
Does that mean an option to locate in target or not really is sufficient? I'm
trying to see if there's really motivation to allow the files to be in any
arbitrary location as that would increase the amount of code changes
significantly, and I'm not sure the impact on the ounce tool itself it that
were possible.
> Ability to control the location of the application and project files
> --------------------------------------------------------------------
>
> Key: MOUNCE-2
> URL: http://jira.codehaus.org/browse/MOUNCE-2
> Project: Maven 2.x Ounce Plugin
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Wendy Smoak
> Assignee: Sam Headrick
> Fix For: 1.3
>
>
> The .paf and .ppf files always get written to ${basedir}. Assuming it's
> supported by the underlying tool, please add configuration options to control
> where these files get written.
> The <applicationFile> parameter exists, but only affects where the file is
> *read* from, not where it is written to.
> Writing the files to ${basedir} breaks the release process, which sees them
> as local changes needing to be checked in before the release can continue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
