Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
+1, although I'm not developer... On Tue, Apr 24, 2012 at 12:08 PM, Karl Wright wrote: > Please vote +1 if you think we should propose to the Incubator that we > graduate as a top level project at this time. > > If this vote passes, I will open a [DISCUSS] thread in > gene...@incubator.apache.org, and turn it into a [VOTE] thread if the > discussion looks positive. > > +1(binding) from me. > > Karl -- With best wishes, Alex Ott http://alexott.net/ Tiwtter: alexott_en (English), alexott (Russian) Skype: alex.ott
Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
+1 Cheers, Tommaso 2012/4/25 Jukka Zitting > Hi, > > On Tue, Apr 24, 2012 at 12:08 PM, Karl Wright wrote: > > Please vote +1 if you think we should propose to the Incubator that we > > graduate as a top level project at this time. > > +1 > > BR, > > Jukka Zitting >
[jira] [Commented] (CONNECTORS-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261687#comment-13261687 ] Erlend Garåsen commented on CONNECTORS-467: --- It seems that we need to go for the first option instead in order to keep JSP 1.x compatibility. Since the tag libraries in JSTL 1.2 have new URIs (e.g. http://java.sun.com/jsp/jstl/core), web containers will probably assume the new URIs unless the old ones are specified. I have placed the directives inside a directive and tested MCF on Resin 4.0.19, Tomcat 7.0.6 and Jetty 7.5.4 without any problems. If there are no comments, I will commit my changes tomorrow. > Remove outdated taglib directives in web.xml > > > Key: CONNECTORS-467 > URL: https://issues.apache.org/jira/browse/CONNECTORS-467 > Project: ManifoldCF > Issue Type: Bug > Components: Framework core >Affects Versions: ManifoldCF 0.5 >Reporter: Erlend Garåsen >Assignee: Erlend Garåsen > Fix For: ManifoldCF 0.6 > > > Resin does not accept the web.xml file which belongs to the web-crawler-ui > application and returns 500 Server error after deployment. Resin complains > about an unexpected -tag. The taglib directive is not longer needed > in JSP 2.0 which we're now using. Some information about how we can configure > MCF properly for JSP 2.0: > http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml > It's probably possible to place the taglib directives inside a > directive as a quick fix as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
Hi, On Tue, Apr 24, 2012 at 12:08 PM, Karl Wright wrote: > Please vote +1 if you think we should propose to the Incubator that we > graduate as a top level project at this time. +1 BR, Jukka Zitting
[jira] [Commented] (CONNECTORS-468) Using ResourceBundle under Velocity has unhelpful behavior when a key is missing
[ https://issues.apache.org/jira/browse/CONNECTORS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261595#comment-13261595 ] Karl Wright commented on CONNECTORS-468: r1330240. Forgot to add the darned file to svn. > Using ResourceBundle under Velocity has unhelpful behavior when a key is > missing > > > Key: CONNECTORS-468 > URL: https://issues.apache.org/jira/browse/CONNECTORS-468 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework core >Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.6 > > > When you use ResourceBundle.getString in a Velocity template, the behavior > for a missing key is to throw an exception - which causes the template to not > render and an exception to be printed in the log. It would be much better if > the behavior was more similar to Messages.getString. We can do this by > wrapping ResourceBundle and using the wrapped class in the context instead of > ResourceBundle itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-468) Using ResourceBundle under Velocity has unhelpful behavior when a key is missing
[
https://issues.apache.org/jira/browse/CONNECTORS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261429#comment-13261429
]
Erlend Garåsen commented on CONNECTORS-468:
---
I'm afraid that this change have some unwanted side effects. I just did a clean
svn co after i upgraded to SVN 1.7, and now I get the following error:
{code}
[javac] Compiling 8 source files to
/Users/erlendfg/tmp/mcf_2012/framework/build/ui-core/classes
[javac]
/Users/erlendfg/tmp/mcf_2012/framework/ui-core/src/main/java/org/apache/manifoldcf/ui/i18n/Messages.java:142:
cannot find symbol
[javac] symbol : class ResourceBundleWrapper
[javac] location: class org.apache.manifoldcf.ui.i18n.Messages
[javac] context.put("ResourceBundle",new
ResourceBundleWrapper(rb,bundleName,locale));
{code}
> Using ResourceBundle under Velocity has unhelpful behavior when a key is
> missing
>
>
> Key: CONNECTORS-468
> URL: https://issues.apache.org/jira/browse/CONNECTORS-468
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Framework core
>Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
>Reporter: Karl Wright
>Assignee: Karl Wright
> Fix For: ManifoldCF 0.6
>
>
> When you use ResourceBundle.getString in a Velocity template, the behavior
> for a missing key is to throw an exception - which causes the template to not
> render and an exception to be printed in the log. It would be much better if
> the behavior was more similar to Messages.getString. We can do this by
> wrapping ResourceBundle and using the wrapped class in the context instead of
> ResourceBundle itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
