-
1. Re: Third-party dependencies in non-maven based projects
bleathem Nov 15, 2011 4:26 PM (in response to lfryc)Thanks for following up with this Lukas.
Without specifying those dependencies, the section: Creating a project with JBoss tools section is incorrect. I feel they should be added, to fully document what is required to start a new RichFaces project.
The alternative is to remove the section altogether, which I don't think is a better solution.
-
2. Re: Third-party dependencies in non-maven based projects
lfryc Nov 16, 2011 11:32 AM (in response to bleathem)The question is if we should add only mandatory dependencies, or optional too and if it's necessary to add dependencies for servlet containers (as oppose to application servers).
Also I feel there are several possible solutions to obtain these deps:
- provide link to upstream project
- provide link to Nexus repo
- provide only name of the project
-
3. Re: Third-party dependencies in non-maven based projects
bleathem Nov 16, 2011 12:30 PM (in response to lfryc)Let's specify all dependencies, indicating which ones are optional, but for which features they are required. Listing the deps is sufficient IMO, we don't need to link to urls - the urls may change.
We also have the wiki pages that provide real links, maybe we can add a note recommending to check the wiki for the latest information.
-
4. Re: Third-party dependencies in non-maven based projects
lfryc Nov 17, 2011 12:40 PM (in response to bleathem)Created a doc issue to cover this one: https://issues.jboss.org/browse/RFPL-1857
-
5. Re: Third-party dependencies in non-maven based projects
yiyuan Nov 25, 2011 12:07 AM (in response to lfryc) -
6. Re: Third-party dependencies in non-maven based projects
lfryc Nov 25, 2011 4:32 PM (in response to yiyuan)Hi yiyuan,
your topic is completely different from initial discussion. :-)
To satisfy your curiosity, you should be able to use <rich:fileUpload onclear=""> or appropriate <f:ajax event="clear" ... />.