[cle-release-team] The revival of full source check out

[Jean-Francois Leveque]

I like to be able to choose which kernel I'm using with 2.8.0 instead of 
the default 1.2.1, and master/pom.xml helps with this.

I also like to be able to replace the default packaged indie for Samigo 
with a patched svn source, and tweaking master/pom.xml and .externals is 
great for this.

I think the default should still be the lean inclusion of indie binaries 
instead of having to build all and it should be well documented.

The full trunk is still helpful when trying diagnosis from source, but I 
don't think it should be used for the default build.

J-F

On 06/10/2011 00:24, Steve Swinsburg wrote:
> By the way, I think we should maintain the full trunk checkout as a separate option for those that want it, but not the default.
>
>
>
> On 06/10/2011, at 9:19 AM, Steve Swinsburg wrote:
>
>> I'm not really a fan of this approach at all and don't see the point of indies if we do this.
>>
>> Would this continue into the releases? Ie 2.9.0 (or 2.10.0) would include everything? I see things getting out of sync fast and people being unable to upgrade without additional work.
>>
>> A user checks out (lets say) 2.9.0 which includes the source of Profile2 1.5.0. I find an issue and release 1.5.1. How do they upgrade? Checkout the source into another location, then they have to build and deploy that? And make sure not to redeploy everything otherwise it will be overwritten with 1.5.0 again? At the moment they can adjust a pom value or expand a zip file.
>>
>> There have a been a couple of requests for the source for indies, but not an overwhelming number (less than 10 I reckon). And it's simple to say, "Project X is currently deployed as a binary, but you can checkout the source from here<url>  and modify and build it yourself. Just don't forget to clean out shared lib and you'll be sweet."
>>
>> One of the reasons of indies is that there is no point in building all of the source if you don't need to.
>>
>> uPortal includes binary overlays of portlets because unless you really need to modify them, you don't need the source. There are a whole stack of tools I believe most people do not modify so there is no point having that source.
>>
>> I dreamt of a Sakai source checkout being a pom.xml once, as really, that is all that is needed if we have indies. Then you can grab the source and modify things if you really need to.
>>
>>
>>
>> On 06/10/2011, at 4:41 AM, csev wrote:
>>
>>> I am completely in favour.   I have the "Dr. Chuck Scripts" to simulate this right now - without them I would go crazy as a developer because grep does not work :)
>>>
>>> /Chuck