3:56 a.m.
WRT: https://jira.jboss.org/jira/browse/JBAS-5607
Let's work this properly and methodically
rather than doing random releases without notification
to the project lead.
The correct order for doing the candidate releases
(and the eventual final releases)
if you look at the dependencies should be:
jboss-reflect
jboss-mdr
jboss-man
jboss-mc
jboss-vfs
jboss-cl
jboss-deployers
Also since we are moving to candidate releases
(which could in effect be final releases)
these projects should be branched in SVN.
When doing a release, you should always check
it has the most up-to-date dependencies
(or at least is using the versions used by
JBossAS) and that the mvn dependency:tree is not
using spurious dependencies due to changes
in dependent poms.
Otherwise the project's unit tests are not
going to find problems that will occur
when the release is included in JBossAS.
Running a pre-release snapshot (equivalent binaries)
in a local JBossAS build is also a good way to make
sure you won't have to redo your releases
when it later gets integrated it into JBossAS.
Admitably, I didn't create the JIRA issues
for JBossCL like the other projects, e.g.
https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&pid...
I also need to look at why Scott's release
didn't create the parent pom .
i.e. whether it is an artifact of Paul's
maven refactoring or whether Scott just didn't
upload it?
I'll create a JBossCL CR2 when I do the proper
release, please treat CR1 as a BETA.
JBossMC, VFS and deployers still have outstanding
(minor?) issues as I mentioned in a thread earlier this week.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
4:16 a.m.
On Fri, 2008-09-05 at 10:56 +0200, Adrian Brock wrote:
WRT: https://jira.jboss.org/jira/browse/JBAS-5607
Let's work this properly and methodically
rather than doing random releases without notification
to the project lead.
e.g. I haven't even validated that Paul's maven
refactoring that he did last night hasn't broken
something.
It's kind of strange when somebody does a
supposedly stable release
and the project lead has never even built or
tested the binary (and in this case
doesn't even have the latest source/build on his machine). :-)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
4:31 a.m.
On Fri, 2008-09-05 at 10:56 +0200, Adrian Brock wrote:
When doing a release, you should always check
it has the most up-to-date dependencies
(or at least is using the versions used by
JBossAS) and that the mvn dependency:tree is not
using spurious dependencies due to changes
in dependent poms.
Otherwise the project's unit tests are not
going to find problems that will occur
when the release is included in JBossAS.
As an example:
The JBossCL CR1 wasn't built with the jboss-man CR1
release, which was the point wasn't it?
[ejort@warjort classloading-vfs]$ mvn dependency:tree | grep jboss-man
[INFO] +- org.jboss.man:jboss-managed:jar:2.0.0.Beta16:compile
It also has the wrong version of "integration" which should be CR2
[ejort@warjort classloading-vfs]$ mvn dependency:tree | grep
jboss-classloading-spi
[INFO] | | \- org.jboss:jboss-classloading-spi:jar:5.0.0.Beta4:compile
MDR which should be Beta17 (really the non-existant CR1)
[ejort@warjort classloading-vfs]$ mvn dependency:tree | grep jboss-mdr
[INFO] | \- org.jboss:jboss-mdr:jar:2.0.0.Beta16:compile
VFS which should be Beta22 (really the non-existant CR1)
[ejort@warjort classloading-vfs]$ mvn dependency:tree | grep jboss-vfs
[INFO] +- org.jboss:jboss-vfs:jar:2.0.0.Beta21:compile
etc.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
9:51 a.m.
On Fri, 2008-09-05 at 10:56 +0200, Adrian Brock wrote:
Running a pre-release snapshot (equivalent binaries)
in a local JBossAS build is also a good way to make
sure you won't have to redo your releases
when it later gets integrated it into JBossAS.
And here's an example where updating jboss-mc
to use the latest jboss-mdr/reflection
reveals a problem:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174640#...
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
10:47 a.m.
On Fri, 2008-09-05 at 10:56 +0200, Adrian Brock wrote:
The correct order for doing the candidate releases
(and the eventual final releases)
if you look at the dependencies should be:
jboss-reflect
jboss-mdr
jboss-man
jboss-mc
jboss-vfs
jboss-cl
jboss-deployers
I've got as far as jboss mc, but it seems
we also need jbossxb CR13 releasing.
And we also need the CR of jboss-vfs
(which is actually in the wrong order in
the list since it has no dependencies
on other MC projects).
So rather than wasting time duplicating
the testing with different versions,
I'll stop there for now.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
8:30 a.m.
On Fri, 2008-09-05 at 10:56 +0200, Adrian Brock wrote:
The correct order for doing the candidate releases
(and the eventual final releases)
if you look at the dependencies should be:
jboss-reflect
jboss-mdr
I've done the CR1 releases for reflect and mdr,
which means next is jboss-man.
NOTE: There's a regression here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141989
that needs looking at before jboss-man is
released.
jboss-man
There's an extra dependency here which is
jbossxb due to an inconsistency in the jaxb api.
https://jira.jboss.org/jira/browse/JBXB-149
which is coming in transivitely via the MC
dependency.
I've also asked Kabir to update aop
such that aop-mc-int and deployers
are not based on a version using MC betas.
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175035#...
jboss-mc
jboss-vfs
jboss-cl
jboss-deployers
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
3:33 p.m.
Corresponding JBAS jira tasks:
https://jira.jboss.org/jira/browse/JBAS-5879 - aop upgrade (2.0.0.CR17)
https://jira.jboss.org/jira/browse/JBAS-5934 - jbossxb upgrade (2.0.0.CR13)
There's an extra dependency here which is
jbossxb due to an inconsistency in the jaxb api.
https://jira.jboss.org/jira/browse/JBXB-149
which is coming in transivitely via the MC
dependency.
I've also asked Kabir to update aop
such that aop-mc-int and deployers
are not based on a version using MC betas.
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175035#...
11:26 a.m.
So with Scott's jboss-man release and
Kabir doing the AOP release, we are just waiting on
jbossxb and jboss-vfs releases.
The jbossxb release should help to resolve the one
remaining MC issue (which isn't critical):
https://jira.jboss.org/jira/browse/JBMICROCONT-336
but we need an upgrade of jbossxb to solve
the jaxb api dependency.
The only issue left in deployers is the removal
of some deprecated code in the structure deployers:
https://jira.jboss.org/jira/browse/JBDEPLOY-70
On Mon, 2008-09-08 at 15:43 -0700, Scott Stark wrote:
The deployer regressions are resolved and jboss-man 2.0.0.CR1 has
been
released and is in use by jbossas trunk.
Adrian Brock wrote:
> On Fri, 2008-09-05 at 10:56 +0200, Adrian Brock wrote:
>
> > The correct order for doing the candidate releases
> > (and the eventual final releases)
> > if you look at the dependencies should be:
> >
> > jboss-reflect
> > jboss-mdr
> >
>
> I've done the CR1 releases for reflect and mdr,
> which means next is jboss-man.
>
> NOTE: There's a regression here:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141989
> that needs looking at before jboss-man is
> released.
>
>
> > jboss-man
> >
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
12:21 p.m.
The only vfs issues is JBVFS-59, a failure to see the updated entries in
a link file. I'll spend a little time looking at it, but its not
critical so I'll postpone it to after CR1 and do the vfs CR1 today if I
can't get JBVFS-59 resolved.
Adrian Brock wrote:
So with Scott's jboss-man release and
Kabir doing the AOP release, we are just waiting on
jbossxb and jboss-vfs releases.
The jbossxb release should help to resolve the one
remaining MC issue (which isn't critical):
https://jira.jboss.org/jira/browse/JBMICROCONT-336
but we need an upgrade of jbossxb to solve
the jaxb api dependency.
The only issue left in deployers is the removal
of some deprecated code in the structure deployers:
https://jira.jboss.org/jira/browse/JBDEPLOY-70
12:58 p.m.
I have all of the vfs tests passing with a workaround for JBVFS-59:
Tests run: 564, Failures: 0, Errors: 0, Skipped: 0
The real problem is JBVFS-60 which I'll delay until after the CR1. I'm
going to do the vfs 2.0.0.CR1 release after checking the trunk against
some of the as/tck tests.
Scott Stark wrote:
The only vfs issues is JBVFS-59, a failure to see the updated entries
in a link file. I'll spend a little time looking at it, but its not
critical so I'll postpone it to after CR1 and do the vfs CR1 today if
I can't get JBVFS-59 resolved.
Adrian Brock wrote:
> So with Scott's jboss-man release and
> Kabir doing the AOP release, we are just waiting on jbossxb and
> jboss-vfs releases.
>
> The jbossxb release should help to resolve the one
> remaining MC issue (which isn't critical):
> https://jira.jboss.org/jira/browse/JBMICROCONT-336
> but we need an upgrade of jbossxb to solve
> the jaxb api dependency.
>
> The only issue left in deployers is the removal
> of some deprecated code in the structure deployers:
> https://jira.jboss.org/jira/browse/JBDEPLOY-70
>
>
2:03 p.m.
I'm going to do the vfs 2.0.0.CR1 release after checking the trunk against
some of the as/tck tests.
I'll do the rest of MC's sub-projects tomorrow.
There is still some Kabir's MC/Kernel JIRA issue where he attached a patch,
but I need to have a proper look at it before using it / moving it to later
version.
2:39 p.m.
vfs 2.0.0.CR1 has been released and jbossas trunk has been updated to
use it.
Scott Stark wrote:
The only vfs issues is JBVFS-59, a failure to see the updated entries
in a link file. I'll spend a little time looking at it, but its not
critical so I'll postpone it to after CR1 and do the vfs CR1 today if
I can't get JBVFS-59 resolved.
Adrian Brock wrote:
> So with Scott's jboss-man release and
> Kabir doing the AOP release, we are just waiting on jbossxb and
> jboss-vfs releases.
>
> The jbossxb release should help to resolve the one
> remaining MC issue (which isn't critical):
> https://jira.jboss.org/jira/browse/JBMICROCONT-336
> but we need an upgrade of jbossxb to solve
> the jaxb api dependency.
>
> The only issue left in deployers is the removal
> of some deprecated code in the structure deployers:
> https://jira.jboss.org/jira/browse/JBDEPLOY-70
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
10:42 a.m.
Microcontainer 2.0.0.CR1 has been released (AS5_trunk updated).
Leaving us only with Classloading (Adrian)
and then Deployers (me).
Yay!
Scott Stark wrote:
vfs 2.0.0.CR1 has been released and jbossas trunk has been updated to
use it.
Scott Stark wrote:
> The only vfs issues is JBVFS-59, a failure to see the updated entries
> in a link file. I'll spend a little time looking at it, but its not
> critical so I'll postpone it to after CR1 and do the vfs CR1 today if
> I can't get JBVFS-59 resolved.
>
> Adrian Brock wrote:
>> So with Scott's jboss-man release and
>> Kabir doing the AOP release, we are just waiting on jbossxb and
>> jboss-vfs releases.
>>
>> The jbossxb release should help to resolve the one
>> remaining MC issue (which isn't critical):
>> https://jira.jboss.org/jira/browse/JBMICROCONT-336
>> but we need an upgrade of jbossxb to solve
>> the jaxb api dependency.
>>
>> The only issue left in deployers is the removal
>> of some deprecated code in the structure deployers:
>> https://jira.jboss.org/jira/browse/JBDEPLOY-70
>>
>>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
12:05 p.m.
Classloading is done.
Ales, tag your it. ;-)
On Wed, 2008-09-10 at 17:42 +0200, Ales Justin wrote:
Microcontainer 2.0.0.CR1 has been released (AS5_trunk updated).
Leaving us only with Classloading (Adrian)
and then Deployers (me).
Yay!
Scott Stark wrote:
> vfs 2.0.0.CR1 has been released and jbossas trunk has been updated to
> use it.
>
> Scott Stark wrote:
>> The only vfs issues is JBVFS-59, a failure to see the updated entries
>> in a link file. I'll spend a little time looking at it, but its not
>> critical so I'll postpone it to after CR1 and do the vfs CR1 today if
>> I can't get JBVFS-59 resolved.
>>
>> Adrian Brock wrote:
>>> So with Scott's jboss-man release and
>>> Kabir doing the AOP release, we are just waiting on jbossxb and
>>> jboss-vfs releases.
>>>
>>> The jbossxb release should help to resolve the one
>>> remaining MC issue (which isn't critical):
>>> https://jira.jboss.org/jira/browse/JBMICROCONT-336
>>> but we need an upgrade of jbossxb to solve
>>> the jaxb api dependency.
>>>
>>> The only issue left in deployers is the removal
>>> of some deprecated code in the structure deployers:
>>> https://jira.jboss.org/jira/browse/JBDEPLOY-70
>>>
>>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
12:37 p.m.
I've lost track: is the AOP pom issue resolved or we are expecting a CR18, as well?
Adrian Brock wrote:
Classloading is done.
Ales, tag your it. ;-)
On Wed, 2008-09-10 at 17:42 +0200, Ales Justin wrote:
> Microcontainer 2.0.0.CR1 has been released (AS5_trunk updated).
>
> Leaving us only with Classloading (Adrian)
> and then Deployers (me).
>
> Yay!
>
> Scott Stark wrote:
>> vfs 2.0.0.CR1 has been released and jbossas trunk has been updated to
>> use it.
>>
>> Scott Stark wrote:
>>> The only vfs issues is JBVFS-59, a failure to see the updated entries
>>> in a link file. I'll spend a little time looking at it, but its not
>>> critical so I'll postpone it to after CR1 and do the vfs CR1 today if
>>> I can't get JBVFS-59 resolved.
>>>
>>> Adrian Brock wrote:
>>>> So with Scott's jboss-man release and
>>>> Kabir doing the AOP release, we are just waiting on jbossxb and
>>>> jboss-vfs releases.
>>>>
>>>> The jbossxb release should help to resolve the one
>>>> remaining MC issue (which isn't critical):
>>>> https://jira.jboss.org/jira/browse/JBMICROCONT-336
>>>> but we need an upgrade of jbossxb to solve
>>>> the jaxb api dependency.
>>>>
>>>> The only issue left in deployers is the removal
>>>> of some deprecated code in the structure deployers:
>>>> https://jira.jboss.org/jira/browse/JBDEPLOY-70
>>>>
>>>>
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
12:50 p.m.
Resolved
On 10 Sep 2008, at 18:37, Dimitris Andreadis wrote:
I've lost track: is the AOP pom issue resolved or we are
expecting a
CR18, as well?
Adrian Brock wrote:
> Classloading is done.
> Ales, tag your it. ;-)
> On Wed, 2008-09-10 at 17:42 +0200, Ales Justin wrote:
>> Microcontainer 2.0.0.CR1 has been released (AS5_trunk updated).
>>
>> Leaving us only with Classloading (Adrian)
>> and then Deployers (me).
>>
>> Yay!
>>
>> Scott Stark wrote:
>>> vfs 2.0.0.CR1 has been released and jbossas trunk has been
>>> updated to use it.
>>>
>>> Scott Stark wrote:
>>>> The only vfs issues is JBVFS-59, a failure to see the updated
>>>> entries in a link file. I'll spend a little time looking at it,
>>>> but its not critical so I'll postpone it to after CR1 and do the
>>>> vfs CR1 today if I can't get JBVFS-59 resolved.
>>>>
>>>> Adrian Brock wrote:
>>>>> So with Scott's jboss-man release and
>>>>> Kabir doing the AOP release, we are just waiting on jbossxb and
>>>>> jboss-vfs releases.
>>>>>
>>>>> The jbossxb release should help to resolve the one
>>>>> remaining MC issue (which isn't critical):
>>>>> https://jira.jboss.org/jira/browse/JBMICROCONT-336
>>>>> but we need an upgrade of jbossxb to solve
>>>>> the jaxb api dependency.
>>>>>
>>>>> The only issue left in deployers is the removal
>>>>> of some deprecated code in the structure deployers:
>>>>> https://jira.jboss.org/jira/browse/JBDEPLOY-70
>>>>>
>>>>>
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
5947
days inactive
5952
days old
jboss-development@lists.jboss.org
17 comments
5 participants
participants (5)
-
Adrian Brock -
Ales Justin -
Dimitris Andreadis -
Kabir Khan -
Scott Stark