Unable to deploy plugin to repo

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

Unable to deploy plugin to repo

Christopher Orr
Hi all,

I'm trying to release a plugin at the moment, but not having much luck.

I discovered the prior thread about updating my pom.xml to include the
maven-release-plugin and new SCM URL stuff, so everything there should
be correct.

But running "mvn release:prepare release:perform" as usual results in
the following failure:


[INFO] [INFO] [deploy:deploy {execution: default-deploy}]

[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] Error deploying artifact: Connection failed: Unable to
connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
[INFO]
[INFO] svn: authentication cancelled
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] For more information, run Maven with the -e switch


I can access that URL from my browser, using my normal java.net credentials.

I tried adding the -Dusername=foo and -Dpassword=bar parameters to the
command line (as mentioned on the wiki), but that fails very early on:


[INFO] [release:perform {execution: default-cli}]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd
/Users/chris/code/android-emulator/target && svn --username orrc
--password '*****' --non-interactive checkout
https://svn.java.net/svn/hudson~svn/tags/android-emulator-1.5 
/Users/chris/code/android-emulator/target/checkout
[INFO] Working directory: /Users/chris/code/android-emulator/target
[ERROR] The svn command failed.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to checkout from SCM
Provider message:
The svn command failed.
Command output:
Unknown command: 'orrc'
Type 'svn help' for usage.


Any ideas what I could be missing?

Thanks,
Chris
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Monty Taylor
+1 (me too)

On 12/17/2010 01:45 PM, Christopher Orr wrote:

> Hi all,
>
> I'm trying to release a plugin at the moment, but not having much luck.
>
> I discovered the prior thread about updating my pom.xml to include the
> maven-release-plugin and new SCM URL stuff, so everything there should
> be correct.
>
> But running "mvn release:prepare release:perform" as usual results in
> the following failure:
>
>
> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [ERROR] BUILD ERROR
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [INFO] Error deploying artifact: Connection failed: Unable to
> connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
> [INFO]
> [INFO] svn: authentication cancelled
> [INFO] [INFO]
> ------------------------------------------------------------------------
> [INFO] [INFO] For more information, run Maven with the -e switch
>
>
> I can access that URL from my browser, using my normal java.net
> credentials.
>
> I tried adding the -Dusername=foo and -Dpassword=bar parameters to the
> command line (as mentioned on the wiki), but that fails very early on:
>
>
> [INFO] [release:perform {execution: default-cli}]
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: /bin/sh -c cd
> /Users/chris/code/android-emulator/target && svn --username orrc
> --password '*****' --non-interactive checkout
> https://svn.java.net/svn/hudson~svn/tags/android-emulator-1.5
> /Users/chris/code/android-emulator/target/checkout
> [INFO] Working directory: /Users/chris/code/android-emulator/target
> [ERROR] The svn command failed.
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to checkout from SCM
> Provider message:
> The svn command failed.
> Command output:
> Unknown command: 'orrc'
> Type 'svn help' for usage.
>
>
> Any ideas what I could be missing?
>
> Thanks,
> Chris
>

Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

kinow
Hi there,

I did a few tests using URL https://svn.dev.java.net/svn/maven2-repository/trunk/repository/ and realized it is using java.net password and not java.net/people password.

When I access my plug-in's SVN to commit I have to use my java.net/people password.

Do you guys are using the same password in java.net and in java.net/people? Could you check it, please? Just log into http://java.net and into http://java.net/people.

Best Regards,
Bruno

--- Em sex, 17/12/10, Monty Taylor <[hidden email]> escreveu:

> De: Monty Taylor <[hidden email]>
> Assunto: Re: Unable to deploy plugin to repo
> Para: [hidden email]
> Data: Sexta-feira, 17 de Dezembro de 2010, 19:49
> +1 (me too)
>
> On 12/17/2010 01:45 PM, Christopher Orr wrote:
> > Hi all,
> >
> > I'm trying to release a plugin at the moment, but not
> having much luck.
> >
> > I discovered the prior thread about updating my
> pom.xml to include the
> > maven-release-plugin and new SCM URL stuff, so
> everything there should
> > be correct.
> >
> > But running "mvn release:prepare release:perform" as
> usual results in
> > the following failure:
> >
> >
> > [INFO] [INFO] [deploy:deploy {execution:
> default-deploy}]
> >
> > [INFO] [INFO]
> >
> ------------------------------------------------------------------------
> > [INFO] [ERROR] BUILD ERROR
> > [INFO] [INFO]
> >
> ------------------------------------------------------------------------
> > [INFO] [INFO] Error deploying artifact: Connection
> failed: Unable to
> > connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
> > [INFO]
> > [INFO] svn: authentication cancelled
> > [INFO] [INFO]
> >
> ------------------------------------------------------------------------
> > [INFO] [INFO] For more information, run Maven with the
> -e switch
> >
> >
> > I can access that URL from my browser, using my normal
> java.net
> > credentials.
> >
> > I tried adding the -Dusername=foo and -Dpassword=bar
> parameters to the
> > command line (as mentioned on the wiki), but that
> fails very early on:
> >
> >
> > [INFO] [release:perform {execution: default-cli}]
> > [INFO] Checking out the project to perform the release
> ...
> > [INFO] Executing: /bin/sh -c cd
> > /Users/chris/code/android-emulator/target &&
> svn --username orrc
> > --password '*****' --non-interactive checkout
> > https://svn.java.net/svn/hudson~svn/tags/android-emulator-1.5
> > /Users/chris/code/android-emulator/target/checkout
> > [INFO] Working directory:
> /Users/chris/code/android-emulator/target
> > [ERROR] The svn command failed.
> > [INFO]
> >
> ------------------------------------------------------------------------
> > [ERROR] BUILD FAILURE
> > [INFO]
> >
> ------------------------------------------------------------------------
> > [INFO] Unable to checkout from SCM
> > Provider message:
> > The svn command failed.
> > Command output:
> > Unknown command: 'orrc'
> > Type 'svn help' for usage.
> >
> >
> > Any ideas what I could be missing?
> >
> > Thanks,
> > Chris
> >
>
>



Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Andrew Bayer
The maven2-repository project at java.net is locked currently, according to what I've been told by the java.net guys, as part of its planned migration to the new infrastructure. So yeah, looks like we're not able to push releases at the moment.

A.

On Fri, Dec 17, 2010 at 2:01 PM, Bruno P. Kinoshita <[hidden email]> wrote:
Hi there,

I did a few tests using URL https://svn.dev.java.net/svn/maven2-repository/trunk/repository/ and realized it is using java.net password and not java.net/people password.

When I access my plug-in's SVN to commit I have to use my java.net/people password.

Do you guys are using the same password in java.net and in java.net/people? Could you check it, please? Just log into http://java.net and into http://java.net/people.

Best Regards,
Bruno

--- Em sex, 17/12/10, Monty Taylor <[hidden email]> escreveu:

> De: Monty Taylor <[hidden email]>
> Assunto: Re: Unable to deploy plugin to repo
> Para: [hidden email]
> Data: Sexta-feira, 17 de Dezembro de 2010, 19:49
> +1 (me too)
>
> On 12/17/2010 01:45 PM, Christopher Orr wrote:
> > Hi all,
> >
> > I'm trying to release a plugin at the moment, but not
> having much luck.
> >
> > I discovered the prior thread about updating my
> pom.xml to include the
> > maven-release-plugin and new SCM URL stuff, so
> everything there should
> > be correct.
> >
> > But running "mvn release:prepare release:perform" as
> usual results in
> > the following failure:
> >
> >
> > [INFO] [INFO] [deploy:deploy {execution:
> default-deploy}]
> >
> > [INFO] [INFO]
> >
> ------------------------------------------------------------------------
> > [INFO] [ERROR] BUILD ERROR
> > [INFO] [INFO]
> >
> ------------------------------------------------------------------------
> > [INFO] [INFO] Error deploying artifact: Connection
> failed: Unable to
> > connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
> > [INFO]
> > [INFO] svn: authentication cancelled
> > [INFO] [INFO]
> >
> ------------------------------------------------------------------------
> > [INFO] [INFO] For more information, run Maven with the
> -e switch
> >
> >
> > I can access that URL from my browser, using my normal
> java.net
> > credentials.
> >
> > I tried adding the -Dusername=foo and -Dpassword=bar
> parameters to the
> > command line (as mentioned on the wiki), but that
> fails very early on:
> >
> >
> > [INFO] [release:perform {execution: default-cli}]
> > [INFO] Checking out the project to perform the release
> ...
> > [INFO] Executing: /bin/sh -c cd
> > /Users/chris/code/android-emulator/target &&
> svn --username orrc
> > --password '*****' --non-interactive checkout
> > https://svn.java.net/svn/hudson~svn/tags/android-emulator-1.5
> > /Users/chris/code/android-emulator/target/checkout
> > [INFO] Working directory:
> /Users/chris/code/android-emulator/target
> > [ERROR] The svn command failed.
> > [INFO]
> >
> ------------------------------------------------------------------------
> > [ERROR] BUILD FAILURE
> > [INFO]
> >
> ------------------------------------------------------------------------
> > [INFO] Unable to checkout from SCM
> > Provider message:
> > The svn command failed.
> > Command output:
> > Unknown command: 'orrc'
> > Type 'svn help' for usage.
> >
> >
> > Any ideas what I could be missing?
> >
> > Thanks,
> > Chris
> >
>
>




Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Kohsuke Kawaguchi
Administrator
In reply to this post by Monty Taylor
Sigh. It's another java.net migration problem. I got a notification
for the batch of projects transitioning from Dec 15th but
maven2-repository was NOT one of them. But apparently it is getting
migrated anyhow [1], and there's no ETA. I should have specifically
asked them to push this to the very end.

You can wait for the repository to come back, or for the time being
you can deploy to
http://maven.hudson-labs.org/content/repositories/releases/ by adding
the following to your POM:

    <distributionManagement>
      <repository>
        <id>java.net-m2-repository</id>
        <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
      </repository>
    </distributionManagement>

I intend to use this for releasing Hudson this week (and next week if
the repository isn't back by then.) I'll merge them (and all the
plugins released in the mean time) back to the java.net m2 repository
when it's back.

This repository is authenticated against new beta java.net. So your
~/.m2/settings.xml needs to have that or the deployment would fail.


[1] https://maven2-repository.dev.java.net/

2010/12/17 Monty Taylor <[hidden email]>:

> +1 (me too)
>
> On 12/17/2010 01:45 PM, Christopher Orr wrote:
>> Hi all,
>>
>> I'm trying to release a plugin at the moment, but not having much luck.
>>
>> I discovered the prior thread about updating my pom.xml to include the
>> maven-release-plugin and new SCM URL stuff, so everything there should
>> be correct.
>>
>> But running "mvn release:prepare release:perform" as usual results in
>> the following failure:
>>
>>
>> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>>
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [ERROR] BUILD ERROR
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [INFO] Error deploying artifact: Connection failed: Unable to
>> connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
>> [INFO]
>> [INFO] svn: authentication cancelled
>> [INFO] [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [INFO] For more information, run Maven with the -e switch
>>
>>
>> I can access that URL from my browser, using my normal java.net
>> credentials.
>>
>> I tried adding the -Dusername=foo and -Dpassword=bar parameters to the
>> command line (as mentioned on the wiki), but that fails very early on:
>>
>>
>> [INFO] [release:perform {execution: default-cli}]
>> [INFO] Checking out the project to perform the release ...
>> [INFO] Executing: /bin/sh -c cd
>> /Users/chris/code/android-emulator/target && svn --username orrc
>> --password '*****' --non-interactive checkout
>> https://svn.java.net/svn/hudson~svn/tags/android-emulator-1.5
>> /Users/chris/code/android-emulator/target/checkout
>> [INFO] Working directory: /Users/chris/code/android-emulator/target
>> [ERROR] The svn command failed.
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Unable to checkout from SCM
>> Provider message:
>> The svn command failed.
>> Command output:
>> Unknown command: 'orrc'
>> Type 'svn help' for usage.
>>
>>
>> Any ideas what I could be missing?
>>
>> Thanks,
>> Chris
>>
>
>



--
Kohsuke Kawaguchi
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Christopher Orr
Ah, that would explain it.  Thanks for the info.

Since there's no ETA on the migration, I attempted the workaround by
adding the distributionManagement tag to my POM, but for some reason I
still get the same error as below, with the same old m2 repo URL.

I checked my plugin's POM and the workaround looks ok (it's just
copy/pasted from below), and there are no references there or in ~/.m2
to the old repo.

Any ideas?

Thanks,
Chris


On 17/12/2010 23:08, Kohsuke Kawaguchi wrote:

> Sigh. It's another java.net migration problem. I got a notification
> for the batch of projects transitioning from Dec 15th but
> maven2-repository was NOT one of them. But apparently it is getting
> migrated anyhow [1], and there's no ETA. I should have specifically
> asked them to push this to the very end.
>
> You can wait for the repository to come back, or for the time being
> you can deploy to
> http://maven.hudson-labs.org/content/repositories/releases/ by adding
> the following to your POM:
>
>      <distributionManagement>
>        <repository>
>          <id>java.net-m2-repository</id>
>          <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
>        </repository>
>      </distributionManagement>
>
> I intend to use this for releasing Hudson this week (and next week if
> the repository isn't back by then.) I'll merge them (and all the
> plugins released in the mean time) back to the java.net m2 repository
> when it's back.
>
> This repository is authenticated against new beta java.net. So your
> ~/.m2/settings.xml needs to have that or the deployment would fail.
>
>
> [1] https://maven2-repository.dev.java.net/
>
> 2010/12/17 Monty Taylor<[hidden email]>:
>> +1 (me too)
>>
>> On 12/17/2010 01:45 PM, Christopher Orr wrote:
>>> Hi all,
>>>
>>> I'm trying to release a plugin at the moment, but not having much luck.
>>>
>>> I discovered the prior thread about updating my pom.xml to include the
>>> maven-release-plugin and new SCM URL stuff, so everything there should
>>> be correct.
>>>
>>> But running "mvn release:prepare release:perform" as usual results in
>>> the following failure:
>>>
>>>
>>> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>>>
>>> [INFO] [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [ERROR] BUILD ERROR
>>> [INFO] [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [INFO] Error deploying artifact: Connection failed: Unable to
>>> connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
>>> [INFO]
>>> [INFO] svn: authentication cancelled
>>> [INFO] [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [INFO] For more information, run Maven with the -e switch
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Kohsuke Kawaguchi
Administrator
I suspect you need to rollback a release and retry.  When you run "mvn
release:prepare" it creates a tag, and "mvn release:perform" just
builds that tag, which presumably doesn't contain your
<distributionManagement> change.

I'd be also happy to run a release for you if you want.

2010/12/17 Christopher Orr <[hidden email]>:

> Ah, that would explain it.  Thanks for the info.
>
> Since there's no ETA on the migration, I attempted the workaround by adding
> the distributionManagement tag to my POM, but for some reason I still get
> the same error as below, with the same old m2 repo URL.
>
> I checked my plugin's POM and the workaround looks ok (it's just copy/pasted
> from below), and there are no references there or in ~/.m2 to the old repo.
>
> Any ideas?
>
> Thanks,
> Chris
>
>
> On 17/12/2010 23:08, Kohsuke Kawaguchi wrote:
>>
>> Sigh. It's another java.net migration problem. I got a notification
>> for the batch of projects transitioning from Dec 15th but
>> maven2-repository was NOT one of them. But apparently it is getting
>> migrated anyhow [1], and there's no ETA. I should have specifically
>> asked them to push this to the very end.
>>
>> You can wait for the repository to come back, or for the time being
>> you can deploy to
>> http://maven.hudson-labs.org/content/repositories/releases/ by adding
>> the following to your POM:
>>
>>     <distributionManagement>
>>       <repository>
>>         <id>java.net-m2-repository</id>
>>
>> <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
>>       </repository>
>>     </distributionManagement>
>>
>> I intend to use this for releasing Hudson this week (and next week if
>> the repository isn't back by then.) I'll merge them (and all the
>> plugins released in the mean time) back to the java.net m2 repository
>> when it's back.
>>
>> This repository is authenticated against new beta java.net. So your
>> ~/.m2/settings.xml needs to have that or the deployment would fail.
>>
>>
>> [1] https://maven2-repository.dev.java.net/
>>
>> 2010/12/17 Monty Taylor<[hidden email]>:
>>>
>>> +1 (me too)
>>>
>>> On 12/17/2010 01:45 PM, Christopher Orr wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I'm trying to release a plugin at the moment, but not having much luck.
>>>>
>>>> I discovered the prior thread about updating my pom.xml to include the
>>>> maven-release-plugin and new SCM URL stuff, so everything there should
>>>> be correct.
>>>>
>>>> But running "mvn release:prepare release:perform" as usual results in
>>>> the following failure:
>>>>
>>>>
>>>> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>>>>
>>>> [INFO] [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] [ERROR] BUILD ERROR
>>>> [INFO] [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] [INFO] Error deploying artifact: Connection failed: Unable to
>>>> connect to
>>>> https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
>>>> [INFO]
>>>> [INFO] svn: authentication cancelled
>>>> [INFO] [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] [INFO] For more information, run Maven with the -e switch
>



--
Kohsuke Kawaguchi
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Christopher Orr
I mentioned this on IRC, but just for completeness I'll mention it here
too: this approach worked, and the plugin should now be released on the
hudson-labs m2 repo.

Thanks!
Chris


On 17/12/2010 23:50, Kohsuke Kawaguchi wrote:

> I suspect you need to rollback a release and retry.  When you run "mvn
> release:prepare" it creates a tag, and "mvn release:perform" just
> builds that tag, which presumably doesn't contain your
> <distributionManagement>  change.
>
> I'd be also happy to run a release for you if you want.
>
> 2010/12/17 Christopher Orr<[hidden email]>:
>> Ah, that would explain it.  Thanks for the info.
>>
>> Since there's no ETA on the migration, I attempted the workaround by adding
>> the distributionManagement tag to my POM, but for some reason I still get
>> the same error as below, with the same old m2 repo URL.
>>
>> I checked my plugin's POM and the workaround looks ok (it's just copy/pasted
>> from below), and there are no references there or in ~/.m2 to the old repo.
>>
>> Any ideas?
>>
>> Thanks,
>> Chris
>>
>>
>> On 17/12/2010 23:08, Kohsuke Kawaguchi wrote:
>>>
>>> Sigh. It's another java.net migration problem. I got a notification
>>> for the batch of projects transitioning from Dec 15th but
>>> maven2-repository was NOT one of them. But apparently it is getting
>>> migrated anyhow [1], and there's no ETA. I should have specifically
>>> asked them to push this to the very end.
>>>
>>> You can wait for the repository to come back, or for the time being
>>> you can deploy to
>>> http://maven.hudson-labs.org/content/repositories/releases/ by adding
>>> the following to your POM:
>>>
>>>      <distributionManagement>
>>>        <repository>
>>>          <id>java.net-m2-repository</id>
>>>
>>> <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
>>>        </repository>
>>>      </distributionManagement>
>>>
>>> I intend to use this for releasing Hudson this week (and next week if
>>> the repository isn't back by then.) I'll merge them (and all the
>>> plugins released in the mean time) back to the java.net m2 repository
>>> when it's back.
>>>
>>> This repository is authenticated against new beta java.net. So your
>>> ~/.m2/settings.xml needs to have that or the deployment would fail.
>>>
>>>
>>> [1] https://maven2-repository.dev.java.net/
>>>
>>> 2010/12/17 Monty Taylor<[hidden email]>:
>>>>
>>>> +1 (me too)
>>>>
>>>> On 12/17/2010 01:45 PM, Christopher Orr wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I'm trying to release a plugin at the moment, but not having much luck.
>>>>>
>>>>> I discovered the prior thread about updating my pom.xml to include the
>>>>> maven-release-plugin and new SCM URL stuff, so everything there should
>>>>> be correct.
>>>>>
>>>>> But running "mvn release:prepare release:perform" as usual results in
>>>>> the following failure:
>>>>>
>>>>>
>>>>> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>>>>>
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] [ERROR] BUILD ERROR
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] [INFO] Error deploying artifact: Connection failed: Unable to
>>>>> connect to
>>>>> https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
>>>>> [INFO]
>>>>> [INFO] svn: authentication cancelled
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] [INFO] For more information, run Maven with the -e switch
>>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Monty Taylor
In reply to this post by Kohsuke Kawaguchi
On 12/17/2010 02:50 PM, Kohsuke Kawaguchi wrote:
> I suspect you need to rollback a release and retry.  When you run "mvn
> release:prepare" it creates a tag, and "mvn release:perform" just
> builds that tag, which presumably doesn't contain your
> <distributionManagement> change.

As a git n00b - lemme as here:

If I'm in the above situation, did mvn release:prepare release:perform
and then hit the locked m2 repo... so now I have a half-staged tree. I'd
love to roll back to before I did that and just start fresh (I haven't
pushed back to github yet) but I have no idea how to do that in git...

Any thoughts?

Thanks!
Monty

> I'd be also happy to run a release for you if you want.
>
> 2010/12/17 Christopher Orr <[hidden email]>:
>> Ah, that would explain it.  Thanks for the info.
>>
>> Since there's no ETA on the migration, I attempted the workaround by adding
>> the distributionManagement tag to my POM, but for some reason I still get
>> the same error as below, with the same old m2 repo URL.
>>
>> I checked my plugin's POM and the workaround looks ok (it's just copy/pasted
>> from below), and there are no references there or in ~/.m2 to the old repo.
>>
>> Any ideas?
>>
>> Thanks,
>> Chris
>>
>>
>> On 17/12/2010 23:08, Kohsuke Kawaguchi wrote:
>>>
>>> Sigh. It's another java.net migration problem. I got a notification
>>> for the batch of projects transitioning from Dec 15th but
>>> maven2-repository was NOT one of them. But apparently it is getting
>>> migrated anyhow [1], and there's no ETA. I should have specifically
>>> asked them to push this to the very end.
>>>
>>> You can wait for the repository to come back, or for the time being
>>> you can deploy to
>>> http://maven.hudson-labs.org/content/repositories/releases/ by adding
>>> the following to your POM:
>>>
>>>     <distributionManagement>
>>>       <repository>
>>>         <id>java.net-m2-repository</id>
>>>
>>> <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
>>>       </repository>
>>>     </distributionManagement>
>>>
>>> I intend to use this for releasing Hudson this week (and next week if
>>> the repository isn't back by then.) I'll merge them (and all the
>>> plugins released in the mean time) back to the java.net m2 repository
>>> when it's back.
>>>
>>> This repository is authenticated against new beta java.net. So your
>>> ~/.m2/settings.xml needs to have that or the deployment would fail.
>>>
>>>
>>> [1] https://maven2-repository.dev.java.net/
>>>
>>> 2010/12/17 Monty Taylor<[hidden email]>:
>>>>
>>>> +1 (me too)
>>>>
>>>> On 12/17/2010 01:45 PM, Christopher Orr wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I'm trying to release a plugin at the moment, but not having much luck..
>>>>>
>>>>> I discovered the prior thread about updating my pom.xml to include the
>>>>> maven-release-plugin and new SCM URL stuff, so everything there should
>>>>> be correct.
>>>>>
>>>>> But running "mvn release:prepare release:perform" as usual results in
>>>>> the following failure:
>>>>>
>>>>>
>>>>> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>>>>>
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] [ERROR] BUILD ERROR
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] [INFO] Error deploying artifact: Connection failed: Unable to
>>>>> connect to
>>>>> https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
>>>>> [INFO]
>>>>> [INFO] svn: authentication cancelled
>>>>> [INFO] [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] [INFO] For more information, run Maven with the -e switch
>>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Kohsuke Kawaguchi
Administrator
You'd first reset the master to the commit before "maven release" kicked in.

$ git reset --hard SHA1

You also need to delete the tag Maven created:

$ git tag -d bazzar-1.7

While you haven't pushed anything, Maven does it automatically. So
assuming it's the bazzar plugin 1.7 that you were trying to release,
it's already pushed to the repository. So you have to reset the master
branch in the repo as well as delete the tag:

$ git push -f origin master
$ git push origin :bazzar-1.7

Make sure you don't have "release.properties" nor
"pom.xml.releaseBackup" or anything like that, then you can tweak POM,
and rerun a release.


Or if all of this sounds too complicated, which it is, the easiest way
out is just forget 1.7 and release 1.8.


2010/12/17 Monty Taylor <[hidden email]>:

> On 12/17/2010 02:50 PM, Kohsuke Kawaguchi wrote:
>> I suspect you need to rollback a release and retry.  When you run "mvn
>> release:prepare" it creates a tag, and "mvn release:perform" just
>> builds that tag, which presumably doesn't contain your
>> <distributionManagement> change.
>
> As a git n00b - lemme as here:
>
> If I'm in the above situation, did mvn release:prepare release:perform
> and then hit the locked m2 repo... so now I have a half-staged tree. I'd
> love to roll back to before I did that and just start fresh (I haven't
> pushed back to github yet) but I have no idea how to do that in git...
>
> Any thoughts?
>
> Thanks!
> Monty
>
>> I'd be also happy to run a release for you if you want.
>>
>> 2010/12/17 Christopher Orr <[hidden email]>:
>>> Ah, that would explain it.  Thanks for the info.
>>>
>>> Since there's no ETA on the migration, I attempted the workaround by adding
>>> the distributionManagement tag to my POM, but for some reason I still get
>>> the same error as below, with the same old m2 repo URL.
>>>
>>> I checked my plugin's POM and the workaround looks ok (it's just copy/pasted
>>> from below), and there are no references there or in ~/.m2 to the old repo.
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> Chris
>>>
>>>
>>> On 17/12/2010 23:08, Kohsuke Kawaguchi wrote:
>>>>
>>>> Sigh. It's another java.net migration problem. I got a notification
>>>> for the batch of projects transitioning from Dec 15th but
>>>> maven2-repository was NOT one of them. But apparently it is getting
>>>> migrated anyhow [1], and there's no ETA. I should have specifically
>>>> asked them to push this to the very end.
>>>>
>>>> You can wait for the repository to come back, or for the time being
>>>> you can deploy to
>>>> http://maven.hudson-labs.org/content/repositories/releases/ by adding
>>>> the following to your POM:
>>>>
>>>>     <distributionManagement>
>>>>       <repository>
>>>>         <id>java.net-m2-repository</id>
>>>>
>>>> <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
>>>>       </repository>
>>>>     </distributionManagement>
>>>>
>>>> I intend to use this for releasing Hudson this week (and next week if
>>>> the repository isn't back by then.) I'll merge them (and all the
>>>> plugins released in the mean time) back to the java.net m2 repository
>>>> when it's back.
>>>>
>>>> This repository is authenticated against new beta java.net. So your
>>>> ~/.m2/settings.xml needs to have that or the deployment would fail.
>>>>
>>>>
>>>> [1] https://maven2-repository.dev.java.net/
>>>>
>>>> 2010/12/17 Monty Taylor<[hidden email]>:
>>>>>
>>>>> +1 (me too)
>>>>>
>>>>> On 12/17/2010 01:45 PM, Christopher Orr wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I'm trying to release a plugin at the moment, but not having much luck..
>>>>>>
>>>>>> I discovered the prior thread about updating my pom.xml to include the
>>>>>> maven-release-plugin and new SCM URL stuff, so everything there should
>>>>>> be correct.
>>>>>>
>>>>>> But running "mvn release:prepare release:perform" as usual results in
>>>>>> the following failure:
>>>>>>
>>>>>>
>>>>>> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>>>>>>
>>>>>> [INFO] [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] [ERROR] BUILD ERROR
>>>>>> [INFO] [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] [INFO] Error deploying artifact: Connection failed: Unable to
>>>>>> connect to
>>>>>> https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
>>>>>> [INFO]
>>>>>> [INFO] svn: authentication cancelled
>>>>>> [INFO] [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] [INFO] For more information, run Maven with the -e switch
>>>
>>
>>
>>
>
>



--
Kohsuke Kawaguchi
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Erik Ramfelt
Darn, I wished I had read this mail thread before trying to do a
release.... Is there any message board stating when the migration will
be done, or at least a status of it so I can commit my new version?

regards
//Erik

On Sat, Dec 18, 2010 at 00:26, Kohsuke Kawaguchi <[hidden email]> wrote:

> You'd first reset the master to the commit before "maven release" kicked in.
>
> $ git reset --hard SHA1
>
> You also need to delete the tag Maven created:
>
> $ git tag -d bazzar-1.7
>
> While you haven't pushed anything, Maven does it automatically. So
> assuming it's the bazzar plugin 1.7 that you were trying to release,
> it's already pushed to the repository. So you have to reset the master
> branch in the repo as well as delete the tag:
>
> $ git push -f origin master
> $ git push origin :bazzar-1.7
>
> Make sure you don't have "release.properties" nor
> "pom.xml.releaseBackup" or anything like that, then you can tweak POM,
> and rerun a release.
>
>
> Or if all of this sounds too complicated, which it is, the easiest way
> out is just forget 1.7 and release 1.8.
>
>
> 2010/12/17 Monty Taylor <[hidden email]>:
>> On 12/17/2010 02:50 PM, Kohsuke Kawaguchi wrote:
>>> I suspect you need to rollback a release and retry.  When you run "mvn
>>> release:prepare" it creates a tag, and "mvn release:perform" just
>>> builds that tag, which presumably doesn't contain your
>>> <distributionManagement> change.
>>
>> As a git n00b - lemme as here:
>>
>> If I'm in the above situation, did mvn release:prepare release:perform
>> and then hit the locked m2 repo... so now I have a half-staged tree. I'd
>> love to roll back to before I did that and just start fresh (I haven't
>> pushed back to github yet) but I have no idea how to do that in git...
>>
>> Any thoughts?
>>
>> Thanks!
>> Monty
>>
>>> I'd be also happy to run a release for you if you want.
>>>
>>> 2010/12/17 Christopher Orr <[hidden email]>:
>>>> Ah, that would explain it.  Thanks for the info.
>>>>
>>>> Since there's no ETA on the migration, I attempted the workaround by adding
>>>> the distributionManagement tag to my POM, but for some reason I still get
>>>> the same error as below, with the same old m2 repo URL.
>>>>
>>>> I checked my plugin's POM and the workaround looks ok (it's just copy/pasted
>>>> from below), and there are no references there or in ~/.m2 to the old repo.
>>>>
>>>> Any ideas?
>>>>
>>>> Thanks,
>>>> Chris
>>>>
>>>>
>>>> On 17/12/2010 23:08, Kohsuke Kawaguchi wrote:
>>>>>
>>>>> Sigh. It's another java.net migration problem. I got a notification
>>>>> for the batch of projects transitioning from Dec 15th but
>>>>> maven2-repository was NOT one of them. But apparently it is getting
>>>>> migrated anyhow [1], and there's no ETA. I should have specifically
>>>>> asked them to push this to the very end.
>>>>>
>>>>> You can wait for the repository to come back, or for the time being
>>>>> you can deploy to
>>>>> http://maven.hudson-labs.org/content/repositories/releases/ by adding
>>>>> the following to your POM:
>>>>>
>>>>>     <distributionManagement>
>>>>>       <repository>
>>>>>         <id>java.net-m2-repository</id>
>>>>>
>>>>> <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
>>>>>       </repository>
>>>>>     </distributionManagement>
>>>>>
>>>>> I intend to use this for releasing Hudson this week (and next week if
>>>>> the repository isn't back by then.) I'll merge them (and all the
>>>>> plugins released in the mean time) back to the java.net m2 repository
>>>>> when it's back.
>>>>>
>>>>> This repository is authenticated against new beta java.net. So your
>>>>> ~/.m2/settings.xml needs to have that or the deployment would fail.
>>>>>
>>>>>
>>>>> [1] https://maven2-repository.dev.java.net/
>>>>>
>>>>> 2010/12/17 Monty Taylor<[hidden email]>:
>>>>>>
>>>>>> +1 (me too)
>>>>>>
>>>>>> On 12/17/2010 01:45 PM, Christopher Orr wrote:
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I'm trying to release a plugin at the moment, but not having much luck..
>>>>>>>
>>>>>>> I discovered the prior thread about updating my pom.xml to include the
>>>>>>> maven-release-plugin and new SCM URL stuff, so everything there should
>>>>>>> be correct.
>>>>>>>
>>>>>>> But running "mvn release:prepare release:perform" as usual results in
>>>>>>> the following failure:
>>>>>>>
>>>>>>>
>>>>>>> [INFO] [INFO] [deploy:deploy {execution: default-deploy}]
>>>>>>>
>>>>>>> [INFO] [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] [ERROR] BUILD ERROR
>>>>>>> [INFO] [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] [INFO] Error deploying artifact: Connection failed: Unable to
>>>>>>> connect to
>>>>>>> https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
>>>>>>> [INFO]
>>>>>>> [INFO] svn: authentication cancelled
>>>>>>> [INFO] [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] [INFO] For more information, run Maven with the -e switch
>>>>
>>>
>>>
>>>
>>
>>
>
>
>
> --
> Kohsuke Kawaguchi
>
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Christopher Orr
Using the simple workaround Kohsuke described at the end of this thread
worked for me yesterday.

As for the original maven repository becoming available again, it seems
there is currently no status available: the original site is now down,
but it doesn't yet seem to been migrated to the new java.net site.

Inserting this information (as well as the new POM SCM entries required
due to the SVN repo change) into the wiki would probably be useful.
I would, but the wiki doesn't ever seem to like remembering my sessions,
remembering passwords I set, or sending me email!

Regards,
Chris


On 18/12/2010 13:57, Erik Ramfelt wrote:

> Darn, I wished I had read this mail thread before trying to do a
> release.... Is there any message board stating when the migration will
> be done, or at least a status of it so I can commit my new version?
>
> regards
> //Erik
>
> On Sat, Dec 18, 2010 at 00:26, Kohsuke Kawaguchi<[hidden email]>  wrote:
>> You'd first reset the master to the commit before "maven release" kicked in.
>>
>> $ git reset --hard SHA1
>>
>> You also need to delete the tag Maven created:
>>
>> $ git tag -d bazzar-1.7
>>
>> While you haven't pushed anything, Maven does it automatically. So
>> assuming it's the bazzar plugin 1.7 that you were trying to release,
>> it's already pushed to the repository. So you have to reset the master
>> branch in the repo as well as delete the tag:
>>
>> $ git push -f origin master
>> $ git push origin :bazzar-1.7
>>
>> Make sure you don't have "release.properties" nor
>> "pom.xml.releaseBackup" or anything like that, then you can tweak POM,
>> and rerun a release.
>>
>>
>> Or if all of this sounds too complicated, which it is, the easiest way
>> out is just forget 1.7 and release 1.8.
>>
>>
>> 2010/12/17 Monty Taylor<[hidden email]>:
>>> On 12/17/2010 02:50 PM, Kohsuke Kawaguchi wrote:
>>>> I suspect you need to rollback a release and retry.  When you run "mvn
>>>> release:prepare" it creates a tag, and "mvn release:perform" just
>>>> builds that tag, which presumably doesn't contain your
>>>> <distributionManagement>  change.
>>>
>>> As a git n00b - lemme as here:
>>>
>>> If I'm in the above situation, did mvn release:prepare release:perform
>>> and then hit the locked m2 repo... so now I have a half-staged tree. I'd
>>> love to roll back to before I did that and just start fresh (I haven't
>>> pushed back to github yet) but I have no idea how to do that in git...
>>>
>>> Any thoughts?
>>>
>>> Thanks!
>>> Monty
>>>
>>>> I'd be also happy to run a release for you if you want.
>>>>
>>>> 2010/12/17 Christopher Orr<[hidden email]>:
>>>>> Ah, that would explain it.  Thanks for the info.
>>>>>
>>>>> Since there's no ETA on the migration, I attempted the workaround by adding
>>>>> the distributionManagement tag to my POM, but for some reason I still get
>>>>> the same error as below, with the same old m2 repo URL.
>>>>>
>>>>> I checked my plugin's POM and the workaround looks ok (it's just copy/pasted
>>>>> from below), and there are no references there or in ~/.m2 to the old repo.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Thanks,
>>>>> Chris
>>>>>
>>>>>
>>>>> On 17/12/2010 23:08, Kohsuke Kawaguchi wrote:
>>>>>>
>>>>>> Sigh. It's another java.net migration problem. I got a notification
>>>>>> for the batch of projects transitioning from Dec 15th but
>>>>>> maven2-repository was NOT one of them. But apparently it is getting
>>>>>> migrated anyhow [1], and there's no ETA. I should have specifically
>>>>>> asked them to push this to the very end.
>>>>>>
>>>>>> You can wait for the repository to come back, or for the time being
>>>>>> you can deploy to
>>>>>> http://maven.hudson-labs.org/content/repositories/releases/ by adding
>>>>>> the following to your POM:
>>>>>>
>>>>>>      <distributionManagement>
>>>>>>        <repository>
>>>>>>          <id>java.net-m2-repository</id>
>>>>>>
>>>>>> <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
>>>>>>        </repository>
>>>>>>      </distributionManagement>
>>>>>>
>>>>>> I intend to use this for releasing Hudson this week (and next week if
>>>>>> the repository isn't back by then.) I'll merge them (and all the
>>>>>> plugins released in the mean time) back to the java.net m2 repository
>>>>>> when it's back.
>>>>>>
>>>>>> This repository is authenticated against new beta java.net. So your
>>>>>> ~/.m2/settings.xml needs to have that or the deployment would fail.
>>>>>>
>>>>>>
>>>>>> [1] https://maven2-repository.dev.java.net/
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Rob Petti-2
In reply to this post by Kohsuke Kawaguchi
Thanks Kohsuke, this saved my butt as well. Should this maybe be added to the Hosting plugins wiki page [1]? I'm willing to bet that plenty more people will run into this in the future, given java.net's track record...

~Rob

[1] http://wiki.hudson-ci.org/display/HUDSON/Hosting+Plugins
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Mirko Friedenhagen-3
Done, see http://wiki.hudson-ci.org/pages/diffpages.action?pageId=18612226&originalId=48857135

On Sun, Dec 19, 2010 at 2:49 AM, Rob Petti <[hidden email]> wrote:
> Thanks Kohsuke, this saved my butt as well. Should this maybe be added to
> the Hosting plugins wiki page [1]? I'm willing to bet that plenty more
> people will run into this in the future, given java.net's track record...
> ~Rob
> [1] http://wiki.hudson-ci.org/display/HUDSON/Hosting+Plugins



--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

kinow
In reply to this post by Kohsuke Kawaguchi
Hi all,

I was having problems to deploy ccm plug-in to the default repository, then switched to the one mentioned below.

I did it yesterday but I think that maybe this repo is not being automaticaly merged with java.net repo.

Usually I release a plug-in at night and always check the plug-in Wiki on the next morning. As you can see in http://wiki.hudson-ci.org/display/HUDSON/CCM+Plugin the current version is still 1.1, so I think the update job hadn't got my changes. Is there a best way of verifying what happened after I performed a release:prepare release:perform?

Please (-:

Thanks in advance!
Bruno

--- Em sex, 17/12/10, Kohsuke Kawaguchi <[hidden email]> escreveu:

> De: Kohsuke Kawaguchi <[hidden email]>
> Assunto: Re: Unable to deploy plugin to repo
> Para: [hidden email]
> Data: Sexta-feira, 17 de Dezembro de 2010, 20:08
> Sigh. It's another java.net migration
> problem. I got a notification
> for the batch of projects transitioning from Dec 15th but
> maven2-repository was NOT one of them. But apparently it is
> getting
> migrated anyhow [1], and there's no ETA. I should have
> specifically
> asked them to push this to the very end.
>
> You can wait for the repository to come back, or for the
> time being
> you can deploy to
> http://maven.hudson-labs.org/content/repositories/releases/
> by adding
> the following to your POM:
>
>     <distributionManagement>
>       <repository>
>        
> <id>java.net-m2-repository</id>
>         <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
>       </repository>
>     </distributionManagement>
>
> I intend to use this for releasing Hudson this week (and
> next week if
> the repository isn't back by then.) I'll merge them (and
> all the
> plugins released in the mean time) back to the java.net m2
> repository
> when it's back.
>
> This repository is authenticated against new beta java.net.
> So your
> ~/.m2/settings.xml needs to have that or the deployment
> would fail.
>
>
> [1] https://maven2-repository.dev.java.net/
>
> 2010/12/17 Monty Taylor <[hidden email]>:
> > +1 (me too)
> >
> > On 12/17/2010 01:45 PM, Christopher Orr wrote:
> >> Hi all,
> >>
> >> I'm trying to release a plugin at the moment, but
> not having much luck.
> >>
> >> I discovered the prior thread about updating my
> pom.xml to include the
> >> maven-release-plugin and new SCM URL stuff, so
> everything there should
> >> be correct.
> >>
> >> But running "mvn release:prepare release:perform"
> as usual results in
> >> the following failure:
> >>
> >>
> >> [INFO] [INFO] [deploy:deploy {execution:
> default-deploy}]
> >>
> >> [INFO] [INFO]
> >>
> ------------------------------------------------------------------------
> >> [INFO] [ERROR] BUILD ERROR
> >> [INFO] [INFO]
> >>
> ------------------------------------------------------------------------
> >> [INFO] [INFO] Error deploying artifact: Connection
> failed: Unable to
> >> connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
> >> [INFO]
> >> [INFO] svn: authentication cancelled
> >> [INFO] [INFO]
> >>
> ------------------------------------------------------------------------
> >> [INFO] [INFO] For more information, run Maven with
> the -e switch
> >>
> >>
> >> I can access that URL from my browser, using my
> normal java.net
> >> credentials.
> >>
> >> I tried adding the -Dusername=foo and
> -Dpassword=bar parameters to the
> >> command line (as mentioned on the wiki), but that
> fails very early on:
> >>
> >>
> >> [INFO] [release:perform {execution: default-cli}]
> >> [INFO] Checking out the project to perform the
> release ...
> >> [INFO] Executing: /bin/sh -c cd
> >> /Users/chris/code/android-emulator/target
> && svn --username orrc
> >> --password '*****' --non-interactive checkout
> >> https://svn.java.net/svn/hudson~svn/tags/android-emulator-1.5
> >>
> /Users/chris/code/android-emulator/target/checkout
> >> [INFO] Working directory:
> /Users/chris/code/android-emulator/target
> >> [ERROR] The svn command failed.
> >> [INFO]
> >>
> ------------------------------------------------------------------------
> >> [ERROR] BUILD FAILURE
> >> [INFO]
> >>
> ------------------------------------------------------------------------
> >> [INFO] Unable to checkout from SCM
> >> Provider message:
> >> The svn command failed.
> >> Command output:
> >> Unknown command: 'orrc'
> >> Type 'svn help' for usage.
> >>
> >>
> >> Any ideas what I could be missing?
> >>
> >> Thanks,
> >> Chris
> >>
> >
> >
>
>
>
> --
> Kohsuke Kawaguchi
>



Reply | Threaded
Open this post in threaded view
|

RE: Re: Unable to deploy plugin to repo

martin.loiselle@medrium.com
This post has NOT been accepted by the mailing list yet.
On vacation:
I will be out of the office starting the Dec. 23rd and
will return on January 10.

for any problem related to your email or computer, please send an email to [hidden email].

For any emergency, call at 1-418-264-6911
Reply | Threaded
Open this post in threaded view
|

Re: Unable to deploy plugin to repo

Farshid Ghods
In reply to this post by kinow
Hi,

I am trying to release a plugin with the latest updates from the
latest source in  github.

I created the /User/../.java.net that Koshuke suggested and added my
java.net userName and password.

mvn release:prepare goes through fine but release:perform fails with
this error

[INFO] [INFO] Error deploying artifact: Connection failed: Unable to
connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/
[INFO]
[INFO] svn: authentication cancelled


I am able to login to java.net with the same user/pass I specified
in .java.net file so i dont think the issue is in the credentials


I also tried the -Dusername=xxx -Dpassword=yyy and that didn't help
either.

https://github.com/hudson/testng-plugin-plugin

anyone faced this issue after java.net migration ?


Thanks,
Farshid

On Dec 22 2010, 3:51 pm, "Bruno P. Kinoshita"
<[hidden email]> wrote:

> Hi all,
>
> I was having problems to deploy ccm plug-in to the default repository, then switched to the one mentioned below.
>
> I did it yesterday but I think that maybe this repo is not being automaticaly merged with java.net repo.
>
> Usually I release a plug-in at night and always check the plug-in Wiki on the next morning. As you can see inhttp://wiki.hudson-ci.org/display/HUDSON/CCM+Pluginthe current version is still 1.1, so I think the update job hadn't got my changes. Is there a best way of verifying what happened after I performed a release:prepare release:perform?
>
> Please (-:
>
> Thanks in advance!
> Bruno
>
> --- Em sex, 17/12/10, Kohsuke Kawaguchi <[hidden email]> escreveu:
>
>
>
>
>
>
>
> > De: Kohsuke Kawaguchi <[hidden email]>
> > Assunto: Re:Unableto deploy plugin to repo
> > Para: [hidden email]
> > Data: Sexta-feira, 17 de Dezembro de 2010, 20:08
> > Sigh. It's another java.net migration
> > problem. I got a notification
> > for the batch of projects transitioning from Dec 15th but
> >maven2-repository was NOT one of them. But apparently it is
> > getting
> > migrated anyhow [1], and there's no ETA. I should have
> > specifically
> > asked them to push this to the very end.
>
> > You can wait for the repository to come back, or for the
> > time being
> > you can deploy to
> >http://maven.hudson-labs.org/content/repositories/releases/
> > by adding
> > the following to your POM:
>
> >     <distributionManagement>
> >       <repository>
> >        
> > <id>java.net-m2-repository</id>
> >         <url>http://maven.hudson-labs.org/content/repositories/releases/</url>
> >       </repository>
> >     </distributionManagement>
>
> > I intend to use this for releasing Hudson this week (and
> > next week if
> > the repository isn't back by then.) I'll merge them (and
> > all the
> > plugins released in the mean time) back to the java.net m2
> > repository
> > when it's back.
>
> > This repository is authenticated against new beta java.net.
> > So your
> > ~/.m2/settings.xml needs to have that or the deployment
> > would fail.
>
> > [1]https://maven2-repository.dev.java.net/
>
> > 2010/12/17 Monty Taylor <[hidden email]>:
> > > +1 (me too)
>
> > > On 12/17/2010 01:45 PM, Christopher Orr wrote:
> > >> Hi all,
>
> > >> I'm trying to release a plugin at the moment, but
> > not having much luck.
>
> > >> I discovered the prior thread about updating my
> > pom.xml to include the
> > >> maven-release-plugin and new SCM URL stuff, so
> > everything there should
> > >> be correct.
>
> > >> But running "mvn release:prepare release:perform"
> > as usual results in
> > >> the following failure:
>
> > >> [INFO] [INFO] [deploy:deploy {execution:
> > default-deploy}]
>
> > >> [INFO] [INFO]
>
> > ------------------------------------------------------------------------
> > >> [INFO] [ERROR] BUILD ERROR
> > >> [INFO] [INFO]
>
> > ------------------------------------------------------------------------
> > >> [INFO] [INFO] Error deploying artifact: Connection
> > failed:Unableto
> > >>connecttohttps://svn.dev.java.net/svn/maven2-repository/trunk/repository/
> > >> [INFO]
> > >> [INFO] svn: authentication cancelled
> > >> [INFO] [INFO]
>
> > ------------------------------------------------------------------------
> > >> [INFO] [INFO] For more information, run Maven with
> > the -e switch
>
> > >> I can access that URL from my browser, using my
> > normal java.net
> > >> credentials.
>
> > >> I tried adding the -Dusername=foo and
> > -Dpassword=bar parameters to the
> > >> command line (as mentioned on the wiki), but that
> > fails very early on:
>
> > >> [INFO] [release:perform {execution: default-cli}]
> > >> [INFO] Checking out the project to perform the
> > release ...
> > >> [INFO] Executing: /bin/sh -c cd
> > >> /Users/chris/code/android-emulator/target
> > && svn --username orrc
> > >> --password '*****' --non-interactive checkout
> > >>https://svn.java.net/svn/hudson~svn/tags/android-emulator-1.5
>
> > /Users/chris/code/android-emulator/target/checkout
> > >> [INFO] Working directory:
> > /Users/chris/code/android-emulator/target
> > >> [ERROR] The svn command failed.
> > >> [INFO]
>
> > ------------------------------------------------------------------------
> > >> [ERROR] BUILD FAILURE
> > >> [INFO]
>
> > ------------------------------------------------------------------------
> > >> [INFO]Unableto checkout from SCM
> > >> Provider message:
> > >> The svn command failed.
> > >> Command output:
> > >> Unknown command: 'orrc'
> > >> Type 'svn help' for usage.
>
> > >> Any ideas what I could be missing?
>
> > >> Thanks,
> > >> Chris
>
> > --
> > Kohsuke Kawaguchi