That's why I've split it up into : core (the core classes) standalone (the uberjar wrapper) webapp (which will generate a war wrapper) plexus (created if someone demands it - as a summit thingamajig I suspect)
The webapp wrapper should be trivial
Cheers,
Ben
Brett Porter wrote:
Cool idea... Any chance of also building a WAR that can be dropped into an existing app server on the intranet? :))
- Brett
-----Original Message-----
From: Ben Walding [mailto:[EMAIL PROTECTED] Sent: Monday, 18 August 2003 2:12 PM
To: [EMAIL PROTECTED]
Subject: Maven-Proxy snapshot available
Hello all,
I've finished a rough prototype of the maven-proxy that I mentioned on IRC last week.
The gist of the concept is this: A common in house repo is good. Although, unless you're mirroring from ibiblio, it is liable to get out of date quickly enough. The maven-proxy solves this by sitting on your intranet server and mimicing ibiblio. All devs are pointed at the intranet server (eg
maven.repo.remote=http://<intranet>:4321 ) When it receives a request, it retrieves from cache / downloads from it's upstream server(s). SNAPSHOT expiration can be faked with a cron job for the time being.
Some halfbaked wiki info - http://wiki.codehaus.org/maven/MavenProxy The binary download is available via the wiki.
It is checked into the codehaus cvs at the moment - host: cvs.codehaus.org cvsroot: /home/cvspublic module: maven-proxy (core / standalone / testrepo)
Issues can be logged into the proxy component on jira Suggestions for features can go into the wiki / jira.
--------------------------------------------------------------------- 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]
