I think what he's saying is that we have pre-exsiting API's. Still, we
could add an isPlatform or even a better a getPlatform which takes an
Agent enum. The convenience methods could be deprecated (or not) and
then simply tie use the much nicer isPlatform method.
The real question becomes,
Not sure Wolfgang. It's marked as patch available but I don't actually
see a submitted patch. Do you want me to cancel the patch so it's once
again open?
Scott
[EMAIL PROTECTED] wrote:
Hi,
has this been fixed or is there a workaorund available. .we also come
into a similar situation:
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633787#action_12633787
]
Scott O'Bryan commented on PORTLETBRIDGE-48:
Felix, we should maybe look
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated PORTLETBRIDGE-48:
---
Status: Open (was: Patch Available)
IllegalStateException in Websphere
[
https://issues.apache.org/jira/browse/TRINIDAD-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-1239:
Status: Open (was: Patch Available)
Error when using with MyFaces portlet bridge JSR
[
https://issues.apache.org/jira/browse/TRINIDAD-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633793#action_12633793
]
Scott O'Bryan commented on TRINIDAD-1239:
-
This patch violated the contract
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12634014#action_12634014
]
Scott O'Bryan commented on PORTLETBRIDGE-48:
Hey Felix, thanks
Leonardo, thanks for filing (and presumably taking care of) this issue.
Scott
Leonardo Uribe (JIRA) wrote:
Remove org.apache.myfaces.portlet from JSF 2.0 branch, because it has no use
anymore
[
https://issues.apache.org/jira/browse/TRINIDAD-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12632737#action_12632737
]
Scott O'Bryan commented on TRINIDAD-1233:
-
This patch removes the jsessionid
[
https://issues.apache.org/jira/browse/TRINIDAD-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12632738#action_12632738
]
Scott O'Bryan commented on TRINIDAD-1233:
-
Please fix the patch and I'll commit
[
https://issues.apache.org/jira/browse/TOMAHAWK-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12632347#action_12632347
]
Scott O'Bryan commented on TOMAHAWK-1331:
-
FYI, I think the 1.1 bridge
[
https://issues.apache.org/jira/browse/TOMAHAWK-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12632354#action_12632354
]
Scott O'Bryan commented on TOMAHAWK-1331:
-
This is the bridge currently included
[
https://issues.apache.org/jira/browse/TOMAHAWK-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12632388#action_12632388
]
Scott O'Bryan commented on TOMAHAWK-1331:
-
Well pppttt. Yeah, that's a problem
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12632416#action_12632416
]
Scott O'Bryan commented on PORTLETBRIDGE-47:
Yeah, I think we may need
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12632420#action_12632420
]
Scott O'Bryan commented on PORTLETBRIDGE-47:
This won't effect Trinidad
[
https://issues.apache.org/jira/browse/TOMAHAWK-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631906#action_12631906
]
Scott O'Bryan commented on TOMAHAWK-1331:
-
BTW- Is there any reason NOT to use
[
https://issues.apache.org/jira/browse/TRINIDAD-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631996#action_12631996
]
Scott O'Bryan commented on TRINIDAD-1203:
-
I already know that I need to rename
[
https://issues.apache.org/jira/browse/TRINIDAD-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631469#action_12631469
]
Scott O'Bryan commented on TRINIDAD-1203:
-
I think I'm going to submit a patch
back. If you are content to
wait until the session times-out, or there is another dialog request,
then it isn't a problem.
-- Blake Sullivan
Scott O'Bryan (JIRA) said the following On 9/16/2008 10:10 AM PT:
[ https://issues.apache.org/jira/browse/TRINIDAD-1203?page
Yeah, what Matt said.. +1
Matt Cooper wrote:
Hi Andy,
+1 to #2 -- I feel this makes the most sense. That browser can hardly
be considered a PDA-quality browser; our interpretation of what
desktop means seems to fit more with iPhone's browser.
Thanks,
Matt
On Tue, Sep 16, 2008 at 2:24 PM,
[
https://issues.apache.org/jira/browse/TRINIDAD-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631564#action_12631564
]
Scott O'Bryan commented on TRINIDAD-1217:
-
Yeah, Jeanne, I see what you
[
https://issues.apache.org/jira/browse/TRINIDAD-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631576#action_12631576
]
Scott O'Bryan commented on TRINIDAD-1217:
-
Sure. First off, supressStyleSheet
[
https://issues.apache.org/jira/browse/TRINIDAD-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-1217:
Status: Patch Available (was: Open)
in portals stylesheet generated in the producer
[
https://issues.apache.org/jira/browse/TRINIDAD-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629532#action_12629532
]
Scott O'Bryan commented on TRINIDAD-1217:
-
Howso, I suspect we're talking a few
[
https://issues.apache.org/jira/browse/TRINIDAD-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629323#action_12629323
]
Scott O'Bryan commented on TRINIDAD-1217:
-
A portlet instance is a copy
Bernd,
So to get this straight, is this going to be an extra jar file that you
add to the classpath and allows for partial lifecycle processing or is
this a change to the Trinidad impl itself?
If the latter, I think we need to be very careful about changing the
unoptimized lifecycle until
[
https://issues.apache.org/jira/browse/TRINIDAD-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628882#action_12628882
]
Scott O'Bryan commented on TRINIDAD-1217:
-
EITHER the stylesheet urls should
Very cool. Thanks..
Sent from my iPhone
On Sep 6, 2008, at 9:45 AM, Bernd Bohmann [EMAIL PROTECTED]
wrote:
Hello Scott,
Scott O'Bryan schrieb:
Bernd,
So to get this straight, is this going to be an extra jar file that
you
add to the classpath and allows for partial lifecycle
I'll take a look at the trim changes Monday.
Sent from my iPhone
On Sep 6, 2008, at 9:53 AM, Bernd Bohmann [EMAIL PROTECTED]
wrote:
Bernd Bohmann schrieb:
Also, is there any real way we can take a look at the code before
it's
committed? Maybe move it to the sandbox first so people can
-1
I agree with both Simon and Paul. Let's try and address the issues
and not just fix the symptom.
Scott
Sent from my iPhone
On Sep 4, 2008, at 12:54 PM, Simon Lessard simon.lessard.
[EMAIL PROTECTED] wrote:
-1
However, it's true that Apache product users often consider
themselves
[
https://issues.apache.org/jira/browse/TRINIDAD-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627839#action_12627839
]
Scott O'Bryan commented on TRINIDAD-1203:
-
I think we need to be very careful
:03 AM, Matthias Wessendorf
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
+1
On Wed, Aug 27, 2008 at 4:48 AM, Scott O'Bryan
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Hi,
I'm trying to release the MyFaces Portlet Bridge Master
1.0.0-alpha-3.
This pom
Vote passed with the following results:
+1: Scott O'Bryan, Manfred Geiler, Michael Freedman, and Matthias Wessendorf
-0: Simon Kitching
The -0 was due to some concerns about the checkstyle sections of the
pom. I will generate a jira ticket to address those concerns in the
next release
not put
our releases up onto the central repo.
Regards,
Simon
On Thu, 2008-08-14 at 12:03 +0200, Matthias Wessendorf wrote:
+1
On Thu, Aug 14, 2008 at 11:46 AM, Scott O'Bryan [EMAIL PROTECTED] wrote:
Hi,
I'm trying to release the MyFaces Portlet Bridge Master POM v2. This pom
file
Hi,
I'm trying to release the MyFaces Portlet Bridge Master POM v2. This
pom file was created in order to support the latest portlet-bridge
project's website as well as the multiple open code lines needed for
this project going forward. This file manages the commonalities between
all of
Oh yeah. +1
Sent from my iPhone
On Aug 14, 2008, at 4:21 AM, Manfred Geiler
[EMAIL PROTECTED] wrote:
+1
On Thu, Aug 14, 2008 at 11:46 AM, Scott O'Bryan
[EMAIL PROTECTED] wrote:
Hi,
I'm trying to release the MyFaces Portlet Bridge Master POM v2.
This pom
file was created in order
[
https://issues.apache.org/jira/browse/TRINIDAD-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615378#action_12615378
]
Scott O'Bryan commented on TRINIDAD-1109:
-
Yeah, this could get messy. Ideally
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614085#action_12614085
]
Scott O'Bryan commented on PORTLETBRIDGE-31:
That's a good question
I don't know why b is an issue. The Caps- case notation I've always
taken to be private statics rather then non-immutible constants. I
know in Trinidad, we use LOG for logs and I suspect the same for
thread locals.
On Jul 4, 2008, at 2:04 PM, simon [EMAIL PROTECTED] wrote:
Hi All,
I
Can we do this outside of core. I'm not a big fan of extending
functionality of the core beyond the spec. For one, I suspect we'll
have issues with the bridge. Asside from that what if JSF 2.1 defines
a competingmechanism to handle this?
At most this extension belogs in the extensions
?
(currently it's also a blocking topic for me to
setup myfaces-extensions-validator.)
regards,
gerhard
2008/6/20 Scott O'Bryan [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]:
Mike, the problem with this approach is one of forward compatibility.
Let me explain. The ExternalContextUtils
Paul, why do the CF versions have to be different. This is no different
(IMO) then what I was talking about except that we could not FORCE
people to backport everything.
I don't see why libraries for older JSF's HAVE to be functionally
equivalent. That is not to say that API's started in
should work with
1.2.8 as well. I think on the commons side, we can just release each
branch as needed because, especially starting off, we're going to have
projects which will require a release of commons in order to do their
release. Especially if there are some enhancements.
Scott
Scott
Yeah, I would accept that... At least until there is basically NO
active development happening on a branch. Maybe when the corresponding
JSF branch goes End of Cycle?
Paul Spencer wrote:
Scott O'Bryan wrote:
Partially ignore this.. :) Let me clairify now that I understand
your proposal
Mike, the problem with this approach is one of forward compatibility.
Let me explain. The ExternalContextUtils in the MyFaces commons, when
it existed in Trinidad, had api's for handling request input streams and
whatnot because the ExternalContext did not. If someone used that API
and then
Hey Leonardo,
Let me take a look at this tonight. As you know, I hope to have the
configurator package checked in soon into commons which will do this as
well. Right now it fits Trinidad's requirements pretty well but I'd
like to see how it stacks up to Tomahawk's. In trinidad I plan to
19, 2008 at 5:05 PM, Scott O'Bryan [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hey Leonardo,
Let me take a look at this tonight. As you know, I hope to have
the configurator package checked in soon into commons which will
do this as well. Right now it fits Trinidad's
I still think this is a bad idea. My question is this, now that JSF 2.0
is getting ready to come out, when is Tomahawk going to finally open a
JSF 1.2 or JSF 2.0 branch?
Further, Matthias has a commons 1.1 branch out there already in
branches. It's mainly for backports. Can we not do this
-1
Leonardo Uribe wrote:
+1
On Thu, Jun 19, 2008 at 5:39 PM, Leonardo Uribe [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi
After several discussions about how myfaces-commons should be,
there are strong reasons to believe that this project
should have some layout
Leonardo Uribe wrote:
On Thu, Jun 19, 2008 at 5:56 PM, Scott O'Bryan [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Right. I know there has been some talk about creating a Tomahawk
JSF 1.2 branch. I don't imagine that Tomahawk would use the
commons before (and if) this happens
It's a very VERY rare occasion.. :)
Matthias Wessendorf wrote:
On Wed, Jun 18, 2008 at 1:09 PM, Scott O'Bryan [EMAIL PROTECTED] wrote:
Well almost completely. File uploads still use IFRAME.. :)
ha, yeah... you got me. :)
Matthias Wessendorf wrote:
Trinidad used to go
Yeah, this is a complex issue. And trinidad doesn't do it right
either. Here is what I was going to do for Trinidad (in my copious
amounts of spare time). :)
Each Portlet would have a root element. When a form is submitted via
ppr, the view state for each javax.faces.ViewState under that
[
https://issues.apache.org/jira/browse/TRINIDAD-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan resolved TRINIDAD-1089.
-
Resolution: Fixed
Fix Version/s: 1.2.9-core
1.0.9-core
Cool
[
https://issues.apache.org/jira/browse/TRINIDAD-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12605006#action_12605006
]
Scott O'Bryan commented on TRINIDAD-1089:
-
BTW- Paul, I looked at classifiers
[
https://issues.apache.org/jira/browse/TRINIDAD-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603922#action_12603922
]
Scott O'Bryan commented on TRINIDAD-1089:
-
While I'm not so keen to provide top
Hey everyone, in order to solve TRINIDAD-1089, I'm proposing some
changes to the Trinidad POM files and I think they will make things much
easier. While I was in there, I also cleaned them up quite a bit and
eliminated much of the redundancy.
The only thing that will change as a result of
Others can correct me if I'm wrong but I think the votes should be
binding. I think this means it is PMC's and commiters and a
descending vote ( called a veto) blocks it.
On Jun 9, 2008, at 6:45 AM, Hazem Saleh [EMAIL PROTECTED] wrote:
Hi Volker,
I think we should take the whole votes,
[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603472#action_12603472
]
Scott O'Bryan commented on PORTLETBRIDGE-35:
Angel, JSR-301 clearly
Congrats...
Andrew Robinson wrote:
Congratulations Matt!
On 6/6/08, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Dear MyFaces community,
please welcome our new MyFaces PMC member Matt Cooper.
Matt is working on the Apache MyFaces and Trinidad stuff.
Therefore last week there was a vote
[
https://issues.apache.org/jira/browse/TRINIDAD-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12601780#action_12601780
]
Scott O'Bryan commented on TRINIDAD-1110:
-
Discussion of this issue should
[
https://issues.apache.org/jira/browse/TRINIDAD-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12601785#action_12601785
]
Scott O'Bryan commented on TRINIDAD-1059:
-
I figured it would. Perhaps for now
+1
Matthias Wessendorf wrote:
+1
On Mon, Jun 2, 2008 at 9:13 AM, Volker Weber [EMAIL PROTECTED] wrote:
+1
Regards,
Volker
2008/6/2 Gerhard Petracek [EMAIL PROTECTED]:
hello,
we discussed whether or not we should start a new myfaces sub-project
(details at: [1] and [2]).
name:
[
https://issues.apache.org/jira/browse/TRINIDAD-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan reopened TRINIDAD-1000:
-
Nevermind, I see this now. Sorry..
Broken links in left navigation bar (on Tag
: 1.2.8-core, 1.0.8-core
Reporter: Scott O'Bryan
Assignee: Scott O'Bryan
Priority: Minor
Fix For: 1.0.9-core, 1.2.9-core
The CoreRenderingContext.getFormData() contains an invalid assert that often
triggers when asserts are turned
[
https://issues.apache.org/jira/browse/TRINIDAD-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-1101:
Status: Patch Available (was: Open)
Invalid assert and comment
[
https://issues.apache.org/jira/browse/TRINIDAD-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-1101:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Invalid assert
of people.apache.org to another.
And secondly, why can't that approved (and uncorrupt) release candidate
zip file just be used rather than regenerating from the tag? Have the
release candidate files already been deleted from their review place on
people.apache.org?
Regards,
Simon
Scott O'Bryan schrieb
of people.apache.org to another.
And secondly, why can't that approved (and uncorrupt) release candidate
zip file just be used rather than regenerating from the tag? Have the
release candidate files already been deleted from their review place on
people.apache.org?
Regards,
Simon
Scott O'Bryan schrieb
the newly generated archives, you can check them out
on my share -
http://people.apache.org/~sobryan/trinidad/1.0.8/
Scott
Scott O'Bryan wrote:
I suppose if it makes you feel better, I can manually reconstruct the
dist package based on the deployed maven artifacts in the release, but
like I say
[
https://issues.apache.org/jira/browse/TRINIDAD-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599591#action_12599591
]
Scott O'Bryan commented on TRINIDAD-1093:
-
Trinidad correctly follows
[
https://issues.apache.org/jira/browse/TRINIDAD-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan reopened TRINIDAD-1093:
-
oh, are you talking about the Built project or the root director. I think the
root
[
https://issues.apache.org/jira/browse/TRINIDAD-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599594#action_12599594
]
Scott O'Bryan commented on TRINIDAD-1093:
-
sorry, having iPod issues.. If your
[
https://issues.apache.org/jira/browse/TRINIDAD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599448#action_12599448
]
Scott O'Bryan commented on TRINIDAD-930:
Point #5 is invalid because although
The Apache MyFaces Trinidad team is pleased to announce the release of
Apache MyFaces Trinidad Core 1.2.8.
Apache MyFaces Trinidad is a JavaServer(tm) Faces 1.2 component library.
Trinidad Core 1.2.8 is available in both binary and source distributions:
*
[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599090#action_12599090
]
Scott O'Bryan commented on TRINIDAD-875:
I'm not sure Opera is one of our
[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598705#action_12598705
]
Scott O'Bryan commented on TRINIDAD-875:
Can others watching this thread verify
IMO this isn't necessary. We already control whether we deploy the
myfaces jars using a profile. Can't we add a profile which includes the
JSTL jars in the demo when it's built? Also, it should be easy enough
to add them to tomcat as a shared library as well.
Scott
Paul Spencer wrote:
The
Hey everyone, the long awaited myfaces-commons-configurator package is
ready to be checked in. Because I'm seeing a lot of people doing things
that might be aided by this framework, I was hoping I could check it
into the commons project and get people to help me test it and fix it
up. Do
copies/version of
JSTL exists )
If not then when should distribute :
A) J2EE version and non-J2EE version of Example.zip/tar.gz
or
B) Example.zip/tar.gz containing a J2EE and non-J2EE version of
trinidad-demo.war and trinidad-blank.war
Paul Spencer
Scott O'Bryan wrote:
IMO
] wrote:
-1
Trinidad-73/Trinidad-978 is a showstopper issue for my application.
Willing to contribute labor to get a fix for this problem into 1.0.8.
Thank you,
Ed
On 5/20/08, Scott O'Bryan [EMAIL PROTECTED] wrote:
Ok Paul, TRINIDAD-1083 has been applied to both trunks, the 1.0.8 label
/trinidad-demo/index.html
I am of the opinion that a demo/example should run as distributed and
the installation should be intuitive. In this case the distribution
is build for a J2EE environment, but it is not obvious to anyone
installing it.
Paul Spencer
Scott O'Bryan wrote:
Well I sort
It looks like the vote is going to pass. We've got our 3 +1 votes and 1
.5. I'll be sure to log the -1 vote and the reason.
Ed, when you get this fixed, ping me. I'd be open to doing another
early release to try to get this in before your deadline. Cool?
Scott O'Bryan wrote:
It's
This vote passed with the following spread:
+1 (x3): Paul Spencer, Scott O'Bryan, Matthias Wessendorf
+ .5 (x1): Andrew Robinson
- 1 (x1): Edward Dowgiallo
The negative one vote was for issues TRINIDAD-73 and TRINIDAD-978. We
may be looking at another release soon to address these issues
-1 Myfaces commons utils is not the place for this. MyFaces core should not
have to depend on the commons project to run. Plus the myfaces commons
utils is a snapshot and not going to release any time soon. Making Trinidad
dependent on this package would mean we can't release util the commons
[
https://issues.apache.org/jira/browse/TRINIDAD-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598836#action_12598836
]
Scott O'Bryan commented on TRINIDAD-875:
Ok, then let me see if we even have our
right?
Just as we have the jetty profile and the jetty plugin registered, we
can do the same for tomcat I think.
The drawback of course is maintaining the poms for different servers
-Andrew
On Wed, May 21, 2008 at 1:36 PM, Scott O'Bryan [EMAIL PROTECTED] wrote:
Well documentation is easy. I'm
, the instructions should also be on the
Demo's web page[1].
Paul Spencer
[1]http://myfaces.apache.org/trinidad/trinidad-1_2/trinidad-demo/index.html
Scott O'Bryan wrote:
Andrew,
Yeah, that's what I proposed. Paul wants us to distribute the
non-j2ee version with our examples...
Scott
building the demo is so easy. In either
case, we'll need some changes to the pom and if we do website
documentation then it'll need some changes to be made to the site as well.
Scott
Scott O'Bryan wrote:
Right. I'm for #3... And lets face it. The EASIEST way to run the
demo is to download
[
https://issues.apache.org/jira/browse/TRINIDAD-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-1083:
Resolution: Fixed
Fix Version/s: 1.2.9-core
1.0.9-core
for
the 1.2.8 fix...
Sent from my iPod.
Am 20.05.2008 um 02:05 schrieb Scott O'Bryan [EMAIL PROTECTED]:
Venkata, we'll need a JIRA issue and a patch if possible. I can
apply it asap.
To the community, I do have a question.. Concerning this vote we
had 2.5 +1's and 1 -1. Technically I think
Ok Paul, TRINIDAD-1083 has been applied to both trunks, the 1.0.8 label
and the 1.2.8 label. All of the artifacts have been regenerated.
When you test it, give me your +1 and I think we're ready to release.
Scott
Scott O'Bryan wrote:
Cool, thanks Matthias. I'm currently regenerating
[
https://issues.apache.org/jira/browse/ORCHESTRA-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598279#action_12598279
]
Scott O'Bryan commented on ORCHESTRA-25:
Trinidad was able to get this working
[
https://issues.apache.org/jira/browse/TRINIDAD-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598282#action_12598282
]
Scott O'Bryan commented on TRINIDAD-1059:
-
I am applying this patch but while
[
https://issues.apache.org/jira/browse/TRINIDAD-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-1059:
Resolution: Fixed
Fix Version/s: (was: 1.2.8-core)
1.2.9
[
https://issues.apache.org/jira/browse/TRINIDAD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-930:
---
Status: Open (was: Patch Available)
tr:selectOneChoice resets value if not in form
[
https://issues.apache.org/jira/browse/TRINIDAD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598294#action_12598294
]
Scott O'Bryan commented on TRINIDAD-930:
I'm not sure that this is a valid issue
[
https://issues.apache.org/jira/browse/TRINIDAD-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598336#action_12598336
]
Scott O'Bryan commented on TRINIDAD-1059:
-
I agree, but the current system
[
https://issues.apache.org/jira/browse/TRINIDAD-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598338#action_12598338
]
Scott O'Bryan commented on TRINIDAD-1060:
-
Sandy, in the future I'm going
[
https://issues.apache.org/jira/browse/TRINIDAD-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598341#action_12598341
]
Scott O'Bryan commented on TRINIDAD-1060:
-
This patch does not contain
[
https://issues.apache.org/jira/browse/TRINIDAD-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-1060:
Status: Open (was: Patch Available)
update tagdoc for RowDisclosureEvent
701 - 800 of 1260 matches
Mail list logo
