On 13 Apr 07, at 12:28 PM 13 Apr 07, John Casey wrote:
so, would the deploy plugin read these properties and set them on
the wagon
at deployment time,
Yah, the deployer in maven-artifact would use this and pop the right
things into Wagon.
or would you have some sort of cron job to keep things
honest?
If you ran a fix script then any subsequent deployment should obey
the the repository properties.
I'm guess you'll have to have both, since older versions of the
deploy plugin won't know to look for the repo.properties...
Yah, though it wouldn't take long for a new deploy plugin to circulate.
Overall, I think it's a decent idea.
-john
On 4/13/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
I'm tired of screwing around with deployments not working with the
right permissions and groups. The last fix to the deployments make
the permissions decent by default but that's not enough as I deployed
something that didn't have a group at all.
So I would like to propose using a simple properties file at the root
of the server that all deployments will obey. Something like:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/maven-
repository.properties
Just a first though but it's simple and should work. The only thing
that would need to be taken into account is a script that would flip
everything if you decided to change any of the listed properties. But
we could easily make a plugin to generate a script, deploy it and run
it.
Jason.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
