2011/2/20 Ondřej Světlík
> Dne 19.2.2011 20:58, Wayne Fay napsal(a):
>
> false
>>>
>>
>> Let me guess -- you're using Maven 3, right?
>>
>> From the Maven 3 compatibility notes:
>> Non-unique Snapshot Deployments
>> The settingfalse for a distribution
>> repository has no effect
Switching to wagon-httpd from lightweight helps. I added:
org.apache.maven.wagon
wagon-http
1.0-beta-7
And authentication works fine.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands
Removing settins-security.xml and placing unencrypted password to
settings.xml didn't help.
Logs don't say anything useful:
[WARNING] Could not transfer metadata xxx/maven-metadata.xml from/to
RVSNet (https://xxx/maven/): Access denied to:
https://xxx/maven-metadata.xml
org.sonatype.aether.transf
Get rid of the encryption. Make it work unencrypted. Then and only
then, add the encryption back.
Use "mvn -X" to get some useful debugging information. And check the
security logs in your repo manager for more help. You may also need to
take this up with the repo manager's user list.
Wayne
---
Dne 19.2.2011 20:58, Wayne Fay napsal(a):
false
Let me guess -- you're using Maven 3, right?
From the Maven 3 compatibility notes:
Non-unique Snapshot Deployments
The settingfalse for a distribution
repository has no effect in version 3.x, snapshot artifacts will
always be de
> With my master password.
...
> With my own encrypted password.
Get rid of the encryption. Make it work unencrypted. Then and only
then, add the encryption back.
Use "mvn -X" to get some useful debugging information. And check the
security logs in your repo manager for more help. You may also ne
> false
Let me guess -- you're using Maven 3, right?
>From the Maven 3 compatibility notes:
Non-unique Snapshot Deployments
The setting false for a distribution
repository has no effect in version 3.x, snapshot artifacts will
always be deployed using a timestamped version.
https:/
Dne 19.2.2011 20:29, Ondřej Světlík napsal(a):
Hello,
I went through all manuals and my configuration should be all right. But
it doesn't work.
I have a repository that uses HTTP authentication. I have created
~/.m2/settings-security.xml:
{...}
With my master password.
I have a section in
Hello,
I went through all manuals and my configuration should be all right. But
it doesn't work.
I have a repository that uses HTTP authentication. I have created
~/.m2/settings-security.xml:
{...}
With my master password.
I have a section in my ~/.m2/settings.xml:
MyRe
Hello,
I have this configuration in my parent POM:
false
my-scp-repo
My Repository
scpexe://example.com/repository/
But when I mvn deploy my projects, they are still uploaded with
generated version. The configu
I'm trying:
$ mvn release:prepare
But then it prints a list of class files under my target directory which
I've set hg to ignore, and then fails:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.1:prepare
> (default-cli) on project X: Cannot
> prepare the releas
11 matches
Mail list logo
