DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=22020>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=22020


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]




------- Additional Comments From [EMAIL PROTECTED]  2005-04-19 21:25 -------
Well, 1.5 years later, I am again in need of something along these lines, so I
figured I might as well ping this bug...

The current scenario is I am trying to set up a simple text based interactive
build that uses input to collect various parameters (rather than having 15
different -D arguments). This will be distributed as part of a zip file and used
by the customer to create a warfile with the tweaks needed for their 
environment.

Since the customer gets the source code ayway, the quickest way to do this zip
up the source and write an small build file that imports the development build,
but hides dangerous targets from the user. It would be a disaster if they
accidentally ran recreate-db against their production DB since the first thing
it does is wipe the entire database.

This need is slightly different than the intent of my patch, but closely
related. I have created duplicate targets in the build file to match the one
imported which helps (forcing the targets to be refered to as
buildname.sometarget instead of just sometarget), but imported targets show up
under project help.

Has any further thought been given to controling access to targets? Have I
missed something in the past year? (I'm re-subscribing to the dev list so feel
free to answer me there)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to