You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ralph Pöllath <li...@poellath.org> on 2005/09/20 14:23:54 UTC

[m2] trouble accessing internal repository with beta1

Hi,

since I upgraded to m2 beta 1, I'm having trouble accessing artifacts  
in my internal company-wide repository.

m2 -X deploy prints

...
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from internal-repo

and then hangs forever. I assume it's not an authentication problem,  
because changing the password in settings.xml fails immediately with  
an AuthenticationException.

Any ideas?

Cheers,
-Ralph.




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Ralph Pöllath <li...@poellath.org>.
On 24.09.2005, at 02:31, Brett Porter wrote:
> Yep, sftp will work. ftp will work if wagon-ftp is added as an  
> extension.

So I switched my access method from scp to sftp with beta-1.

Now I'm trying to deploy a project that does not yet exist in either  
the local or internal (company-wide) repository, and m2 fails like this:

---
[INFO] [install:install]
[INFO] [deploy:deploy]
Uploading: sftp://internal.example.com/home/maven/maven2/blah/blah/ 
0.1/blah-0.1.jar
[INFO] Retrieving previous metadata from internal
[INFO]  
------------------------------------------------------------------------ 
----
[ERROR] BUILD ERROR
[INFO]  
------------------------------------------------------------------------ 
----
[INFO] Diagnosis: Error deploying artifact
[INFO]  
------------------------------------------------------------------------ 
----
[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: Error deploying artifact
...
Caused by:  
org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error  
deploying artifact:
...
Caused by:  
org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: U 
nable to retrieve metadata
....
Caused by: org.apache.maven.wagon.TransferFailedException: Error  
occured while downloading from the remote repository:[internal] ->  
sftp://internal.example.com/home/maven/maven2
...
Caused by: No such file
         at com.jcraft.jsch.ChannelSftp.throwStatusError(Unknown Source)
         at com.jcraft.jsch.ChannelSftp.stat(Unknown Source)
         at com.jcraft.jsch.ChannelSftp.get(Unknown Source)
         at com.jcraft.jsch.ChannelSftp.get(Unknown Source)
         at org.apache.maven.wagon.providers.ssh.SftpWagon.get 
(SftpWagon.java:216)
---

In the internal repository, the jar, jar.md5 and jar.sha1 files have  
been created, but no pom. I'm wondering what file m2 is trying to  
retrieve? The "No such file" error message could be improved by  
adding the expected file name.

> The doco on this area is a little lean, but we're working on it now.

Thanks Brett, your work on m2 and help on this list is highly  
appreciated!

Cheers,
-Ralph.

> On 9/23/05, Ralph Pöllath <li...@poellath.org> wrote:
>
>> Hi,
>>
>> since deployment via scp is broken for me in beta-1, is there a
>> possible alternative, like sftp or ftp?
>>
>> Maybe I'm lacking sleep or caffeine, but I just cannot find any
>> documentation on this.
>>
>> Cheers,
>> -Ralph.
>>
>> On 22.09.2005, at 12:45, Ralph Pöllath wrote:
>>
>>> On 22.09.2005, at 11:53, Brett Porter wrote:
>>>
>>>> Not what I wanted to see :(
>>>>
>>>> Can you post this to JIRA for tracking, and I'll take a look at  
>>>> what
>>>> has changed since alpha-3 to try and narrow it down.
>>>>
>>>
>>> Done: http://jira.codehaus.org/browse/MNG-959
>>>
>>>
>>>> Do other jdks or servers succeed?
>>>>
>>>
>>> I have no way of trying right now, but will comment on MNG-959 once
>>> I find out.
>>>
>>> Cheers,
>>> -Ralph.
>>>
>>>
>>>> On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
>>>>
>>>>
>>>>> "Connect thread maven.example.com session" prio=5 tid=0x005651b0
>>>>> nid=0x1e20000 runnable [f0c89000..f0c89ac0]
>>>>>          at java.net.SocketInputStream.socketRead0(Native Method)
>>>>>          at java.net.SocketInputStream.read
>>>>> (SocketInputStream.java:129)
>>>>>          at com.jcraft.jsch.IO.getByte(Unknown Source)
>>>>>          at com.jcraft.jsch.Session.read(Unknown Source)
>>>>>          at com.jcraft.jsch.Session.run(Unknown Source)
>>>>>          at java.lang.Thread.run(Thread.java:552)
>>>>>
>>>>> "main" prio=5 tid=0x00500e30 nid=0x1804600 in Object.wait()
>>>>> [f07fe000..f08002c8]
>>>>>          at java.lang.Object.wait(Native Method)
>>>>>          - waiting on <0x650a5f08> (a com.jcraft.jsch.Channel
>>>>> $MyPipedInputStream)
>>>>>          at java.io.PipedInputStream.read(PipedInputStream.java: 
>>>>> 229)
>>>>>          - locked <0x650a5f08> (a com.jcraft.jsch.Channel
>>>>> $MyPipedInputStream)
>>>>>          at org.apache.maven.wagon.providers.ssh.ScpWagon.checkAck
>>>>> (ScpWagon.java:614)
>>>>>          at org.apache.maven.wagon.providers.ssh.ScpWagon.get
>>>>> (ScpWagon.java:407)
>>>>>
>>>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Brett Porter <br...@gmail.com>.
Yep, sftp will work. ftp will work if wagon-ftp is added as an extension.

The doco on this area is a little lean, but we're working on it now.

- Brett

On 9/23/05, Ralph Pöllath <li...@poellath.org> wrote:
> Hi,
>
> since deployment via scp is broken for me in beta-1, is there a
> possible alternative, like sftp or ftp?
>
> Maybe I'm lacking sleep or caffeine, but I just cannot find any
> documentation on this.
>
> Cheers,
> -Ralph.
>
> On 22.09.2005, at 12:45, Ralph Pöllath wrote:
> > On 22.09.2005, at 11:53, Brett Porter wrote:
> >> Not what I wanted to see :(
> >>
> >> Can you post this to JIRA for tracking, and I'll take a look at what
> >> has changed since alpha-3 to try and narrow it down.
> >
> > Done: http://jira.codehaus.org/browse/MNG-959
> >
> >> Do other jdks or servers succeed?
> >
> > I have no way of trying right now, but will comment on MNG-959 once
> > I find out.
> >
> > Cheers,
> > -Ralph.
> >
> >> On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
> >>
> >>> "Connect thread maven.example.com session" prio=5 tid=0x005651b0
> >>> nid=0x1e20000 runnable [f0c89000..f0c89ac0]
> >>>          at java.net.SocketInputStream.socketRead0(Native Method)
> >>>          at java.net.SocketInputStream.read
> >>> (SocketInputStream.java:129)
> >>>          at com.jcraft.jsch.IO.getByte(Unknown Source)
> >>>          at com.jcraft.jsch.Session.read(Unknown Source)
> >>>          at com.jcraft.jsch.Session.run(Unknown Source)
> >>>          at java.lang.Thread.run(Thread.java:552)
> >>>
> >>> "main" prio=5 tid=0x00500e30 nid=0x1804600 in Object.wait()
> >>> [f07fe000..f08002c8]
> >>>          at java.lang.Object.wait(Native Method)
> >>>          - waiting on <0x650a5f08> (a com.jcraft.jsch.Channel
> >>> $MyPipedInputStream)
> >>>          at java.io.PipedInputStream.read(PipedInputStream.java:229)
> >>>          - locked <0x650a5f08> (a com.jcraft.jsch.Channel
> >>> $MyPipedInputStream)
> >>>          at org.apache.maven.wagon.providers.ssh.ScpWagon.checkAck
> >>> (ScpWagon.java:614)
> >>>          at org.apache.maven.wagon.providers.ssh.ScpWagon.get
> >>> (ScpWagon.java:407)
> >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Ralph Pöllath <li...@poellath.org>.
Hi,

since deployment via scp is broken for me in beta-1, is there a  
possible alternative, like sftp or ftp?

Maybe I'm lacking sleep or caffeine, but I just cannot find any  
documentation on this.

Cheers,
-Ralph.

On 22.09.2005, at 12:45, Ralph Pöllath wrote:
> On 22.09.2005, at 11:53, Brett Porter wrote:
>> Not what I wanted to see :(
>>
>> Can you post this to JIRA for tracking, and I'll take a look at what
>> has changed since alpha-3 to try and narrow it down.
>
> Done: http://jira.codehaus.org/browse/MNG-959
>
>> Do other jdks or servers succeed?
>
> I have no way of trying right now, but will comment on MNG-959 once  
> I find out.
>
> Cheers,
> -Ralph.
>
>> On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
>>
>>> "Connect thread maven.example.com session" prio=5 tid=0x005651b0
>>> nid=0x1e20000 runnable [f0c89000..f0c89ac0]
>>>          at java.net.SocketInputStream.socketRead0(Native Method)
>>>          at java.net.SocketInputStream.read 
>>> (SocketInputStream.java:129)
>>>          at com.jcraft.jsch.IO.getByte(Unknown Source)
>>>          at com.jcraft.jsch.Session.read(Unknown Source)
>>>          at com.jcraft.jsch.Session.run(Unknown Source)
>>>          at java.lang.Thread.run(Thread.java:552)
>>>
>>> "main" prio=5 tid=0x00500e30 nid=0x1804600 in Object.wait()
>>> [f07fe000..f08002c8]
>>>          at java.lang.Object.wait(Native Method)
>>>          - waiting on <0x650a5f08> (a com.jcraft.jsch.Channel
>>> $MyPipedInputStream)
>>>          at java.io.PipedInputStream.read(PipedInputStream.java:229)
>>>          - locked <0x650a5f08> (a com.jcraft.jsch.Channel
>>> $MyPipedInputStream)
>>>          at org.apache.maven.wagon.providers.ssh.ScpWagon.checkAck
>>> (ScpWagon.java:614)
>>>          at org.apache.maven.wagon.providers.ssh.ScpWagon.get
>>> (ScpWagon.java:407)
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Ralph Pöllath <li...@poellath.org>.
On 22.09.2005, at 11:53, Brett Porter wrote:
> Not what I wanted to see :(
>
> Can you post this to JIRA for tracking, and I'll take a look at what
> has changed since alpha-3 to try and narrow it down.

Done: http://jira.codehaus.org/browse/MNG-959

> Do other jdks or servers succeed?

I have no way of trying right now, but will comment on MNG-959 once I  
find out.

Cheers,
-Ralph.

> On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
>> "Connect thread maven.example.com session" prio=5 tid=0x005651b0
>> nid=0x1e20000 runnable [f0c89000..f0c89ac0]
>>          at java.net.SocketInputStream.socketRead0(Native Method)
>>          at java.net.SocketInputStream.read(SocketInputStream.java: 
>> 129)
>>          at com.jcraft.jsch.IO.getByte(Unknown Source)
>>          at com.jcraft.jsch.Session.read(Unknown Source)
>>          at com.jcraft.jsch.Session.run(Unknown Source)
>>          at java.lang.Thread.run(Thread.java:552)
>>
>> "main" prio=5 tid=0x00500e30 nid=0x1804600 in Object.wait()
>> [f07fe000..f08002c8]
>>          at java.lang.Object.wait(Native Method)
>>          - waiting on <0x650a5f08> (a com.jcraft.jsch.Channel
>> $MyPipedInputStream)
>>          at java.io.PipedInputStream.read(PipedInputStream.java:229)
>>          - locked <0x650a5f08> (a com.jcraft.jsch.Channel
>> $MyPipedInputStream)
>>          at org.apache.maven.wagon.providers.ssh.ScpWagon.checkAck
>> (ScpWagon.java:614)
>>          at org.apache.maven.wagon.providers.ssh.ScpWagon.get
>> (ScpWagon.java:407)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Brett Porter <br...@gmail.com>.
Not what I wanted to see :(

Can you post this to JIRA for tracking, and I'll take a look at what
has changed since alpha-3 to try and narrow it down.

Do other jdks or servers succeed?

- Brett

On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
> "Connect thread maven.example.com session" prio=5 tid=0x005651b0
> nid=0x1e20000 runnable [f0c89000..f0c89ac0]
>          at java.net.SocketInputStream.socketRead0(Native Method)
>          at java.net.SocketInputStream.read(SocketInputStream.java:129)
>          at com.jcraft.jsch.IO.getByte(Unknown Source)
>          at com.jcraft.jsch.Session.read(Unknown Source)
>          at com.jcraft.jsch.Session.run(Unknown Source)
>          at java.lang.Thread.run(Thread.java:552)
>
> "main" prio=5 tid=0x00500e30 nid=0x1804600 in Object.wait()
> [f07fe000..f08002c8]
>          at java.lang.Object.wait(Native Method)
>          - waiting on <0x650a5f08> (a com.jcraft.jsch.Channel
> $MyPipedInputStream)
>          at java.io.PipedInputStream.read(PipedInputStream.java:229)
>          - locked <0x650a5f08> (a com.jcraft.jsch.Channel
> $MyPipedInputStream)
>          at org.apache.maven.wagon.providers.ssh.ScpWagon.checkAck
> (ScpWagon.java:614)
>          at org.apache.maven.wagon.providers.ssh.ScpWagon.get
> (ScpWagon.java:407)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Ralph Pöllath <li...@poellath.org>.
On 22.09.2005, at 11:26, Brett Porter wrote:
> This looks fine, but the id you have (internal) is different to the
> log (internal-repo). Is that right?

Sorry, I changed the real names inconsistently. Should be unrelated  
to the problem.

> It's hard to tell why it might be hanging - can you take a thread dump
> at the time? (kill -3 on unix, ctrl-bkspace on windows).

Here it is:

----
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from internal
Full thread dump Java HotSpot(TM) Client VM (1.4.2-54 mixed mode):

"Connect thread maven.example.com session" prio=5 tid=0x005651b0  
nid=0x1e20000 runnable [f0c89000..f0c89ac0]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at com.jcraft.jsch.IO.getByte(Unknown Source)
         at com.jcraft.jsch.Session.read(Unknown Source)
         at com.jcraft.jsch.Session.run(Unknown Source)
         at java.lang.Thread.run(Thread.java:552)

"Signal Dispatcher" daemon prio=10 tid=0x00508210 nid=0x1823a00  
waiting on condition [0..0]

"Finalizer" daemon prio=8 tid=0x00506ca0 nid=0x1810800 in Object.wait 
() [f0a04000..f0a04ac0]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x657178d0> (a java.lang.ref.ReferenceQueue$Lock)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
         - locked <0x657178d0> (a java.lang.ref.ReferenceQueue$Lock)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
         at java.lang.ref.Finalizer$FinalizerThread.run 
(Finalizer.java:159)

"Reference Handler" daemon prio=10 tid=0x00506970 nid=0x1803e00 in  
Object.wait() [f0983000..f0983ac0]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x65717938> (a java.lang.ref.Reference$Lock)
         at java.lang.Object.wait(Object.java:429)
         at java.lang.ref.Reference$ReferenceHandler.run 
(Reference.java:115)
         - locked <0x65717938> (a java.lang.ref.Reference$Lock)

"main" prio=5 tid=0x00500e30 nid=0x1804600 in Object.wait()  
[f07fe000..f08002c8]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x650a5f08> (a com.jcraft.jsch.Channel 
$MyPipedInputStream)
         at java.io.PipedInputStream.read(PipedInputStream.java:229)
         - locked <0x650a5f08> (a com.jcraft.jsch.Channel 
$MyPipedInputStream)
         at org.apache.maven.wagon.providers.ssh.ScpWagon.checkAck 
(ScpWagon.java:614)
         at org.apache.maven.wagon.providers.ssh.ScpWagon.get 
(ScpWagon.java:407)
         at  
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile 
(DefaultWagonManager.java:325)
         at  
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadat 
a(DefaultWagonManager.java:256)
         at  
org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataM 
anager.resolveAlways(DefaultRepositoryMetadataManager.java:198)
         at  
org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataM 
anager.resolveAlways(DefaultRepositoryMetadataManager.java:183)
         at  
org.apache.maven.artifact.transform.SnapshotTransformation.resolveLatest 
SnapshotBuildNumber(SnapshotTransformation.java:130)
         at  
org.apache.maven.artifact.transform.SnapshotTransformation.transformForD 
eployment(SnapshotTransformation.java:75)
         at  
org.apache.maven.artifact.transform.DefaultArtifactTransformationManager 
.transformForDeployment(DefaultArtifactTransformationManager.java:58)
         at  
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
(DefaultArtifactDeployer.java:62)
         at  
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy 
(DefaultArtifactDeployer.java:53)
         at org.apache.maven.plugin.deploy.DeployMojo.execute 
(DeployMojo.java:142)
         at org.apache.maven.plugin.DefaultPluginManager.executeMojo 
(DefaultPluginManager.java:357)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
(DefaultLifecycleExecutor.java:479)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec 
ycle(DefaultLifecycleExecutor.java:452)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
(DefaultLifecycleExecutor.java:438)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( 
DefaultLifecycleExecutor.java:273)
         at  
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
(DefaultLifecycleExecutor.java:131)
         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
         at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.codehaus.classworlds.Launcher.launchEnhanced 
(Launcher.java:315)
         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
         at org.codehaus.classworlds.Launcher.mainWithExitCode 
(Launcher.java:430)
         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

"VM Thread" prio=5 tid=0x005061f0 nid=0x1804e00 runnable

"VM Periodic Task Thread" prio=10 tid=0x00508150 nid=0x1823600  
waiting on condition
"Exception Catcher Thread" prio=10 tid=0x00500f90 nid=0x1804a00 runnable
----

Thanks,
-Ralph.


> On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
>
>> On 22.09.2005, at 01:17, Brett Porter wrote:
>>
>>> On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
>>>
>>>
>>>> I would like to isolate the problem, but don't know where to start.
>>>>
>>>
>>> Can you share the <distributionManagement> section of your POM, and
>>> any relevant settings you have set?
>>>
>>
>> Here's distributionManagement and settings.xml:
>>
>> // in pom.xml
>> ...
>> <distributionManagement>
>>      <repository>
>>          <id>internal</id>
>>          <name>internal repository</name>
>>          <url>scp://maven.example.com/home/maven/maven2</url>
>>      </repository>
>> </distributionManagement>
>> ...
>>
>> // in ~/.m2/settings.xml
>> <settings>
>>      <servers>
>>          <server>
>>              <id>internal</id>
>>              <username>maven</username>
>>              <password>secret</password>
>>          </server>
>>      </servers>
>> </settings>
>>
>> Thanks,
>> -Ralph.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Brett Porter <br...@gmail.com>.
This looks fine, but the id you have (internal) is different to the
log (internal-repo). Is that right?

It's hard to tell why it might be hanging - can you take a thread dump
at the time? (kill -3 on unix, ctrl-bkspace on windows).

- Brett

On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
> On 22.09.2005, at 01:17, Brett Porter wrote:
> > On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
> >
> >> I would like to isolate the problem, but don't know where to start.
> >
> > Can you share the <distributionManagement> section of your POM, and
> > any relevant settings you have set?
>
> Here's distributionManagement and settings.xml:
>
> // in pom.xml
> ...
> <distributionManagement>
>      <repository>
>          <id>internal</id>
>          <name>internal repository</name>
>          <url>scp://maven.example.com/home/maven/maven2</url>
>      </repository>
> </distributionManagement>
> ...
>
> // in ~/.m2/settings.xml
> <settings>
>      <servers>
>          <server>
>              <id>internal</id>
>              <username>maven</username>
>              <password>secret</password>
>          </server>
>      </servers>
> </settings>
>
> Thanks,
> -Ralph.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Ralph Pöllath <li...@poellath.org>.
On 22.09.2005, at 01:17, Brett Porter wrote:
> On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
>
>> I would like to isolate the problem, but don't know where to start.
>
> Can you share the <distributionManagement> section of your POM, and
> any relevant settings you have set?

Here's distributionManagement and settings.xml:

// in pom.xml
...
<distributionManagement>
     <repository>
         <id>internal</id>
         <name>internal repository</name>
         <url>scp://maven.example.com/home/maven/maven2</url>
     </repository>
</distributionManagement>
...

// in ~/.m2/settings.xml
<settings>
     <servers>
         <server>
             <id>internal</id>
             <username>maven</username>
             <password>secret</password>
         </server>
     </servers>
</settings>

Thanks,
-Ralph.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Brett Porter <br...@gmail.com>.
On 9/22/05, Ralph Pöllath <li...@poellath.org> wrote:
> I would like to isolate the problem, but don't know where to start.

Can you share the <distributionManagement> section of your POM, and
any relevant settings you have set?

> Is it possible to force m2 beta-1 to use maven-deploy-plugin alpha-3?

No, they are incompatible.

Thanks,
Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Ralph Pöllath <li...@poellath.org>.
I just downgraded to m2 alpha-3 and everything works just like before.

I would like to isolate the problem, but don't know where to start.  
Is it possible to force m2 beta-1 to use maven-deploy-plugin alpha-3?

Cheers,
-Ralph.

On 21.09.2005, at 16:15, Yann Le Du wrote:
> I worked around by using <repositories> in my POM.
>
> Now :
>  * my settings.xml is empty of <mirrors> and <*repositories>
>  * my POM contains :
> ~   <project>
> ~   ...
> ~     <repositories>
> ~       <repository>
> ~         <id>central</id>
> ~         <url>http://ricfiled.as.asd.asf/maven/repository</url>
> ~         <snapshotPolicy>always</snapshotPolicy>
> ~       </repository>
> ~     </repositories>
> ~   ...
> ~   </project>
>
> I manage to access all artifacts, releases (plains) and snapshots.
>
> Ralph, I don't know if it can help you, because your problem seems  
> to be
> happening at a later phase than mine (could be a network/proxy  
> problem, but you
> said it was working in alpha-3...) but give it a shot :)
>
> Anyway, the fact that I can't access snapshots by mirroring central in
> settings.xml sounds like a regression to me. Shall I file in JIRA ?
>
> Yann
>
> --- Ralph Pöllath <li...@poellath.org> a écrit :
>
>
>> On 20.09.2005, at 14:39, Yann Le Du wrote:
>>
>>> I'm also having troubles accessing artifacts from my corp
>>> repository. More
>>> exactly, I can access plain versions (e.g. 1.0.3), but not
>>> snapshots (e.g.,
>>> 1.0.4-SNAPSHOT).
>>>
>>
>> I noticed that after changing the version from 0.1-SNAPSHOT to 0.1,
>> m2 -X deploy prints
>>
>> [INFO] [deploy:deploy]
>> Uploading: scp://maven.example.com/home/maven/maven2/blah/blah/0.1/
>> blah-0.1.jar
>>
>> and then hangs forever. I tried deleting ~/.m2/repository, but that
>> didn't make any difference at all.
>>
>> Any ideas on how to diagnose the problem? I'd really appreciate it if
>> someone could help, since this is a real show stopper for me.
>> Everything worked with m2 alpha-3, and I'd hate having to downgrade.
>>
>> Thanks,
>> -Ralph.
>>
>>
>>> --- Ralph Pöllath <li...@poellath.org> a écrit :
>>>
>>>> since I upgraded to m2 beta 1, I'm having trouble accessing  
>>>> artifacts
>>>> in my internal company-wide repository.
>>>>
>>>> m2 -X deploy prints
>>>>
>>>> ...
>>>> [INFO] [deploy:deploy]
>>>> [INFO] Retrieving previous build number from internal-repo
>>>>
>>>> and then hangs forever. I assume it's not an authentication  
>>>> problem,
>>>> because changing the password in settings.xml fails immediately  
>>>> with
>>>> an AuthenticationException.
>>>>
>>>> Any ideas?
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Yann Le Du <le...@yahoo.com>.
I worked around by using <repositories> in my POM.

Now :
 * my settings.xml is empty of <mirrors> and <*repositories>
 * my POM contains :
~   <project>
~   ...
~     <repositories>
~       <repository>
~         <id>central</id>
~         <url>http://ricfiled.as.asd.asf/maven/repository</url>
~         <snapshotPolicy>always</snapshotPolicy>
~       </repository>
~     </repositories>
~   ...
~   </project>

I manage to access all artifacts, releases (plains) and snapshots.

Ralph, I don't know if it can help you, because your problem seems to be
happening at a later phase than mine (could be a network/proxy problem, but you
said it was working in alpha-3...) but give it a shot :)

Anyway, the fact that I can't access snapshots by mirroring central in
settings.xml sounds like a regression to me. Shall I file in JIRA ?

Yann

--- Ralph Pöllath <li...@poellath.org> a écrit :

> On 20.09.2005, at 14:39, Yann Le Du wrote:
> > I'm also having troubles accessing artifacts from my corp  
> > repository. More
> > exactly, I can access plain versions (e.g. 1.0.3), but not  
> > snapshots (e.g.,
> > 1.0.4-SNAPSHOT).
> 
> I noticed that after changing the version from 0.1-SNAPSHOT to 0.1,  
> m2 -X deploy prints
> 
> [INFO] [deploy:deploy]
> Uploading: scp://maven.example.com/home/maven/maven2/blah/blah/0.1/ 
> blah-0.1.jar
> 
> and then hangs forever. I tried deleting ~/.m2/repository, but that  
> didn't make any difference at all.
> 
> Any ideas on how to diagnose the problem? I'd really appreciate it if  
> someone could help, since this is a real show stopper for me.  
> Everything worked with m2 alpha-3, and I'd hate having to downgrade.
> 
> Thanks,
> -Ralph.
> 
> > --- Ralph Pöllath <li...@poellath.org> a écrit :
> >> since I upgraded to m2 beta 1, I'm having trouble accessing artifacts
> >> in my internal company-wide repository.
> >>
> >> m2 -X deploy prints
> >>
> >> ...
> >> [INFO] [deploy:deploy]
> >> [INFO] Retrieving previous build number from internal-repo
> >>
> >> and then hangs forever. I assume it's not an authentication problem,
> >> because changing the password in settings.xml fails immediately with
> >> an AuthenticationException.
> >>
> >> Any ideas?
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: [m2] trouble accessing internal repository with beta1

Posted by Ralph Pöllath <li...@poellath.org>.
On 20.09.2005, at 14:39, Yann Le Du wrote:
> I'm also having troubles accessing artifacts from my corp  
> repository. More
> exactly, I can access plain versions (e.g. 1.0.3), but not  
> snapshots (e.g.,
> 1.0.4-SNAPSHOT).

I noticed that after changing the version from 0.1-SNAPSHOT to 0.1,  
m2 -X deploy prints

[INFO] [deploy:deploy]
Uploading: scp://maven.example.com/home/maven/maven2/blah/blah/0.1/ 
blah-0.1.jar

and then hangs forever. I tried deleting ~/.m2/repository, but that  
didn't make any difference at all.

Any ideas on how to diagnose the problem? I'd really appreciate it if  
someone could help, since this is a real show stopper for me.  
Everything worked with m2 alpha-3, and I'd hate having to downgrade.

Thanks,
-Ralph.

> --- Ralph Pöllath <li...@poellath.org> a écrit :
>> since I upgraded to m2 beta 1, I'm having trouble accessing artifacts
>> in my internal company-wide repository.
>>
>> m2 -X deploy prints
>>
>> ...
>> [INFO] [deploy:deploy]
>> [INFO] Retrieving previous build number from internal-repo
>>
>> and then hangs forever. I assume it's not an authentication problem,
>> because changing the password in settings.xml fails immediately with
>> an AuthenticationException.
>>
>> Any ideas?


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: [m2] trouble accessing internal repository with beta1

Posted by Yann Le Du <le...@yahoo.com>.
Erratum : the [3] sample is
common-framework/1.0.4-SNAPSHOT/maven-metadata-local.xml, of course.

--- Yann Le Du <le...@yahoo.com> a écrit :

> Hi,
> 
> I'm also having troubles accessing artifacts from my corp repository. More
> exactly, I can access plain versions (e.g. 1.0.3), but not snapshots (e.g.,
> 1.0.4-SNAPSHOT).
> 
> Here's my conf, which was working well before m2b1 :
> 
> [1] On my corp. repo :
> ~   common-framework
> ~   +-- maven-metadata-local.xml [2]
> ~   +-- 1.0.3
> ~       +-- common-framework-1.0.3.jar
> ~       +-- common-framework-1.0.3.pom
> ~   +-- 1.0.4-SNAPSHOT
> ~       +-- common-framework-1.0.4-SNAPSHOT.jar
> ~       +-- common-framework-1.0.4-SNAPSHOT.pom
> ~       +-- maven-metadata-local.xml [3]
> 
> [2] common-framework/maven-metadata-local.xml :
> ~   <metadata>
> ~     <groupId>fr.as.common</groupId>
> ~     <artifactId>common-framework</artifactId>
> ~     <versioning>
> ~       <versions>
> ~         <version>1.0.4-SNAPSHOT</version>
> ~         <version>1.0.3</version>
> ~       </versions>
> ~     </versioning>
> ~   </metadata>
> 
> [3] common-framework/maven-metadata-local.xml :
> ~   <metadata>
> ~     <groupId>fr.as.common</groupId>
> ~     <artifactId>common-framework</artifactId>
> ~     <version>1.0.4-SNAPSHOT</version>
> ~     <versioning>
> ~       <snapshot>
> ~         <localCopy>true</localCopy>
> ~       </snapshot>
> ~     </versioning>
> ~   </metadata>
> 
> [4] In my local settings.xml :
> ~     <mirrors>
> ~       <mirror>
> ~         <mirrorOf>central</mirrorOf>
> ~         <url>http://ricfiled.as.asd.asf/maven/repository</url>
> ~       </mirror>
> ~       <mirror>
> ~         <mirrorOf>central-plugins</mirrorOf>
> ~         <url>http://ricfiled.as.asd.asf/maven/repository</url>
> ~       </mirror>
> ~       <mirror>
> ~         <mirrorOf>central-plugins-snapshots</mirrorOf>
> ~         <url>http://ricfiled.as.asd.asf/maven/repository</url>
> ~       </mirror>
> ~     </mirrors>
> ...
> ~     <profiles>
> ~       <profile>
> ~         <repositories>
> ~           <repository>
> ~             <id>central</id>
> ~             <url>http://ricfiled.as.asd.asf/maven/repository</url>
> ~             <snapshotPolicy>always</snapshotPolicy>
> ~           </repository>
> ~         </repositories>
> ~         <pluginRepositories>
> ~           <pluginRepository>
> ~             <id>central-plugins</id>
> ~             <url>http://ricfiled.as.asd.asf/maven/repository</url>
> ~             <snapshotPolicy>always</snapshotPolicy>
> ~           </pluginRepository>
> ~           <pluginRepository>
> ~             <id>central-plugins-snapshots</id>
> ~             <url>http://ricfiled.as.asd.asf/maven/repository</url>
> ~             <snapshotPolicy>always</snapshotPolicy>
> ~           </pluginRepository>
> ~         </pluginRepositories>
> ~       </profile>
> ~     </profiles>
> 
> Yann
> 
> 
> --- Ralph Pöllath <li...@poellath.org> a écrit :
> 
> > Hi,
> > 
> > since I upgraded to m2 beta 1, I'm having trouble accessing artifacts  
> > in my internal company-wide repository.
> > 
> > m2 -X deploy prints
> > 
> > ...
> > [INFO] [deploy:deploy]
> > [INFO] Retrieving previous build number from internal-repo
> > 
> > and then hangs forever. I assume it's not an authentication problem,  
> > because changing the password in settings.xml fails immediately with  
> > an AuthenticationException.
> > 
> > Any ideas?
> > 
> > Cheers,
> > -Ralph.
> > 
> > 
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> > 
> > 
> 
> 
> Yahoo! Mail - Votre e-mail personnel et gratuit qui vous suit partout !
>  Créez votre Yahoo! Mail sur http://mail.yahoo.fr
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: [m2] trouble accessing internal repository with beta1

Posted by Yann Le Du <le...@yahoo.com>.
Hi,

I'm also having troubles accessing artifacts from my corp repository. More
exactly, I can access plain versions (e.g. 1.0.3), but not snapshots (e.g.,
1.0.4-SNAPSHOT).

Here's my conf, which was working well before m2b1 :

[1] On my corp. repo :
~   common-framework
~   +-- maven-metadata-local.xml [2]
~   +-- 1.0.3
~       +-- common-framework-1.0.3.jar
~       +-- common-framework-1.0.3.pom
~   +-- 1.0.4-SNAPSHOT
~       +-- common-framework-1.0.4-SNAPSHOT.jar
~       +-- common-framework-1.0.4-SNAPSHOT.pom
~       +-- maven-metadata-local.xml [3]

[2] common-framework/maven-metadata-local.xml :
~   <metadata>
~     <groupId>fr.as.common</groupId>
~     <artifactId>common-framework</artifactId>
~     <versioning>
~       <versions>
~         <version>1.0.4-SNAPSHOT</version>
~         <version>1.0.3</version>
~       </versions>
~     </versioning>
~   </metadata>

[3] common-framework/maven-metadata-local.xml :
~   <metadata>
~     <groupId>fr.as.common</groupId>
~     <artifactId>common-framework</artifactId>
~     <version>1.0.4-SNAPSHOT</version>
~     <versioning>
~       <snapshot>
~         <localCopy>true</localCopy>
~       </snapshot>
~     </versioning>
~   </metadata>

[4] In my local settings.xml :
~     <mirrors>
~       <mirror>
~         <mirrorOf>central</mirrorOf>
~         <url>http://ricfiled.as.asd.asf/maven/repository</url>
~       </mirror>
~       <mirror>
~         <mirrorOf>central-plugins</mirrorOf>
~         <url>http://ricfiled.as.asd.asf/maven/repository</url>
~       </mirror>
~       <mirror>
~         <mirrorOf>central-plugins-snapshots</mirrorOf>
~         <url>http://ricfiled.as.asd.asf/maven/repository</url>
~       </mirror>
~     </mirrors>
...
~     <profiles>
~       <profile>
~         <repositories>
~           <repository>
~             <id>central</id>
~             <url>http://ricfiled.as.asd.asf/maven/repository</url>
~             <snapshotPolicy>always</snapshotPolicy>
~           </repository>
~         </repositories>
~         <pluginRepositories>
~           <pluginRepository>
~             <id>central-plugins</id>
~             <url>http://ricfiled.as.asd.asf/maven/repository</url>
~             <snapshotPolicy>always</snapshotPolicy>
~           </pluginRepository>
~           <pluginRepository>
~             <id>central-plugins-snapshots</id>
~             <url>http://ricfiled.as.asd.asf/maven/repository</url>
~             <snapshotPolicy>always</snapshotPolicy>
~           </pluginRepository>
~         </pluginRepositories>
~       </profile>
~     </profiles>

Yann


--- Ralph Pöllath <li...@poellath.org> a écrit :

> Hi,
> 
> since I upgraded to m2 beta 1, I'm having trouble accessing artifacts  
> in my internal company-wide repository.
> 
> m2 -X deploy prints
> 
> ...
> [INFO] [deploy:deploy]
> [INFO] Retrieving previous build number from internal-repo
> 
> and then hangs forever. I assume it's not an authentication problem,  
> because changing the password in settings.xml fails immediately with  
> an AuthenticationException.
> 
> Any ideas?
> 
> Cheers,
> -Ralph.
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 


Yahoo! Mail - Votre e-mail personnel et gratuit qui vous suit partout !
 Créez votre Yahoo! Mail sur http://mail.yahoo.fr

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org