Re: Thoughts on graduation?
Hi Karl 2012/4/23 Karl Wright daddy...@gmail.com Hi Tommaso, I didn't see anything in the checklist we hadn't done. Indeed, for some things (like the name) we've done it more than once. Do you think we're missing anything? Do you think the incubator page is sufficiently up to date as well? Looked reasonable to me... same here, just I wanted to remind us to have a look in order to double check, I think we're fine. Are we agreed that ManifoldCF would graduate as a TLP at this time? The Lucene PMC dropped us some two years ago so it would be appropriate, I think. +1 just since that needs to be explicitly figured out we need that at least the PPMC is aware and happy with that. Tommaso Karl On Mon, Apr 23, 2012 at 8:05 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: Hi Karl, I think times are mature for talking about graduation, it may be helpful to explicitly get through the graduation requirements [1][2] and open a [DISCUSSION] thread before start voting to check everyone is happy with it and also, for example, to choose the right target (TLP or subproject). However I'm confident we can graduate soon. Tommaso [1] : http://incubator.apache.org/guides/graduation.html [2] : http://incubator.apache.org/guides/graduation.html#checklist 2012/4/23 Karl Wright daddy...@gmail.com It may be a little too soon after the last (somewhat traumatic) release, but I'm thinking we've pretty well met the diversity requirement now for graduation. Should we open a graduation vote in the incubator at this time? Karl
[jira] [Commented] (CONNECTORS-467) MCF version 0.5 does not run on Resin
[
https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260373#comment-13260373
]
Erlend Garåsen commented on CONNECTORS-467:
---
bq. Alternatively, if there is a way to do the same thing without wrecking JSP
1.x compatibility, then we can just fix this.
JSP 1.2 TLD files, to which the path is referenced in our web.xml, should be
upward compatible. There should be no need to change them in order to be
compatible with JSP 2.0. Some web containers, such as Resin, complains because
we are now pointing to an XSD which does not have any reference to a taglib
alement:
{code}
http://java.sun.com/xml.ns/javaee/web-app_2_5.xsd; version=2.5
{code}
We have two options:
1. Place the taglib directives inside a jsp-config directive.
2. Just remove the taglibs directives. JSP containers should automatically look
for TLD files in all subfolders of app/WEB-INF which is the case for MCF
(they are placed inside the subfolder jsp).
I think we should go for the last option. I can try to deploy the application
on both Resin and Tomcat in order to test whether it works as expected. Do you
think we should open a vote thread for these two options mentioned above?
MCF version 0.5 does not run on Resin
-
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 taglib-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 jsp-config
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
[jira] [Commented] (CONNECTORS-467) MCF version 0.5 does not run on Resin
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260385#comment-13260385 ] Karl Wright commented on CONNECTORS-467: You would only need to open a vote thread if you are removing an option or destroying backwards compatibility. So please just go ahead with (2). MCF version 0.5 does not run on Resin - 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 taglib-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 jsp-config 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
[VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
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
Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
big +1 from me :) Piergiorgio Il giorno 24 aprile 2012 12:08, Karl Wright daddy...@gmail.com ha scritto: 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 -- Piergiorgio Lucidi http://www.open4dev.com
Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
+1 from me. On Tue, Apr 24, 2012 at 3:13 PM, Piergiorgio Lucidi piergior...@apache.org wrote: big +1 from me :) Piergiorgio Il giorno 24 aprile 2012 12:08, Karl Wright daddy...@gmail.com ha scritto: 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 -- Piergiorgio Lucidi http://www.open4dev.com -- -- Feroz Zahid
[jira] [Created] (CONNECTORS-468) Using ResourceBundle under Velocity has unhelpful behavior when a key is missing
Karl Wright created CONNECTORS-468: -- Summary: 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
Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
+1 Erlend On 24.04.12 12.08, 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 -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Build fails with Maven while building MCF from trunk
On 12.04.12 23.46, Karl Wright wrote: The build process has changed. The incubator required we remove all binaries. You will need to do one of the following: (a) Download the -lib package from the release candidate and follow the instructions I tried to place all the jars from the lib distribution into a lib folder in my working trunk version. I tried to follow the instructions in the README file. What exactly is the corresponding lib distribution if you work with trunk? The latest 0.5 release? Here's what I did: 1. Downloaded apache-manifoldcf-0.5-incubating-lib.tar.gz and unpacked it 2. Created a lib directory in the project root and copied all jars from the lib distribution into that directory 3. ran ant build (nothing really happens) 4. Tried ant make-deps followed by ant build. I guess there is one detail I have missed. Your suggestions work perfectly if I download the corresponding source package, but not with the latest version from trunk. Erlend (b) Make sure you have svn 1.7 installed and run ant make-core-deps It's not straight forward to upgrade SVN to version 1.7 on OS X. Fink is the most common tool for installing/upgrading SVN, but the current/stable version is 1.6.17-4: http://pdb.finkproject.org/pdb/package.php/svn If I _should_ use SVN 1.7, I can try to install it from MacPorts. Erlend -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Build fails with Maven while building MCF from trunk
Trunk is now built using different jars because we've gone to jdk 1.6. On trunk there is no -lib distribution you can download; you must build it: ant clean-core-deps make-core-deps Thanks, Karl On Tue, Apr 24, 2012 at 3:13 PM, Erlend Garåsen e.f.gara...@usit.uio.no wrote: On 12.04.12 23.46, Karl Wright wrote: The build process has changed. The incubator required we remove all binaries. You will need to do one of the following: (a) Download the -lib package from the release candidate and follow the instructions I tried to place all the jars from the lib distribution into a lib folder in my working trunk version. I tried to follow the instructions in the README file. What exactly is the corresponding lib distribution if you work with trunk? The latest 0.5 release? Here's what I did: 1. Downloaded apache-manifoldcf-0.5-incubating-lib.tar.gz and unpacked it 2. Created a lib directory in the project root and copied all jars from the lib distribution into that directory 3. ran ant build (nothing really happens) 4. Tried ant make-deps followed by ant build. I guess there is one detail I have missed. Your suggestions work perfectly if I download the corresponding source package, but not with the latest version from trunk. Erlend (b) Make sure you have svn 1.7 installed and run ant make-core-deps It's not straight forward to upgrade SVN to version 1.7 on OS X. Fink is the most common tool for installing/upgrading SVN, but the current/stable version is 1.6.17-4: http://pdb.finkproject.org/pdb/package.php/svn If I _should_ use SVN 1.7, I can try to install it from MacPorts. Erlend -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Build fails with Maven while building MCF from trunk
On 24.04.12 21.16, Karl Wright wrote: ant clean-core-deps make-core-deps OK, SVN 1.7 is required. I can try to install it from MacPorts. patch-source-via-svn: [exec] Unknown command: 'patch' [exec] Type 'svn help' for usage. BUILD FAILED -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
[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-tabpanelfocusedCommentId=13260867#comment-13260867 ] Karl Wright commented on CONNECTORS-468: r1329957 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] [Resolved] (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:all-tabpanel ] Karl Wright resolved CONNECTORS-468. Resolution: Fixed 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
Re: [VOTE] Propose graduation of ManifoldCF from the Incubator as a Top Level Project
+1 from me. Shinichiro Abe On 2012/04/24, at 19:08, 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
