As expected, the build failed locally and on hudson (see
TRINIDAD-2006) due to the site plugin.
However it is possible to use our Hudson machine with Maven 3.0.2 -
currently I am doing that,
with the patch from TRINIDAD-2006.
-M
On Thu, Jan 27, 2011 at 7:16 AM, Matthias Wessendorf
Hello Matt,
Oh I don't mind...in fact I think this update will be good for Trinidad
builds.
On Thu, Jan 27, 2011 at 4:16 AM, Matthias Wessendorf mat...@apache.orgwrote:
Hi,
what are folks thinking about using Maven3. I did some tests for
Trinidad and Maven 3 yesterday ([1]).
Things like the
Ok, the hosted Maven3.0.2 works fine with the current version of our
pom (which now (kinda) requires m3).
Most important: the nightly builds works, as they worked before.
So, that part would be fixed - for now I am keeping this
improvement, at least temporary.
(I will keep 2006 open for a bit,
[
https://issues.apache.org/jira/browse/TRINIDAD-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12987433#action_12987433
]
Matthias Weßendorf commented on TRINIDAD-2006:
--
I managed to run the
Hi,
In our internal testing we've noticed that
org.apache.myfaces.config.annotation.LifecycleProviderFactory's are
_never_ released. I don't think it's a problem for the default
implementations, but our container integration uses a special
implementation that needs to hold on to resources for
The message for 'source' target is not correct in the case of DateIsType.same
--
Key: EXTVAL-124
URL: https://issues.apache.org/jira/browse/EXTVAL-124
Project: MyFaces
[
https://issues.apache.org/jira/browse/EXTVAL-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12987532#action_12987532
]
Rudy De Busscher commented on EXTVAL-124:
-
For the source component, the {0} is
For the @DateIs validation annotation, allow a date pattern to be specified for
the error message.
--
Key: EXTVAL-125
URL:
Implement the DateIsType.beforeOrSame and DateIsType.afterOrSame date
comparisons
-
Key: EXTVAL-126
URL: https://issues.apache.org/jira/browse/EXTVAL-126
Project:
Dear developers,
I would like to request you an important feature that is missing in MyFaces
- the Flash scope.
Similar to Mojarra, MyFaces could have the ELFlash class with static
methods, to make it possible to store and retrieve objects from flash scope,
like example bellow:
PPR problems in Firefox and Chrome
--
Key: TRINIDAD-2022
URL: https://issues.apache.org/jira/browse/TRINIDAD-2022
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 2.0.0-beta-1
How is the entire reporting secion doing, the last time I did a deep
check maven3 did not have the reporting anymore and the new external
modules were under development.
Werner
Am 27.01.11 07:16, schrieb Matthias Wessendorf:
Hi,
what are folks thinking about using Maven3. I did some tests
+1
Am 26.01.11 23:35, schrieb Jakob Korherr:
+1
Regards,
Jakob
2011/1/26 Grant Smithwork.gr...@gmail.com:
+1
On Wed, Jan 26, 2011 at 10:27 AM, Gerhardgerhard.petra...@gmail.com
wrote:
+1
regards,
gerhard
2011/1/26, Matthias Wessendorfmat...@apache.org:
+1
On Wed, Jan 26, 2011 at 10:51
Hi Alexandre,
MyFaces does implement the Flash Scope (every valid JSF 2
implementation has to). Take a look at the standardized class
javax.faces.context.Flash.
ELFlash, however, seems to be the internal implementation of the Flash
object in Mojarra. This is only an implementation detail and
Hi Curtiss,
This is definitely a bug.
As you said, the only place this method is used, is inside some test cases.
Big +1 on inserting the call to LifecycleProviderFactory.release()
after FactoryFinder.releaseFactories(); in
StartupServletContextListener.
Regards,
Jakob
2011/1/27 Curtiss
mvn site works locally (I changed the site plugin version).
Trinidad Tagdoc, JavaDoc, RAT, Findbugs = all work (at least locally
on my Ubuntu box)
-M
On Thu, Jan 27, 2011 at 2:58 PM, Werner Punz werner.p...@gmail.com wrote:
How is the entire reporting secion doing, the last time I did a deep
Should be possible to define different types of treeNodeCommands at once
Key: TOBAGO-968
URL: https://issues.apache.org/jira/browse/TOBAGO-968
Project: MyFaces Tobago
There was this
https://issues.apache.org/jira/browse/TRINIDAD-1632
On 1/26/2011 10:15 AM, MAX STARETS wrote:
Blake,
Andy and I have discussed this offline a bit, and his preference was we do not
hack the flag
to be off explicitly (he thought it would create even more confusion). He also
It looks like that was fixed, so is the problem now TRINIDAD-1635
https://issues.apache.org/jira/browse/TRINIDAD-1635.
-- Blake
On 1/27/11 2:18 PM, Gabrielle Crawford wrote:
There was this
https://issues.apache.org/jira/browse/TRINIDAD-1632
On 1/26/2011 10:15 AM, MAX STARETS wrote:
Blake,
CheckSerializationConfigurator should use the Trinidad specific
ObjectInputStream (ObjectInputStreamResolveClass) class
Key: TRINIDAD-2023
[
https://issues.apache.org/jira/browse/TRINIDAD-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12987975#action_12987975
]
Matthias Weßendorf commented on TRINIDAD-2023:
--
The readObject() calls
[
https://issues.apache.org/jira/browse/TRINIDAD-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12987976#action_12987976
]
Matthias Weßendorf commented on TRINIDAD-2023:
--
In Trinidad we do already
22 matches
Mail list logo
