1 2 Previous Next 19 Replies Latest reply on Mar 18, 2008 12:02 PM by adrian.brock

Moving to CR1 releases of the MC projects

adrian.brock Mar 17, 2008 1:05 PM

In an effort to try to get the codebase stable I want to move to more
frequent releases of the betas with the codebase in an easy integratable state
into JBossAS.

If we think a beta is stable then we can move it to an CR1 meaning there
will be no more new features (however minor), just bug fixes.

So starting from this week, I'm going to be doing beta releases on Fridays
of the MC projects if they have changes during the week.

These are the main projects used by the AS that I'm responsbile for at the moment,
i.e. not VFS, managed, reliance, OSGI

With that in bind, JIRA needs updating with what we think will be done end of
Thursday. Friday will be testing and bug fixing only until I've got the releases out. :-)

I'll be spending most of my time testing and fixing the AS anyway.

Anything that doesn't make it must be reverted and done again in the next week,
so plan accordingly.
(if we move to project to a CRx then I'll create a branch such that new
development/features can continue in trunk).

I'm hoping we can get to CRx/GA releases very quickly,
hopefully within a couple of weeks?

1. Re: Moving to CR1 releases of the MC projects

adrian.brock Mar 17, 2008 1:07 PM (in response to adrian.brock)

"adrian@jboss.org" wrote:

So starting from this week, I'm going to be doing beta releases on Fridays
of the MC projects if they have changes during the week.

If we can get a release out before Friday all the better.
e.g. I'd like to get the reflection and MDR projects with the latest "private fields"
changes/fixes beta12 out as soon as possible since the other projects depend on those.
Actions
2. Re: Moving to CR1 releases of the MC projects

alesj Mar 17, 2008 2:28 PM (in response to adrian.brock)

"adrian@jboss.org" wrote:

e.g. I'd like to get the reflection and MDR projects with the latest "private fields" changes/fixes beta12 out as soon as possible since the other projects depend on those.

I'm currently hacking in the field injection features in the Kernel module.
ATM I don't see any other fixes/addition to Reflection or MDR, but I'm not done yet, specially not with the full blown tests.
But I promise I'll be done by Thursday. With all 3 modules.
Actions
3. Re: Moving to CR1 releases of the MC projects

adrian.brock Mar 17, 2008 2:38 PM (in response to adrian.brock)

"alesj" wrote:
"adrian@jboss.org" wrote:

e.g. I'd like to get the reflection and MDR projects with the latest "private fields" changes/fixes beta12 out as soon as possible since the other projects depend on those.

I'm currently hacking in the field injection features in the Kernel module.
ATM I don't see any other fixes/addition to Reflection or MDR, but I'm not done yet, specially not with the full blown tests.
But I promise I'll be done by Thursday. With all 3 modules.

I'd prefer it you said Wednesday. But I want to get those changes tested in the AS
before I do the other releases.

They are core to the other dependencies which is why I want those projects
at CR1 ASAP.

reflection/mdr -> microcontainer
reflection -> jbossxb
mdr -> aop
microcontainer -> classloaders
microcontainer -> deployers
Actions
4. Re: Moving to CR1 releases of the MC projects

alesj Mar 17, 2008 2:41 PM (in response to adrian.brock)

"adrian@jboss.org" wrote:

I'd prefer it you said Wednesday. But I want to get those changes tested in the AS before I do the other releases.

OK, I think we can agree on the Wednesday evening. :-)
Actions
5. Re: Moving to CR1 releases of the MC projects

adrian.brock Mar 18, 2008 6:13 AM (in response to adrian.brock)

I also don't see feature requests for

ControllerMode == asynchronous (requested by Bela)
or the error handling mechanism (requested by Tom)

We should add api for these even if we don't implement them in 2.0.0.GA
That way they can be implemented in 2.0.X

e.g. we can automatically change asynchronous to automatic until it is done.
Actions
6. Re: Moving to CR1 releases of the MC projects

alesj Mar 18, 2008 6:19 AM (in response to adrian.brock)

"adrian@jboss.org" wrote:
I also don't see feature requests for

One feature at the time. :-)

"adrian@jboss.org" wrote:

or the error handling mechanism (requested by Tom)

You mean Julien. ;-)

"adrian@jboss.org" wrote:

We should add api for these even if we don't implement them in 2.0.0.GA
That way they can be implemented in 2.0.X

I can start on this after what I'm currently doing.
Like you said, to at least get the API in.

Can you add JIRAs for this?
Actions
7. Re: Moving to CR1 releases of the MC projects

adrian.brock Mar 18, 2008 6:44 AM (in response to adrian.brock)

"alesj" wrote:

Can you add JIRAs for this?

I was only asking that you raise the JIRA issues so we don't forget them for CR1. :-)

All that's required for CR1 is that the api exists
(we can't change the public api after CR1). It can be "mocked" until
we actually implement it, e.g. with big warnings and ignoring the request.
Actions
8. Re: Moving to CR1 releases of the MC projects

alesj Mar 18, 2008 6:51 AM (in response to adrian.brock)

"adrian@jboss.org" wrote:

I was only asking that you raise the JIRA issues so we don't forget them for CR1. :-)

OK, I'll do it.
And assign them to you. :-)
Actions
9. Re: Moving to CR1 releases of the MC projects

adrian.brock Mar 18, 2008 6:54 AM (in response to adrian.brock)

Something else we don't have a JIRA issue for:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130852
check we compile on JDK6
Actions
10. Re: Moving to CR1 releases of the MC projects

adrian.brock Mar 18, 2008 6:54 AM (in response to adrian.brock)

"adrian@jboss.org" wrote:
Something else we don't have a JIRA issue for:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130852
check we compile on JDK6

All projects.
Actions
11. Re: Moving to CR1 releases of the MC projects

adrian.brock Mar 18, 2008 6:56 AM (in response to adrian.brock)

Another in/uncallbacks in BeanMetaDataBuilder
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130106
Actions
12. Re: Moving to CR1 releases of the MC projects

adrian.brock Mar 18, 2008 6:57 AM (in response to adrian.brock)

There's also the issue of fixing getChild() in the VFS and testing against
the latest VFS release.

I was still seeing FileNotFoundException from getChild() when I was testing
yesterday.

VFS must be final for the deployers to go final.
Actions
13. Re: Moving to CR1 releases of the MC projects

alesj Mar 18, 2008 8:22 AM (in response to adrian.brock)
"adrian@jboss.org" wrote:

I was still seeing FileNotFoundException from getChild() when I was testing
yesterday.

Perhaps the same problem as Scott was having?
- http://www.jboss.org/index.html?module=bb&op=viewtopic&t=131032

Since the only place that FNFE gets thrown is in FileHandler constructor.
public FileHandler(FileSystemContext context, VirtualFileHandler parent, File file, URL url) throws IOException { super(context, parent, url, file.getName()); this.file = file; if (file.exists() == false) throw new FileNotFoundException("File does not exist: " + file.getCanonicalPath()); setVfsUrl(new URL("vfs" + url)); }

And the only usage of this constructor has a check before:
else if (file.exists()) { handler = new FileHandler(this, parent, file, uri); }

OK, in theory if you looked at the code few mins before, there were more FNFE usages, but they were never used.
I now removed them, doing a bit of cleanup.
Actions
14. Re: Moving to CR1 releases of the MC projects

alesj Mar 18, 2008 9:26 AM (in response to adrian.brock)

"adrian@jboss.org" wrote:
"adrian@jboss.org" wrote:
Something else we don't have a JIRA issue for:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130852
check we compile on JDK6

All projects.

http://jira.jboss.com/jira/browse/JBMICROCONT-267
Actions

1 2 Previous Next

Go to original post