ubject: RE: [m2] manually "deploying"?
It does upload the files now, but for some reason a checksum is only
generated for a metadata XML file, and not for the JAR or POM.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2008 4:33 PM
"deploying"?
Change your pom to use file:/// or scp:///
-Original Message-
From: Allen, Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2008 4:27 PM
To: Maven Users List
Subject: RE: [m2] manually "deploying"?
What do you mean? Change it how?
-Origin
Change your pom to use file:/// or scp:///
-Original Message-
From: Allen, Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2008 4:27 PM
To: Maven Users List
Subject: RE: [m2] manually "deploying"?
What do you mean? Change it how?
-Original Message-
Fro
16:27 -0400, Allen, Daniel wrote:
> What do you mean? Change it how?
>
> -Original Message-
> From: Brian E. Fox [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 26, 2008 2:49 PM
> To: Maven Users List
> Subject: RE: [m2] manually "deploying"?
>
>
What do you mean? Change it how?
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2008 2:49 PM
To: Maven Users List
Subject: RE: [m2] manually "deploying"?
If you have file or scp access to the repo, why not just change the
distMgt
If you have file or scp access to the repo, why not just change the
distMgt url in the meantime?
-Original Message-
From: Allen, Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2008 2:42 PM
To: Maven Users List
Subject: RE: [m2] manually "deploying"?
Something
3 PM
To: Maven Users List
Subject: RE: [m2] manually "deploying"?
Wouldn't it be easier to have someone else deploy it for you?
Every file that goes into the repository gets a sha1 and md5 hash. That
minimally means the pom and the jar.
--
This message may contain confidential,
Maven Users List
Subject: [m2] manually "deploying"?
Ok, so I know it's sort of an asinine thing to do. However, currently
mvn deploy is returning an HTTP 405 error from our repository, and I
don't really have control over our company repository (new employee
doesn't get
Ok, so I know it's sort of an asinine thing to do. However, currently
mvn deploy is returning an HTTP 405 error from our repository, and I
don't really have control over our company repository (new employee
doesn't get permissions for a while), so I can only do a manual copy to
the appropriate poin
