Hi all,
I am struggling with the issue again (we previously fixed it using the
file:/ protocol, which we can't use any more, and I got webdav to work, but
we can't use it now as well...). I am trying the example maven recipe by
Jason van Zyl (using $maven_home/lib/ext) and it seems to work only fo
Go for it. I won't be using the maven site plugin anytime soon.
On Aug 29, 2011, at 12:30 PM, Stephen Connolly wrote:
> Jason. it would be great if we had this documented somewhere in the maven
> site.
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonse
Jason. it would be great if we had this documented somewhere in the maven
site.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 29 Aug 2011 08:30, "Jason van Zyl" wrote:
>
You can either use the ext/ directory in the Maven installation, or use the
extension classpath property so that the scp wagon will load. I created a
little recipe with an example of each method:
https://github.com/jvanzyl/maven-recipes/tree/master/deploy-with-scp-extension
On Aug 29, 2011, at
Just create a pom.xml with dummy coords and run from the directory
with that pom using deploy:deploy-file
4.0.0
localdomain.localhost
dummy
1-SNAPSHOT
mvn deploy:deploy-file -DgroupId=my.groupId -DartifactId=my-artifact
-Dversion=62.65 -Dfile=... -Dpackaging=... -
Maxime Gréau wrote:
>
> In all cases (I mean if you have an existing pom.xml or not), there will
> be
> a pom.xml with the artifact in the remote repository.
>
> If you want to deploy an existing file (jar, war...) in a remote
> repository,
> you have 2 choices :
> - use deploy:deploy-file goal,
In all cases (I mean if you have an existing pom.xml or not), there will be
a pom.xml with the artifact in the remote repository.
If you want to deploy an existing file (jar, war...) in a remote repository,
you have 2 choices :
- use deploy:deploy-file goal, this goal can be execute with or withou
Maxime Gréau wrote:
>
>
>
> 2) If you want to use an other protocol like DAV (or SCP, FTP...), you
> have
> to add an extension in your POM, this is the example for DAV :
>
What if you don't have a pom? I have some jars produced by other means and
want to push it to a maven repository to hav
Hi,
Since Maven 3.0, by default, you can only use HTTP protocol to deploy
artefacts in a remote repository.
1) If you want to use HTTP protocol, you have to ensure that
- your remote repository allow HTTP PUT method
- your credentials are ok
2) If you want to use an other protocol like DAV (or S
Hi. I am trying to deploy a custom artifact to our internal repo using maven
3.0.2:
mvn deploy:deploy-file -Dfile=file.jar -Dversion=1.0.0 -DgroupId=com.example
-DartifactId=artifact -Dpackaging=jar -DrepositoryId=internal
-Durl=dav:http://10.1.1.7/maven_repo
where a corresponding elemen
10 matches
Mail list logo
