Hi Mark,
On 19/04/2008, at 5:13 PM, Mark Struberg wrote:
To be more specific:
Look at the maven-deploy-plugin
http://maven.apache.org/plugins/maven-deploy-plugin/usage.html
and use the
mvn deploy:deploy-file
mojo
Example:
mvn deploy:deploy-file -DrepositoryId=myrepo.id \
-Dfile=myjartoupload.jar \
-DgroupId=my.groupId \
-DartifactId=my-artifactId \
-Dversion=myversion \
-Dpackaging=jar \
You can use this mojo from everywhere, since it is marked as
'@requiresProject false'.
If this was successfull (check your ~/.m2/repository), you may
remove this jar from your lib
folder and add the dependency in your pom.
I'm wondering how this helps another developer who checks out the
project? Or indeed if my system gets somehow hosed?
I have no permissions to be creating a shared repo. Thus I need to be
able to keep the jars with the project. With ant this was completely
simple (one of the few nice things about ant)... so I don't quite
appreciate why it needs to be so complex with maven?
Fair enough for world-sharable jars (i.e., all the various open-source
projects out there) - but for a private jar I can't see the sense in
it (at least yet).
Thanks...
with regards,
--
Lachlan Deck
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
