buildr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pepijn Van Eeckhoudt <pepijn.vaneeckho...@luciad.com>
Subject Re: POM uploaded multiple times for attached artifacts
Date Thu, 11 Feb 2010 11:08:38 GMT
How does this look?

I've been programming Java for 9 years now, so there might be some 
java-isms in there...

Pepijn

On 11/2/2010 10:15, Antoine Toulme wrote:
> That's a bug.
>
> Look line 163 of artifact.rb.
>
> Instead of calling the upload method, you could encapsulate in a task and
> add it as a prerequisite, I guess. Make sure to use a task name that would
> work on the project.
>
> On Thu, Feb 11, 2010 at 01:09, Pepijn Van Eeckhoudt<
> pepijn.vaneeckhoudt@luciad.com>  wrote:
>
>> When executing 'buildr upload' on a simple java project with the following
>> buildfile, the pom gets uploaded twice; once for each package
>>
>> define 'attachedartifacts' do
>>   project.group = "attached"
>>   project.version = "1.0"
>>
>>   package(:jar)
>>   package(:sources)
>> end
>>
>> This doesn't work when uploading to a 'release' maven2 repository as these
>> often don't allow updating of files. In practice I'm trying to upload to a
>> release repository on a Nexus server.
>>
>> Is this intentional behavior of buildr or is this a bug? Any idea how to
>> work around this problem?
>>
>> If you guys can give me some pointers, I can work on a patch for this. I
>> think to correct this the upload operation for each artifact should be a
>> task itself as well. This would ensure upload is only invoked once for each
>> pom.
>>
>> Pepijn
>>
>


-- 
Pepijn Van Eeckhoudt - Project Leader
T +32 16 23 95 91
F +32 16 29 34 22 | pepijn.vaneeckhoudt@luciad.com

LUCIAD - high performance visualization
Wetenschapspark Arenberg | Gaston Geenslaan 9
3001 Leuven | Belgium | www.luciad.com


Mime
View raw message