So, the next issue is deploying the peripheral files that aren't in
Maven, re. the section in core/pom.xml calling deploy-file and trying
to send the results to ${deploy.url}. This needs to be changed to
send the results to the Nexus server along with the other artifacts.
-Grant
On Oct 26
Sure, I updated the release wiki, but would be good to add that link
too.
On Oct 26, 2009, at 7:02 PM, Sean Owen wrote:
Ah yes, maybe we should link to this:
http://maven.apache.org/developers/committer-settings.html
which has some general committer settings included this one.
On Mon, Oct 2
Ah yes, maybe we should link to this:
http://maven.apache.org/developers/committer-settings.html
which has some general committer settings included this one.
On Mon, Oct 26, 2009 at 10:58 PM, Grant Ingersoll wrote:
> Now working, I believe. I added:
>
>
> apache.releases.https
> *
Now working, I believe. I added:
apache.releases.https
**
***
To my settings.xml section. This username/pass should be
your ASF svn user/pass
On Oct 26, 2009, at 6:07 PM, Grant Ingersoll wrote:
Following this lead:
http://www.sonatype.com/books/nexu
Following this lead:
http://www.sonatype.com/books/nexus-book/reference/staging-sect-deployment.html#staging-sect-deploy-credentials
On Oct 26, 2009, at 5:55 PM, Grant Ingersoll wrote:
Hmm, seems it uses your SVN credentials. I can log in to Nexus w/
those creds.
On Oct 26, 2009, at 5:53 P
Hmm, seems it uses your SVN credentials. I can log in to Nexus w/
those creds.
On Oct 26, 2009, at 5:53 PM, Grant Ingersoll wrote:
Yeah, I'm guessing this is where I/we need to get Nexus
credentials. Digging in.
On Oct 26, 2009, at 5:41 PM, Sean Owen wrote:
Whelp at least there is a s
Yeah, I'm guessing this is where I/we need to get Nexus credentials.
Digging in.
On Oct 26, 2009, at 5:41 PM, Sean Owen wrote:
Whelp at least there is a small clue here, HTTP 401 -- sounds like
something didn't get a username/password it wants.
is this 'far enough' that we can take a peek
Whelp at least there is a small clue here, HTTP 401 -- sounds like
something didn't get a username/password it wants.
is this 'far enough' that we can take a peek at the release candidate?
On Mon, Oct 26, 2009 at 9:38 PM, Grant Ingersoll wrote:
> [INFO] [INFO] [deploy:deploy]
> [INFO] Uploading:
[INFO] [INFO] [deploy:deploy]
[INFO] Uploading:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/mahout/mahout/0.2/mahout-0.2.pom
[INFO] 4/4K
[INFO] 4/4K
[INFO] 4K uploaded
[INFO] [INFO]
[INFO]
That's great, since it likely means I can get past this point too. I
will abandon my experiment on p.a.o.
Sean
On Mon, Oct 26, 2009 at 9:00 PM, Grant Ingersoll wrote:
> Success. Trying release:perform now.
Success. Trying release:perform now.
On Oct 26, 2009, at 4:53 PM, Grant Ingersoll wrote:
On Oct 26, 2009, at 4:44 PM, Grant Ingersoll wrote:
On Oct 26, 2009, at 4:28 PM, Sean Owen wrote:
Good, since this is exactly where I am stuck. Do tell!
I think it has to do w/ the tag in the pom
On Oct 26, 2009, at 4:44 PM, Grant Ingersoll wrote:
On Oct 26, 2009, at 4:28 PM, Sean Owen wrote:
Good, since this is exactly where I am stuck. Do tell!
I think it has to do w/ the tag in the pom.xml. I just
checked in a change and am trying it now.
OK, pretty sure it is now due to t
On Oct 26, 2009, at 4:28 PM, Sean Owen wrote:
Good, since this is exactly where I am stuck. Do tell!
I think it has to do w/ the tag in the pom.xml. I just checked
in a change and am trying it now.
What's the remoteTagging business, and is there any workaround other
using US servers,
Good, since this is exactly where I am stuck. Do tell!
What's the remoteTagging business, and is there any workaround other
using US servers, which didn't seem to do it for me, from London.
On Mon, Oct 26, 2009 at 8:02 PM, Grant Ingersoll wrote:
> I think I see the problem
>
It look like the 'remoteTagging' business from the symptoms reported.
On Mon, Oct 26, 2009 at 4:02 PM, Grant Ingersoll wrote:
> I think I see the problem
>
>
> On Oct 26, 2009, at 3:22 PM, Grant Ingersoll wrote:
>
> Progress:
>> [INFO] [INFO] Mahout utilities
I think I see the problem
On Oct 26, 2009, at 3:22 PM, Grant Ingersoll wrote:
Progress:
[INFO] [INFO] Mahout
utilities .. SUCCESS [15.683s]
[INFO] [INFO] Mahout
examples ... SUCCESS [52.623s]
[INFO] [INFO]
---
Progress:
[INFO] [INFO] Mahout utilities ..
SUCCESS [15.683s]
[INFO] [INFO] Mahout examples ...
SUCCESS [52.623s]
[INFO] [INFO]
[INFO] [INFO]
---
If you are stuck, and you want to give me a brevette promotion to committer,
I'll make some time to try and cook this in the next few evenings.
On Mon, Oct 26, 2009 at 12:32 PM, Grant Ingersoll wrote:
> What happens if you run with mvn -e -X
>
> Here's how I've been running:
> mvn -Prelease,maho
What happens if you run with mvn -e -X
Here's how I've been running:
mvn -Prelease,mahout_release release:prepare // I've updated the
Wiki
In my settings.xml, I have:
mahout_release
*
mahout.releases::default::scp://people.apache.org/home/gsingers/public
Ah I guess whatever notes I found on this problem were misleading,
sounds like you've shown it is a path length issue. Sounds like the
possible ways forward are...
- Can you just do release builds from /tmp or something like /mahout?
- Can we switch to .zip packaging? I don't particularly care abo
I get past the TAR problem when I check out into /tmp. It really is
just an issue w/ long names. I'm on a Mac, Snow Leopard. I don't
know what to do about TAR.
My tar is:
tar --version
tar (GNU tar) 1.16.1
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software. You may r
It's kind of hard to do release management without commit access. I've done
releases for two other Apache projects, but I think I've sent along all the
suggestions I can make from the sidelines.
On Mon, Oct 26, 2009 at 7:58 AM, Sean Owen wrote:
> Ah, I see how that works now. I was using the ap
Ah, I see how that works now. I was using the apache-release profile
but it also needed to be configured with as well.
(Actually I found I needed to run my own gpg-agent too -- "eval
'gpg-agent --daemon'" -- anyone think that sounds wrong? checking
before I add it to the wiki.)
I now get:
[INFO
This could again be my misunderstanding. This was my attempt to get
all artifacts signed and this appeared to do it. But if it was already
in place via the parent pom, yes, I doubt it actually does anything.
Let us observe the result -- seems like we're making progress in
integrating with the apach
On Mon Sean Owen wrote:
> I don't know enough about GPG to know whether I should be seeing this
> at all (since my passphrase is already in settings.xml?) or how else
> this is supposed to work? does anyone see this?
You shouldn't be asked for the password if you set it in your
settings.xml and a
On Fri Grant Ingersoll wrote:
> Why was gpg-plugin just added to the core pom and not higher up?
> All the artifacts produced need to be signed.
The gpg-plugin is part of the apache-root-pom. See also:
http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?revision=766951&view=markup
http:/
26 matches
Mail list logo
