Hi Maven Gurus,
When executing "mvn deploy:deploy", I see this error:
"The packaging for this project did not assign a file to the build
artifact".
The deployment works fine with "mvn deploy" since it executes all the
prior maven lifecycle phases.
I'm jus
All,
When attempting to use mvn deploy:deploy or even if I try mvn
deploy:deploy-file I am getting an error that reads "The packaging for this
project did not assign a file to the build artifact" . I am trying to use
the deploy command to release a jar into our local repository. I
All,
When attempting to use mvn deploy:deploy or even if I try mvn
deploy:deploy-file I am getting an error that reads "The packaging for this
project did not assign a file to the build artifact" . I am trying to use
the deploy command to release a jar into our local repository. I
All,
When attempting to use mvn deploy:deploy or even if I try mvn
deploy:deploy-file I am getting an error that reads "The packaging for this
project did not assign a file to the build artifact" . I am trying to use
the deploy command to release a jar into our local repository. I
> The deployment works fine with "mvn deploy" since it executes all the prior
> maven lifecycle phases.
> I'm just wondering can "mvn deploy:deploy" work as an independenct
> lifecycle phase?
You should probably look at using "mvn deploy:deploy-file&
Does "mvn deploy:deploy" work? Has anyone successfully executed
"deploy" goal with maven-deploy-plugin?
Wayne Fay wrote:
The deployment works fine with "mvn deploy" since it executes all the prior
maven lifecycle phases.
I'm just wondering can "mv
> Does "mvn deploy:deploy" work? Has anyone successfully executed "deploy"
> goal with maven-deploy-plugin?
If you've ever deployed anything from Maven via "mvn deploy", then
you've used the deploy mojo in the maven-deploy-plugin. That is what
runs
"deploy" goal but
looks like maven-deploy-plugin does not allow you to directly execute
the deploy goal.
Jane
Wayne Fay wrote:
Does "mvn deploy:deploy" work? Has anyone successfully executed "deploy"
goal with maven-deploy-plugin?
If you've ever de
not allow you to directly execute the
> deploy goal.
>
> Jane
>
>
>
> Wayne Fay wrote:
>
>> Does "mvn deploy:deploy" work? Has anyone successfully executed "deploy"
>>> goal with maven-deploy-plugin?
>>>
>>>
>>
>> If you
need to deploy with something like a
shell script etc. But this will not work with simply "mvn
deploy:deploy" as you've discovered.
Take a look at Nexus Pro's staging functionality, if you're looking
for this kind of feature and have a budget for it. Or build it
yoursel
There is no file been set to your artifact. Try to execute mvn deploy only
-allan
Raymond N. Ritz wrote:
All,
When attempting to use mvn deploy:deploy or even if I try mvn
deploy:deploy-file I am getting an error that reads "The packaging for this
project did not assign a file to the
When attempting to use mvn deploy:deploy or even if I try mvn
> deploy:deploy-file I am getting an error that reads "The packaging for this
> project did not assign a file to the build artifact" . I am trying to use
> the deploy command to release a jar into our local reposit
I have a question about mvn deploy:deploy-file. I would like to be able
to specify the repository URL on its own, because I am using maven-proxy
as a method of serving our company repository to the team. Therefore I
don't need an entry in the settings.xml.
If I don't specify the reposi
So can't you add the internal repository anyway for deployment purposes? -K
On 6/5/06 12:38 PM, "Adam Hardy" <[EMAIL PROTECTED]> wrote:
> I have a question about mvn deploy:deploy-file. I would like to be able
> to specify the repository URL on its own, because I
;Adam Hardy" <[EMAIL PROTECTED]> wrote:
I have a question about mvn deploy:deploy-file. I would like to be able
to specify the repository URL on its own, because I am using maven-proxy
as a method of serving our company repository to the team. Therefore I
don't need an entry in the s
06 12:38 PM, "Adam Hardy" <[EMAIL PROTECTED]> wrote:
>
>> I have a question about mvn deploy:deploy-file. I would like to be able
>> to specify the repository URL on its own, because I am using maven-proxy
>> as a method of serving our company repository to the te
Great! That's just what I need. Now I ditch the profile from my
settings.xml.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
ben short
Sent: 05 June 2006 23:10
To: Maven Users List
Subject: Re: [m2] mvn deploy:deploy-file
Adam,
You can us
Hi folks,
We are using Maven 2.1.0 and have provided the following settings.xml file:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd";>
I am trying to run mvn deploy:deploy-file using PSCP using maven 3 on
windows 7. I have made it work without using maven using the following
command:
pscp bob.txt m...@repository:/var/lib/tomcat5.5/webapps/p2/deploytest/bob.txt
but when I try to run the following maven goal:
mvn deploy:deploy
Hi Afkham Azeez
The id is the field that connects the server entry to the repository entry. It
should be the same in both places. And you need a server entry for each
repository.
In our project's POM file, we have the following distribution
management section:
wso2-
would do something like this:
mvn deploy:deploy-file -DartifactId=spring-mock \
-Dfile=spring-mock-v1.2.4.jar \
-DgeneratePom=true \
-DgroupId=org.springframework \
-Dversion=1.2.4 \
-Dpackaging=jar \
-Durl=http://10.0.0.200/repository \
-DrepositoryId=dwfa
I tried this and got a 405 response
Hi,
I need to deploy a txt file with license info to a remote Nexus repository.
Can this be done with mvn deploy:deploy-file
mvn deploy:deploy-file -DgroupId=com.xyz -DartifactId=zyx-component
-Dversion=1.0.0 -Dfile=C:/licesne.txt -Dpackaging=txt
-Durl=http://my.nexus.url
I tried the above but
On 4/25/06, Douglas WF Acheson <[EMAIL PROTECTED]> wrote:
> I expected to be prompted for the password for the user www, but I was
> prompted for my password, h. So my question is, how do I specify
> the uid and password or key (for ssh) for this goal?
In ~/.m2/settings.xml, add a for dwfa.
Hello,
I have added the element and appropriate inner elements (at
least I think I did) to my settings.xml - thx for the help. But, I am
still being prompted for my password. I want to use a different uid not
the one I am logged in with. Here is my settings.xml file
Perhaps you spelled the name of the file incorrectly?
On Thu, Apr 12, 2012 at 9:59 AM, DK wrote:
> Hi,
>
> I need to deploy a txt file with license info to a remote Nexus repository.
> Can this be done with mvn deploy:deploy-file
>
> mvn deploy:deploy-file -DgroupId=com.xy
Hi,
I have filed an issue with WebDAV here.. Have I missed anything obvious?
http://jira.codehaus.org/browse/MRM-408
Damon.
--
View this message in context:
http://www.nabble.com/The-mvn-deploy%3Adeploy-file-command-gives-409-%22Parent-doesn%27t-exist%22-tf3846842.html#a10895032
Sent from
Hi,
While using the upload to nexus repository, used the following command
and it worked fine:
mvn -e deploy:deploy-file -DfilePath=testDir -DartifactId=test
-Dpackaging.type=ear
In this case the pom.xml containg the repository details is in the same
directory.
To make it more generic I
:
mvn deploy:deploy-file -Dfile=myLib-x64-natives-linux.zip
-Dclassifier=natives-linux -DgroupId=com.myCompany -DartifactId=myLib
-Dversion=1.0.0 -DrepositoryId=archiva.internal
-Durl=http://centos-dev:8090/repository/internal/
On a Windows computer:
mvn deploy:deploy-file -Dfile=jre-x64-natives-wi
Hi all,
I have a WAR and I have no problem to deploy it to Tomcat manually. Then I
try using "mvn tomcat:stop -Dmaven.tomcat.url=http://localhost:8585/manager"; to
deploy it. Normally the WAR and all the directories and files will be copied to
the webapps. But it's by me not the case. I ca
You can find the documentation for the parameters of this plugin goal at
this URL:
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
You need to supply both the "url" and "file" parameters.
surendra.na...@verizonwireless.com wrote:
> Hi,
>
> While using the upload to nex
[mailto:denn...@apache.org]
Sent: Thursday, April 16, 2009 3:45 PM
To: Maven Users List
Subject: Re: Help on using -DpomFile option in "mvn deploy:deploy-file"
command
You can find the documentation for the parameters of this plugin goal at
this URL:
http://maven.apache.org/plugins/maven-dep
Maven. I have
> 2 Jenkins jobs building the same native library on 2 different
> systems (win / lin). At the end of each one, I want to deploy them
> on my Archiva repo. So I execute the following commands :
>
> On a Linux computer: mvn deploy:deploy-file
> -Dfile=myLib-x64-native
the native libraries (mvn install there,
not mvn deploy!),
- and then collect the artifacts generated from the
multiconfiguration job and deploy them to your
repository:
mvn deploy:deploy-file \
-Durl=http://centos-dev:8090/repository/internal/ \
-DrepositoryId=archiva.internal
Hello all,
> >
> > I'm in the process of converting an existing build to Maven. I have
> > 2 Jenkins jobs building the same native library on 2 different
> > systems (win / lin). At the end of each one, I want to deploy them
> > on my Archiva repo. So I execute the fo
Best regards,
> >
> > Sandra
> >
> > Am 29.06.2015 um 09:53 schrieb Francois MAROT:
> > > Hello all,
> > >
> > > I'm in the process of converting an existing build to Maven. I have
> > > 2 Jenkins jobs building the same native library on
s build -Dclassifier=win.
> > >
> > > Best regards,
> > >
> > > Sandra
> > >
> > > Am 29.06.2015 um 09:53 schrieb Francois MAROT:
> > > > Hello all,
> > > >
> > > > I'm in the process of converting an
-and-deploy approach.
> -Original Message-
> From: Francois Marot [mailto:francois.ma...@gmail.com]
> Sent: Monday, June 29, 2015 9:50 AM
> To: Maven Users List
> Subject: [EXTERNAL] Re: mvn deploy:deploy-file with same groupId &
> artifactId but different classifiers
>
> @Je
OK all, so I've taken the "not so clean but should solve my problem faster"
road... I publish the 2 zips separatly on Archiva.
But now, my main build that declare dependencies on them both (as 'runtime')
seems to randomly fail, looking for one or the other. If I publish one of
the 2, the main build
OK, so Maven only sees the most recent one uploaded because on Archiva, the
"maven-metadata.xml" file is updated each time with the timestamp of the
most recent one (either *-linux or *-win). But the 2 qualified artifacts do
not share the same timestamp so one of those is not found leading to build
39 matches
Mail list logo
