[
http://jira.codehaus.org/browse/MOUNCE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189582#action_189582
]
Wendy Smoak commented on MOUNCE-2:
----------------------------------
As discussed on irc... there are different workflows for these files.
Mine is to generate them and throw them away after the build, so I want them in
target. Having them at the project root requires each project to configure
svn:ignore (after their first release breaks and they learn what's wrong.)
But I understand that other people check these files into svn and manage them,
so target wouldn't be appropriate for them.
> 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
