[
https://issues.apache.org/jira/browse/TRINIDAD-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved TRINIDAD-556.
Fix Version/s: 1.2.1-core
1.0.1-core
Resolution: Fixed
Indeed
instead.
-- Blake Sullivan
Simon Lessard said the following On 4/8/2010 6:17 AM PT:
-1. I really don't like it. It should be an implementation detail of the
ChangeManager to either replace/chain the attribute change in the
addComponentChange (or any other change for that matter). We have
Hi,
You could also override the readResolve method of your application scoped
bean to reflect its singleton status. However that does create an annoying
dependency since the application scoped bean will knows its managed bean
name. But if you're using @ManagedBean or @Named, it already does
() as appropriate. No api
changes and the change is encapsulated in UIXFacesBeanImpl and
UIXComponentBase.
-- Blake Sullivan
\Simon Lessard said the following On 1/6/2010 10:40 AM PT:
Hi Blake,
Yep, that's exactly what I meant. I'm aware that the main risk lies with
compatibility, but I
Looks great, thanks!
On Thu, Jan 7, 2010 at 7:17 PM, Bruno Aranda brunoara...@gmail.com wrote:
Excellent! Looks fantastic. Something long due to trinidad.
Thanks,
Bruno
2010/1/7 Matt Cooper mcoo...@apache.org
Wow this looks fantastic, nice work!
Thanks,
Matt
On Thu, Jan 7, 2010 at
Hi Blake,
Yep, that's exactly what I meant. I'm aware that the main risk lies with
compatibility, but I think it's minimal.
Regards,
~ Simon
On Tue, Jan 5, 2010 at 8:00 PM, Blake Sullivan blake.sulli...@oracle.comwrote:
Simon Lessard said the following On 1/5/2010 2:34 PM PT:
Blake
Hi,
Why not simply NOT support a PropertyKey for the id attribute? I know it
isn't consistent with the other properties, but id is a very special case
not supporting EL anyway. In all the project I ever did, I never used
FacesBean.getProperty(ID_PROPERTY_KEY). The only drawback I would see is if
...@oracle.comwrote:
The reason is that we need to support AttributeMap/component accessor
equivalence--get/set of the id attribute through the Map is supposed to work
correctly. The ValueExpression only exists to make this work.
-- Blake Sullivan
Simon Lessard said the following On 1/5/2010 10:57 AM
to explicitly handle id
-- Blake Sullivan
Simon Lessard said the following On 1/5/2010 12:08 PM PT:
Have the AttributeMap call the getId/setId. The contract for the Map
returned by getAttributes is supposed to call the getter/setter method on
the component anyway,
fromhttp://java.sun.com/javaee
, since the pay the cost of both reflection
and Map access.
-- Blake Sullivan
Simon Lessard said the following On 1/5/2010 12:32 PM PT:
Hi Blake,
Actually it's harsher/simpler than that. Assuming that .getAttributes() is
very rarely used in a Trinidad application (exception for custom
Hi,
The context parameter is the way to go, but it might not be working yet in
MyFaces alpha.
~ Simon
On Fri, Dec 25, 2009 at 10:21 PM, Mark Struberg strub...@yahoo.de wrote:
Hi!
Since RichFaces-3.3.3 is not compatible with the builtin JSF-2.0 facelets 2
version, I need to disable it and
Hi,
Although I wouldn't mind if this is needed, I do find it weird for the
portle bridge to work with the VDL at all. VDL is supposed to have pretty
much a single purpose: convert a physical document to a JSF component tree.
That being said the JSP VDL most likely uses Servlet API too since,
Looks good to me as well. I've got to admit that this ProjectStage thing
seems to get more useful than what I was thinking when I first saw it pop on
the EG list
On Thu, Dec 10, 2009 at 1:12 PM, Matthias Wessendorf mat...@apache.orgwrote:
awesome.
I plan to start development on that next
Hi,
I'm pretty sure this was discussed on the EG list, so yeah it looks like a
hole in the spec and Mojarra being right here.
~ Simon
On Mon, Nov 30, 2009 at 6:28 PM, Michael Kurz michi.k...@gmx.at wrote:
Hi,
I have recently created a bunch of applications with Mojarra 2.0 that I'm
+1
On Wed, Nov 25, 2009 at 9:39 AM, Michael Concini mconc...@gmail.com wrote:
+1
Bruno Aranda wrote:
+1
2009/11/25 Cagatay Civici cagatay.civ...@gmail.com:
+1
On Wed, Nov 25, 2009 at 2:20 PM, Matthias Wessendorf mat...@apache.org
wrote:
+1
On Wed, Nov 25, 2009 at 2:27 PM,
*;
}
*public* *void* setNavigationBar(HtmlNavigationBar navigationBar)
{
*this*.navigationBar = navigationBar;
}
}
Thanks.
*Simon Lessard simon.lessar...@gmail.com*
10/27/2009 07:13 PM
Please respond to
MyFaces Development dev@myfaces.apache.org
on a command button like this:
*h:commandButton* value=*Submit* action
=#{testBean.formSubmitted}/
Thanks.
*Simon Lessard simon.lessar...@gmail.com*
10/27/2009 07:43 PM
Please respond to
MyFaces Development dev@myfaces.apache.org
To
MyFaces Development dev
Hi,
This is a good explanation. Is it possible for you to test a JSP version? To
be honest, I'm a bit flabbergasted to see something like that happen in
Facelet. Can you check the state of the component's children within the
formSubmitted method?
~ Simon
On Tue, Oct 27, 2009 at 11:43 AM,
Hi Jakob,
Because after restore view is actually one of the most used (along with
before render) and was specifically added to 2.0 for that purpose. It's not
possible to make it different because the spec say so, and thus MyFaces
might not pas the TCK if it was made differently. So, there's
Hi all,
Personally, I would prefer to see that class divided in more specialized
classes like :
XhtmlElements
{
public static final String DIV = div; (or could be DIVISION)
public static final String TABLE = table;
public static final String TABLE_BODY = tbody;
public static
+1 for the project stage idea.
On Tue, Oct 13, 2009 at 10:28 AM, Michael Concini mconc...@gmail.comwrote:
What about using project stage to determine which behavior to follow? If
we're in production stage we don't check for best performance, but in
development/test stages we perform the
+1 for jul. However, I think we should add an utility class
(ServletContextListnener? This is the easiest way I know of, if it qualifies
for easiest at all) in myfaces-shared or extension to make it easier to
configure the logger because it's way more annoying to configure than
commons-logging
Hi,
The last messages that were exchanged on that subject were still on the
requirement list, see http://markmail.org/message/ixfdm4ajl7f6zbxl. We were
not so much agreeing and there was still the portlet issue to resolve. It's
an important issue, and would be a great addition, reviving the
Hi,
I wouldn't mind seeing that part shared.
~ Simon
On Tue, Sep 22, 2009 at 5:30 PM, Udo Schnurpfeil u...@schnurpfeil.de wrote:
Hi Marius,
it sounds very nice for me. Can I take a look to the implementation
anywhere? I would like to check if it fits to Tobago.
So we can share the code
Hi Werner,
I'll reread the spec about your example, I think it should be on both
component, but I'll try to make sure of it. Also, I'm not against putting
the support for that functionality in the impl, but I'm not too warm about
it either, since custom component developers won't be able to
+1
On Fri, Aug 14, 2009 at 7:09 AM, Leonardo Uribe lu4...@gmail.com wrote:
+1
2009/8/14 Jan-Kees van Andel jankeesvanan...@gmail.com
+1
2009/8/14 Bruno Aranda brunoara...@gmail.com:
+1
2009/8/14 Matthias Wessendorf mat...@apache.org:
+1 :-)
On Fri, Aug 14, 2009 at 11:24 AM,
Hi,
Since it's an internal API I think we should just flush the class down the
drain.
~ Simon
On Mon, Aug 10, 2009 at 12:47 PM, Jan-Kees van Andel
jankeesvanan...@gmail.com wrote:
Removing the view-handler / element from my faces-config.xml did the
trick.
Funny that everything worked
Hmm,
I used the latest nightly build when I integrated the code. However, that
was about 3~4 months ago, so maybe it changed a little since then, or there
was another usable branch that I was unaware of. That being said, maybe we
should add the required changes by ourselves. Even if Facelets is
Ah, the incredibly messy JSR-299 issue... About everything about it is done
badly. JSF 2.0 is going to depend on it to support some of the annotation
and conversation scope. While JSR-299 activates conversation only when JSF
is present, lovely circular dependency isn't it? Most of the times I
Hi,
They used to be under javax.faces.model. However, due to overlap with
JSR-299 they were moved to javax.faces.bean, see the companion JavaDoc
(under \managed-bean-javadocs).
Regards,
~ Simon
On Mon, Aug 3, 2009 at 10:12 AM, Curtiss Howard curtiss.how...@gmail.comwrote:
Hi,
The JSF 2.0
the
DataModels...
/JK
2009/8/3 Simon Lessard simon.lessar...@gmail.com:
Hi,
They used to be under javax.faces.model. However, due to overlap with
JSR-299 they were moved to javax.faces.bean, see the companion JavaDoc
(under \managed-bean-javadocs).
Regards,
~ Simon
On Mon
with the current code, but I
didn't try it.
Regards,
~ Simon
On Tue, Jul 28, 2009 at 12:05 PM, Michael Concini mconc...@gmail.comwrote:
Great news. Thanks a lot.
Simon Lessard wrote:
Hi,
I'll try to commit that tonight.
~ Simon
On Tue, Jul 28, 2009 at 10:20 AM, Michael Concini mconc
Hi,
I'll try to commit that tonight.
~ Simon
On Tue, Jul 28, 2009 at 10:20 AM, Michael Concini mconc...@gmail.comwrote:
Hi Simon,
I wanted to do a quick follow up here. There are a few of us who are ready
to start filling in the gaps once the initial commit is done. Have you had
a
Hi,
I'm trying to work on it, but frankly I'm overloaded beyond what I was
expecting so I could use help quite badly. Theoretically, three parts
remains to the integration:
1. Link the Facelets code with the Delegate pattern on API side;
2. Finish the Facelet VDL (Facelets compiler integration)
Hi Michael,
Personally I think it should be a different branch, I just never created it
because I'm not familiar enough with it. This will also allow addition of
1.5 features in it so I'm all for it.
Regards,
~ Simon
On Mon, Jul 6, 2009 at 2:25 PM, Michael Concini mconc...@gmail.com wrote:
Hi,
I'm working on it. Hopefully it'll be done by next Sunday. So far I think I
should be able to handle it on my own. If not ready by Sunday, then I guess
some help would be needed. As for the taglib, we keep the tags defined by
the spec.
Regards,
~ Simon
On Mon, Jun 29, 2009 at 8:54 AM,
Hi Curtiss,
Yes and no. Facelets is now ASL2 licensed so we're not reinventing the
wheel, we use the original code, modified only to include Java 5 features
(generics), repackage the classes and integrate the PDL semantics. However,
if I have time, I want to do some performance tests with current
Hi,
I think the Shale-test drop has been made, but we still need to integrate it
with the codebase. We'll also have to determine how to distribute it. I
would see it as myfaces-api artifact-id, but using test-jar packaging as I
think it's the only safe way to handle the bidirectional dependency
Hi Matthias,
If we use myfaces-test we'll have the exact same issues as with shale-test
artifacts. That is, myfaces-test-2.0 will depend on myfaces-api-2.0 whereas
myfaces-api-2.0 requires myfaces-test to be tested and released. However,
Maven provide another, yet less known, feature that allow
Hi,
On my side I'll try to work and finish Facelets part within 2 weeks, fater
than that is impossible for me atm.
Regards,
~ Simon
On Tue, Jun 9, 2009 at 9:53 AM, Werner Punz werner.p...@gmail.com wrote:
Matthias Wessendorf schrieb:
regarding tree visitor, this may help:
Simon Lessard schrieb:
Hi,
On my side I'll try to work and finish Facelets part within 2 weeks,
fater
than that is impossible for me atm.
Regards,
~ Simon
On Tue, Jun 9, 2009 at 9:53 AM, Werner Punz werner.p...@gmail.com
mailto:werner.p...@gmail.com wrote
+1
On Thu, May 28, 2009 at 2:23 AM, Matthias Wessendorf mat...@apache.orgwrote:
sure!
On Thu, May 28, 2009 at 6:34 AM, Leonardo Uribe lu4...@gmail.com wrote:
+1, but just a small suggestion. Right now I'm running the necessary
steps
for release myfaces core 1.2.7, core 1.1.7, so I would
Sounds acceptable then.
~ Simon
On Sun, May 17, 2009 at 9:09 PM, Blake Sullivan
blake.sulli...@oracle.comwrote:
Simon Lessard said the following On 5/17/2009 6:19 AM PT:
Hi Blake,
*Prefer the same what? Are you talking about the ExternalContext?*
I meant placing register the listeners
Hi Blake,
*Prefer the same what? Are you talking about the ExternalContext?*
I meant placing register the listeners the Window itself, not the Manager,
same as isNew.
~ Simon
On Sat, May 16, 2009 at 1:18 AM, Blake Sullivan
blake.sulli...@oracle.comwrote:
Simon Lessard said the following
Hi Blake,
I'm + 1 with the idea and the general API, but I have some concerns:
1. I don't really like the API to expose a read only map through
WindowManager.getWindows, I would prefer
WindowManager.getWindowIds(ExternalContext) and
WindowManager.getWindow(ExternalContext, String);
Sounds pretty decent to me, we'll just have to make sure we still pass the
TCK after though since the spec also define the default.
~ Simon
On Thu, May 14, 2009 at 2:27 PM, Matthias Wessendorf
mwessend...@gmail.comwrote:
Of course ordering after the standard...
Sent from my iPod.
Am
Well I guess you're right, there's no way that the property will be set
during the tests.
On Thu, May 14, 2009 at 5:52 PM, Matthias Wessendorf
mwessend...@gmail.comwrote:
I guess the tck has no org.apache.** cfg param as sys prop
Sent from my iPod.
Am 14.05.2009 um 22:45 schrieb Simon
+1
On Mon, May 11, 2009 at 7:21 PM, Jeanne Waldman
jeanne.wald...@oracle.comwrote:
+1 to the name
Is everyone ok with trinidadinternal plus a comment staying it is private
being enough to make this 'private' so that we are free to remove it and/or
change the default behavior after it has
and enable dependency management and nested
modules)
and things work fine :-)
real man's IDE ;-)
Funny that it does not work in Netbeans. The IDEs I am using (JDEV and
Eclipse) understand
those generated artifcats. Tools just should work, eh ? :)
Best Regards,
Ganesh
Simon Lessard schrieb
Not sure on my side, I'm really not into AJAX. I followed the discussions,
but really not deeply enough to get that kind of detail. :(
~ Simon
On Wed, May 6, 2009 at 1:02 PM, Werner Punz werner.p...@gmail.com wrote:
Ok Since Ganesh pointed it out, this is even better.
We probably wont need a
$0.02
-M
On Tue, May 5, 2009 at 7:54 PM, Simon Lessard simon.lessar...@gmail.com
wrote:
Weird, it certainly overlaps BIG time, most of what their spec seem to
have
is already in JSR-299 too... Maybe I'm missing something...
On Tue, May 5, 2009 at 1:45 PM, Matthias Wessendorf mat
Yeah PartialPageContextImpl does, I'll try to find the best possible design,
I don't really like moving methods to public API unless they really have to
be there. I'll work on that this weekend most likely, along with some 2.0
tasks.
~ Simon
On Fri, May 1, 2009 at 1:12 PM, Blake Sullivan
Hi,
Currently Trinidad won't allow to redefine the RequestContextFactory once
it's defined, preventing any attempt to decorate it. Would it be ok with you
if I removed that check?
Regards,
~ Simon
Hi,
I won't -1 it, most likely +0, but I'm curious, why can't
RenderKit.getRenderer be used for that case use case? The only case it does
not cover would be a component not getting its Renderer the standard way,
but to my knowledge all UIXComponent do so I'm not sure.
Regards,
~ Simon
On Thu,
Hi Michael,
Definitely 3. It's true that JSF 2.0's ViewHandler no longer do much, it
pretty much only deal with HTTP headers and such while most of the work is
delegated to the VDL. 2 might break the TCK I think so it's not a good
option.
~ Simon
On Thu, Apr 30, 2009 at 4:47 PM, Michael Concini
Hi,
Along the same line as my previous post, in order to successfully decorate a
RequestContext, public IteratorString getPartialTargets() would have to be
graduated from RequestContextImpl to RequestContext in order to remove a
dependency between PartialPageContextImpl and RequestContextImpl. If
Congratulations and thanks for the great work.
On Tue, Apr 28, 2009 at 4:28 AM, Werner Punz werner.p...@gmail.com wrote:
Matthias Wessendorf schrieb:
The Myfaces PMC is proud to announce a new addition to our community.
Please welcome Michael Concini as the newest MyFaces committer!
Congratulations and thanks for the great work on JSF 2.0 AJAX.
On Tue, Apr 28, 2009 at 4:35 AM, Matthias Wessendorf mat...@apache.orgwrote:
welcome!
-- Forwarded message --
From: Cagatay Civici cagatay.civ...@gmail.com
Date: Tue, Apr 28, 2009 at 10:27 AM
Subject: Re:
[1] +1
[2] -1
[3] -1
[4] +0
On Fri, Apr 24, 2009 at 9:40 AM, Cagatay Civici cagatay.civ...@gmail.comwrote:
[1] +1
[2] -1
[3] -1
[4] +0
On Fri, Apr 24, 2009 at 2:32 PM, Werner Punz werner.p...@gmail.comwrote:
[1] +1
[2] -1
[3] -1
[4] +1
Werner
Ganesh schrieb:
Hi,
We are
Awesome, thanks to everyone who helped with that.
Now I gotta do my part and finish Facelets...
~ Simon
On Thu, Apr 23, 2009 at 6:06 AM, Matthias Wessendorf mat...@apache.orgwrote:
On Thu, Apr 23, 2009 at 11:46 AM, Werner Punz werner.p...@gmail.com
wrote:
Hello everyone
as it seems,
Definitely +1
~ Simon
On Tue, Apr 21, 2009 at 3:27 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi
Just for information purposes and as start point, what we have right now is
this wiki page:
http://wiki.apache.org/myfaces/MyFaces_Archetypes_for_Maven
The archetypes available
/component/
Can you please check this again?
Best Regards,
Ganesh
Simon Lessard schrieb:
Hi Ganesh,
I think you forgot to execute mvn install on the build maybe because it
compiles fine for me.
As for running the whole thing I don't think it would be working yet since
some Lifecycle
Hi Ganesh,
I think you forgot to execute mvn install on the build maybe because it
compiles fine for me.
As for running the whole thing I don't think it would be working yet since
some Lifecycle phases were already modified to use the new Ajax API on
partial request, but there's no impl for that
Simon Lessard schrieb:
Hi all,
This is a simple post to inform you that the final JSF 2.0 draft was
released yesterday
(http://jcp.org/aboutJava/communityprocess/pfd/jsr314/index.html) and
that
the 2.0 branch is in sync with it (at least to my knowledge). Not
everything
is integrated
: Simon Lessard
Assignee: Simon Lessard
JSF 2.0 requires Facelets integration. Since I'm going to deal with this whole
thing I'm creating this ticket to keep track of it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
[
https://issues.apache.org/jira/browse/MYFACES-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard updated MYFACES-2081:
---
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard updated MYFACES-2178:
---
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Status: Resolved
[
https://issues.apache.org/jira/browse/MYFACES-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard updated MYFACES-2179:
---
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Status: Resolved
[
https://issues.apache.org/jira/browse/MYFACES-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard updated MYFACES-2180:
---
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Status: Resolved
[
https://issues.apache.org/jira/browse/MYFACES-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard updated MYFACES-2181:
---
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Status: Resolved
[
https://issues.apache.org/jira/browse/MYFACES-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard updated MYFACES-2182:
---
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Status: Resolved
[
https://issues.apache.org/jira/browse/MYFACES-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2105.
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Was resolved with Application
[
https://issues.apache.org/jira/browse/MYFACES-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2102.
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Was resolved with Application
[
https://issues.apache.org/jira/browse/MYFACES-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-1950.
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Was resolved with Application
[
https://issues.apache.org/jira/browse/MYFACES-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2036.
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Applied patch on the branch
[
https://issues.apache.org/jira/browse/MYFACES-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2003.
Resolution: Invalid
Fix Version/s: 2.0.0-alpha
This ticket is no longer valid
[
https://issues.apache.org/jira/browse/MYFACES-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-1998.
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Already in as of revision 763448
[
https://issues.apache.org/jira/browse/MYFACES-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-1942.
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-1980.
Resolution: Invalid
Fix Version/s: 2.0.0-alpha
No longer exists
[
https://issues.apache.org/jira/browse/MYFACES-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard updated MYFACES-2184:
---
Resolution: Fixed
Fix Version/s: 2.0.0-alpha
Status: Resolved
[
https://issues.apache.org/jira/browse/MYFACES-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2040.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2062.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2056.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2041.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2053.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2046.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2042.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2061.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2065.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2045.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2054.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2067.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
I'm integrating all Facelets
[
https://issues.apache.org/jira/browse/MYFACES-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2048.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2052.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2057.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2066.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2063.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2070.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2064.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
[
https://issues.apache.org/jira/browse/MYFACES-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Lessard resolved MYFACES-2047.
Resolution: Duplicate
Fix Version/s: 2.0.0-alpha
Assignee: Simon Lessard
1 - 100 of 557 matches
Mail list logo
