- Are we looking to define internal utilities shared among
Trinidad/Tomahawk/Tobago?
yes that's my understanding
- Are we looking to define public APIs shared among these
projects?
yes common api for these projects but not necessarily immutable
- Are we going to have a common package
+1 Thanks to all the new (and old) faces putting this release together.
Sean
On 2/15/07, Greg Reddin [EMAIL PROTECTED] wrote:
+1 non-binding. I'm using the bits right now in our app that will be
deployed to production Friday.
Greg
Any MyFaces developers going to be at ApacheCon in Amsterdam? I know
Matthias and I will be there? Who else?
Looking forward to meeting some of my Europen counterparts... also to
catch up on the MyFaces world since I've been a bit out of touch
lately.
Sean
I think we had this issue one other time where the server actually had
to be physically rebooted. Very weird.
Sean
On 1/16/07, Bernd Bohmann [EMAIL PROTECTED] wrote:
Hello Matthias,
continuum doesn't response anymore. It's look like java or solaris is
hanging in the network stack. But I'm
A patch release certainly would be a good idea but it takes time and
resources to pull off each release. Its probably worth the effort
since we tend to shoot ourselves in the foot when we release a whole
set of features that sometimes contain radical changes and have not
been tested extensively.
will merge the maven-faces-plugin with the changes for
myfaces, with the official branch 1.2 for that plugin (in trinidad)
and I will update the info in the 1.2 myfaces branch,
I guess, you get this message because the UIMessage class is not
properly autogenerated,
Cheers,
Bruno
On 30/11/06, Sean
+1 for promoting to tomahawk now and perhaps moving stuff to commons
later. Now I need to read the commons proposal ...
sean
On 11/27/06, Manfred Geiler [EMAIL PROTECTED] wrote:
Yes, d'accord!
I agree with Zubin that these are two different pairs of shoes.
+1 for moving s:selectItems out of
I'm unable to build locally using a fresh checkout.
D:\open-source\myfaces-1.2\core\api\target\maven-faces-plugin\main\java\javax\fa
ces\component\UIMessage.java:[76,16] illegal start of expression
Sean
On 11/5/06, Dennis Byrne [EMAIL PROTECTED] wrote:
This runs fine for me locally. A
: Data List
Affects Versions: 1.1.5-SNAPSHOT
Reporter: sean schofield
t:dataTable rowCountVar=rowCount rendered=#{rowCount 1} does not
work as expected. The EL expression always evaluates to false.
Workaround:
Add a h:panelGroup rendered=#{rowCount 1} immediately inside
That's a really bad time of year for a conference! I'd love to make
it to Javapolis some year since I hear its so much fun but right
before Christmas is tough.
Sean
ps. You going to ApacheCon europe next year? I will be there.
On 11/4/06, Bruno Aranda [EMAIL PROTECTED] wrote:
Hey, any of
I think we should be very careful about adding a feature that
encourages people to drift away from the spec. I agree with the
reasons that Craig laid out for why the outcomes behave the way they
do now.
Its true that its not our job to force people to do follow certain
standards. Its also true
This is probably best discussed on the users list. The dev list is
for discussion of new components and general project coordination.
Sean
On 10/31/06, kevin_zhai [EMAIL PROTECTED] wrote:
My table maybe each row(column) need different UI
component(radio,button,checkbox,textbox,etc),
so,use
[
http://issues.apache.org/jira/browse/TOMAHAWK-738?page=comments#action_12442929
]
sean schofield commented on TOMAHAWK-738:
-
I was under the impression the original bug Catagay was trying to fix was that
Lists were not being saved
[
http://issues.apache.org/jira/browse/TOMAHAWK-738?page=comments#action_12442960
]
sean schofield commented on TOMAHAWK-738:
-
Thanks for clarifying. The only stuff I didn't revert was a testcase that
passes under 1.1.4 code
[
http://issues.apache.org/jira/browse/TOMAHAWK-738?page=comments#action_12443114
]
sean schofield commented on TOMAHAWK-738:
-
Again, nobody is saying there's not a problem here its just this solution
merely covers up a problem
Maven is complaining about a facelets plugin. Its not available in a
public repo and it doesn't seem to be in the myfaces/maven project.
Sean
On 10/16/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: tomsp
Date: Mon Oct 16 04:55:58 2006
New Revision: 464453
URL:
it's failing in your case, can you give more details?
Cagatay
On 10/16/06, Sean Schofield [EMAIL PROTECTED] wrote:
Catagay this breaks my code. Serializable should also be supported.
I have a bunch of Hibernate domain objects that are serializable that
I use in a multi page
[
http://issues.apache.org/jira/browse/TOMAHAWK-738?page=comments#action_12442650
]
sean schofield commented on TOMAHAWK-738:
-
I discovered the reason why Catagay's fix breaks my code. By not calling
saveAttachedState for Serializable
Found some more info. Lets move the discussion to TOMAHAWK-738.
Sean
On 10/16/06, Sean Schofield [EMAIL PROTECTED] wrote:
Well it worked fine before. Now I get ...
java.lang.IllegalStateException: Unknown object type
javax.faces.component.UIComponentBase.restoreAttachedState
[
http://issues.apache.org/jira/browse/TOMAHAWK-738?page=comments#action_12442661
]
sean schofield commented on TOMAHAWK-738:
-
I undid the most of the changes from revision 464151. I tried to create a
suitable test alternative but I
[
http://issues.apache.org/jira/browse/TOMAHAWK-491?page=comments#action_12442440
]
sean schofield commented on TOMAHAWK-491:
-
m having a problemn passing a commandButton parameter inside of a t:column. I
wonder if this is due
Catagay this breaks my code. Serializable should also be supported.
I have a bunch of Hibernate domain objects that are serializable that
I use in a multi page table where I need save state. I'm going to
reopen the JIRA issue.
Sean
On 10/15/06, Cagatay Civici [EMAIL PROTECTED] wrote:
Yes
[ http://issues.apache.org/jira/browse/TOMAHAWK-738?page=all ]
sean schofield reopened TOMAHAWK-738:
-
Catagay this breaks my code. Serializable should also be supported. I have a
bunch of Hibernate domain objects that are serializable
[ http://issues.apache.org/jira/browse/TOMAHAWK-491?page=all ]
sean schofield updated TOMAHAWK-491:
Status: Resolved (was: Patch Available)
Fix Version/s: 1.1.5-SNAPSHOT
Resolution: Fixed
I tested the fix and it works great
here, since that seams not to be a common
use case, right?
(I think we already said that during this thread)
regards,
Martin
On 10/10/06, Sean Schofield [EMAIL PROTECTED] wrote:
Martin,
What is the big deal about EditableValueHolder? Why should tree2
implement
that. Let me see if I can work
with what you have.
Sean
On 10/5/06, Martin Marinschek [EMAIL PROTECTED] wrote:
No, it's a pity that not, but I can't. I'm at a client here in Germany
until end of November, can't take off a week.
regards,
Martin
On 10/5/06, Sean Schofield [EMAIL PROTECTED
All of the recent changes to the Shale project look nice. I just
tried rebuilding an app with the latest snapshot. Its nice how the
MyFaces deps have been cleared up so that they don't end up in your
webapp automatically. I'm using the RI to test some facelets stuff
and before these recent
Can we start a roll call of who is going to be at Apache Con and on
what days? I'm posting this to both Shale and MyFaces list since I
feel there is a lot of overlap between our two groups.
I will be there Tuesday (late afternoon) - Friday (leaving early in the morning)
Sean
There is a special startup script that Bernd wrote. Apparently the
standard solaris script wasn't sufficient b/c of the processors used
on the zone.
/usr/local/continuum/bin/solaris-amd64/run.sh start
I have always started it as the mrmaven user but it might be
possible to start as yourself.
A *huge* thank you to Wendy for taking the lead on the release.
sean
On 9/15/06, Bernd Bohmann [EMAIL PROTECTED] wrote:
Hello Wendy,
can we add the Tobago Announcement to the Core Announcement?
Regards
Bernd
Matthias Wessendorf wrote:
Wendy thanks for helping out on the release.
Go ahead
There was a gentleman agreement that there is no commit from Tobagos
to MyFaces, after the toboago incubation was done. Bernd and Volker
are committers of MyFaces.
This was only during the incubation period since the decision was made
to host the incubated Tobago at MyFaces. Now that they are
it has
something to do w/ the fact that you are only building tomahawk, not the whole
thing. Hope this helps.
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 31, 2006 10:01 PM
To: 'MyFaces Development'
Subject: Unable to build Tomahawk
Sean, do you have a release diary or notes on the Core 1.1.3 release?
I can only find http://wiki.apache.org/myfaces/Release_Procedure but I
thought I had seen more detailed notes somewhere.
Sorry. We were once again in a rush and I was doing everything
myself. I'm aftraid that's it.
The
I can't seem to do a clean checkout and build of Tomahawk.
D:\open-source\myfaces\tomahawk\core\src\main\java\org\apache\myfaces\custom\tre
e\renderkit\html\HtmlTreeNodeRenderer.java:[40,16] getHiddenCommandLinkFieldName
(java.lang.String) in
I can' t seem to kill the one process (even as root). I've asked
INFRA to reboot the zone.[1]
Sean
[1] http://issues.apache.org/jira/browse/INFRA-925
On 8/25/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
yeah,
same here :(
anyone listening ?
On 8/24/06, Bernd Bohmann [EMAIL PROTECTED]
What about getting this current version of the core trunk released?
If we don't get a decent version of the 1.1.x core out there soon we
won't have anybody interested in a 1.2.x version. If we manage to get
a stable core release done I think we can just leave the trunk
alone.
There shouldn't be
I think it would be highly desirable to provide some sort of basic
button functionality (previous, next, ok and cancel). I'm not
saying we render buttons on the dialog for the user, but I am saying
that most dialogs have certain things in common that we should just
incorporate into the basic
Doh. Wrong list again.
On 8/24/06, Sean Schofield [EMAIL PROTECTED] wrote:
I think it would be highly desirable to provide some sort of basic
button functionality (previous, next, ok and cancel). I'm not
saying we render buttons on the dialog for the user, but I am saying
that most dialogs
I suspect what Adam is asking about is Shale getting in the business of
creating visual components like buttons in order to implement the
Next/Previous type of thing. That's an area I have wanted to shy away from,
and this kind of thing is a case in point for why. No matter what we do,
our
.
On 8/20/06, Adam Winer [EMAIL PROTECTED] wrote:
Even easier than that - there''s a link right off the main
Browse Project page... Look under Project Summary
at http://issues.apache.org/jira/browse/MYFACES
-- Adam
On 8/20/06, Sean Schofield [EMAIL PROTECTED] wrote:
Is there any way to search
+1 for removing wish. Its all a wish - even the bugs. I think the
current voting system is a better way for finding what the popular
requests are. IMO those take second priority over Patch Available.
sean
On 8/18/06, Cagatay Civici [EMAIL PROTECTED] wrote:
for a wish ?
Yes, I do it if
Do you have an account yet? If not, I can create one for you.
Sean
On 8/16/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
see offline email
On 8/16/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Can I get an account on the MyFaces zone?
Recent discussion about the Core 1.1.4 release indicated
+1
We basically decided on this a long time ago but not everyone is
following it. Newer versions of JIRA (in use with Shale but not
MyFaces) also allows you to disable email on bulk changes.
At some point I will change the JIRA workflow so that you can not
directly close a feature (it must be
Issue Type: Task
Components: General
Reporter: sean schofield
Assigned To: sean schofield
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure
Can you do it so this is only required for Fixed issues?
Invalid/Won't Fix issues should be closed directly.
Why should these be closed directly? Maybe we would revisit one of
these before the release is done. Also, I believe having them
resolved (instead of closed) allows the user to appeal
Is there any way to search for Patch Available issues?
I haven't been able to figure this out yet myself.
Just create a custom search under Find Issues Be sure to change the
project to MyFaces and click the refresh link that they show you.
Otherwise you are stuck with options available for all
message --
From: Sean Schofield [EMAIL PROTECTED]
Date: Jan 1, 2006 10:35 PM
Subject: Re: Maven Build (Ongoing Work Thread)
To: MyFaces Development dev@myfaces.apache.org
[...]
I wonder if there is an easy way to share website resources in maven?
I don't think we should have 10 copies
myfaces repo is fine for me
+1 This has the extra benefit of being available as a backup if
ibiblio is unavailable. We can just leave them there if they pass the
TCK.
I think myfaces repo is fine, b/c there is no real shared.jar which
the users need.
Agreed.
Matthias Wessendorf
Sean
And how are we going to handle the vote? I think we should tag and
build it as 1.1.4, run the TCK, then vote. Other opinions? (The
guidelines on the wiki may need to be revised.)
So the plan is:
1.) Deploy to the snapshot repo
2.) Vote
3.) Manually copy to the ibiblio sync dirs?
And we do
I'm guessing var and value work like any UIData component (and it
should be simple to copy those into the tlddocs from dataTable).
You guessed correctly.
However, varNodeToggler doesn't have any non-code documentation that I
could find. I'm guessing it's an object that implements some kind
No documentation on what the allowable facets are. No documentation
stating that expand and collapse facets need to be UIGraphic
components. [Guess I shouldn't have tried replacing these with
h:outputTexts]
The facets should be named after the node type. I know we need more
documentation - I
I used it a while ago but I think you can bypass it by just using mvn
deploy (if the repos in the pom are the production locations). The
main thing it does is make sure there are no SNAPSHOT refs. It will
also tag your release, etc. but if you mess up, its a real PITA to
start over.
My
+1
On 8/2/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On 8/2/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
I have opened http://issues.apache.org/jira/browse/MYFACES-1377 on this.
However, I've marked it priority Minor since it only generates an
error message rather than breaking
What about adding new MyFaces examples using facelets? We will need it
to test tomahawk facelet support.
I am currently writing such an example over at Shale (just getting it
started.) It uses Shale, MyFaces, Tomahawk, Facelets, Hibernate and
Spring. IMO this single example would suffice for
on this and concludes its tomahawk,
please keep as blocker level severity and move it to the tomahawk
project. Its still a major bug that needs to be dealt with.
Sean
On 8/2/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 8/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
We are majorly bogged down
Tell me what revision the check in was so I can revert it. Then just
apply to the trunk ok?
Sean
On 8/3/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 8/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
Why not apply it to 1.1.4 branch and merge it down? Eventually we
need to merge
I agree with Mike here. Matthias, can you explain the problem in more
detail? We should fix this problem before releasing (if there's a
problem to fix.)
Sean
On 8/3/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 8/3/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
As for the
I patched the 1.1.4 branch; so now 1.1.4 core works with
tomahawk 1.1.5-Snap
and tomahawk 1.1.4-SNAP (after you compile it against the *patched* shared_203)
Great.
-Matthias
Sean
I'm assuming you mean apply it to the branch.
Sorry. That's what I meant.
As for the revision,
http://issues.apache.org/jira/browse/TOMAHAWK-467?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel
states 428204
I'm more than happy to learn how to do this myself
I understand why we want to clean up our namespaces, but is this
cleanup really important enough to warrant breaking compatibility in
the 1.1 releases?
No.
getScrolling has been used for a long time, and it's not just going to
break between 1.1.3 and 1.1.4, it's going to break anyone who's
It's that unit test vs integration test thing again. Your
example will show that facelets works as an integration test, but
isn't really as comprehensive as having a facelets example for every
component.
Yes a facelets example for every component wouldn't hurt. Also,
Wendy's work with the
looks like all people here are
-1 on keeping (or +1 on putting it to the 1.2 branch)
I'll wait until tonight (US time) and do some stuff there;
Makes sense?
Yes. Thanks for helping (again.)
Matthias Wessendorf
Sean
This means that we can't release Tomahawk until the dependency is
final. Shouldn't be a problem at the rate we're going these days ...
Sean
On 8/1/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Ok, I asked b/c of the -SNAPSHOT :)
On 8/1/06, Grant Smith [EMAIL PROTECTED] wrote:
I can't see
Can you give an example of a class that is a problem and how you
propose to fix it? I'm not terribly familiar with facelets but I was
able to get tree2 working without adding special facelets packages.
There were just some differences in properties and how facelets
expected to find them.
Sean
If we design our MyFaces components right, the only component classes
that will need facelets tag handlers are those with method bindings.
The method binding method signature for an attribute has be specified
in a facelets component tag handler.
Well lets make sure we do this part whenever
For most of the remaining problem components, it's simply a matter of
taking care of the generic attributes and making them explicit html
attributes like you did for tree2.
OK so there's not much of a need for this new package directory but we
do need it in a few limited cases right?
The only
, Sean Schofield [EMAIL PROTECTED] wrote:
OK I am doing a quick test of the core release candidate using the
link from the wiki. In the meantime, should we release the shared
dependency? This really needs to come first. Ideally we could
release it to the myfaces internal repo for testing
: General
Affects Versions: 1.1.4-SNAPSHOT
Reporter: sean schofield
Priority: Blocker
Fix For: 1.1.4-SNAPSHOT
tree2NiceWrap.jsf throws a javascript error when you try to expand the node
--
This message is automatically generated by JIRA.
-
If you think
We are majorly bogged down on the Core 1.1.4 release. We need
*everyone* to do what they can to help get this release out the door.
Please see the wiki[1] and test the release candidate there. A good
start is to build the simple examples in the tomahawk HEAD and replace
the myfaces core jars
I know and we're nowhere near releasing tomahawk at this rate so we
should be fine.
On 8/2/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Craig is about to release 1.0.3
On 8/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
This means that we can't release Tomahawk until the dependency
[
http://issues.apache.org/jira/browse/MYFACES-1376?page=comments#action_12425401
]
sean schofield commented on MYFACES-1376:
-
schedule1.jsf component is also experiencing this problem when you try to
advance the calendar
[ http://issues.apache.org/jira/browse/MYFACES-1376?page=all ]
sean schofield updated MYFACES-1376:
Status: Open (was: Patch Available)
getScrolling is not defined in simple tree2 example
[
http://issues.apache.org/jira/browse/MYFACES-1376?page=comments#action_12425406
]
sean schofield commented on MYFACES-1376:
-
Apparently Michael Hartman marked this as patch available but I don't see one.
Changing status back to Open
PROTECTED] wrote:
On 8/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
We are majorly bogged down on the Core 1.1.4 release. We need
*everyone* to do what they can to help get this release out the door.
Please see the wiki[1] and test the release candidate there. A good
start is to build the simple
Why not apply it to 1.1.4 branch and merge it down? Eventually we
need to merge everything down. My vote is to fix it once merge it the
second time. But I don't know the nature of the fix so maybe I'm way
off here.
Sean
On 8/2/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Sounds good
So Dennis, why did you blow the whistle on the RC? Was it from
reading about a problem someone else had or was it b/c the TCK failed?
I'm assuming you were just reporting a problem that someone else had
and thought that it was present in the RC.
I do agree we need to slow down and make sure
OK I am doing a quick test of the core release candidate using the
link from the wiki. In the meantime, should we release the shared
dependency? This really needs to come first. Ideally we could
release it to the myfaces internal repo for testing and then tag it.
Then we can re-release the
-SNAPSHOT
Environment: JSF 1.2 RI
Reporter: sean schofield
I'm getting this stack trace:
WARNING: phase(RENDER_RESPONSE 6,[EMAIL PROTECTED]) threw exception:
java.lang.NoSuchMethodError:
org.apache.myfaces.renderkit.html.util.DummyFormUtils.isWriteDummyForm(Ljavax/faces
What's going on with this? Last I heard there was at least one major
bug? Can somebody summarize the status and likely timetable for
getting this out? This should be everyone's top MyFaces priority. If
you've got other personal stuff to do - fine - but this should be our
top priority
done to
MyFaces state management.
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, July 31, 2006 01:23 PM
To: 'MyFaces Development'
Subject: Core 1.1.4
What's going on with this? Last I heard there was at least one major
bug? Can somebody
[
http://issues.apache.org/jira/browse/MYFACES-1368?page=comments#action_12424595
]
sean schofield commented on MYFACES-1368:
-
According to the SVN logs these changes were made July 4th which was after the
June 21st date where matzew
of five fixes result in another bug.
Dennis Byrne
-Matthias
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, July 31, 2006 01:23 PM
To: 'MyFaces Development'
Subject: Core 1.1.4
What's going on with this? Last I heard
version2.0.3-SNAPSHOT/version
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, July 31, 2006 02:32 PM
To: 'MyFaces Development'
Subject: Re: Core 1.1.4
Ok the classes mentioned in MYFACES-1368 don't seem to be in the 1.1.4
branch. So
/1_1_4/impl/pom.xml?view=markup
It's pointed to the snap shot.
groupIdorg.apache.myfaces.shared/groupId
artifactIdmyfaces-shared-impl/artifactId
version2.0.3-SNAPSHOT/version
Dennis Byrne
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, July 31, 2006 02
Sorry. Missed the bit about the shared branch in the wiki. I thought
Matthias had told me that he created it.
Sean
On 7/31/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 7/31/06, Sean Schofield [EMAIL PROTECTED] wrote:
I guess there was no branch made for the shared project at the same
time
OK I missed this one:
myfaces/shared/trunk/core/src/main/java/org/apache/myfaces/shared/util/StateUtils.java
If we revert this change do we think this will fix the problem? I can
certainly take care of that ...
Sean
On 7/31/06, Sean Schofield [EMAIL PROTECTED] wrote:
Sorry. Missed the bit
, but I do not see how that should
only affect anything other than trunk once the pom in the 1.1.4 branch is
pointed to the correct shared version.
Sean
On 7/31/06, Sean Schofield [EMAIL PROTECTED] wrote:
Sorry. Missed the bit about the shared branch in the wiki. I thought
Matthias had told me
By the way, the test worked this morning so it would seem to be a
timezone or daylight savings problem. Test failed at 11:00 ESDT last
night.
Sean
On 7/28/06, Sean Schofield [EMAIL PROTECTED] wrote:
I recently tried to rebuild from scratch and I can't build Tomahawk
now. The UserDataTest
I recently tried to rebuild from scratch and I can't build Tomahawk
now. The UserDataTest is failing for me.
Test set: org.apache.myfaces.custom.date.UserDataTest
---
Tests run: 12, Failures: 1, Errors: 0, Skipped: 0,
or have an alternative solution...
Bruno
On 7/21/06, Sean Schofield [EMAIL PROTECTED] wrote:
I believe I read that there is some kind of adapter for IDE's.
Perhaps the same adapter can be used for maven testing?
Sean
On 7/21/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 7/21/06, Matthias
That doesn't really answer Wendy's question about where is the issue in JIRA ...
Sean
On 7/21/06, Dennis Byrne [EMAIL PROTECTED] wrote:
What is a 'final RC' ? At this point, we've asked both the dev and
user lists to test snapshots built from the branch, and Dennis has run
the TCK against
There's more to it than that... take a look at the 'release procedure'
wiki page. Apparently, Maven will change the version numbers and do
the tags. (I'm not entirely sure I trust it against the live repo,
but Sean has done it before.) The jars need to be deployed to a
staging repo (on the
We're generally using PNG but I suppose JPEG or GIF is acceptable.
Sean
On 7/17/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
gimp ? :)
On 7/17/06, Paul Spencer [EMAIL PROTECTED] wrote:
The wiki mentions including a screen shot in the documentation,
[EMAIL PROTECTED] wrote:
I'm ok with it.
On 7/14/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hey folks,
any issue in beeing host for Shale's continuum build?
I'd like to add Shale to our zone
-- Forwarded message --
From: Sean Schofield [EMAIL PROTECTED]
Date: Jul
Probably everyone already saw this but this obviously affects our
project. Its interesting that there will one day be an official ASF
maven repository.
Sean
-- Forwarded message --
From: Henri Yandell [EMAIL PROTECTED]
Date: Jul 18, 2006 12:14 AM
Subject: New location for Maven
Kienenberger [EMAIL PROTECTED] wrote:
I'm ok with it.
On 7/14/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hey folks,
any issue in beeing host for Shale's continuum build?
I'd like to add Shale to our zone
-- Forwarded message --
From: Sean Schofield [EMAIL PROTECTED
A component that doesn't work with both implementations is simply broken.
Instead of relying on help from a JSF implementation, it should be
redesigned to include its own help.
I don't think there would be many +1 votes for releasing new
components that depend on the MyFaces implementation. I
To sum up my point:
* Its nothing bad to move now and document its not compatible to RI
* But, as soon as possible we should have a look at making form/command*
RI compatible
So do we have a definitive answer on whether this works with the RI?
If not, then I'm -1 for promotion. We have had too
Ok reading the end of the thread now it seems this has been addressed?
Sean
On 7/15/06, Sean Schofield [EMAIL PROTECTED] wrote:
To sum up my point:
* Its nothing bad to move now and document its not compatible to RI
* But, as soon as possible we should have a look at making form/command
I agree with Mike on both points.
On 7/14/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 7/14/06, Martin Marinschek [EMAIL PROTECTED] wrote:
moving s:form has nothing to do with RI compatibility - we remain as
compatible as before.
So let me reopen the vote, s:form is well documented
1 - 100 of 1914 matches
Mail list logo
