no we tried to go for the simplest route at this point.
what you propose is certainly interesting although moving our modules around does not preclude from adopting it at some point (but making the move un-necessary). One of the thing that was proposed earlier was to have nucleus being built using not only a different workspace but also a dedicated version (not sync'ed with glassfish's version).
I thought it was an overkill at this point and I really wanted to keep a single version for all artifacts for as long as possible but could you clarify how your proposal would work if we find ourselves having to do separate releases of nucleus from its appserver counterpart ?
jerome
On Jul 15, 2011, at 12:05 AM, Sahoo wrote:
> Upon further thinking about this, I would like to know if we considered not moving the modules around. Instead, how about just providing a top level target in pom.xml to just check out the modules corresponding to a particular distribution? This would allow us to keep all the modules under one root and give us the flexibility to build disjoint distributions. The proposed source code layout seems to assume that all the distributions have a subset/superset relationships.
>
> Thanks,
> Sahoo
> On Friday 15 July 2011 06:17 AM, Shreedhar Ganapathy wrote:
>> Hello all
>> While work on 3.1.1 is heading to the finish line, we are looking into opportunities for doing some long pending code reorganization that will benefit us for future releases.
>>
>> To this end, we will be making several changes to
>> trunk workspace layout and build procedure over the next couple of days
>> .
>>
>> Please read through and let us know if you have any questions or concerns or if work on something will be severely affected that we need to reconsider currently planned workspace migration schedule.
>>
>> What we plan to do :
>>
>> 1. The current trunk workspace will be moved
>> from
>>
>> https://svn.java.net/svn/glassfish~svn/trunk/v3
>>
>> to
>>
>> https://svn.java.net/svn/glassfish~svn/trunk/main/appserver
>>
>> using svn move command in order to preserve change history.
>>
>> 2. Workspace modules which are part of "atomic" module will be moved from their current location under trunk/v3 to new location under
>> https://svn.java.net/svn/glassfish~svn/trunk/main/nucleus
>> repository. Relative location of a module compared to top level nucleus directory will remain the same.
>> This nucleus workspace will be used for bringing together modules that should belong here to will make up nucleus as a core component for server runtimes.
>>
>> How are you going to be affected and what you need to do:
>>
>> 1. If you have any pending checkins, especially in "atomic" modules please make sure that you check them in by
>> Friday, 07/15/2011 2 PM PST
>> deadline. At that time we'll start moving workspace content to the new URLs. It is very likely that you will need to do fresh checkout after the move is completed as, in the past, we had issues with module renaming/moving if you try to update or migrate you existing workspace.
>>
>> 2. If you have any pending merges from 3.1.1 branch please check them in by the same deadline i.e
>> Friday, 07/15/2011 2 pm PST
>> . You will still be able to merge after the workspace reorganization since svn move preserves past layout history, but it is easier to get it done while the trunk workspace more closely resembles 3.1.1 branch.
>>
>> 3. Expect workspace build to be broken or unstable for at least several hours and up to a day while the module migration is going on. If you have work that cannot wait please keep a copy of old workspace and track your changes so that they can be manually applied to new workspace if necessary.
>> Do not check anything in after 2 PM PST Friday until you are notified that new workspace is ready and available
>> .
>>
>> 4. After the migration is completed, you will need to check out
>> https://svn.java.net/svn/glassfish~svn/trunk/main
>> as your new workspace and you will be able to build both nucleus and the rest of GlassFish from this top level directory.
>>
>> 5. As we progress with nucleus development and content cleanup, more modules will need to be moved to
>> https://svn.java.net/svn/glassfish~svn/trunk/main/nucleus
>> . Detailed instructions for module migration will be provided once we complete "atomic" content migration.
>>
>> Thanks
>>
>> Shreedhar Ganapathy
>>
>