BCEL future

[Henri Yandell <fl...@gmail.com>]

aka scheme to resurrect BCEL activity. This email is cc'd to addresses
found for Enver and Markus, but chances are they're not active
addresses anymore.

I asked the PMC list for volunteers to assist with getting things
restarted here. Conor MacNeil (already a BCEL committer), Simon
Kitching and Henning Schmiedehausen all stepped forward. Simon's asked
to be able to commit, so I'll grant him karma in a bit.

In a separate thread I'll nominate Dave Brosius for committership so
he can start applying patches, and another to give Torsten Curdt karma
so he can commit too. It'll take a while to get through the usual
CLA/fax stuff for Dave, but I'm sure things will move anyway.

I'd like to suggest some topics for thought:

How much code has changed since the last release?
How many bugs are out there?
How many have patches?
What should the next version be? I assume it should be a minor release
of some kind with bugs/patches dealt with.
Are there major plans? (1.5 support?)
When should the SVN migration happen?
Should a Wiki exist?

Torsten also suggested:

come up with junit testcases
get rid of the static repository approach?

BCEL's a blackbox to me, so I'll try not to get too involved in any
technical discussions and just offer help on infra/pmc bits.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: bcel-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bcel-dev-help@jakarta.apache.org

Re: BCEL future

[Niclas Hedhman <ni...@hedhman.org>]

On Tuesday 01 February 2005 01:18, Henri Yandell wrote:

> What should the next version be? I assume it should be a minor release
> of some kind with bugs/patches dealt with.

The current CVS breaks compatibility with latest release, as one public method 
now has an "throws Exception". I have posted a issue about this somewhere 
2004 Q2.

The change broke Excalibur Fortress, and the work-around for being compatible 
with both 5.1 and CVS is ugly.

Mailing list archive (which ain't that big) contains some more bug reports and 
patches I think, which should be worthwhile looking at.

Cheers
Niclas

---------------------------------------------------------------------
To unsubscribe, e-mail: bcel-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bcel-dev-help@jakarta.apache.org

Re: BCEL future

[db...@qis.net]

Quoting Henri Yandell <fl...@gmail.com>:

> I'd like to suggest some topics for thought:
> 
> How much code has changed since the last release?
Not sure, but i don't think much, can look into it.

> How many bugs are out there?
Bugzilla reports 22, many of which have code fix suggestions

> How many have patches?
Bugzilla reports 9

> What should the next version be? I assume it should be a minor release
> of some kind with bugs/patches dealt with.
My feeling is a 5.2 relatively minor release with java 5.0 support
Resolve bugzilla issues
Improve JavaDoc

> Are there major plans? (1.5 support?)
Add support for Annotations/Enums attributes
Add support for above access flags (patch existing)

> When should the SVN migration happen?
I vote for asap

> Should a Wiki exist?
i vote yes.

Future work: Not necessarily for this version:
Integration with Eclipse
Ant tasks
XML in/out (BCELSource for XML Transformer?)


> 
> Torsten also suggested:
> 
> come up with junit testcases
> get rid of the static repository approach?
> 
> BCEL's a blackbox to me, so I'll try not to get too involved in any
> technical discussions and just offer help on infra/pmc bits.
> 
> Hen




---------------------------------------------------------------------
To unsubscribe, e-mail: bcel-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bcel-dev-help@jakarta.apache.org

Re: BCEL future

[Markus Dahm <m....@gmx.de>]

Hi,

I 'd be glad if there would some more activity in the future, since I 
still have ideas
to add yet not enough time to realize currently. There are important changes
however like 1.5 support that should be added asap.

I also have a problem with the Apache org, because my main contact
was Jason van Zyl jvanzyl@zenplex.com which I haven't been able
to contact for quite a while.

There have been requests e.g. for new volunteer developers which I couldn't
fulfill.

Anyway I think the current version of BCEL is pretty stable yet lacks some
new ideas. There are also some comparable projects on the net now with
some interesting new features.


Cheers
    Markus


Henri Yandell wrote:

>aka scheme to resurrect BCEL activity. This email is cc'd to addresses
>found for Enver and Markus, but chances are they're not active
>addresses anymore.
>
>I asked the PMC list for volunteers to assist with getting things
>restarted here. Conor MacNeil (already a BCEL committer), Simon
>Kitching and Henning Schmiedehausen all stepped forward. Simon's asked
>to be able to commit, so I'll grant him karma in a bit.
>
>In a separate thread I'll nominate Dave Brosius for committership so
>he can start applying patches, and another to give Torsten Curdt karma
>so he can commit too. It'll take a while to get through the usual
>CLA/fax stuff for Dave, but I'm sure things will move anyway.
>
>I'd like to suggest some topics for thought:
>
>How much code has changed since the last release?
>How many bugs are out there?
>How many have patches?
>What should the next version be? I assume it should be a minor release
>of some kind with bugs/patches dealt with.
>Are there major plans? (1.5 support?)
>When should the SVN migration happen?
>Should a Wiki exist?
>
>Torsten also suggested:
>
>come up with junit testcases
>get rid of the static repository approach?
>
>BCEL's a blackbox to me, so I'll try not to get too involved in any
>technical discussions and just offer help on infra/pmc bits.
>
>Hen
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: bcel-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bcel-dev-help@jakarta.apache.org