Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-Id: <5B2C232E-419F-424F-818B-E5B9E8F89068@sonatype.com>
From: Jason van Zyl <jvanzyl@sonatype.com>
To: legal-discuss@apache.org
In-Reply-To: <510143ac0904290030s7ff9d21br6ed636089f24704b@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Clarification on the release requirements
Date: Wed, 29 Apr 2009 06:36:00 -0700
References: <49F71CCF.4030204@infinity.nu> <49F76AF5.3070903@infinity.nu>
  <EA990BCE-46D0-4D06-9067-30203292E067@gbiv.com>
 <49F78F77.4000904@infinity.nu>
  <1997BA4E-ABD8-4ADB-B90A-16B8669C04AB@gbiv.com>
 <9707508E-30B3-4814-A475-137414B2D285@yahoo.com>
  <510143ac0904282317n380256ld1eb9bf4c436b8b8@mail.gmail.com>
  <DC0CDEAB-4F48-4678-A467-82DDF61A8D50@sonatype.com>
 <510143ac0904282330w7ea5a2a8p6b47b462c6504d1e@mail.gmail.com>
  <29342E60-DAC3-45A3-A598-74DB5AD59BC1@sonatype.com>
 <510143ac0904290030s7ff9d21br6ed636089f24704b@mail.gmail.com>


On 29-Apr-09, at 12:30 AM, Jukka Zitting wrote:

> Hi,
>
> On Wed, Apr 29, 2009 at 8:43 AM, Jason van Zyl  
> <jvanzyl@sonatype.com> wrote:
>> So you do exactly what Maven does. Roy's argument is those  
>> convenience JARs
>> are not self-buildable and are not created properly because the Maven
>> tooling doesn't create the binary from the archive first.
>
> In Jackrabbit we actually start with the source package and mvn deploy
> (via a staged repository, manual for now, repository.a.o soon) from
> there (i.e. we don't use the release plugin). But the end result is
> pretty much equivalent to having a source assembly.
>
> Anything that (essentially) matches the contents of svn and can be
> built to produce the other release artifacts is IMHO fine as a source
> release.
>

I agree and this is generally standard practice by SCM teams. It's  
predicated on immutable tagging and the SCM being reliable. I can see  
why Roy wants it done from the source archive here because we've never  
setup CVS or SVN to follow SCM best practices and it's not uncommon  
for SVN to be out for unacceptable periods of time. So I can see where  
Roy's methodology came from. I've seen lots of diddled tags (though  
this is pretty much impossible with mvn -B release:prepare  
release:perform) and SVN has been unavailable more often then I would  
like to admit to the outside world.

>> You do what every Maven project does that uses the Maven release  
>> plugin in
>> conjunction with a source assembly for the official release.
>
> Having a source assembly for the release is IMHO perfectly fine.
>

I agree, and it's also probably not too hard to change things in a  
standard way on the Maven side to roll the source assembly and build  
the binary distributable from that given our best effort setup here.

> I think the controversy started with the Shindig release that didn't
> have such a package, only the -sources jars targeted for IDEs. Not
> sure whether same applies to Maven plugin releases.
>

Yup.

> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------

Selfish deeds are the shortest path to self destruction.

  -- The Seven Samuari, Akira Kurosawa


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org