You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Leo Sutic <le...@inspireinfrastructure.com> on 2004/02/25 10:26:28 UTC
Release status update
Just in case anyone was wondering:
+ All components build.
+ -component and -logger have a circular dependency.
+ -xmlutil builds, but fails almost all unit tests.
Will have to look into that before I can release anything -
I don't know if the JAR is correct or not with that
many failures.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Release status update
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wednesday 25 February 2004 17:26, Leo Sutic wrote:
> Just in case anyone was wondering:
>
> + All components build.
>
> + -component and -logger have a circular dependency.
>
> + -xmlutil builds, but fails almost all unit tests.
> Will have to look into that before I can release anything -
> I don't know if the JAR is correct or not with that
> many failures.
I couldn't compile most of it, so I have also spent time trying to put things
in order. It now compiles on my system.
"datasource and "xmlutil" still doesn't pass the testcases.
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Release status update
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wednesday 25 February 2004 17:26, Leo Sutic wrote:
> Just in case anyone was wondering:
>
> + All components build.
>
> + -component and -logger have a circular dependency.
>
> + -xmlutil builds, but fails almost all unit tests.
> Will have to look into that before I can release anything -
> I don't know if the JAR is correct or not with that
> many failures.
And I "may" have some typos committed during the massive edit over the last
few hours.
I hope you are patient enough if that's the case, and fixes it, as I have to
run out for the rest of the day...
Niclas
--
+---------//-------------------+
| 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
RE: Release status update, remove dependecy on AvalonLogger
Posted by David Gray <gr...@pcug.org.au>.
At 11:39 AM 26/02/2004 +0100, you wrote:
>The AvalonLogger class is absent from all commons-logging releases.
>
>I have notified commons-dev about this, and I suggest we cut this
>functionality out of FortressBean in order to just get on with the
>release.
Yes noticed this the other night, the code actually exists in CVS but not
in any of the 3 releases that I downloaded.
-----------------------------------------------------------------------
Is this the 5 minute argument or the full half-hour?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Release status update, remove dependecy on AvalonLogger
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Leo Simons
> Sent: den 26 februari 2004 15:14
> To: dev@avalon.apache.org
> Subject: Re: Release status update, remove dependecy on AvalonLogger
>
>
> Niclas Hedhman wrote:
> > On Thursday 26 February 2004 20:19, Leo Sutic wrote:
> >
> >>>From: Niclas Hedhman
> >>>Example; Saxon7, Java Mail, JSSE.
> >>
> >>A: Download 'em yourself.
> >>
> >>Yes, it is that bad.
> >
> > How are we going to explain that to Gump?
>
> download 'em yourself, and feed them to gump. For example:
>
> http://lsd.student.utwente.nl/gump/packages.html
>
> > IMHO, external resources that is not available in
> repository, should
> > be part
> > of CVS.
>
> some of these we can't distribute (javamail, jsse). I don't
> know what's
> the deal with saxon or why it is not in the ibiblio repo.
>
> >>You compile excalibur-component. Then you make a copy of
> the jar, and
> >>remove the excalibur.component classes from the first copy and the
> >>excalibur.testcase classes from the second. Then you rename
> the first
> >>excalibur-testcase and the second excalibur-component.
> >>
> >>Yes, it is that bad.
>
> I changed this as I tried to make excalibur fit the tool. Sorry on
> behalf of the tool.
>
> >>If we break out testcase to a separate project you get
> circular deps
> >>between component and testcase. Yes, it is that bad.
> >>
> >>I'm up for a "reduction of jars"-spree shortly after the release.
>
> I seem to recall having a single excalibur source tree a long
> time ago.
> I think it produced a single jar dubbed 'excalibur.jar'.
> Several years
> of fooling around with complex and failing builds later, that doesn't
> sound as bad as it did at the time ;)
The reason we split things up into multiple jars is because they
are developed independently and weren't released simultaneously.
For example, excalibur-pool would be ready for release with
important bugfixes, while excalibur-event would still be a mess
due to refactoring going on.
All we have to do is get the circular dependencies out, and
we should be good to go. This will involve some merging and
splitting of projects into -api and -impl jars. For example,
I think that the logger package can be split into -api and
-impl projects, while the -component and -testcase jars should
be merged.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Release status update, remove dependecy on AvalonLogger
Posted by Leo Simons <le...@apache.org>.
Niclas Hedhman wrote:
> On Thursday 26 February 2004 20:19, Leo Sutic wrote:
>
>>>From: Niclas Hedhman
>>>Example; Saxon7, Java Mail, JSSE.
>>
>>A: Download 'em yourself.
>>
>>Yes, it is that bad.
>
> How are we going to explain that to Gump?
download 'em yourself, and feed them to gump. For example:
http://lsd.student.utwente.nl/gump/packages.html
> IMHO, external resources that is not available in repository, should be part
> of CVS.
some of these we can't distribute (javamail, jsse). I don't know what's
the deal with saxon or why it is not in the ibiblio repo.
>>You compile excalibur-component. Then you make a copy of the jar,
>>and remove the excalibur.component classes from the first copy and
>>the excalibur.testcase classes from the second. Then you rename
>>the first excalibur-testcase and the second excalibur-component.
>>
>>Yes, it is that bad.
I changed this as I tried to make excalibur fit the tool. Sorry on
behalf of the tool.
>>If we break out testcase to a separate project you get circular
>>deps between component and testcase.
>>Yes, it is that bad.
>>
>>I'm up for a "reduction of jars"-spree shortly after the release.
I seem to recall having a single excalibur source tree a long time ago.
I think it produced a single jar dubbed 'excalibur.jar'. Several years
of fooling around with complex and failing builds later, that doesn't
sound as bad as it did at the time ;)
--
cheers,
- Leo Simons
-----------------------------------------------------------------------
Weblog -- http://leosimons.com/
IoC Component Glue -- http://jicarilla.org/
Articles & Opinions -- http://articles.leosimons.com/
-----------------------------------------------------------------------
"We started off trying to set up a small anarchist community, but
people wouldn't obey the rules."
-- Alan Bennett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Release status update, remove dependecy on AvalonLogger
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 26 February 2004 20:19, Leo Sutic wrote:
> > From: Niclas Hedhman
> > Example; Saxon7, Java Mail, JSSE.
>
> A: Download 'em yourself.
>
> Yes, it is that bad.
:o(
How are we going to explain that to Gump?
IMHO, external resources that is not available in repository, should be part
of CVS.
> You compile excalibur-component. Then you make a copy of the jar,
> and remove the excalibur.component classes from the first copy and
> the excalibur.testcase classes from the second. Then you rename
> the first excalibur-testcase and the second excalibur-component.
>
> Yes, it is that bad.
I have added a postGoal, that creates the excalibur-testcase jar.
The testcases are left in the original though.
> If we break out testcase to a separate project you get circular
> deps between component and testcase.
> Yes, it is that bad.
>
> I'm up for a "reduction of jars"-spree shortly after the release.
--
+---------//-------------------+
| 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
Re: Release status update, remove dependecy on AvalonLogger
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 26 February 2004 20:19, Leo Sutic wrote:
> If we break out testcase to a separate project you get circular
> deps between component and testcase.
There are a LOT of circular dependencies...
> I'm up for a "reduction of jars"-spree shortly after the release.
or something !
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Release status update, remove dependecy on AvalonLogger
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> From: Niclas Hedhman
>
> Q;
> There is a fair amount of dependencies to external components
> that are not
> available on ibiblio.org/maven.
> How is this intended to work then?
>
> Example; Saxon7, Java Mail, JSSE.
A: Download 'em yourself.
Yes, it is that bad.
> Q: excalibur-component/jars/excalibur-testcase-1.2.jar
A: From excalibur-component.
You compile excalibur-component. Then you make a copy of the jar,
and remove the excalibur.component classes from the first copy and
the excalibur.testcase classes from the second. Then you rename
the first excalibur-testcase and the second excalibur-component.
Yes, it is that bad.
This is caused by the fact that maven has "one project -> one jar".
If we break out testcase to a separate project you get circular
deps between component and testcase.
Yes, it is that bad.
I'm up for a "reduction of jars"-spree shortly after the release.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Release status update, remove dependecy on AvalonLogger
Posted by Niclas Hedhman <ni...@hedhman.org>.
Just go ahead without me, but I will spend some more time trying to get the
whole excalibur to build properly from scratch.
Q;
There is a fair amount of dependencies to external components that are not
available on ibiblio.org/maven.
How is this intended to work then?
Example; Saxon7, Java Mail, JSSE.
Cheers
Niclas
On Thursday 26 February 2004 19:29, Leo Sutic wrote:
> > From: Niclas Hedhman [mailto:niclas@hedhman.org]
> >
> > Get a lot of downloads can not be made.
>
> Probably my fault - I've updated the depndencies for
> the packages that are about to be released. You'll have
> to do
>
> maven jar:install
>
> on those dependencies yourself. For example, excalibur-logger,
> excalibur-component.
>
> I suggest give it another ten minutes, and if you haven't
> solved it, we release anyway. Remember, this code *is being
> used*, and it is working well enough.
>
> /LS
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
--
+---------//-------------------+
| 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
Re: Release status update, remove dependecy on AvalonLogger
Posted by Niclas Hedhman <ni...@hedhman.org>.
Where does this bugger supposed to be coming from?
excalibur-component/jars/excalibur-testcase-1.2.jar
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Release status update, remove dependecy on AvalonLogger
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> From: Niclas Hedhman [mailto:niclas@hedhman.org]
>
> Get a lot of downloads can not be made.
Probably my fault - I've updated the depndencies for
the packages that are about to be released. You'll have
to do
maven jar:install
on those dependencies yourself. For example, excalibur-logger,
excalibur-component.
I suggest give it another ten minutes, and if you haven't
solved it, we release anyway. Remember, this code *is being
used*, and it is working well enough.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Release status update, remove dependecy on AvalonLogger
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 26 February 2004 19:07, Leo Sutic wrote:
> Is this a DOM1/DOM2 issue, perhaps?
That's what I suspected too...
I am currently getting things in excalibur to build... :o(
Get a lot of downloads can not be made.
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Release status update, remove dependecy on AvalonLogger
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
Yeah, well, in a couple of ours I will xslt-transform that into a
NON-issue.
(I.e. ignore it and release anyway.)
/LS
(That's a NON1-issue, to be specific.)
> From: Niclas Hedhman [mailto:niclas@hedhman.org]
>
> On Thursday 26 February 2004 19:07, Leo Sutic wrote:
>
> > Is this a DOM1/DOM2 issue, perhaps?
>
> Maybe even a DOM2/DOM3 issue !!
>
> Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Release status update, remove dependecy on AvalonLogger
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 26 February 2004 19:07, Leo Sutic wrote:
> Is this a DOM1/DOM2 issue, perhaps?
Maybe even a DOM2/DOM3 issue !!
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Release status update, remove dependecy on AvalonLogger
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> -----Original Message-----
> From: Niclas Hedhman [mailto:niclas@hedhman.org]
> Sent: den 26 februari 2004 12:00
> To: Avalon Developers List
> Subject: Re: Release status update, remove dependecy on AvalonLogger
>
>
> On Thursday 26 February 2004 18:39, Leo Sutic wrote:
>
> > The AvalonLogger class is absent from all commons-logging releases.
> >
> > I have notified commons-dev about this, and I suggest we cut this
> > functionality out of FortressBean in order to just get on with the
> > release.
>
> +1
>
>
> > Finally, all tests for xmlutil pass except one:
> >
> > Testcase: testCreateDOMHandler took 0,281 sec
> > FAILED
> > Wrong namespace uri expected:<http://localhost/test> but was:<null>
> > junit.framework.ComparisonFailure: Wrong namespace uri
> > expected:<http://localhost/test> but was:<null>
> > at
> > org.apache.excalibur.xml.dom.test.DefaultDOMHandlerFactoryTestCase.
> > testCreateDOMHandler(DefaultDOMHandlerFactoryTestCase.java:63)
> >
> >
> > I have no idea what is causing this - can somebody please check?
>
> Will try.
Some points that I did figure out:
The parser reads the XML correctly - the SAX events being fed to the
DOMResult *do* contain namespace information. But there's something in
the
DOMResult that throws away the NS.
Is this a DOM1/DOM2 issue, perhaps?
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Release status update, remove dependecy on AvalonLogger
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 26 February 2004 18:39, Leo Sutic wrote:
> The AvalonLogger class is absent from all commons-logging releases.
>
> I have notified commons-dev about this, and I suggest we cut this
> functionality out of FortressBean in order to just get on with the
> release.
+1
> Finally, all tests for xmlutil pass except one:
>
> Testcase: testCreateDOMHandler took 0,281 sec
> FAILED
> Wrong namespace uri expected:<http://localhost/test> but was:<null>
> junit.framework.ComparisonFailure: Wrong namespace uri
> expected:<http://localhost/test> but was:<null>
> at
> org.apache.excalibur.xml.dom.test.DefaultDOMHandlerFactoryTestCase.
> testCreateDOMHandler(DefaultDOMHandlerFactoryTestCase.java:63)
>
>
> I have no idea what is causing this - can somebody please check?
Will try.
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Release status update, remove dependecy on AvalonLogger
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>
> Leo Sutic wrote:
> >
> > Just in case anyone was wondering:
> >
> > + All components build.
> >
> Great!
Spoke too soon. Seems like I missed to check fortress-tools.
C:\Home\leo\Private\Apache\avalon\fortress\tools\src\java\org\apache\ava
lon\fort
ress\tools\FortressBean.java:34: cannot resolve symbol
symbol : class AvalonLogger
location: package impl
import org.apache.commons.logging.impl.AvalonLogger;
^
C:\Home\leo\Private\Apache\avalon\fortress\tools\src\java\org\apache\ava
lon\fort
ress\tools\FortressBean.java:86: cannot resolve symbol
symbol : variable AvalonLogger
location: class org.apache.avalon.fortress.tools.FortressBean
AvalonLogger.setDefaultLogger(cm.getLogger());
The AvalonLogger class is absent from all commons-logging releases.
I have notified commons-dev about this, and I suggest we cut this
functionality out of FortressBean in order to just get on with the
release.
Finally, all tests for xmlutil pass except one:
Testcase: testCreateDOMHandler took 0,281 sec
FAILED
Wrong namespace uri expected:<http://localhost/test> but was:<null>
junit.framework.ComparisonFailure: Wrong namespace uri
expected:<http://localhost/test> but was:<null>
at
org.apache.excalibur.xml.dom.test.DefaultDOMHandlerFactoryTestCase.
testCreateDOMHandler(DefaultDOMHandlerFactoryTestCase.java:63)
I have no idea what is causing this - can somebody please check?
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Release status update
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Leo Sutic wrote:
>
> Just in case anyone was wondering:
>
> + All components build.
>
Great!
> + -component and -logger have a circular dependency.
:( Now, I think after the release we have to think about the
logger package anyway, especially with the new avalon logging
package.
>
> + -xmlutil builds, but fails almost all unit tests.
> Will have to look into that before I can release anything -
> I don't know if the JAR is correct or not with that
> many failures.
>
Don't know. If you want I can take a look at the tests at the
weekend.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org