I did this and it worked. No 502. So I fear this is somehow local to
Sean. However,for someone else to take over, they'd have to blow off
the tag and rollback the poms and start over, unless there's a release
plugin trick that I don't know.

On Thu, Oct 21, 2010 at 9:48 PM, Drew Farris <[email protected]> wrote:
> Sean, you can do a SNAPSHOT deployment that includes the distribution
> archives by doing:
>
> mvn -Prelease deploy
>
> I pulled apart the distribution and the 45M size seems somewhat
> reasonable. Uncompressed, the distribution is 75M and looks like:
>
> 8.0K    ./bin
> 96K     ./conf
> 38M     ./docs
> 12M     ./lib
> 1.3M    ./mahout-core-0.4-SNAPSHOT.jar
> 8.4M    ./mahout-core-0.4-SNAPSHOT-job.jar
> 260K    ./mahout-examples-0.4-SNAPSHOT.jar
> 9.8M    ./mahout-examples-0.4-SNAPSHOT-job.jar
> 348K    ./mahout-math-0.4-SNAPSHOT.jar
> 6.2M    ./mahout-taste-webapp-0.4-SNAPSHOT.war
> 132K    ./mahout-utils-0.4-SNAPSHOT.jar
>
> I dug into the docs directory and based on the number and side of
> files, 38M is reasonable. It probably doesn't help that many of the
> dependencies are packaged in both lib, and the job jars, but there's
> really no way around that.
>
> Drew
>
> On Thu, Oct 21, 2010 at 8:22 PM, Benson Margulies <[email protected]> 
> wrote:
>> I ran it. You run 'mvn deploy' with credentials set up.
>>
>> It worked. I'll try it again with -Prelease to be sure. However, there
>> are some pretty big items in, for example, a CXF release, so I'm
>> having a hard time beliving it's size. Has anyone asked
>> infrastructure@ for help?
>>
>> On Thu, Oct 21, 2010 at 6:49 PM, Sean Owen <[email protected]> wrote:
>>> How do I do a snapshot deployment myself? they appear to be working from
>>> Hudson in that there are snapshots out there.
>>>
>>> The big distro file is 45MB.
>>>
>>> On Thu, Oct 21, 2010 at 11:16 PM, Ted Dunning <[email protected]> wrote:
>>>
>>>> Sean,
>>>>
>>>> How big is that file?
>>>>
>>>> On Thu, Oct 21, 2010 at 1:34 PM, Sean Owen <[email protected]> wrote:
>>>>
>>>> > I should say I suspect this has to do with perhaps a file upload size
>>>> > limit.
>>>> > Clearly it's getting several modules' worth of files into the repo, I can
>>>> > see it. However when it goes to upload the biggest one (80MB+) this
>>>> happens
>>>> >
>>>>
>>>
>>
>

Reply via email to