Hi Dennis!
Right now the best solution that I see is to tag shared as close to the core
tag as possible ( speaking of time here ). I am still trying to find
problems with this idea.
As I said, AddResource had a massive bug. It is possible to deliver
responses to other clients than the
[
http://issues.apache.org/jira/browse/TOMAHAWK-175?page=comments#action_12369008
]
Stefan Betermieux commented on TOMAHAWK-175:
Hi Jurgen,
I have compiled your patch, and I like what I saw. Eventually, we can combine
our two appraoches,
I've added compiler support for deferred expressions within Tomcat 6.
While there's still more to do (round .tag files at least), I am able to
run the RI 1.2 samples without problems.
--
Jacob Hookom - Minneapolis
JSF-EG, JSF-RI, EL, Facelets
+1 (also non-binding)
-Matthias
On 3/6/06, Martin Marinschek [EMAIL PROTECTED] wrote:
Hi *,
Tobago would like to sign-off from the incubator.
This is the link to the project-status page:
http://incubator.apache.org/projects/tobago.html
My (non-binding) +1.
regards,
Martin
--
Martin's last commit appears to make this work.
It doesn't work for me. I get ...
D:\open-source\myfaces-core-1.1.2\impl\src\main\java\org\apache\myfaces\webapp\f
ilter\JavaScriptDetectorFilter.java:[58,23] setJavascriptDetected(javax.servlet.
http.HttpSession,boolean) in
Hi Sean!
Martin's last commit appears to make this work.
It doesn't work for me. I get ...
Martins commit wasn't meant to fix this problem.
D:\open-source\myfaces-core-1.1.2\impl\src\main\java\org\apache\myfaces\webapp\f
ilter\_javascript_DetectorFilter.java:[58,23]
Hi!
Our new license boilerplate?
myfaces/tomahawk/trunk/sandbox/core/src/main/resources/org/apache/myfaces/custom/inputsuggestajax/resource/tableSuggest.js
Mon Mar 6 05:25:56 2006
@@ -1,7 +1,15 @@
/**
- * Copyright 2006 The Apache Software Foundation.
*
- * Licensed under the Apache
[
http://issues.apache.org/jira/browse/TOMAHAWK-175?page=comments#action_12369030
]
Jurgen Lust commented on TOMAHAWK-175:
--
I think that returning the start time and end time is not the responsibility of
the schedule component anymore. When you can
What shared revision do you use now?
I did this last night using the latest shared trunk.
This is one of my changed I made to shared - and also moved the
JavaScriptDetectorFilter out of core to tomahawk.
This javascript detection is a myfaces extension and thus I decided to move
it away
shared-impl and shared-tomahawk are only virtual they are generated
during mvn install. And are in fact a copy from shared-core.
Do you mean by core *and* tomahawk the shared-* stuff? Then this
demarcation do not exist within shared itself.
Thanks. This explains it.
Dennis Byrne
I meant Martin's commit fixed trunk shared w/ trunk core. I'm sure you have
already found that this is not true for the core branch.
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, March 6, 2006 07:06 AM
To: 'MyFaces Development'
Subject:
This seems like a good idea to me. The timing would be best to do
this right now or to wait a few weeks after we create a tomahawk
branch. I think we should hold off on tomahawk branch until the core
release.
Sean
On 3/3/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
I'm looking at
On 3/6/06, Sean Schofield [EMAIL PROTECTED] wrote:
The timing would be best to do
this right now or to wait a few weeks after we create a tomahawk
branch.
The timing for creating the ValidatorBase class, or the timing for
putting it into a Commons package?
OK, then I will branch the shared like we discussed. Any objections?
Sean
On 3/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
I meant Martin's commit fixed trunk shared w/ trunk core. I'm sure you have
already found that this is not true for the core branch.
Dennis Byrne
-Original
Well there is no commons package yet and I definitely think we should
hold off on that decision for a little while. (I assume you mean the
new commons and not the current shared.)
So if you were to create it in tomahawk that would be ok. If its
useful for impl then it could go in shared.
Sean
Right, I meant the currently-uncreated commons, not shared.
I don't see a point in putting it in shared -- we're not allowed to
change the behavior of the standard validators, and the existing
validators work per spec.
I was pretty sure you just meant to add it to tomahawk, but I wanted
to make
No objections at this point, but what about tomahawk? If the next release of
tomahawk is to run along side w/ this release of core, it will have to be
compatible w/ the only branch for shared. Are there any obstacles to this? I
am at my day job now so I can't look into this too deeply.
Actually the shared stuff prevents this from being a problem. Since
maven will refactor things into their own packages there is no longer
the potential to have a shared conflict between tomahawk and core.
Sean
On 3/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
No objections at this point, but
Hi Sean!
Actually the shared stuff prevents this from being a problem. Since
maven will refactor things into their own packages there is no longer
the potential to have a shared conflict between tomahawk and core.
(non binding) -1 from me, sorry. (Reason: The ExtensionFilter bug)
Please
(non binding) -1 from me, sorry. (Reason: The ExtensionFilter bug)
Please tell me why we cant tag the current trunks - all projects (except
tomahawk)?
Is the ExtensionFilter bug something that already exists in the
current 1.1.1 release? If its not a new bug then I don't mind
releasing with
Hi!
Is the ExtensionFilter bug something that already exists in the
current 1.1.1 release?
IMHO no.
This bug were introduced during the creation of AddResourceFactory which
was 2006-02-08. So after the 1.1.1 release.
If its not a new bug then I don't mind
releasing with the bug in place.
Hi,
The SVN repository for MyFaces has a directory called 'release/tags'
which is presumably the location from which you could check out the
source for a given MyFaces release. However, these tags use
svn:externals which can have some unintended consequences; namely
that they're not
This is pure speculation on my part due to my inexperience with SVN,
but have you tried checking out the stuff under
http://svn.apache.org/repos/asf/myfaces/release/tags/1_1_1?
On 3/6/06, Garrett Conaty [EMAIL PROTECTED] wrote:
Hi,
The SVN repository for MyFaces has a directory called
We have discontinued use of svn externals (except for in current) for
this very reason. You best bet for this source code is to get the
source release.
Sean
On 3/6/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
This is pure speculation on my part due to my inexperience with SVN,
but have you
Ok so should we create a new myfaces core branch then (off the current
trunk.) That seems like the best option given the choices ...
Sean
On 3/6/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Is the ExtensionFilter bug something that already exists in the
current 1.1.1 release?
IMHO
What is lost if we just start over? Seriously.
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, March 6, 2006 03:01 PM
To: 'MyFaces Development'
Subject: Re: Testing Progress?
Ok so should we create a new myfaces core branch then (off the
Hi Sean!
Ok so should we create a new myfaces core branch then (off the current
trunk.) That seems like the best option given the choices ...
And here is my +1 for this :-)
---
Mario
What is lost if we just start over? Seriously.
Not much that I can think of. That's basically what I am proposing.
Start over with the branch.
Dennis Byrne
Sean
my +1, too.
in fact - in the end all these problems have probably been caused by
me being extremely busy with a project going into production right
now, and (together with Bruno, Werner, Thomas, Gerald) adding tons
over tons of features right at a time when we wanted to release.
So blame me!
We just need to make sure there are no *new* core check-ins since the
last merge. If so, we will need to merge them down before abandoning.
I am still creating a shared branch (off the current trunk code) to
go with the new core branch. This will prevent this problem from
happening again should
Hi Martin!
So blame me! It's my fault!
No need to stand in first line :-)
The bug could have been fixed without tempering the release process.
It was me who started the refactoring at the same time as I wasn't aware
about the slightly different (and lengthy) release process here in
Hi Martin!
So blame me! It's my fault!
No need to stand in first line :-)
The bug could have been fixed without tempering the release process.
It was me who started the refactoring at the same time as I wasn't aware
about the slightly different (and lengthy) release process here in
Open Source group therapy. We're all sorry ;)
regards,
Martin
On 3/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
Hi Martin!
So blame me! It's my fault!
No need to stand in first line :-)
The bug could have been fixed without tempering the release process.
It was me who started the
Hi!
I'll invite everyone who has some time to a meeting in vienna/austria.
Location: Ma Pitom
Date: 28.3.2006
Time: 18:30
We have no free stickers, no t-shirts or any other gift, just a meeting
to drink a beer - or two - maximum.
You meet me (if this is of any interest) and some guys from the
[
http://issues.apache.org/jira/browse/TOBAGO-2?page=comments#action_12369048 ]
Bernd Bohmann commented on TOBAGO-2:
This is a problem of the jsf spec.
We can't solved this in tobago this must be solved in the spec.
Maybe it is solved in a future
Martin Marinschek schrieb:
Yes, of course, one beer maximum!
(at a time, per person ;)
regards,
Martin
No stereo beers that is ...
Yes, of course, one beer maximum!
(at a time, per person ;)
regards,
Martin
On 3/6/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
I'll invite everyone who has some time to a meeting in vienna/austria.
Location: Ma Pitom
Date: 28.3.2006
Time: 18:30
We have no free stickers, no
Hi *,
anyone willing to share their JMeter configuration scripts for
load-testing (our huge production level app with 200+jspx files) with
us?
The app runs fast, but we want to be even faster -
MyFaces performance. We want more of it ;)
regards,
Martin
--
http://www.irian.at
Your JSF
[
http://issues.apache.org/jira/browse/TOMAHAWK-126?page=comments#action_12369118
]
Neil Hoskins commented on TOMAHAWK-126:
---
I've looked into this issue extensively as it is blocking a project I am
working on. I'm fairly new to JSF but after a bit
We now have a stable 1.1.2 build of the MyFaces Core ready for
testing. You can find the build at
http://cvs.apache.org/builds/myfaces/nightly/. Please be sure to test
the core 1.1.2 snapshot *only*. The rest (including core 1.1.3) is
nightly stuff that is automatically produced from the trunk
Can you please make it use a 1.3 compiler?
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, March 6, 2006 08:32 PM
To: 'MyFaces Discussion', 'MyFaces Development', announce@myfaces.apache.org
Subject: [ANNOUNCE] MyFaces Core 1.1.2 Ready For
41 matches
Mail list logo
