k I'l be out later. Have a quick minute.. Going to give you the weird hack
that I used to get the releases out. (I think that if we have Validate goal in
the `release-profile` somewhere, there would be no need for the hack.
Wow i really wish I'd just rewritten all of this in gradle rather
okay
but if my settings points to that machine then a release will go honking wrong
U had gitbox in your settings.xml?
I think maybe it's now.. I was using the GitHub repo before.
I'm not getting a response from it
Did you do add the servers from that pr to your settings.xml?
wish me luck
I'm trying out a release, can I go for it?
Ahhh the release was deployed as a Snapshot.. sitll will look into structure.
FYI halfway through RC4, but i think there may be an issue. I had to make
local changes to get the root pom parsable, was attempting to validate it,
however it deployed artifacts, I will look through them if i can tonight, and
if I can not finish, will rollback the release.
before calling it
Ok thanks, I'll try to give another shot now too. Testing right now, and will
push and try an RC agaian. But if it doesnt go through I'll have to leav it
for the morning. Soeey again..
Okay np will try in the morning
hey Andrew.
No it was my fault - I figured out what it was. I didn't push my last commit.
Sorry about that
]--andy
base colleenpalumbo ~ sandbox mahout master 2✎ 2? $ git diff
diff --git a/distribution/src/main/resources/assembly/bin.xml
build works here
```[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Mahout .. SUCCESS [ 3.277 s]
[INFO] Mahout Core SUCCESS [01:11
Yeah I did and got the same error; I'll see what changed and try to fix
Yeah I did and got the same error; I'll see what changed and try to fix
On Fri, Jan 31, 2020 at 16:52 Andy Palumbo - [mahout] [slack] <
0-14-0-rele...@mahout.mailclark.ai> wrote:
> Never saw that, unless I introduced it this morning when trying to roll
> back. Maybe clean out your .m2 cache
>
>
Never saw that, unless I introduced it this morning when trying to roll back.
Maybe clean out your .m2 cache
?
```INFO] [INFO] BUILD FAILURE
[INFO] [INFO]
[INFO] [INFO] Total time: 39.490 s
[INFO] [INFO] Finished at: 2020-01-31T16:48:39-08:00
[INFO] [INFO]
FYI, all, since I pushed the (small) refactor through late at night, directory
structure will be as detailed here:
https://issues.apache.org/jira/browse/MAHOUT-2084#. PR
here:https://github.com/apache/mahout/pull/389/files sorry for the odd hours
and for having to push things through like
Hey all, FYI I started work on RC4 this morning. I'll be working on it later
today, but it may need a rollback. There was a small refactor that i pushed
through last night to adhere with some the asf release guidelines. I.e.
releasing all distribution artifacts into a single directory[1]:
I think i have most of it figured out over night.. I'm really looking forward
to getting away from this release we're almost there.
rawkintrevo [4:24 AM]
lol, like all of the releases
apalumbo [4:26 AM]
seriously full out release hell my war with maven will end in with this
apalumbo [3:35 PM]
```Downloading:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/mahout/mahout-core_2.12/14.1/mahout-core_2.12-14.1.pom
Downloaded:
to test I need the resolver location. What is the URL for the staged binary? Is
it on the Nexus or Sonatype?
I need Scala 2.11
We have RC3 staged.. there are still some odd naming issuse.. the distribution
is named `distribution-14.1_12.2-bin.tar.gz` e.g. however it is uploaded
differently:
```INFO] --- maven-assembly-plugin:2.6:single (distro-assembly-src) @
distribution_2.12 ---
[INFO] Reading assembly
figured out a my gpg signing issue. Working on cutting RC3 now.
No prob Andy, feel better soon; I am on a deadline and may need to skip
tomorrow too
Hey all I'm not going to be able to make tomorrows eeting due to a bad flu. I
can make next week, I'm not even sure that There has been a time set for
tomorrow. Otherwise please do try to capture some broad strokes - I have the
notes from last meeting. At some time we should just set up a
And @abybody else.
Oops forgot link..
https://docs.google.com/document/d/10oWUL890PsFc8Bhbnd10OxLN7ef9wGcEYhpg9-L1Fnc/edit?usp=drivesdk
https://docs.google.com/document/d/10oWUL890PsFc8Bhbnd10OxLN7ef9wGcEYhpg9-L1Fnc/edit?usp=drivesdk
Hey @akm and @all I started a gdoc for this week's meet.
Thanks @akm, @all the release issues are trivial now. Everything is ready to
release, and RC builds. I'm running on a Mac and just updated. It may just be
a question of restating the key-server there may have been some security
updates that locked down access to gpg keys. It's only a
Thanks, Andrew, Turns out i have a pretty bad Respiratory infection..
so on top of everything else, that. I'm pretty shot. Ill try again tomorrow,
since I'm going to be sitting around doing nothing.
Okay I can work on this later in the week, hope you feel better soon
RC status update: I'm having an issue with what I think is my gpg2 key-server.
There was a MacOs update last week that may require new congratulations. So k
can't sign and deploy the artifacts to staging.
Have been sick and am feeling better but still need to go to Dr for
Antibiotics.
Hey @all I'm just getting over some kinda flu .. I should be able to cut a
release in the next couple of days.
Just FYI- still on it. Possibly tomorrow.
--andy
On Dec 22, 2019 11:19 PM, "Andy Palumbo - [mahout] [slack]"
<0-14-0-rele...@mahout.mailclark.ai> wrote:
Hey guys i was trying but
Hey @all I'm just getting over some kinda flu .. I should be able to cut a
release in the next couple of days.
Just FYI- still on it. Possibly tomorrow.
--andy
37 matches
Mail list logo
