I know I will open a can of works with this discussion here.
Given I toyed around with the Jetbrains ai a little bit, what is the
general opinion on using ai to generate comments.
I am aware that using ai for generating standard code is mostly a no go
because of unresolved copyright issues where
henningn merged pull request #753:
URL: https://github.com/apache/myfaces-tobago/pull/753
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service,
henningn opened a new pull request #753:
URL: https://github.com/apache/myfaces-tobago/pull/753
Some xhtmls contain the old apiController.base reference.
This is now replaced.
Issue: TOBAGO-2070
--
This is an automated message from the Apache Git Service.
To respond to the
bohmber merged pull request #320:
URL: https://github.com/apache/myfaces-tobago/pull/320
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
bohmber opened a new pull request #320:
URL: https://github.com/apache/myfaces-tobago/pull/320
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
bohmber merged pull request #317:
URL: https://github.com/apache/myfaces-tobago/pull/317
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
bohmber opened a new pull request #317:
URL: https://github.com/apache/myfaces-tobago/pull/317
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
://builds.apache.org/job/Tobago%20Trunk/1364/])
TOBAGO-1889: Rearrange the documentation into the demo application (lofwyr: rev
f0af1beeb537b5cbbc5603da41961dfd85e4134b)
* (edit) src/site/apt/howto-test.apt
* (edit) src/site/apt/getting-started.apt
* (add)
tobago-example/tobago-example-demo/src/main
Udo Schnurpfeil created TOBAGO-1889:
---
Summary: Rearrange the documentation into the demo application
Key: TOBAGO-1889
URL: https://issues.apache.org/jira/browse/TOBAGO-1889
Project: MyFaces Tobago
tag library documentation
> --
>
> Key: TOBAGO-1829
> URL: https://issues.apache.org/jira/browse/TOBAGO-1829
> Project: MyFaces Tobago
> Issue Type: Improvement
>
/taglib/component/SheetTagDeclaration.java
> Put description for markups into the tag library documentation
> --
>
> Key: TOBAGO-1829
> URL: https://issues.apache.org/jira/browse/TOBAGO-1829
>
Henning Noeth created TOBAGO-1829:
-
Summary: Put description for markups into the tag library
documentation
Key: TOBAGO-1829
URL: https://issues.apache.org/jira/browse/TOBAGO-1829
Project: MyFaces
:
---
[~mkienenb] Would you please check my wiki role? I would like to change it but
AFAICS i have no edit role.
was (Author: tandraschko):
[~mkienenb] Would you please check my wiki role? I would like to change it but
AFAIK i have no edit role.
> Documentation wrong about Error handl
? I would like to change it but
AFAIK i have no edit role.
> Documentation wrong about Error handling
>
>
> Key: MYFACES-4012
> URL: https://issues.apache.org/jira/browse/MYFACES-4012
> Pro
[
https://issues.apache.org/jira/browse/MYFACES-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058103#comment-15058103
]
Thomas Andraschko commented on MYFACES-4012:
Thanks Mike!
Done!
> Documentation wrong ab
[
https://issues.apache.org/jira/browse/MYFACES-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko resolved MYFACES-4012.
Resolution: Fixed
Assignee: Thomas Andraschko
> Documentation wrong ab
://builds.apache.org/job/tobago-trunk/1400/])
TOBAGO-1480: Documentation on how to setup my project to work with Portlets
(lofwyr: [http://svn.apache.org/viewvc/?view=rev=1706418])
* tobago-trunk/src/site/fml/faq.fml
> Documentation on how to setup my project to work with Portl
? Or do you have an ICLA on file with the ASF?
If so, I can give you direct access to edit the Confluence wiki pages.
See this URL for details on submitting an Individual Contributor License
Agreement (ICLA):
http://www.apache.org/dev/new-committers-guide.html#cla
> Documentation wrong ab
Matthew Alexander created MYFACES-4012:
--
Summary: Documentation wrong about Error handling
Key: MYFACES-4012
URL: https://issues.apache.org/jira/browse/MYFACES-4012
Project: MyFaces Core
[
https://issues.apache.org/jira/browse/TOBAGO-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst resolved TOBAGO-573.
---
Resolution: Fixed
tc:command entry for supported facet popup in TLD documentation
://builds.apache.org/job/tobago-trunk/1391/])
TOBAGO-573: tc:command entry for supported facet popup in TLD documentation
is missing (deki: http://svn.apache.org/viewvc/?view=revrev=1696720)
*
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/taglib/component
://builds.apache.org/job/tobago-3.0.x/59/])
Merged from trunk
TOBAGO-573: tc:command entry for supported facet popup in TLD documentation
is missing [from revision 1696720] (deki:
http://svn.apache.org/viewvc/?view=revrev=1696721)
* /myfaces/tobago/branches/tobago-3.0.x
*
/myfaces/tobago/branches/tobago
with mvn in that directory and deploy it. You may
change the dependencies, this depends on the server (e.g. if the server brings
a JSF implementation with).
Hope that helps
Documentation on how to setup my project to work with Portlets
Hugo Dias created TOBAGO-1480:
-
Summary: Documentation on how to setup my project to work with
Portlets
Key: TOBAGO-1480
URL: https://issues.apache.org/jira/browse/TOBAGO-1480
Project: MyFaces Tobago
So I've spent several hours trying to figure out how to make
documentation changes. I think I'm ready to write up some
documentation on the process, but I need to fill in some of the gaps.
So far, this Documentation thread started by Grant Smith back on
November 19th, 2012 seems to be our only
Ashwin Prabhu created TRINIDAD-2485:
---
Summary: Some attribute behaviors in tr:validateDateRestriction
donot match their documentation
Key: TRINIDAD-2485
URL: https://issues.apache.org/jira/browse/TRINIDAD-2485
in tr:validateDateRestriction donot match their
documentation
--
Key: TRINIDAD-2485
URL: https://issues.apache.org/jira/browse/TRINIDAD-2485
Project: MyFaces Trinidad
Issue Type
Hi
By reasons you already know, we are on the process of migrate the
documentation that was is available in confluence:
https://cwiki.apache.org/confluence/display/MYFACES/Index
to apache cms. I have published the resulting documentation, so you
can take a look at:
http://myfaces.apache.org
(was: Patch Available)
Applied the patch from Anand
documentation about cilent side rules does not mention about aliases
Key: TRINIDAD-2437
URL: https://issues.apache.org/jira/browse/TRINIDAD-2437
updated TRINIDAD-2437:
---
Status: Patch Available (was: Open)
documentation about cilent side rules does not mention about aliases
Key: TRINIDAD-2437
URL
Anand V Nath created TRINIDAD-2437:
--
Summary: documentation about cilent side rules does not mention
about aliases
Key: TRINIDAD-2437
URL: https://issues.apache.org/jira/browse/TRINIDAD-2437
Project
[
https://issues.apache.org/jira/browse/TRINIDAD-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand V Nath updated TRINIDAD-2437:
---
Status: Patch Available (was: Open)
documentation about cilent side rules does
Available)
r1485788 | jwaldman | 2013-05-23 17:55:16 + | 2 lines
Changed paths:
M /myfaces/trinidad/trunk/src/site/xdoc/devguide/skinning.xml
TRINIDAD-2389 review and fix values for @platform in skinning documentation
thanks to Anand V Nath for the patch
review and fix values
paths:
M /myfaces/trinidad/trunk/src/site/xdoc/devguide/configuration.xml
TRINIDAD-2385 trinidad-config documentation wrong for time-zone parameter
defaulting
Thanks to Yee-Wah Lee for the patch
trinidad-config documentation wrong for time-zone parameter defaulting
if switchType=reloadPage, otherwise
dropdown drops the data.
The tc:tabgroup component has wrong documentation of attrbiute immediate:
Default: false is wrong!!
---
Key
.
The tc:tabgroup component has wrong documentation of attrbiute immediate:
Default: false is wrong!!
---
Key: TOBAGO-1242
URL: https://issues.apache.org/jira/browse/TOBAGO
review and fix values for @platform in skinning documentation
-
Key: TRINIDAD-2389
URL: https://issues.apache.org/jira/browse/TRINIDAD-2389
Project: MyFaces Trinidad
Issue
Anand V Nath created TRINIDAD-2389:
--
Summary: review and fix values for @platform in skinning
documentation
Key: TRINIDAD-2389
URL: https://issues.apache.org/jira/browse/TRINIDAD-2389
Project
documentation
-
Key: TRINIDAD-2389
URL: https://issues.apache.org/jira/browse/TRINIDAD-2389
Project: MyFaces Trinidad
Issue Type: Bug
Components: Skinning
Affects
\src\site\xdoc\devguide\configuration.xml
Completed: At revision: 1483020
trinidad-config documentation wrong for time-zone parameter defaulting
--
Key: TRINIDAD-2385
URL
Yee-Wah Lee created TRINIDAD-2385:
-
Summary: trinidad-config documentation wrong for time-zone
parameter defaulting
Key: TRINIDAD-2385
URL: https://issues.apache.org/jira/browse/TRINIDAD-2385
Project
and fix values for @agent in skinning documentation
--
Key: TRINIDAD-2382
URL: https://issues.apache.org/jira/browse/TRINIDAD-2382
Project: MyFaces Trinidad
Issue Type: Bug
documentation
--
Key: TRINIDAD-2382
URL: https://issues.apache.org/jira/browse/TRINIDAD-2382
Project: MyFaces Trinidad
Issue Type: Bug
Components: Skinning
Affects Versions
Anand V Nath created TRINIDAD-2382:
--
Summary: review and fix values for @agent in skinning documentation
Key: TRINIDAD-2382
URL: https://issues.apache.org/jira/browse/TRINIDAD-2382
Project: MyFaces
with that.
The tc:tabgroup component has wrong documentation of attrbiute immediate:
Default: false is wrong!!
---
Key: TOBAGO-1242
URL: https://issues.apache.org/jira
Andreas Precht created TOBAGO-1242:
--
Summary: The tc:tabgroup component has wrong documentation of
attrbiute immediate: Default: false is wrong!!
Key: TOBAGO-1242
URL: https://issues.apache.org/jira/browse
:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location,
and I
am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have to answer myself
Hi
It seems the staging area is working:
http://myfaces.staging.apache.org/index1.html
but when I tried to publish the site nothing is happening.
Anyway, with the staging area we can start to move the documentation.
regards,
Leonardo Uribe
2013/1/17 Leonardo Uribe lu4...@gmail.com:
Hi
for Apache MyFaces
2013/1/17 Leonardo Uribe lu4...@gmail.com
Hi
It seems the staging area is working:
http://myfaces.staging.apache.org/index1.html
but when I tried to publish the site nothing is happening.
Anyway, with the staging area we can start to move the documentation.
regards
, but
we need
to wait infra guys to do some additional steps.
regards,
Leonardo Uribe
Werner
Am 10.12.12 16:49, schrieb Werner Punz:
Hia, shouldnt svnpubsub be working?
I published updated documentation
:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I
am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have to answer myself, some of the links do
svnpubsub be working?
I published updated documentation to the svn location, and I
am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have to answer myself, some of the links do not work
(the module
guys to do some additional steps.
regards,
Leonardo Uribe
Werner
Am 10.12.12 16:49, schrieb Werner Punz:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I
am still
[
https://issues.apache.org/jira/browse/EXTSCRIPT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Werner Punz resolved EXTSCRIPT-186.
---
Resolution: Fixed
Documentation update for Extscript 1.0.5
Werner Punz:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I
am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have to answer myself, some
,
Leonardo Uribe
Werner
Am 10.12.12 16:49, schrieb Werner Punz:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I
am still
getting the old files.
Werner
Werner Punz created EXTSCRIPT-186:
-
Summary: Documentation update for Extscript 1.0.5
Key: EXTSCRIPT-186
URL: https://issues.apache.org/jira/browse/EXTSCRIPT-186
Project: MyFaces Extensions Scripting
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have to answer myself, some of the links do not work (the module
links) with a simple site:site, as it seems
be working?
I published updated documentation to the svn location, and I am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have to answer myself, some of the links do not work (the module
links) with a simple site:site, as it seems.
Werner
Am 06.12.12 12:38
documentation to the svn location, and I am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have to answer myself, some of the links do not work (the module
links) with a simple site:site, as it seems.
Werner
Am 06.12.12 12:38, schrieb Werner Punz:
Hi
steps.
regards,
Leonardo Uribe
Werner
Am 10.12.12 16:49, schrieb Werner Punz:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have
steps.
regards,
Leonardo Uribe
Werner
Am 10.12.12 16:49, schrieb Werner Punz:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have
to wait infra guys to do some additional steps.
regards,
Leonardo Uribe
Werner
Am 10.12.12 16:49, schrieb Werner Punz:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I am still
getting the old files.
Werner
Am 06.12.12 12
, schrieb Werner Punz:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have to answer myself, some of the links do not work (the
module
process before I try to make
any documentation changes. If I understand you correctly, once you make
the
above changes, all I need to do to build the docs and deploy them are:
1. mvn site:stage-deploy (in EACH of the modules)
2. svn commit
Is that correct ?
Thanks,
-Grant.
On Tue, Nov 27, 2012
for svnpubsub, so I reopened the issue on
INFRA.
regards,
Leonardo Uribe
2012/11/27, Grant Smith grantsm...@apache.org:
Leo,
OK, I'll wait for you to finish the release process before I try to
make
any documentation changes. If I understand you correctly, once you make
the
above changes, all I need
the site for the release, but it seems something is
still not working well for svnpubsub, so I reopened the issue on
INFRA.
regards,
Leonardo Uribe
2012/11/27, Grant Smith grantsm...@apache.org:
Leo,
OK, I'll wait for you to finish the release process before I try to make
any documentation changes
Smith grantsm...@apache.org:
Leo,
OK, I'll wait for you to finish the release process before I try to make
any documentation changes. If I understand you correctly, once you make
the
above changes, all I need to do to build the docs and deploy them are:
1. mvn site:stage-deploy (in EACH
Ping: Leonardo, how can we publish currently our documentation?
Werner
Am 26.11.12 13:57, schrieb Werner Punz:
Am 23.11.12 16:16, schrieb Grant Smith:
Leo Werner,
Thanks for the update on this. For now, I want to be able to edit the
xdocs, and have the resulting changes appear
of myfaces core 2.1.10 /
2.0.16 . I'm still trying to find how to do the necessary changes in
our pom.xml
regards,
Leonardo Uribe
2012/11/27 Werner Punz werner.p...@gmail.com:
Ping: Leonardo, how can we publish currently our documentation?
Werner
Am 26.11.12 13:57, schrieb Werner Punz:
Am
/
2.0.16 . I'm still trying to find how to do the necessary changes in
our pom.xml
regards,
Leonardo Uribe
2012/11/27 Werner Punz werner.p...@gmail.com:
Ping: Leonardo, how can we publish currently our documentation?
Werner
Am 26.11.12 13:57, schrieb Werner Punz:
Am 23.11.12 16:16
Leo,
OK, I'll wait for you to finish the release process before I try to make
any documentation changes. If I understand you correctly, once you make the
above changes, all I need to do to build the docs and deploy them are:
1. mvn site:stage-deploy (in EACH of the modules)
2. svn commit
Am 23.11.12 16:16, schrieb Grant Smith:
Leo Werner,
Thanks for the update on this. For now, I want to be able to edit the
xdocs, and have the resulting changes appear on the website. Any Idea
how to accomplish this simple task ?
Guess only Leonardo can answer that for now.
Werner
On
Leo Werner,
Thanks for the update on this. For now, I want to be able to edit the
xdocs, and have the resulting changes appear on the website. Any Idea how
to accomplish this simple task ?
Thanks,
-Grant.
On Thu, Nov 22, 2012 at 12:59 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi
to a combined SVNPUBUSB and CMS infrastructure
there must be a landing page at the old url, obviously, will this page
be CMS or svnpubusb hosted? How can we test this before going online.
The documentation regarding the entire cms is rather vague.
Werner
Am 20.11.12 01:07, schrieb Grant Smith
Hi
2012/11/22 Werner Punz werner.p...@gmail.com:
As for the site. Not sure if this one already is served by svnpubsub or
still by the old system. Leonardo knows more. My guess is it still is served
by the old system. I guess his plan is to have the entire site hosted by
svnpubsub for now, and
Hi all,
I'm going through some of the site documentation, and I can't for the life
of me remember how to build and publish the xdocs so that they appear on
the website. I remember a few emails a while back by Leo regarding
svnpubsub.. is this related ? If so, how does it work ?
It seems the wiki
Hi Grant!
Werner already created http://svn.apache.org/repos/asf/myfaces/cms-site/trunk
The CMS documentation can be found here: http://www.apache.org/dev/cms.html
There is a maven plugin for doing the svnpubsub from a mvn site:
http://maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin
already created
http://svn.apache.org/repos/asf/myfaces/cms-site/trunk
The CMS documentation can be found here:
http://www.apache.org/dev/cms.html
There is a maven plugin for doing the svnpubsub from a mvn site:
http://maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin/examples/importing
enough, not perfect, but it should
minimize the manual labor we have to perform.
Prepare the Documentation for the CMS Transition
Key: EXTSCRIPT-179
URL: https://issues.apache.org/jira/browse
Werner Punz created EXTSCRIPT-179:
-
Summary: Prepare the Documentation for the CMS Transition
Key: EXTSCRIPT-179
URL: https://issues.apache.org/jira/browse/EXTSCRIPT-179
Project: MyFaces Extensions
update
Documentation doesn't mention required dependencies
---
Key: EXTSCRIPT-170
URL: https://issues.apache.org/jira/browse/EXTSCRIPT-170
Project: MyFaces Extensions Scripting
[
https://issues.apache.org/jira/browse/TRINIDAD-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand V Nath updated TRINIDAD-2327:
---
Status: Patch Available (was: Open)
update RenderingContext.getIcon() documentation
in txn 1397132
Committed to trunk in txn 1397133
update RenderingContext.getIcon() documentation
---
Key: TRINIDAD-2327
URL: https://issues.apache.org/jira/browse/TRINIDAD-2327
Project
)
Thx for the check in!
Improvement in the component id description to align with the JSF Spec
documentation
Key: TRINIDAD-2313
URL: https://issues.apache.org
with the JSF Spec
documentation
Key: TRINIDAD-2313
URL: https://issues.apache.org/jira/browse/TRINIDAD-2313
Project: MyFaces Trinidad
Issue Type: Improvement
Ji Kim created TRINIDAD-2313:
Summary: Improvement in the component id description to align with
the JSF Spec documentation
Key: TRINIDAD-2313
URL: https://issues.apache.org/jira/browse/TRINIDAD-2313
Kito D. Mann created EXTSCRIPT-170:
--
Summary: Documentation doesn't mention required dependencies
Key: EXTSCRIPT-170
URL: https://issues.apache.org/jira/browse/EXTSCRIPT-170
Project: MyFaces
. With that info, it shouldn't be hard to add the
necessary annotations and generate the javascript documentation.
regards,
Leonardo Uribe
2012/7/5 Blake Sullivan blake.sulli...@oracle.com:
Leonardo,
I'm not sure what you are asking. Are you asking what prototype means in
JavaScript? If that is what
, it shouldn't be hard to add the
necessary annotations and generate the javascript documentation.
regards,
Leonardo Uribe
2012/7/5 Blake Sullivan blake.sulli...@oracle.com:
Leonardo,
I'm not sure what you are asking. Are you asking what prototype means in
JavaScript? If that is what you are asking
Hi
I tried to add this to trinidad-impl pom.xml:
profiles
profile
idgenerate-assembly/id
build
plugins
plugin
groupIdorg.apache.myfaces.buildtools/groupId
artifactIdmyfaces-jsdoc-plugin/artifactId
Leonardo,
I'm not sure what you are asking. Are you asking what prototype means
in JavaScript? If that is what you are asking, then the quickie answer
is that Javascript uses template-based inheritance. Every JS Object has
a prototype property pointing to the instance that this JS Object
documentation for 1.0.3 public anncouncement
Key: EXTSCRIPT-163
URL: https://issues.apache.org/jira/browse/EXTSCRIPT-163
Project: MyFaces Extensions Scripting
Issue Type: Task
[
https://issues.apache.org/jira/browse/EXTSCRIPT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Werner Punz resolved EXTSCRIPT-157.
---
Resolution: Fixed
prepare and improve the site documentation for the 1.0.2 and 1.0.3
prepare and improve the site documentation for the 1.0.2 and 1.0.3 release
announcments in the users list.
--
Key: EXTSCRIPT-157
URL: https
improve documentation about alternative window-handler
--
Key: EXTCDI-274
URL: https://issues.apache.org/jira/browse/EXTCDI-274
Project: MyFaces CODI
Issue Type: Task
Affects Versions
the documentation for 1.0 and 1.0.1
--
Key: EXTSCRIPT-147
URL: https://issues.apache.org/jira/browse/EXTSCRIPT-147
Project: MyFaces Extensions Scripting
Issue Type: Improvement
Reporter
the @deprecated tag in the javadoc part should end in
the generated documentation
Key: TOBAGO-1072
URL: https://issues.apache.org/jira/browse/TOBAGO-1072
[
https://issues.apache.org/jira/browse/TOBAGO-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Schnurpfeil resolved TOBAGO-1070.
-
Resolution: Fixed
Fix Version/s: 1.5.2
Documentation: attribute inline
Doc: The comment after the @deprecated tag in the javadoc part should end in
the generated documentation
Key: TOBAGO-1072
URL: https://issues.apache.org/jira
1 - 100 of 377 matches
Mail list logo
