[jboss-dev] Moving microcontainer -> kernel

[Ales Justin]

Afaik no.

As you know already, we need to first cleanup a few transient  
failures, only then we will be ready to use the new stuff.

Once Kabir is done with asynch fixes and I port your MDR changes to  
trunk w/o failures, we'll update the AS trunk.

Sent from my iPod

On 25.9.2009, at 20:03, Scott Marlow <smarlow at redhat.com> wrote:

> Did the AS trunk switch over to the new kernel project yet?
>
>
> On 06/04/2009 01:05 PM, Kabir Khan wrote:
>> Done. From
>> http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235449#4235449:
>>
>> As advertised the move has now happened. To check out the kernel
>> project, neé microcontainer ,
>> you now check out
>> https://svn.jboss.org/repos/jbossas/projects/kernel/trunk/ .
>>
>> https://svn.jboss.org/repos/jbossas/projects/microcontainer/branches[/url]
>> and
>> [url]https://svn.jboss.org/repos/jbossas/projects/microcontainer/ 
>> tags contain
>> the existing tags and branches for the current releases.
>>
>> Further 2.2.x releases will be tagged from
>> https://svn.jboss.org/repos/jbossas/projects/kernel/branches/Branch_2_2/[/url] 
>> ,
>> which will be a branch of
>> [url]https://svn.jboss.org/repos/jbossas/projects/kernel/trunk/
>>
>> https://svn.jboss.org/repos/jbossas/projects/microcontainer/mcdocs
>> contains the documentation, managing its own branches and tags.
>> https://svn.jboss.org/repos/jbossas/projects/microcontainer/mc-release/ 
>>  contains
>> the tool for uploading all the mc artifacts to the downloads area,
>> again managing its own branches and tags.
>> Further projects 'global' to MC should be added under
>> https://svn.jboss.org/repos/jbossas/projects/microcontainer .
>>
>> The renames of the maven artifacts are as follows. This will only  
>> take
>> effect from further 2.2.0 releases:
>> org.jboss.microcontainer:jboss-microcontainer ->
>> org.jboss.kernel:jboss-mc-kernel (parent)
>>
>> org.jboss.microcontainer:aop-mc-int -> org.jboss.kernel:aop-mc-int
>> org.jboss.microcontainer:guice-int -> org.jboss.kernel:guice-int
>> org.jboss.microcontainer:jboss-dependency ->
>> org.jboss.kernel:jboss-dependency
>> org.jboss.microcontainer:jboss-kernel -> org.jboss.kernel:jboss- 
>> kernel
>> org.jboss.microcontainer:jmx-aop-mc-int ->
>> org.jboss.kernel:jmx-aop-mc-int
>> org.jboss.microcontainer:jmx-mc-int -> org.jboss.kernel:jmx-mc-int
>> org.jboss.microcontainer:spring-int -> org.jboss.kernel:spring-int
>>
>> If there are more 2.1.x releases they will use the old group ids.
>>
>>
>> On 4 Jun 2009, at 17:25, Kabir Khan wrote:
>>
>>> This move is happening now
>>> On 28 May 2009, at 14:44, Kabir Khan wrote:
>>>
>>>> Of course, that is the plan
>>>> On 28 May 2009, at 09:29, Dimitris Andreadis wrote:
>>>>
>>>>> Just make sure the "old" branches are maintainable, because that
>>>>> what's is used in EAP5.
>>>>>
>>>>> Kabir Khan wrote:
>>>>>> If anybody else has any comments on this, please add them to this
>>>>>> thread:
>>>>>> http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156023
>>>>>> On 26 May 2009, at 16:10, Andrew Lee Rubinger wrote:
>>>>>>> Will you please follow up, when complete, with the complete:
>>>>>>>
>>>>>>> groupId:artifactId:version
>>>>>>>
>>>>>>> ...of all the projects affected, as well as their old names?
>>>>>>>
>>>>>>> Likely we'll want to be adding some rules to the various  
>>>>>>> Enforcer
>>>>>>> Plugin configurations to ban the old stuff.
>>>>>>>
>>>>>>> S,
>>>>>>> ALR
>>>>>>>
>>>>>>> Kabir Khan wrote:
>>>>>>>> We plan to make some changes to the microcontainer project over
>>>>>>>> the next few days/week, and wanted to give you all a bit of
>>>>>>>> advance warning. The reason is that the microcontainer project
>>>>>>>> has grown since its inception and is an umbrella for numerous
>>>>>>>> sub-projects: jboss-reflect, jboss-man, jboss-mdr,
>>>>>>>> jboss-mdr-cache, jboss-cl, jboss-deployers, jboss-vfs as well  
>>>>>>>> as
>>>>>>>> the 'microcontainer' project, which is really the kernel.
>>>>>>>> Hence, we plan to rebrand the existing 'microcontainer' core as
>>>>>>>> 'kernel', and here is what will change:
>>>>>>>> *** JIRA ***
>>>>>>>> We have already moved it in JIRA, so the old JBMICROCONT issues
>>>>>>>> have been moved to JBKERNEL.
>>>>>>>> The existing JBMICROCONT project will be kept to deal with
>>>>>>>> global microcontainer issues.
>>>>>>>> *** SVN ***
>>>>>>>> https://svn.jboss.org/repos/jbossas/projects/microcontainer/trunk/
>>>>>>>> will move to
>>>>>>>> https://svn.jboss.org/repos/jbossas/projects/kernel/trunk/
>>>>>>>> But we will leave the existing tags under
>>>>>>>> https://svn.jboss.org/repos/jbossas/projects/microcontainer/tags/
>>>>>>>> as well as the branch these releases have been taken from:
>>>>>>>> https://svn.jboss.org/repos/jbossas/projects/microcontainer/branches/Branch_2_0/ 
>>>>>>>>  The
>>>>>>>> plan is for the
>>>>>>>> https://svn.jboss.org/repos/jbossas/projects/microcontainer/trunk/
>>>>>>>> to be come a holder projects for things like tools, docs etc.
>>>>>>>> that bind together the individual sub-projects.
>>>>>>>> The upcoming 2.2.x releases will be tagged from
>>>>>>>> https://svn.jboss.org/repos/jbossas/projects/kernel/branches/Branch_2_2 
>>>>>>>>  (this
>>>>>>>> branch will be created later once we're ready for 2.2.x )
>>>>>>>> *** MAVEN ***
>>>>>>>> From 2.2.0 onwards the existing microcontainer artifacts will
>>>>>>>> have a new groupId
>>>>>>>> org.jboss.microcontainer -> org.jboss.kernel
>>>>>>>> The 2.0.x releases will keep on using org.jboss.microcontainer.
>>>>>>>> Cheers,
>>>>>>>> Kabir
>>>>>>>> _______________________________________________
>>>>>>>> jboss-development mailing list
>>>>>>>> jboss-development at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>>>
>>>>>>> -- 
>>>>>>> Andrew Lee Rubinger
>>>>>>> Sr. Software Engineer
>>>>>>> JBoss, a division of Red Hat, Inc.
>>>>>>> http://exitcondition.alrubinger.com
>>>>>>> _______________________________________________
>>>>>>> jboss-development mailing list
>>>>>>> jboss-development at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>> _______________________________________________
>>>>>> jboss-development mailing list
>>>>>> jboss-development at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development