I think this question might be better suited to the Nexus ML, but anyway we
actually use nexus and don't use ssh protocol, simple http (webdav) and it
works fine.
I don't even know if Nexus supports ssh transport.
In your case, if possible, I'd try using http instead of ssh.
If not possible, mayb
Hi There,
I am totally desperated! I try to deploy an artifact via maven to my own
nexus server. But every time when I run "mvn deploy" I got the following
stacktrace:
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ core ---
Uploading:
scpexe://nexus.innosquared.com/nexus/content/rep
YES I found out !!!
I tried to add the distributionManagement Tag in each module of my
multi-module project..
and it worked !!
Still dunno why deploy goal does no need it, and perform goal needs.. but,
it works !!
Thanks everyone for your help, sincerely
Jeremy
--
View this message in contex
Hi Mark,
I do you think that it might be a permission problem even if the deploy goal
does work ?
It seems that I'm not the first one encounting that issue.. but I just don't
find any workaround..
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-fa
Stephen is right about how to set up Nexus.
You probably should have got all this advice from the Nexus installation
docs.
Read them and direct some/most of these questions to the Nexus forum.
Ron
On 18/01/2011 4:25 AM, Stephen Connolly wrote:
On 18 January 2011 09:08, jeb001 wrote:
ok...
I tried that, still the same result...
I begin to think that a single module project should be more easy to work
with...
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3346186.html
Sent from the Maven - Users maili
-0.0.5.pom
, right?
--- On Tue, 1/18/11, jeb001 wrote:
> From: jeb001
> Subject: Re: Maven release:perform deploy failed access denied
> To: users@maven.apache.org
> Date: Tuesday, January 18, 2011, 12:48 PM
>
> Hum.. I tried something else, I launched the mvn:deploy
&g
Hum.. I tried something else, I launched the mvn:deploy task, and it works !!
... I jus't don't understand... any idea ?
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3346122.html
Sent from the Maven - Users mailing
On 18 January 2011 09:40, jeb001 wrote:
>
> Ok, so..
>
> In my settings.xml :
>
> repository
> Miror nexus
> http://nexus/content/groups/MyRepositories/
>
> *,!repository-releases,!reposito
..unfortunately, I think I'm right in the pom structure :
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/maven-4.0.0.xsd";>
4.0.0
xxx/groupId>
xx
> So please, once you sort this out, post back with the root cause and
> your solution, for the benefit of others on the ml...
Hmmm going back and looking at a few of those emails, I think the
problem is that people are putting the distributionManagement node in
the wrong spot in their pom file. I
> INFO] [DEBUG] Trace
> [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Error
> configuring: org.apache.maven.plugins:maven-deploy-plugin. Reason: Unable to
> parse the created DOM for plugin configuration
I've seen this a few times related to the deploy plugin in the last ~8
months
with more details from the logs...
INFO] [DEBUG] Trace
[INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Error
configuring: org.apache.maven.plugins:maven-deploy-plugin. Reason: Unable to
parse the created DOM for plugin configuration
[INFO] at
org.apache.maven.lifecycle.DefaultLif
Ok, so..
In my settings.xml :
repository
Miror nexus
http://nexus/content/groups/MyRepositories/
*,!repository-releases,!repository-snapshots
in the pom.xml I remov
On 18 January 2011 09:25, Stephen Connolly
wrote:
> On 18 January 2011 09:08, jeb001 wrote:
>>
>> ok... If I try to sum up...
>>
>> First issue was to use a groups URL of nexus.. ok, it's correct now.
>
> Correct
>
>> Then, both of the distMgt tag and repository set the same URL..
>
> Incorrect..
On 18 January 2011 09:08, jeb001 wrote:
>
> ok... If I try to sum up...
>
> First issue was to use a groups URL of nexus.. ok, it's correct now.
Correct
> Then, both of the distMgt tag and repository set the same URL..
Incorrect...
distMgt should point to the repo. repositories should point to
Normally, the urls for deploying snapshots and release are different.
Surely there must be some kind of help/info where you work on how to
configure this? Most of these configs depend on how the infrastructure is
set up and it's very hard for us to tell you how your environment is.
/Anders
On Tue
ok... If I try to sum up...
First issue was to use a groups URL of nexus.. ok, it's correct now.
Then, both of the distMgt tag and repository set the same URL.. but
repositories tag have to
be moved in the settings.xml.
Am I right now ?
--
View this message in context:
http://maven.40175.n5
Nope.
you can (and should) deploy to your nexus/artifactory server.
you can (and should) pull dependencies from your nexus/artifactory server.
However, you might use groups to aggregate several repos in your nexus
server so that you only need the one definition (and
better yet keep that in your
Ok !
So, repository should design my nexus server ? and distMgt should design a
file server ?
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345828.html
Sent from the Maven - Users mailing list archive at Nabble.com
Those are two totally different things. distMgmt is where you want to deploy
to. repositories declare what repos you want to pull artifacts you depend
on.
/Anders
On Tue, Jan 18, 2011 at 09:40, jeb001 wrote:
>
> Ok, I'll try to precise what I'm saying.
> I understand that in the distrMgt, I hav
Ok, I'll try to precise what I'm saying.
I understand that in the distrMgt, I have to set snapshot, release and
eventually site url.. I understood in the log that the deploy task needs
that tag.
I noticed too that I need another tag in the pom file, a repositories tag.
I wonder why I have to set
Regarding special args for release:peform I don't understand the question.
What args to spec depends on what you want to do. Try it, read/google and
come back when you have a specific question.
Regarding distMagmt you need to spec a snapshot repo if you deloy snapshots
and a (release) repo if you
Ok, I guess it's getting a little better... but there's something I'm not
sure to understand.
First, my project is a multi-module project, should I set special arguments
when I launch release:perform ?
An then, I wonder what's the differences, in my main pom.xml between the tag
distributionManag
Go talk to your Nexus admins?
/Anders
On Fri, Jan 14, 2011 at 08:15, jeb001 wrote:
>
> Hum... no other suggestions ?
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3340910.html
> Sent from the Maven - Users
Hum... no other suggestions ?
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3340910.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
Nope. You need either os access or ui/rest access.
/Anders
On Thu, Jan 13, 2011 at 13:45, jeb001 wrote:
>
> Hum, ok... but, I'm using a distant nexus server.. I'm not administrator...
> Is there a way for me to see those logs ?
>
> thx
> --
> View this message in context:
> http://maven.40175.n
Hum, ok... but, I'm using a distant nexus server.. I'm not administrator...
Is there a way for me to see those logs ?
thx
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3339723.html
Sent from the Maven - Users mailin
You don't have access?
I suggest you have a look in the Nexus logs. It will tell you what it
doesn't like with your credentials.
/Anders
On Thu, Jan 13, 2011 at 10:54, jeb001 wrote:
>
> Hi,
>
>
> I'm trying to build my first release of my multi-modules projects.
> In my settings.xml :
>
>
Hi,
I'm trying to build my first release of my multi-modules projects.
In my settings.xml :
my-releases
deployer
123
in my main pom.xml :
30 matches
Mail list logo
