[JBoss JIRA] Created: (RF-9531) Create profile for build plugins that does not applicable in IDE.
by Alexander Smirnov (JIRA)
Create profile for build plugins that does not applicable in IDE.
-----------------------------------------------------------------
Key: RF-9531
URL: https://jira.jboss.org/browse/RF-9531
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Environment: Maven 2.0,3.0 , m2eclipse
Reporter: Alexander Smirnov
Fix For: 4.0.0.Milestone4
Some maven plugins like buildNumber, checkstyle does not work properly in IDE or may decrease build time.
It makes sense to create special profile for these plugins, that can be disabled in Eclipse or other ide.
That profile should be enabled by default but can be disabled by some special variable or profile.
The best solution seems as two opposite profiles ( CLI / IDE ). By default, build should use CLI profile and disable it if IDE is active.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (RF-6450) DataTable: add ajax sort event/request customization
by Gerrit Brehmer (JIRA)
DataTable: add ajax sort event/request customization
----------------------------------------------------
Key: RF-6450
URL: https://jira.jboss.org/jira/browse/RF-6450
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.2
Environment: JSF Sun RI 1.2_12, RichFaces 3.2.2
Reporter: Gerrit Brehmer
We need the common RichFaces ajax-request parameters like ajaxSingle or onSubmit for column sorting feature. Otherwise we get thread-safety problems, because if i click sort icon on one column and right after that (before response from first click arrived) click on another column-sort-icon. Because we have input fields in some columns, the values will be set to the wrong entries, because generated client-ids which will be sent by the second request are generated before response and new ids of the first request are applied to the table on client side. But during the second request, the table is already sorted (first column) in the backend. If we can drop applying table values or show a modalPanel on submit, we could avoid this thread/concurrent request related problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months