[seam-dev] Seam 2.1 branch
Pete Muir
pmuir at redhat.com
Sun Apr 19 14:25:21 EDT 2009
On 19 Apr 2009, at 19:19, Pete Muir wrote:
>
> On 19 Apr 2009, at 12:48, Shane Bryzak wrote:
>
>> The majority of the restructure is now complete, and what was in
>> Seam trunk has now been moved to the Seam_2_1 branch:
>>
>> https://svn.jboss.org/repos/seam/branches/community/Seam_2_1/
>>
>> Any further development on Seam 2.1.x should be done in this
>> branch, and only Seam 3.x development should now be happening in
>> trunk. From here onward there is still a lot of work to get trunk
>> to a stable form, which will be my top priority this week. In no
>> particular order:
>
> Can we shift the new stuff up one level, having it in trunk/modules/
> trunk is weird ;-)
>
> Let's leave all the legacy stuff (build, bootstrap, random scripts,
> eclipse project info) in trunk for now.
>
> Common should start empty and we can move code from the old seam
> core bit by bit.
BTW Any dependency on common/addition to common should be very
carefully considered - we can't just dump code in there.
>
>
> Personally, I would start all modules empty - it saves on having to
> apply updates to trunk and the 2.1 branch for now (until it is
> actually ported).
>
>>
>>
>> 1. The build needs to be fixed. We will be moving to a maven-based
>> build at least for modules and common. This gets number one
>> priority.
>
> We should use maven to build example artifacts too probably, and use
> ant for the deployment.
>
>
>>
>> 2. Examples build needs to be fixed - Dan do you think you could
>> work on this?
>> 3. Docs build need to be fixed. As each module has now become its
>> own standalone project, the documentation will need to be self-
>> contained within each module. So for example, docs for the pdf
>> feature should be contained under modules/trunk/pdf/docs. We still
>> need a master documentation build for when we do a full Seam
>> release, which will include the docs for all modules. We also need
>> to notify the documentation team so that they can update their
>> build system. Pete do you know who we should contact for this?
>
> How do you mean? What will break?
>
>>
>> 4. The Hudson build is currently broken, so for now we should
>> disable it for trunk. We also need to set up new Hudson builds for
>> the 2_1 branch. Pete, can you please delegate this task to the
>> appropriate person?
>
> Ondrej, can you take care of this?
>
>>
>> 5. We need to start porting the modules to JSR-299. Our goal here
>> should be to have implementation-independent modules, so that it
>> should be possible to drop in any of our modules into any JSR-299
>> implementation and have it work in that environment. Security will
>> be first off the bat as it is required by the booking example.
>> 6. The booking example needs to be ported to run on JSR-299 (very
>> high priority).
>
> and JSF2
>
>>
>> 7. We should possibly evaluate whether any of the other major
>> features such as framework, bpm, rules, etc deserve to be in their
>> own module.
>
> bpm will be done for Web Beans. All major features should be in
> their own module. There is no Seam "core" anymore.
>
>>
>>
>> That's the state of things at the moment, I'll try to post regular
>> progress updates this week. I'll also post something to the forums
>> to let the community know about the changes.
>
> Thanks Shane!
>
>>
>>
>> Shane
>>
>>
>> Shane Bryzak wrote:
>>> I'm now starting the restructuring work on Seam trunk, so the code
>>> freeze is now in effect. I'll send another mail once it's done.
>>>
>>> Thanks,
>>> Shane
>>>
>>> Shane Bryzak wrote:
>>>> All,
>>>>
>>>> Shortly (tomorrow evening my time) I'm going to branch Seam trunk
>>>> into a Seam_2_1 branch, and start working on the directory
>>>> structure for Seam 3 in trunk. After discussing with Pete, we've
>>>> decided that we are going to go with a modular directory
>>>> structure which will make it possible to do separate releases for
>>>> individual Seam modules (as well as other advantages). The new
>>>> directory structure will look somewhat like this:
>>>>
>>>> /seam/trunk
>>>> /modules/trunk
>>>> /excel
>>>> /mail
>>>> /pdf
>>>> /remoting
>>>> /resteasy
>>>> /rss
>>>> /security
>>>> /sandbox/trunk
>>>> /other sandbox
>>>> modules go here,
>>>> /and once stable they
>>>> move to /modules
>>>> /examples/trunk
>>>> /existing seam
>>>> examples go here
>>>> /docs/trunk
>>>> /common/trunk
>>>>
>>>> Could we please have all code checked in before this change -
>>>> I'll probably begin around the following time, and require a
>>>> short code freeze (hopefully just a few hours) while the
>>>> restructuring is taking place.
>>>>
>>>> http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=19&year=2009&hour=18&min=0&sec=0&p1=47
>>>> <http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=19&year=2009&hour=18&min=0&sec=0&p1=47
>>>> >
>>>>
>>>> Thanks,
>>>> Shane
>>>> _______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>
> --
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
More information about the seam-dev
mailing list