You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <bl...@apache.org> on 2001/08/13 16:04:16 UTC
Interface Versions
I want to know if this will work:
1) Compile a Component against a Work interface with
a static final Version object set to 1.0.0.
2) Run the Component in an environment where the interface
is different (i.e. 1.0.1).
3) Test the Component's interface version and get the one
it was compiled against.
Is this in anyway possible? Or do we need to state the
Version in every object that implements it?
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Interface Versions
Posted by Peter Donald <do...@apache.org>.
On Tue, 14 Aug 2001 00:49, Peter Donald wrote:
> Thats one way of doing it. Another is to actually implement proper
> ClassLoaders that follow the jdk1.3 spec with respect to package
> dependencies and version interfaces at package level.
That may not be clear. What I mean is that instead of depending on
Configurable V1.0.0 you depend on the Avalon Framework specification 4.0 and
assume any jar that exports that spec has compliant interfaces.
--
Cheers,
Pete
*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof." *
* - John Kenneth Galbraith *
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [PATCH] Logkit - building without javax.jms and javax.sql
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Peter Donald wrote:
>
> On Thu, 16 Aug 2001 21:06, Charles Benett wrote:
> > Peter Donald wrote:
> > > On Thu, 16 Aug 2001 19:19, Paul Hammant wrote:
> > > > Trying to reapply this patch (as per invitation to commit it myself)
> > > > and it does not work. Depite trying numerous combinations of the
> > > > <exclude> for org/apache/log/output/db/**, it never excludes the
> > > > package from compilation !!?!
> > > >
> > > > Can somone else test this to make sure I am not going insane..
> > >
> > > Try adding
> > > <exclude name="org/apache/log/output/test/DBTargetTestlet.java"
> > > unless="javax.sql.present"/>
> > >
> > > The compiler is probably trying to include the classes because they are
> > > referenced from that file.
> >
> > Done. But there's still an issue with junit - build scripts aren't
> > picking the jar.
>
> hmm .. seems to work fine here. Picks up junit from
>
> ../jakarta-avalon/tools/lib/junit-3.7.jar
>
I've just patched the buildfile to include tools.class.path in the javac
classpath.
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [PATCH] Logkit - building without javax.jms and javax.sql
Posted by Peter Donald <do...@apache.org>.
On Thu, 16 Aug 2001 21:06, Charles Benett wrote:
> Peter Donald wrote:
> > On Thu, 16 Aug 2001 19:19, Paul Hammant wrote:
> > > Trying to reapply this patch (as per invitation to commit it myself)
> > > and it does not work. Depite trying numerous combinations of the
> > > <exclude> for org/apache/log/output/db/**, it never excludes the
> > > package from compilation !!?!
> > >
> > > Can somone else test this to make sure I am not going insane..
> >
> > Try adding
> > <exclude name="org/apache/log/output/test/DBTargetTestlet.java"
> > unless="javax.sql.present"/>
> >
> > The compiler is probably trying to include the classes because they are
> > referenced from that file.
>
> Done. But there's still an issue with junit - build scripts aren't
> picking the jar.
hmm .. seems to work fine here. Picks up junit from
../jakarta-avalon/tools/lib/junit-3.7.jar
>
> Charles
>
> > > - Paul
> > >
> > > Paul Hammant wrote:
> > > > Compiling Logkit is fails if you don't have javax.sql and javax.jms
> > > > in lib.
> > > >
> > > > Patch follows.
> > > >
> > > > - PH
> > > >
> > > > C:/Apache-CVS/cvs.exe diff -r HEAD build.xml
> > > > Index: build.xml
> > > > ===================================================================
> > > > RCS file: /home/cvspublic/jakarta-avalon-logkit/build.xml,v
> > > > retrieving revision 1.38
> > > > diff -r1.38 build.xml
> > > > 155a156,163
> > > >
> > > > > <available property="javax.sql.present"
> > > > > classname="javax.sql.DataSource"
> > > > > classpathref="project.class.path" />
> > > > >
> > > > > <available property="javax.jms.present"
> > > > > classname="javax.jms.TopicConnection"
> > > > > classpathref="project.class.path" />
> > > >
> > > > 167a176,179
> > > >
> > > > > <exclude name="org/apache/log/output/db/**"
> > > > > unless="javax.sql.present"/> >
> > > >
> > > > <exclude name="org/apache/log/output/jms/**"
> > > >
> > > > > unless="javax.jms.present"/>
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
> >
> > --
> > Cheers,
> >
> > Pete
> >
> > *-----------------------------------------------------*
> > * "Faced with the choice between changing one's mind, *
> > * and proving that there is no need to do so - almost *
> > * everyone gets busy on the proof." *
> > * - John Kenneth Galbraith *
> > *-----------------------------------------------------*
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
--
Cheers,
Pete
*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof." *
* - John Kenneth Galbraith *
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [PATCH] Logkit - building without javax.jms and javax.sql
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Peter Donald wrote:
>
> On Thu, 16 Aug 2001 19:19, Paul Hammant wrote:
> > Trying to reapply this patch (as per invitation to commit it myself) and
> > it does not work. Depite trying numerous combinations of the <exclude>
> > for org/apache/log/output/db/**, it never excludes the package from
> > compilation !!?!
> >
> > Can somone else test this to make sure I am not going insane..
>
> Try adding
> <exclude name="org/apache/log/output/test/DBTargetTestlet.java"
> unless="javax.sql.present"/>
>
> The compiler is probably trying to include the classes because they are
> referenced from that file.
Done. But there's still an issue with junit - build scripts aren't
picking the jar.
Charles
>
> >
> > - Paul
> >
> > Paul Hammant wrote:
> > > Compiling Logkit is fails if you don't have javax.sql and javax.jms in
> > > lib.
> > >
> > > Patch follows.
> > >
> > > - PH
> > >
> > > C:/Apache-CVS/cvs.exe diff -r HEAD build.xml
> > > Index: build.xml
> > > ===================================================================
> > > RCS file: /home/cvspublic/jakarta-avalon-logkit/build.xml,v
> > > retrieving revision 1.38
> > > diff -r1.38 build.xml
> > > 155a156,163
> > >
> > > > <available property="javax.sql.present"
> > > > classname="javax.sql.DataSource"
> > > > classpathref="project.class.path" />
> > > >
> > > > <available property="javax.jms.present"
> > > > classname="javax.jms.TopicConnection"
> > > > classpathref="project.class.path" />
> > >
> > > 167a176,179
> > >
> > > > <exclude name="org/apache/log/output/db/**"
> > > > unless="javax.sql.present"/> >
> > >
> > > <exclude name="org/apache/log/output/jms/**"
> > >
> > > > unless="javax.jms.present"/>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
>
> --
> Cheers,
>
> Pete
>
> *-----------------------------------------------------*
> * "Faced with the choice between changing one's mind, *
> * and proving that there is no need to do so - almost *
> * everyone gets busy on the proof." *
> * - John Kenneth Galbraith *
> *-----------------------------------------------------*
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [PATCH] Logkit - building without javax.jms and javax.sql
Posted by Peter Donald <do...@apache.org>.
On Thu, 16 Aug 2001 19:19, Paul Hammant wrote:
> Trying to reapply this patch (as per invitation to commit it myself) and
> it does not work. Depite trying numerous combinations of the <exclude>
> for org/apache/log/output/db/**, it never excludes the package from
> compilation !!?!
>
> Can somone else test this to make sure I am not going insane..
Try adding
<exclude name="org/apache/log/output/test/DBTargetTestlet.java"
unless="javax.sql.present"/>
The compiler is probably trying to include the classes because they are
referenced from that file.
>
> - Paul
>
> Paul Hammant wrote:
> > Compiling Logkit is fails if you don't have javax.sql and javax.jms in
> > lib.
> >
> > Patch follows.
> >
> > - PH
> >
> > C:/Apache-CVS/cvs.exe diff -r HEAD build.xml
> > Index: build.xml
> > ===================================================================
> > RCS file: /home/cvspublic/jakarta-avalon-logkit/build.xml,v
> > retrieving revision 1.38
> > diff -r1.38 build.xml
> > 155a156,163
> >
> > > <available property="javax.sql.present"
> > > classname="javax.sql.DataSource"
> > > classpathref="project.class.path" />
> > >
> > > <available property="javax.jms.present"
> > > classname="javax.jms.TopicConnection"
> > > classpathref="project.class.path" />
> >
> > 167a176,179
> >
> > > <exclude name="org/apache/log/output/db/**"
> > > unless="javax.sql.present"/> >
> >
> > <exclude name="org/apache/log/output/jms/**"
> >
> > > unless="javax.jms.present"/>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
--
Cheers,
Pete
*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof." *
* - John Kenneth Galbraith *
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [PATCH] Logkit - building without javax.jms and javax.sql
Posted by Peter Donald <do...@apache.org>.
On Tue, 14 Aug 2001 17:09, Paul Hammant wrote:
> >Looks good ... couldn't you patch this yourself ... ? ;)
>
> Err <cough/> I did not seek a new password after the May Apache hack,
> when all committers were disabled. Then I was concentrating too much on
> Jesktop to be useful to Avalon ;-)
Sounds like the perfect opportunity to turn that around now then ;)
--
Cheers,
Pete
*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof." *
* - John Kenneth Galbraith *
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [PATCH] Logkit - building without javax.jms and javax.sql
Posted by Paul Hammant <Pa...@yahoo.com>.
>
>
>Looks good ... couldn't you patch this yourself ... ? ;)
>
Err <cough/> I did not seek a new password after the May Apache hack,
when all committers were disabled. Then I was concentrating too much on
Jesktop to be useful to Avalon ;-)
-PH
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [PATCH] Logkit - building without javax.jms and javax.sql
Posted by Peter Donald <do...@apache.org>.
Looks good ... couldn't you patch this yourself ... ? ;)
On Tue, 14 Aug 2001 07:36, Paul Hammant wrote:
> Compiling Logkit is fails if you don't have javax.sql and javax.jms in lib.
>
> Patch follows.
>
> - PH
>
> C:/Apache-CVS/cvs.exe diff -r HEAD build.xml
> Index: build.xml
> ===================================================================
> RCS file: /home/cvspublic/jakarta-avalon-logkit/build.xml,v
> retrieving revision 1.38
> diff -r1.38 build.xml
> 155a156,163
>
> > <available property="javax.sql.present"
> > classname="javax.sql.DataSource"
> > classpathref="project.class.path" />
> >
> > <available property="javax.jms.present"
> > classname="javax.jms.TopicConnection"
> > classpathref="project.class.path" />
>
> 167a176,179
>
> > <exclude name="org/apache/log/output/db/**"
> > unless="javax.sql.present"/>
> > <exclude name="org/apache/log/output/jms/**"
> > unless="javax.jms.present"/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
--
Cheers,
Pete
*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof." *
* - John Kenneth Galbraith *
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [PATCH] Logkit - building without javax.jms and javax.sql
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Paul Hammant wrote:
>
> Trying to reapply this patch (as per invitation to commit it myself) and
> it does not work. Depite trying numerous combinations of the <exclude>
> for org/apache/log/output/db/**, it never excludes the package from
> compilation !!?!
>
> Can somone else test this to make sure I am not going insane..
NO - you are dead right. I tried applying your patch yesturday and got
exactly the same error!
I just assumed it was me being slow!
Charles
>
> - Paul
>
> Paul Hammant wrote:
>
> > Compiling Logkit is fails if you don't have javax.sql and javax.jms in
> > lib.
> >
> > Patch follows.
> >
> > - PH
> >
> > C:/Apache-CVS/cvs.exe diff -r HEAD build.xml
> > Index: build.xml
> > ===================================================================
> > RCS file: /home/cvspublic/jakarta-avalon-logkit/build.xml,v
> > retrieving revision 1.38
> > diff -r1.38 build.xml
> > 155a156,163
> > > <available property="javax.sql.present"
> > > classname="javax.sql.DataSource"
> > > classpathref="project.class.path" />
> > >
> > > <available property="javax.jms.present"
> > > classname="javax.jms.TopicConnection"
> > > classpathref="project.class.path" />
> > >
> > 167a176,179
> > > <exclude name="org/apache/log/output/db/**"
> > > unless="javax.sql.present"/> >
> > <exclude name="org/apache/log/output/jms/**"
> > > unless="javax.jms.present"/>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: [PATCH] Logkit - building without javax.jms and javax.sql
Posted by Paul Hammant <Pa...@yahoo.com>.
Trying to reapply this patch (as per invitation to commit it myself) and
it does not work. Depite trying numerous combinations of the <exclude>
for org/apache/log/output/db/**, it never excludes the package from
compilation !!?!
Can somone else test this to make sure I am not going insane..
- Paul
Paul Hammant wrote:
> Compiling Logkit is fails if you don't have javax.sql and javax.jms in
> lib.
>
> Patch follows.
>
> - PH
>
> C:/Apache-CVS/cvs.exe diff -r HEAD build.xml
> Index: build.xml
> ===================================================================
> RCS file: /home/cvspublic/jakarta-avalon-logkit/build.xml,v
> retrieving revision 1.38
> diff -r1.38 build.xml
> 155a156,163
> > <available property="javax.sql.present"
> > classname="javax.sql.DataSource"
> > classpathref="project.class.path" />
> >
> > <available property="javax.jms.present"
> > classname="javax.jms.TopicConnection"
> > classpathref="project.class.path" />
> >
> 167a176,179
> > <exclude name="org/apache/log/output/db/**"
> > unless="javax.sql.present"/> >
> <exclude name="org/apache/log/output/jms/**"
> > unless="javax.jms.present"/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
[PATCH] Logkit - building without javax.jms and javax.sql
Posted by Paul Hammant <Pa...@yahoo.com>.
Compiling Logkit is fails if you don't have javax.sql and javax.jms in lib.
Patch follows.
- PH
C:/Apache-CVS/cvs.exe diff -r HEAD build.xml
Index: build.xml
===================================================================
RCS file: /home/cvspublic/jakarta-avalon-logkit/build.xml,v
retrieving revision 1.38
diff -r1.38 build.xml
155a156,163
> <available property="javax.sql.present"
> classname="javax.sql.DataSource"
> classpathref="project.class.path" />
>
> <available property="javax.jms.present"
> classname="javax.jms.TopicConnection"
> classpathref="project.class.path" />
>
167a176,179
> <exclude name="org/apache/log/output/db/**"
> unless="javax.sql.present"/>
> <exclude name="org/apache/log/output/jms/**"
> unless="javax.jms.present"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Interface Versions
Posted by Berin Loritsch <bl...@apache.org>.
Paul Hammant wrote:
>
> > [..] The only time
> > I think we need to worry about specific interfaces is if we implement multiple
> > work interfaces. I don't like that approach though.
>
> Is that not part of the nature of Java programming though?
My definition of "work interface" is documented in the Programming with Avalon
document on the site. The work interface is basically the *type* of block we
are creating. In the Block paradigm, it is refering to the Service we are
implementing.
Hopefully, it is best to only implement one service at a time....
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Interface Versions
Posted by Paul Hammant <pa...@yahoo.com>.
> [..] The only time
> I think we need to worry about specific interfaces is if we implement multiple
> work interfaces. I don't like that approach though.
Is that not part of the nature of Java programming though?
Maybe not for one's own blocks, but it would be nice to ask a component what version of "Block"
does it implement. Even via AbstractBlock...
Under Ant control, all of this could be automated ... <filter> ... etc.
- PH
=====
Regards - Paul H
====
CVS -1, Perforce +1
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Interface Versions
Posted by Berin Loritsch <bl...@apache.org>.
Paul Hammant wrote:
>
> > Interface version numbers
>
> Great idea. Let's think twice about implementing it as a static final obj.... methods may be more
> cumbersome, but will have more long term flexibility. Also let's differentiate between the impl
> and the interface..
>
> Version getInterfaceVersionImplemented(String interfaceClassName);
> Version getImplementationVersion();
I would prefer:
Version getInterfaceVersion();
Version getComponentVersion(); // can be getImplementationVersion()
The interface version _always_ refers to the work interface. The only time
I think we need to worry about specific interfaces is if we implement multiple
work interfaces. I don't like that approach though.
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Interface Versions
Posted by Paul Hammant <pa...@yahoo.com>.
> Interface version numbers
Great idea. Let's think twice about implementing it as a static final obj.... methods may be more
cumbersome, but will have more long term flexibility. Also let's differentiate between the impl
and the interface..
Version getInterfaceVersionImplemented(String interfaceClassName);
Version getImplementationVersion();
- PH
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Interface Versions
Posted by Peter Donald <do...@apache.org>.
On Tue, 14 Aug 2001 00:04, Berin Loritsch wrote:
> I want to know if this will work:
>
> 1) Compile a Component against a Work interface with
> a static final Version object set to 1.0.0.
That should work! ;)
> 2) Run the Component in an environment where the interface
> is different (i.e. 1.0.1).
I think that should fail - however the reverse should be possible. (ie run a
1.0.1 in a 1.0.0 environment).
Remembering that a minor version does not make any binary incompatible
changes or any changes to semantics. (Just docco fixxes and added forward
compatible features).
> 3) Test the Component's interface version and get the one
> it was compiled against.
You mean something like MyWorker.VERSION - that should be workable.
> Is this in anyway possible? Or do we need to state the
> Version in every object that implements it?
Thats one way of doing it. Another is to actually implement proper
ClassLoaders that follow the jdk1.3 spec with respect to package dependencies
and version interfaces at package level.
--
Cheers,
Pete
*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof." *
* - John Kenneth Galbraith *
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org