[
https://issues.apache.org/jira/browse/EXTSCRIPT-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858330#action_12858330
]
Werner Punz commented on EXTSCRIPT-115:
---------------------------------------
Afair this is a jetty related issue, I did some testing regarding restarting a
while ago and it worked on Tomcat, but I might have broken something again.
Nevertheless I cannot even restart myfaces in a jetty environment here with my
testing examples, I do not even reach the NPE :-)
But seriously, I will do another round of testing in this area and will post
about the results.
It probably is better to simply restart jetty if you do a dependency update,
since you can cover most other changes with ext-scripting I guess this is
bearable.
> Better logging when developer specifies a non existent source directory
> -----------------------------------------------------------------------
>
> Key: EXTSCRIPT-115
> URL: https://issues.apache.org/jira/browse/EXTSCRIPT-115
> Project: MyFaces Extensions Scripting
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0-Beta-2
> Reporter: Jan-Kees van Andel
> Assignee: Werner Punz
>
> When I make a typo in a source directory, like:
> D:/dev/work/idea9/parleys/web-html5/src/main/jav (notice the missing 'a' at
> the end)
> I don't get a message suggesting I made an error, but ExtScript fails
> silently by not reloading the classes in this directory.
> There is a javac message in the log:
> INFO: [EXT-SCRITPING] starting class dependency scan
> 18-apr-2010 16:53:24
> org.apache.myfaces.extensions.scripting.loaders.java.jsr199.JSR199Compiler
> compile
> INFO: [EXT-SCRIPTING] Doing a full recompile
> javacTask: no source files
> Usage: javacTask <options> <source files>
> use -help for a list of possible options
> But it's easy to miss it because MyFaces and other frameworks also emit a lot
> of logging. Something heavier (ERROR level or maybe an initializer exception)
> might be better, so the user won't get confused/angry.
> I think such a check is even more appropriate because file paths in Java are
> always error-prone (I always make mistakes with paths)...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
