You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Stephen McConnell <mc...@apache.org> on 2004/05/10 04:06:58 UTC
[VOTE] avalon product release
The following Avalon release candidates have been posted to
http://www.apache.org/~mcconnell/candidates
* avalon-framework (api/impl) 4.2 RC2
* avalon-logging 1.0 RC2
* avalon-logkit 2.0 RC1
* avalon-meta 1.4 RC1
* avalon-repository 2.0 RC2
* avalon-util 1.2 RC1
* cornerstone 2.0 RC1
* excalibur-datasource 1.2 RC1
* excalibur-lifecycle (api/impl) 1.1 RC1
* excalibur-pool (api/impl) 2.0 RC1
* excalibur-thread (api/impl) 2.0 RC1
* merlin 3.3 RC6
This votes calls for a recommendation to the Avalon PMC to publish the
above release candidates. The merlin RC6 distribution includes
substantial enhancements over 3.2.5 related to the separation of model
and runtime semantics, the addition of several new features supporting
remote artifact resolution, a new installer, improved deployment
management, separation of the runtime as a selectable plugin, together
with wide-ranging documentation and tutorial updates.
Committer Vote (quorum 3):
[ ] yes
[ ] no
[ ] abstain
Stephen.
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [VOTE] avalon product release
Posted by Stephen McConnell <mc...@apache.org>.
> This votes calls for a recommendation to the Avalon PMC to publish the
> above release candidates.
[X] yes
[ ] no
[ ] abstain
Stephen.
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [VOTE] avalon product release
Posted by Stephen McConnell <mc...@apache.org>.
Alexis Agahi wrote:
> On Wednesday 12 May 2004 00:47, Stephen McConnell wrote:
>
>>Alexis Agahi wrote:
>>
>>>On Monday 10 May 2004 04:06, Stephen McConnell wrote:
>>>
>>>>The following Avalon release candidates have been posted to
>>>>http://www.apache.org/~mcconnell/candidates
>>>> * merlin 3.3 RC6
>>>
>>>Sorry for my intrusion, but I've trouble running 3.3RC6 (yes I've just
>>>downloaded the last rc and tryed to run OpenIM with it).
>>>I've a curious ;) message "Unknown key: urn:avalon:home".
>>>Did I miss something?
>>>
>>>I've recompiled the whole project using distrib maven plugin.
>>
>>Does the component that is doing the context entry lookup declare the
>>context entry? E.g.:
>>
>> /**
>> * @avalon.entry key="urn:avalon:home" type="java.io.File"
>> */
>> public void contextualize( Context context )
>> {
>> File home = (File) context.get( "urn:avalon:home" );
>> }
>
>
> Ok one beer for you.
Done!!
> Tested with openim 1.3A1 => it works perfectly !
Glad to hear it.
Cheers, Steve.
> [non] Committer Vote (quorum 3):
>
> [x ] yes
> [ ] no
> [ ] abstain
>
> ;)
>
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [VOTE] avalon product release
Posted by Alexis Agahi <al...@users.sourceforge.net>.
On Wednesday 12 May 2004 00:47, Stephen McConnell wrote:
> Alexis Agahi wrote:
> > On Monday 10 May 2004 04:06, Stephen McConnell wrote:
> >>The following Avalon release candidates have been posted to
> >>http://www.apache.org/~mcconnell/candidates
> >> * merlin 3.3 RC6
> >
> > Sorry for my intrusion, but I've trouble running 3.3RC6 (yes I've just
> > downloaded the last rc and tryed to run OpenIM with it).
> > I've a curious ;) message "Unknown key: urn:avalon:home".
> > Did I miss something?
> >
> > I've recompiled the whole project using distrib maven plugin.
>
> Does the component that is doing the context entry lookup declare the
> context entry? E.g.:
>
> /**
> * @avalon.entry key="urn:avalon:home" type="java.io.File"
> */
> public void contextualize( Context context )
> {
> File home = (File) context.get( "urn:avalon:home" );
> }
Ok one beer for you.
Tested with openim 1.3A1 => it works perfectly !
[non] Committer Vote (quorum 3):
[x ] yes
[ ] no
[ ] abstain
;)
--
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [VOTE] avalon product release
Posted by Stephen McConnell <mc...@apache.org>.
Alexis Agahi wrote:
> On Monday 10 May 2004 04:06, Stephen McConnell wrote:
>
>>The following Avalon release candidates have been posted to
>>http://www.apache.org/~mcconnell/candidates
>> * merlin 3.3 RC6
>
>
> Sorry for my intrusion, but I've trouble running 3.3RC6 (yes I've just
> downloaded the last rc and tryed to run OpenIM with it).
> I've a curious ;) message "Unknown key: urn:avalon:home".
> Did I miss something?
>
> I've recompiled the whole project using distrib maven plugin.
Does the component that is doing the context entry lookup declare the
context entry? E.g.:
/**
* @avalon.entry key="urn:avalon:home" type="java.io.File"
*/
public void contextualize( Context context )
{
File home = (File) context.get( "urn:avalon:home" );
}
Stephen.
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [VOTE] avalon product release
Posted by Alexis Agahi <al...@users.sourceforge.net>.
On Monday 10 May 2004 04:06, Stephen McConnell wrote:
> The following Avalon release candidates have been posted to
> http://www.apache.org/~mcconnell/candidates
> * merlin 3.3 RC6
Sorry for my intrusion, but I've trouble running 3.3RC6 (yes I've just
downloaded the last rc and tryed to run OpenIM with it).
I've a curious ;) message "Unknown key: urn:avalon:home".
Did I miss something?
I've recompiled the whole project using distrib maven plugin.
When running the application I get this exception.
-----------------------------------
---- runtime exception report
--------------------------------------------------
Exception: java.lang.reflect.UndeclaredThrowableException
Message: null
---- cause
---------------------------------------------------------------------
Exception: org.apache.avalon.activation.LifecycleException
Message: Unable to create a new component instance in appliance
[/openim/storage/RosterListRepositoryHolder] due to a component deployment
failure.
---- cause
---------------------------------------------------------------------
Exception: org.apache.avalon.activation.LifecycleException
Message: Contextualization failure in
[/openim/storage/RosterListRepositoryHolder].
---- cause
---------------------------------------------------------------------
Exception: org.apache.avalon.framework.context.ContextException
Message: Unknown key: urn:avalon:home.
---- stack trace
---------------------------------------------------------------
org.apache.avalon.framework.context.ContextException: Unknown key:
urn:avalon:home.
org.apache.avalon.composition.model.impl.DefaultContext.get(DefaultContext.java:91)
net.java.dev.openim.data.storage.RosterListRepositoryHolderImpl.contextualize(RosterListRepositoryHolderImpl.java:68)
org.apache.avalon.framework.container.ContainerUtil.contextualize(ContainerUtil.java:116)
org.apache.avalon.activation.impl.DefaultComponentFactory.applyContext(DefaultComponentFactory.java:874)
org.apache.avalon.activation.impl.DefaultComponentFactory.incarnation(DefaultComponentFactory.java:302)
org.apache.avalon.activation.impl.DefaultComponentFactory.incarnate(DefaultComponentFactory.java:130)
org.apache.avalon.activation.impl.SingletonLifestyleManager.refreshReference(SingletonLifestyleManager.java:144)
org.apache.avalon.activation.impl.SingletonLifestyleManager.handleResolve(SingletonLifestyleManager.java:94)
org.apache.avalon.activation.impl.AbstractLifestyleManager.resolve(AbstractLifestyleManager.java:115)
org.apache.avalon.activation.impl.DefaultAppliance.resolve(DefaultAppliance.java:166)
org.apache.avalon.activation.impl.ApplianceInvocationHandler.getInstance(ApplianceInvocationHandler.java:183)
org.apache.avalon.activation.impl.ApplianceInvocationHandler.invoke(ApplianceInvocationHandler.java:113)
$Proxy27.getRosterList(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:324)
org.apache.avalon.activation.impl.BlockInvocationHandler.invoke(BlockInvocationHandler.java:108)
$Proxy4.getRosterList(Unknown Source)
net.java.dev.openim.data.jabber.UserImpl.getRosterItemList(UserImpl.java:155)
--
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [VOTE] avalon product release
Posted by Timothy Bennett <ex...@comcast.net>.
Stephen McConnell wrote:
>
> * avalon-framework (api/impl) 4.2 RC2
> * avalon-logging 1.0 RC2
> * avalon-logkit 2.0 RC1
> * avalon-meta 1.4 RC1
> * avalon-repository 2.0 RC2
> * avalon-util 1.2 RC1
> * cornerstone 2.0 RC1
> * excalibur-datasource 1.2 RC1
> * excalibur-lifecycle (api/impl) 1.1 RC1
> * excalibur-pool (api/impl) 2.0 RC1
> * excalibur-thread (api/impl) 2.0 RC1
> * merlin 3.3 RC6
>
> This votes calls for a recommendation to the Avalon PMC to publish the
> above release candidates.
>
Committer Vote (quorum 3):
[x] yes
[ ] no
[ ] abstain
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [VOTE] avalon product release
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Monday 10 May 2004 10:06, Stephen McConnell wrote:
> * avalon-framework (api/impl) 4.2 RC2
> * avalon-logging 1.0 RC2
> * avalon-logkit 2.0 RC1
> * avalon-meta 1.4 RC1
> * avalon-repository 2.0 RC2
> * avalon-util 1.2 RC1
> * cornerstone 2.0 RC1
> * excalibur-datasource 1.2 RC1
> * excalibur-lifecycle (api/impl) 1.1 RC1
> * excalibur-pool (api/impl) 2.0 RC1
> * excalibur-thread (api/impl) 2.0 RC1
> * merlin 3.3 RC6
Committer Vote (quorum 3):
[ x ] yes
[ ] no
[ ] abstain
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
[VOTE:RESULT] avalon product release
Posted by Stephen McConnell <mc...@apache.org>.
The community vote for the release of the following products has PASSED.
* avalon-framework (api/impl) 4.2 RC2
* avalon-logging 1.0 RC2
* avalon-logkit 2.0 RC1
* avalon-meta 1.4 RC1
* avalon-repository 2.0 RC2
* avalon-util 1.2 RC1
* cornerstone 2.0 RC1
* excalibur-datasource 1.2 RC1
* excalibur-lifecycle (api/impl) 1.1 RC1
* excalibur-pool (api/impl) 2.0 RC1
* excalibur-thread (api/impl) 2.0 RC1
* merlin 3.3 RC6
Committer votes recorded include:
Stephen McConnell +1
Andreas Oberhack +1
Niclas Hedhman +1
Timothy Bennett +1
During the vote process two items were raised that I suggested be
resolved during the publication cycle. These include the addition of a
NOTICE file to the respective distributions, and secondly - the removal
of the security configuration directives from the default kernel.
Neither of these actions have any runtime impact. I'll be cutting the
distribution release this weekend and initiating a PMC vote for publication.
Cheers, Stephen.
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: avalon product release - james/phoenix question
Posted by Stephen McConnell <mc...@apache.org>.
peter royal wrote:
> On May 10, 2004, at 6:03 AM, Stephen McConnell wrote:
>
>>> In the context of my inquiry, I couldn't care less whether Merlin even
>>> compiles. We, James, are likely going to want to put out the next
>>> release after 2.2 using the merged code, and I want to make
>>> sure that the released version of Phoenix, which is what
>>> James uses, works with these new packages
>>
>> Phoenix compatibility is not a release criteria.
>
> Do we have "release criteria" documented somewhere?
Yes we do.
Within the Avalon documentation you will find the following page
http://avalon.apache.org/community/process/release.html which basically
provides a bunch of links. The closest thing to "release criteria" is
reflected in the opinion and decisions of the release manager. The is
clearly documented under the HTTP release procedure documentation:
http://httpd.apache.org/dev/release.html
Regarding what makes it into a release, the RM is the
unquestioned authority. No one can contest what makes it
into the release. The community will judge the release's
quality after it has been issued, but the community can
not force the RM to include a feature that they feel
uncomfortable adding. Remember that this document is only
a guideline to the community and future RMs - each RM may
run a release in a different way. If you don't like what
an RM is doing, start preparing for your own competing
release.
Clearly, release criteria is what the release manager considers
appropriate and necessary. In this particular scenario I'm the release
manager and I consider that a success gump run against a _dead_ product
as more than sufficient. Don't forget everyone can download and test
the candidates against whatever they want - and from that - vote
accordingly.
Stephen.
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: avalon product release - james/phoenix question
Posted by peter royal <pr...@apache.org>.
On May 10, 2004, at 6:03 AM, Stephen McConnell wrote:
>> In the context of my inquiry, I couldn't care less whether Merlin even
>> compiles. We, James, are likely going to want to put out the next
>> release
>> after 2.2 using the merged code, and I want to make sure that the
>> released
>> version of Phoenix, which is what James uses, works with these new
>> packages.
>
> Phoenix compatibility is not a release criteria.
Do we have "release criteria" documented somewhere?
Otherwise, how was Phoenix removed from this list?
Unless there are insurmountable or very difficult technical reasons not
to do so, our releases should be backwards-compatible with our previous
releases. Especially with one of the most widely-used Avalon containers
out there.
-pete
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
avalon product release - james/phoenix question
Posted by Stephen McConnell <mc...@apache.org>.
Noel J. Bergman wrote:
>>>Do the non-Merlin-specific packages work with the released version of
>>>Phoenix? For example, can they be dropped into the James MAIN branch,
>>>and that continue to work properly?
>
>
>>The non-Merlin specific packages have been build and tested against all
>>of the cornerstone candidates and validated against JAMES MAIN.
>
>
> To be clear: using Phoenix?
The current CVS head of Phoenix builds against the release candidates as
demonstrated by recent Gump reports.
>>A single conflict exist relative to the James reference to content
>>that was deprecated in excalibur-thread which is handled in james
>>with a special "deprecation handler". Removal of the handler
>>results in a clean james build and deployment under the Merlin platform.
>
>
> Details?
Perhaps the best example would be demonstrated by putting together a
gump descriptor for James that is container independent. This would
provide the James community complete and ongoing going information about
compatibility of James CVS with Avalon. In fact, given that the James
CVS HEAD has no direct Phoenix compile or runtime dependencies - it's
probably a good idea to just update the existing gump descriptor by
simply removing the phoenix references.
If your interested in setting up some integration tests then I and
others can probably put a solution together reasonably quickly based on
the current Avalon platform.
>
>>This message is sent to you via James backed by the entire candidate
>>suite (framework, excalibur, util, logging, repository, meta, merlin).
>
>
> In the context of my inquiry, I couldn't care less whether Merlin even
> compiles. We, James, are likely going to want to put out the next release
> after 2.2 using the merged code, and I want to make sure that the released
> version of Phoenix, which is what James uses, works with these new packages.
Phoenix compatibility is not a release criteria. However, this should
not be a problem. Products that choose to remain dependent on the last
Phoenix release can continue to use the associated packages that are
known to be compatible. Alternatively, products can migrate to Merlin -
Avalon's container solution.
Stephen.
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: [VOTE] avalon product release
Posted by "Noel J. Bergman" <no...@devtech.com>.
> > Do the non-Merlin-specific packages work with the released version of
> > Phoenix? For example, can they be dropped into the James MAIN branch,
> > and that continue to work properly?
> The non-Merlin specific packages have been build and tested against all
> of the cornerstone candidates and validated against JAMES MAIN.
To be clear: using Phoenix?
> A single conflict exist relative to the James reference to content
> that was deprecated in excalibur-thread which is handled in james
> with a special "deprecation handler". Removal of the handler
> results in a clean james build and deployment under the Merlin platform.
Details?
> This message is sent to you via James backed by the entire candidate
> suite (framework, excalibur, util, logging, repository, meta, merlin).
In the context of my inquiry, I couldn't care less whether Merlin even
compiles. We, James, are likely going to want to put out the next release
after 2.2 using the merged code, and I want to make sure that the released
version of Phoenix, which is what James uses, works with these new packages.
> For reference - we can setup a deployment model whereby james runs from
> a remote url, qualified by a single local overriding configuration
> (passwords and other sensitive or site specific content). If your
> interested I would more happy to provide the block model and sample
> configuration.
After the branch merger, and after I'm satisfied that we can put out new
releases based upon Phoenix, I'll be perfectly happy to look at optional
Merlin deployment.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [VOTE] avalon product release
Posted by mcconnell <mc...@osm.net>.
Noel J. Bergman wrote:
>>The following Avalon release candidates have been posted to
>>http://www.apache.org/~mcconnell/candidates
>
>
>>This votes calls for a recommendation to the Avalon PMC to publish the
>>above release candidates.
>
>
> Do the non-Merlin-specific packages work with the released version of
> Phoenix? For example, can they be dropped into the James MAIN branch, and
> that continue to work properly?
The non-Merlin specific packages have been build and tested against all
of the cornerstone candidates and validated against JAMES MAIN. A
single conflict exist relative to the James reference to content that
was deprecated in excalibur-thread which is handled in james with a
special "deprecation handler". Removal of the handler results in a
clean james build and deployment under the Merlin platform.
This message is sent to you via James backed by the entire candidate
suite (framework, excalibur, util, logging, repository, meta, merlin).
For reference - we can setup a deployment model whereby james runs from
a remote url, qualified by a single local overriding configuration
(passwords and other sensitive or site specific content). If your
interested I would more happy to provide the block model and sample
configuration.
Cheers, Stephen.
--
|---------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org |
|---------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: [VOTE] avalon product release
Posted by "Noel J. Bergman" <no...@devtech.com>.
> The following Avalon release candidates have been posted to
> http://www.apache.org/~mcconnell/candidates
> This votes calls for a recommendation to the Avalon PMC to publish the
> above release candidates.
Do the non-Merlin-specific packages work with the released version of
Phoenix? For example, can they be dropped into the James MAIN branch, and
that continue to work properly?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org