Hi Stephen,
On 19/04/2008, at 6:10 PM, Stephen Connolly wrote:
The following is _not_ recommended.
Once you get more used to Maven you will realize that storing your
binary
artifacts in SVN is a "bad thing".
Fundamentally, they are a different creature from the source code.
I mostly concur - however in this case, the particular jar files of
interest seem more like a static resource as they're provided by a 3rd
party, will rarely be updated, and come pre-built. They simply need to
be on the classpath at compile/runtime.
What you should do is use a Maven repository manager (e.g. Nexus,
Artifactory, etc) and deploy your binary artifacts to that manager.
Not possible in this scenario... for better or worse.
There is a poor man's solution to your problem... and that is to
fake a
remote repository in subversion providing your subversion is served
over
http (if Maven > 2.0) or https (if Maven > 2.0.5)
You add a repository definition where the repository URL is the
place in SVN
where you are keeping your remote repository
Basically, you'd be doing similar to what has been done at
https://maven2-repository.dev.java.net
That way your binaries are kept in SVN, but the developer does not
check out
the trunk of that repository, only accesses it via HTTP
Just to be clear - the only jars that'll be in this psuedo repo will
be those used by the project. But what you're suggesting would be
quite useful. Naturally that'll require authentication in each persons
settings file. No problems.
Okay I think my next question would be: is there an easy maven command
for culling jars prior to a certain version from a repository?
e.g., say I've added versions 1, 2, 3 and 4 to the repository (such as
nightly builds or something)... is there a command that would easily
remove versions prior to 3?
Thanks again...
with regards,
--
Lachlan Deck
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
