[
http://jira.codehaus.org/browse/MOUNCE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189414#action_189414
]
Brian Fox commented on MOUNCE-2:
--------------------------------
The thought behind this was that it is exactly like eclipse:eclipse where it
generates the files needed by the ide in the root and the scm system is told to
ignore those files just like we do with .classpath, .project etc.
Assuming that won't work, then the next logical place is to just put them in
/target. Making it completely configurable is probably unnecessary and overly
complicated. The benefit (or drawback, not sure) is that target is wiped on a
clean build.
> 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
