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 2003/02/08 12:57:05 UTC
[LOGKIT] dist target failure
Having problems building the dist target for logkit:
1. javadoc errors due to the fact that the compat sources are not
included in the target
2. an error generating the announcement target
3. javadoc warning under a 1.4 build because of a ?? in a method
description
Also, (4) no manifest is defined. I've fixed 1,3 and 4 but I'm somewhat
stumped on (2).
Pending resolution of (2). Due to the fact that there is a RC6 in
evaluation/vote - I didn't want to commit these changes without checking
first. So, does anyone have any objections to me updating the build to
include the manifest declaration and javadoc fix?
Cheers, Steve.
announcement:
[copy] Copying 14 files to
F:\dev\avalon-logkit\build\documentation\xdocs
[style] Processing
F:\dev\avalon-logkit\build\documentation\xdocs\announcement.xml to
F:\dev\avalon-logkit\Announcement.txt
[style] Loading stylesheet F:\dev\avalon\tools\announcement2txt.xsl
[style] Processing
F:\dev\avalon-logkit\build\documentation\xdocs\announcement.xml to
F:\dev\avalon-logkit\distributions\HEADER.html
[style] Loading stylesheet F:\dev\avalon\tools\announcement2header.xsl
[style] Processing
F:\dev\avalon-logkit\build\documentation\xdocs\announcement.xml to
F:\dev\avalon-logkit\distributions\README.html
[style] Loading stylesheet F:\dev\avalon\tools\announcement2readme.xsl
[style] Processing
F:\dev\avalon-logkit\build\documentation\xdocs\announcement.xml to
F:\dev\avalon-logkit\jakarta-news.xml
[style] Loading stylesheet F:\dev\avalon\tools\announcement2site.xsl
[style] java.lang.reflect.InvocationTargetException
[style] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[style] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[style] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[style] at java.lang.reflect.Method.invoke(Method.java:324)
[style] at
org.apache.xalan.extensions.ExtensionHandlerGeneral.<init>(ExtensionHandlerGeneral.java:289)
[style] at
org.apache.xalan.templates.ElemExtensionDecl.runtimeInit(ElemExtensionDecl.java:330)
[style] at
org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1159)
[style] at
org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:638)
[style] at
org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1088)
[style] at
org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1066)
[style] at
org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:188)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:506)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:220)
[style] at org.apache.tools.ant.Task.perform(Task.java:317)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at org.apache.tools.ant.Target.performTasks(Target.java:334)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[style] at
org.apache.tools.ant.Project.executeTargets(Project.java:1250)
[style] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[style] at org.apache.tools.ant.Main.start(Main.java:196)
[style] at org.apache.tools.ant.Main.main(Main.java:235)
[style] Caused by: com.ibm.bsf.BSFException: unable to load
language: javascript
[style] at
com.ibm.bsf.BSFManager.loadScriptingEngine(BSFManager.java:324)
[style] ... 21 more
[style] : Fatal Error! Could not compile extension Cause:
java.lang.reflect.InvocationTargetException
[style] Failed to process
F:\dev\avalon-logkit\build\documentation\xdocs\announcement.xml
BUILD FAILED
--
Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [LOGKIT] dist target failure
Posted by Stephen McConnell <mc...@apache.org>.
Berin Loritsch wrote:
> Stephen McConnell wrote:
>
>>
>>
>> Berin Loritsch wrote:
>>
>>> Stephen McConnell wrote:
>>>
>>>>
>>>> Having problems building the dist target for logkit:
>>>>
>>>> 1. javadoc errors due to the fact that the compat sources are not
>>>> included in the target
>>>
>>>
>>>
>>>
>>> It doesn't prevent you from building the dist.
>>
>>
>>
>>
>> It means that te documentation provided with the release does not
>> include any of the depricated classes.
>
>
> Good. If people don't know about them, they won't use them.
So lets ignore the fact that deprecation is a statement that something
is GOING AWAY and pretend that this is a statement that something has
GONE AWAY therefore because is GONE we don't need to tell the user
anything. Yep - sounds good to me - treat them like idiots and they will
probably come back for more!
ROTFL
>
>
>>>> 3. javadoc warning under a 1.4 build because of a ?? in a method
>>>> description
>>>
>>>
>>>
>>>
>>> Again, it does not prevent us from building the dist.
>>
>>
>>
>>
>> True - but is this a satisfactory level of quality for a
>> distribution? If this was the only issue - I would pass - but I
>> happen to think that the missing javadoc and manifest issues are
>> sufficient to require a RC7.
>
>
> It's not like its not already been released like that. What I don't
> want to see, and what I get the feeling I will see is I make an RC7
> and then there are a few "niggling" more points that you won't budge on.
>
> We have bigger fish to fry, let's catch them.
Go fishing - its the after effect that pissing me off.
That standard answer is do a 1.2.1 - i.e. "its not my problem because
I'm in a hurry".
Is that the approach we are going to take for the entire ACR?
>>
>> You are obviously not leveraging extension management. Non-inclusion
>> of a manifest detailing an extension name, version and implementation
>> version means that users *must* declare the jar in a classpath and
>> cannot leverage extension mechanisms in containers such a Tomcat,
>> Merlin, Phoenix, etc. These declarations are included
>> across-the-board in the framework, excalibur, sandbox, and
>> cornerstone jars. Getting this in place in LogKit is fixing an
>> oversight that is well and truly overdue.
>
>
> What does it *really* buy you? You are right, I am not leveraging
> extension management. 90% of the people out there won't know what
> it *really* buys them. The skip it. Esp. when you have very popular
> IDEs like JBuilder, etc. which do not directly support their generation.
All good reasons why you don't need this.
:-)
>
>>> Is this something that would prevent LogKit from working properly?
>>
>>
>> It will not prevent logkit from working properly but it does
>> complicate matters if a user is building jar files that declare
>> extension depedecies on other jar files. Without the manifest logkit
>> cannot participate as a shareable extension and must be explicity
>> included in a classpath.
>
>
> All that's hidden by the o.a.a.f.logger.LogEnabled interface anyway.
> It's not that big a deal. If any component has an explicit dependency
> on LogKit as opposed to Framework, it is broken IMO.
LogKit is a product that can be used independently of the framework
irrespective of your opinion. Such an application is NOT broken. Its
simply an application using content that we are providing! Ok, so you
personally don't see any benefit in doing things that make the life of
users easier - that's ok - but at least stay away from unfounded
opinions - after all - we don't want to misslead anyone do we!
Oh well - I guess its a pattern - we stuffed up a earlier release of
LogKit because we left out some adapters. We stuffed up an earlier
release of framework because we left out an entire package. Gee - we
can stuff up this release by leaving leaving out the really important
information about what is changing. But at least we are consistent!
;-)
Cheers, Steve.
--
Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [LOGKIT] dist target failure
Posted by Berin Loritsch <bl...@apache.org>.
Stephen McConnell wrote:
>
>
> Berin Loritsch wrote:
>
>> Stephen McConnell wrote:
>>
>>>
>>> Having problems building the dist target for logkit:
>>>
>>> 1. javadoc errors due to the fact that the compat sources are not
>>> included in the target
>>
>>
>>
>> It doesn't prevent you from building the dist.
>
>
>
> It means that te documentation provided with the release does not
> include any of the depricated classes.
Good. If people don't know about them, they won't use them.
>>> 3. javadoc warning under a 1.4 build because of a ?? in a method
>>> description
>>
>>
>>
>> Again, it does not prevent us from building the dist.
>
>
>
> True - but is this a satisfactory level of quality for a distribution?
> If this was the only issue - I would pass - but I happen to think that
> the missing javadoc and manifest issues are sufficient to require a RC7.
It's not like its not already been released like that. What I don't
want to see, and what I get the feeling I will see is I make an RC7
and then there are a few "niggling" more points that you won't budge on.
We have bigger fish to fry, let's catch them.
>
> You are obviously not leveraging extension management. Non-inclusion of
> a manifest detailing an extension name, version and implementation
> version means that users *must* declare the jar in a classpath and
> cannot leverage extension mechanisms in containers such a Tomcat,
> Merlin, Phoenix, etc. These declarations are included across-the-board
> in the framework, excalibur, sandbox, and cornerstone jars. Getting this
> in place in LogKit is fixing an oversight that is well and truly overdue.
What does it *really* buy you? You are right, I am not leveraging
extension management. 90% of the people out there won't know what
it *really* buys them. The skip it. Esp. when you have very popular
IDEs like JBuilder, etc. which do not directly support their generation.
>> Is this something that would prevent LogKit from working properly?
>
> It will not prevent logkit from working properly but it does complicate
> matters if a user is building jar files that declare extension
> depedecies on other jar files. Without the manifest logkit cannot
> participate as a shareable extension and must be explicity included in a
> classpath.
All that's hidden by the o.a.a.f.logger.LogEnabled interface anyway.
It's not that big a deal. If any component has an explicit dependency
on LogKit as opposed to Framework, it is broken IMO.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [LOGKIT] dist target failure
Posted by Stephen McConnell <mc...@apache.org>.
Berin Loritsch wrote:
> Stephen McConnell wrote:
>
>>
>> Having problems building the dist target for logkit:
>>
>> 1. javadoc errors due to the fact that the compat sources are not
>> included in the target
>
>
> It doesn't prevent you from building the dist.
It means that te documentation provided with the release does not
include any of the depricated classes.
>
>> 2. an error generating the announcement target
>
>
> You need BSF.jar and Rhino.jar along with and XML parser and an
> XSLT processor (i.e. Xerces/Xalan).
So in principal this could be updated in the build with a conditional if
everything present then do announcement target otherwise skip it -
bottom line it does not effect the release so I'm not too bugged by this
point.
>> 3. javadoc warning under a 1.4 build because of a ?? in a method
>> description
>
>
> Again, it does not prevent us from building the dist.
True - but is this a satisfactory level of quality for a distribution?
If this was the only issue - I would pass - but I happen to think that
the missing javadoc and manifest issues are sufficient to require a RC7.
>
>> Also, (4) no manifest is defined. I've fixed 1,3 and 4 but I'm
>> somewhat stumped on (2).
>
>
> Include the proper libraries and we should be good.
You are obviously not leveraging extension management. Non-inclusion of
a manifest detailing an extension name, version and implementation
version means that users *must* declare the jar in a classpath and
cannot leverage extension mechanisms in containers such a Tomcat,
Merlin, Phoenix, etc. These declarations are included across-the-board
in the framework, excalibur, sandbox, and cornerstone jars. Getting this
in place in LogKit is fixing an oversight that is well and truly overdue.
>
>> Pending resolution of (2). Due to the fact that there is a RC6 in
>> evaluation/vote - I didn't want to commit these changes without
>> checking first. So, does anyone have any objections to me updating
>> the build to include the manifest declaration and javadoc fix?
>
>
> Is this something that would prevent LogKit from working properly?
It will not prevent logkit from working properly but it does complicate
matters if a user is building jar files that declare extension
depedecies on other jar files. Without the manifest logkit cannot
participate as a shareable extension and must be explicity included in a
classpath.
>
> Let's wait until we have a release.
Lets' do a release that we don't need to update.
Cheers, Steve.
--
Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [LOGKIT] dist target failure
Posted by Berin Loritsch <bl...@apache.org>.
Stephen McConnell wrote:
>
> Having problems building the dist target for logkit:
>
> 1. javadoc errors due to the fact that the compat sources are not
> included in the target
It doesn't prevent you from building the dist.
> 2. an error generating the announcement target
You need BSF.jar and Rhino.jar along with and XML parser and an
XSLT processor (i.e. Xerces/Xalan).
> 3. javadoc warning under a 1.4 build because of a ?? in a method
> description
Again, it does not prevent us from building the dist.
> Also, (4) no manifest is defined. I've fixed 1,3 and 4 but I'm somewhat
> stumped on (2).
Include the proper libraries and we should be good.
> Pending resolution of (2). Due to the fact that there is a RC6 in
> evaluation/vote - I didn't want to commit these changes without checking
> first. So, does anyone have any objections to me updating the build to
> include the manifest declaration and javadoc fix?
Is this something that would prevent LogKit from working properly?
Let's wait until we have a release. We should be considering LogKit
under code freeze.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org