Yes I am interested too in how to organize MyFaces in
Eclipse.
The build.xml seems to be too complexe to be used for
import in Eclipse.
--- Martin Bosak [EMAIL PROTECTED] wrote:
For those of you who use Eclipse:
How do you organize your MyFaces workspace?
Do you set up one big project
[
http://issues.apache.org/jira/browse/MYFACES-177?page=comments#action_63795 ]
Josh Holtzman commented on MYFACES-177:
---
Upon closer inspection, the value percent is indeed what is defined in the
JSF 1.1 spec. The API documentation on sun's
[
http://issues.apache.org/jira/browse/MYFACES-213?page=comments#action_63804 ]
Brandon Goodin commented on MYFACES-213:
Is this going to marked as a bug? It is definetly not working for me. I'm just
curious if any MyFaces developers can
Never mind. I was confused. I saw the change in my cvs email but
hadn't actually updated yet. I now see that you were fixing a problem
and I just fixed it again (and caused a conflict.) I'm all straight
now.
sean
On 4/26/05, Sean Schofield [EMAIL PROTECTED] wrote:
Grant,
Is there a
[
http://issues.apache.org/jira/browse/MYFACES-92?page=comments#action_63813 ]
sean schofield commented on MYFACES-92:
---
I am unable to get this working. I have fixed MyFaces-197 and used the changes
you sent me offlist (which were essentially
Sean,
Please don't revert the change. the file named ${sign.script} was
probably there from when you ran the build before I made my change. My
change FIXES the problem you describe.
The line:
property file="sign.script" location="${release.dir}/sign.sh"/
is definitely invalid. it MUST be:
Right. See my follow up email where I realized my mistake ;-)
On 4/26/05, Grant Smith [EMAIL PROTECTED] wrote:
Sean,
Please don't revert the change. the file named ${sign.script} was probably
there from when you ran the build before I made my change. My change FIXES
the problem you
Are there any guidelines for documentation we should be following ?
I would like to improve our documentation; the extended components in
particular. Should everything be done through Forrest ?
Thanks,
Grant.
2005/4/26, Grant Smith [EMAIL PROTECTED]:
Are there any guidelines for documentation we should be following ?
I would like to improve our documentation; the extended components in
particular. Should everything be done through Forrest ?
Yes, please.
We could also try to enable the pdf
[ http://issues.apache.org/jira/browse/MYFACES-197?page=all ]
sean schofield resolved MYFACES-197:
Resolution: Fixed
Fix Version: Nightly Build
Thanks to Marty Bosak for finding and fixing this one.
TLDDocs Index page only has WAP tags
I have some experience with the PDF generation of javadoc. I can look
into that. As for website documentation we are using forrest see
src/documentation/content. We do have a template for component
documentation. In the components folder you can make a copy of
component-template.xml and fill
[
http://issues.apache.org/jira/browse/MYFACES-177?page=comments#action_63820 ]
Ray Davis commented on MYFACES-177:
---
I've just submitted a bug report on the JSF 1.1 tlddocs to Sun.
NumberConverter expects percent rather than percentage in type
[
http://issues.apache.org/jira/browse/MYFACES-213?page=comments#action_63826 ]
Rob Decker commented on MYFACES-213:
Try moving the value attribute out of the commandLink and make it an outputText
child instead. I think the bug is that when a
Sean,
The original build/foo/build.xml files did some processing based on the
value of the
tomcat.pre.5.5.version
property.
Is this not required anymore ? I noticed that your build-webapps.xml
ignores it.
+1 on the idea of having deploy-webapps.xml some kind of
cactus-tests.xml and
[
http://issues.apache.org/jira/browse/MYFACES-213?page=comments#action_63868 ]
Brandon Goodin commented on MYFACES-213:
Nope that does not work either. I tried ever combo of the x: and h: tags along
with request and session of the managed
15 matches
Mail list logo
