On Thu, Feb 5, 2009 at 11:10 AM, ant elder <[email protected]> wrote:
> > > On Tue, Feb 3, 2009 at 11:37 AM, ant elder <[email protected]> wrote: > >> >> >> On Tue, Feb 3, 2009 at 7:31 AM, Luciano Resende <[email protected]>wrote: >> >>> We have made good progress, and we should be really near getting a >>> good Java SCA 2.0-M1 RC ready for voting. >>> >>> In the mean time, I have created some stable distributions [1] so >>> people can start looking and making sure we are all comfortable with >>> the direction we are taking with the distributions, it's structure, >>> etc. >>> >>> I'll start reviewing the open JIRAS to see what is a must for this >>> release, and start moving things to the 2.0 queue. >>> >>> [1] >>> http://people.apache.org/~lresende/tuscany/20-M1-Stable/<http://people.apache.org/%7Elresende/tuscany/20-M1-Stable/> >>> >>> -- >>> Luciano Resende >>> Apache Tuscany, Apache PhotArk >>> http://people.apache.org/~lresende<http://people.apache.org/%7Elresende> >>> http://lresende.blogspot.com/ >>> >> >> >> One thing i noticed in the src distro is that lots of things seem to be >> included three times in the archive, i think we've had that in the past >> caused by something like overlapping includes in the src assembly xml. I've >> tried building the binary all distro today and it goes into a loop saying: >> >> at >> org.codehaus.plexus.archiver.AbstractArchiver$1.hasNext(AbstractArchiver.java:406) >> >> and then just ends with no message. >> >> Looking at the 2.0-M1 JIRAs there are two I think we should try really >> hard to fix for M1 - TUSCANY-2800 and TUSCANY-2805. >> >> ...ant >> >> > Some more issues with the src distro are that its missing lots of pom.xml > files so doesn't build, and its also missing lots of folders like > distribution, itests, etc. > > Thinking about what the src distribution should be like all we really want > is a complete archive of the SVN tree with any generated files excluded and > the correct legal and release info files put in the top level folder. If we > do that we no longer have _any_ of the issues with making sure the src > distro builds and is in line with the bin distro etc. We could also have > things like the LICENSE/NOTICE/BUILDING files in the SVN root folder so you > get them with an SVN checkout as well as the src distro. What do other > think? Seems so much simpler to me and we have to fix the current one anyway > so I'll start doing this now. > > ...ant > > > > Big +1 from me if we can avoid having to mess about with configuration to exclude temporary files and hence remove the subsequent checking we had to do to ensure that we had the configuration correct. Re, " complete archive of the SVN tree " I assume you mean the java/sca bit. Also that we ned to organize that so that it only contains the modules that we feel are ready for release. That's OK by me b.t.w as it mean we also don't have to go through the process when we branch of picking out the modules that should stay. In the future we have to decide what to do with modules that are in development but not ready for release. But I'm happy to defer that for M1. Simon
