On 8/21/06, Craig McClanahan [EMAIL PROTECTED] wrote:
If you have tried out the dialog manager feature of Shale, you're probably
well aware that it has some limitations and bugs. Indeed, I see improving
this as the most important thing to tackle next. In reviewing the
outstanding bug reports,
On 8/23/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 8/23/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 8/20/06, Sean Schofield [EMAIL PROTECTED] wrote:
snip/
So my proposal is to involve everyone in the beta testing but do not
distribute the final version to vote on so we can
On 8/24/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
In my ideal world scenario, we'll be able to rebuild things on the inside,
with minimal-to-none impact on how an application developer uses it.
However, I'm not convinced that goal is actually achievable, if we're going
to have a
I'd like Shale to support both the current dialog notation and SCXML
as stated here [1], and both can use the same underlying engine. The
current dialog notation by virtue of being the incumbent, and SCXML
because:
* SCXML is a well-defined distillation of all variants of state
machine theory.
On 8/24/06, David Geary [EMAIL PROTECTED] wrote:
Would anyone like to review material on Shale dialogs from the upcoming 2nd
ed of Core JSF (about 15 pages)? I have an example with a Bill Pay dialog
that has a Wire Transfer subdialog. The data entered into the subdialog is
incorporated into the
As step 0 of SHALE-263 [1], here [2] is an initial cut of the
stylesheet for producing the needed SCXML documents from Shale dialog
configuration files. That directory [2] also contains the result of
styling the dialog-config.xml that comes with the Shale usecases
application (log on / edit
On 8/25/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 8/25/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
I would like to propose a best practice for the name attribute used in
various bits of the XML vocabulary for Shale dialogs that recommends
restricting these to alphanumeric characters
On 8/25/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 8/25/06, Paul Spencer [EMAIL PROTECTED] wrote:
An advantage with the current dialog.data bean is that it allows a the
use of a common view when the underlying data objects are different. How
would this be done with dialog managed
On 8/25/06, Sean Schofield [EMAIL PROTECTED] wrote:
I have few initial concerns after looking over the excellent
documentation and examples on the Commons SCXML site.
So far, my concerns are as follows:
1.) I'm not wild about having to run an XSL transform on dialogs
during compile time
snip/
On 8/25/06, Craig McClanahan [EMAIL PROTECTED] wrote:
Rahul,
I'm trying to set up a quick Shale Sandbox project where we can experiment
with the SCXML integration we've been discussing on the Shale Dev list.
snip/
Cool, should be fun.
I notice that you've released version 0.5, but I don't
On 8/30/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
I'll be able to pick this up tonight and play with it. Can someone remind
me of the syntax to change the eol properties on the existing files?
snap/
svn propset, see:
http://svnbook.red-bean.com/en/1.0/re23.html
-Rahul
Craig
On 8/30/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 8/28/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Correct, that schema is immutable as far as we're concerned. And for
obvious reasons, since we can't really model an on-exception
transition attribute in a UML state chart (its too Java
On 8/30/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 8/30/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Some notes from looking at the dialog2 sandbox modules:
a) Dealing with failures in:
Context#advance(FacesContext, String)
It is possible that advancing a dialog might fail (say
On 8/30/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 8/30/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
The init and destroy commands for the Shale dialog configs will need
to have mods for dialog2 (atleast init).
Should we copy them over to the sandbox so we can work with them? Need
On 9/1/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Fri Sep 1 19:57:25 2006
New Revision: 439525
URL: http://svn.apache.org/viewvc?rev=439525view=rev
Log:
Per discussion on the dev list, make dialog and state names omit
embedded spaces.
Modified:
auth group, so I should be all set there.
-Rahul
Sean
On 9/5/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Just returning from a trip, and a few days behind on email, so sorry
if I misunderstood anything about the sandbox karma proposal. It
appears that it is now open to existing Apache
On 9/9/06, Craig McClanahan [EMAIL PROTECTED] wrote:
Sean's changes fo the dialog2 sandbox implementation in r440205 includes the
following change that I object to:
---
shale/sandbox/shale-dialog2/src/main/java/org/apache/shale/dialog2/faces/Dialog2NavigationHandler.java
(original)
+++
(top-posting on purpose)
And no action states to stuff in dialog data makes things cleaner still !
As an aside, I've restored 1.4 source compatibility for the
shale-dialog2-legacy module. I believe that any module that doesn't
inherently need tiger features should stay at 1.4 source.
Can a
On 9/11/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip-entire-email/
:-)
PS: Now, on to getting the SCXML implementation up to date with the API
changes ...
snap/
Should be more or less there now. I've created a test app for the
SCXML bits as well, all feedback on that is welcome.
for developing speech
applications. One thing iam not clear on is the Shale+SCXML engine
integration architecture, I will try looking at the code.
Thanks
Jayant
-Original Message-
From: Rahul Akolkar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 12:40 PM
To: dev
On 9/12/06, Craig McClanahan [EMAIL PROTECTED] wrote:
As Shale moves towards maturity, one of the usability issues on my mind is
the set of dependencies that we currently mandate in shale-core and
friends.
snip/
The thread will be interesting in more than one ways ... in addition
to the
On 9/14/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 9/14/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 9/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Thu Sep 14 14:34:35 2006
New Revision: 443481
URL: http://svn.apache.org/viewvc?view=revrev=443481
On 9/26/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi
Yes, I did indeed build the framework first.
snip/
OK, shale-parent should dictate the version. I svn up'ed everything
and clean install'ed in sequence.
-Rahul
Hermod
-Original Message-
From: Rahul Akolkar [mailto:[EMAIL
On 9/26/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 9/25/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 9/26/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi
I am also getting an error when I try to build the sandbox componente
from the top:
[INFO] Error building POM (may
the
parent has chosen the version (1.1.4) which should simply continue to
hold.
-Rahul
[1] http://svn.apache.org/repos/asf/shale/maven/trunk/master-pom/pom.xml
Hermod
-Original Message-
From: Rahul Akolkar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 26, 2006 8:50 AM
To: dev
On 9/26/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi
Now it build (almost) ok. Got build errors on shale-test-dialog2-legacy:
snip/
Thats a good sign. clean install shale-apps. Then retry sandbox.
-Rahul
Compiling 5 source files to E:\Apache\Shale\sandbox\shale-test-dialog2-legacy\ta
The code review tool flags the instance variable data (the dialog
data) being declared as an Object, in relevant places in both the
basic and scxml impl. While we do document the fact that dialog data
should be Serializable, we do not enforce that in code. Any downside
to changing the type of
Here's the abbreviated reactor summary on the framework build:
[INFO] Shale Test Framework
[INFO] Shale Core Library
[INFO] Shale Application Controller Support
[INFO] Shale Clay Plugin
[INFO] Shale Dialog Manager Integration
[INFO] Shale Dialog Manager (Basic Implementation)
[INFO] Shale Dialog
On 10/13/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 10/13/06, Craig McClanahan [EMAIL PROTECTED] wrote:
One caution on the unused imports warnings ... Checkstyle does not
consider a javadoc comment like [EMAIL PROTECTED] Foo} to be a use, but
Javadoc
cannot create a correct link unless you
On 9/25/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Someone on IRC brought up a good point about the Shale home page: We
don't say what Shale *is* until 1/3 of the way down the page.
I think the information in the paragraph that starts Thus, Shale
is... belongs up at the top of the page.
I've changed the artifact names as outlined below.
-Rahul
On 10/13/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
How about ditching the library, support and plugin qualifiers? How
does this look:
[INFO] Shale Test Framework
[INFO] Shale Core
[INFO] Shale Application Controller
[INFO
On 10/18/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 10/18/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: rahul
Date: Wed Oct 18 13:49:36 2006
New Revision: 465366
URL: http://svn.apache.org/viewvc?view=revrev=465366
Log:
Adding props that should've been part of r465311 and
PROTECTED]:
On 10/18/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 9/25/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Someone on IRC brought up a good point about the Shale home page: We
don't say what Shale *is* until 1/3 of the way down the page.
I think the information
On 10/19/06, Craig McClanahan [EMAIL PROTECTED] wrote:
I've been fleshing out the front page docs of several of the new
subproject modules[1][2][3], but on the actual site these pages don't have
the overall banner and logo that the front page has. Shouldn't they?
snip/
There is supposed to be
On 10/18/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: gvanmatre
Date: Wed Oct 18 16:37:05 2006
New Revision: 465422
URL: http://svn.apache.org/viewvc?view=revrev=465422
Log:
This is a fix for the Clay implicit anchored tag mapping that was not assigning
the href to the component's
On 10/20/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 10/20/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Unrelated question, but subject still applicable:
Is the site updated manually (mvn site-deploy) or nightly? If
manually, any caveats to be aware of?
We're sharing the Continuum instance
On 10/20/06, Gary VanMatre [EMAIL PROTECTED] wrote:
From: Rahul Akolkar [EMAIL PROTECTED]
On 10/18/06, [EMAIL PROTECTED] wrote:
Author: gvanmatre
Date: Wed Oct 18 16:37:05 2006
New Revision: 465422
URL: http://svn.apache.org/viewvc?view=revrev=465422
Log:
This is a fix
On 10/20/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 10/20/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 10/20/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Unrelated question, but subject still applicable:
Is the site updated manually (mvn site-deploy) or nightly? If
manually, any
On 10/20/06, Gary VanMatre [EMAIL PROTECTED] wrote:
From: Rahul Akolkar [EMAIL PROTECTED]
snip/
I was actually mentioning the missing ASF license header (that should
be at the top of source files) in that comment. As far as svn props
are concerned, I add keywords to (java) test cases
On 10/23/06, James Mitchell [EMAIL PROTECTED] wrote:
Wendy or anyone who knows...
I added the maven config to shale-tiger and shale-apps/shale-sql-
browser a while back, but I can't seem to figure out how to have
those as part of the assembly...
Here's what I do now:
$ cd shale/framework/
Replying to the most relevant list ...
On 10/25/06, Kito D. Mann [EMAIL PROTECTED] wrote:
Hello,
I'm currently looking for people who are interested in writing great
articles for JSF Central about MyFaces, Tomahawk, Tobago, Trinidad, or
Shale. If you're interested, please reply!
snip/
I'd
On 10/26/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi Guys,
I know the main focus, or one of the main points of a 1.0.4 was the
dialog manager.
I saw that Craig/Raul were active on that.
Is there any timeframe when you guys like to go with a new release ?
snip/
I need a week to wrap
On 10/29/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 10/27/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 10/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
We have a jul Logger and a JCL log in oasv.CommonsValidator
We're still using JCL elsewhere, so unless there is an
all
Getting failures for cobertura directories in modules (for example:
shale-core). Probably need Sean (schof) to g+w them, whenever he sees
this.
-Rahul
On 11/7/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 11/7/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Getting failures for cobertura directories in modules (for example:
shale-core). Probably need Sean (schof) to g+w them, whenever he sees
this.
Sean owns them because it's his key
On 11/8/06, Craig McClanahan [EMAIL PROTECTED] wrote:
I'm setting up a clean build environment to get rid of some wierd ghosts in
my environment, and just checked out a fresh set of Shale sources (and a
clean Maven2 repository). When I get to the shale-tiles build, I get the
following error:
On 11/10/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
SHALE-230 -- Restore publishing the dialog_1.0.dtd file (and any other DTDs
defined by Shale)
snap/
Note to self: Drop in a DTD for the dialog-config in SCXML dialogs for
a validating digester.
Up For Grabs:
SHALE-286 --
On 11/11/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 11/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Fri Nov 10 20:16:19 2006
New Revision: 473638
URL: http://svn.apache.org/viewvc?view=revrev=473638
Log:
Partial fix for cleaning up static resources
On 11/13/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
6.0.1 -- Cannot use the manager app at all because the tomcat-users.xml file
gets wiped out (I filed a Tomcat bug on this one). Also get JSP errors when
trying to run the app manually ... this is likely due to either more Tomcat
On 11/13/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
AHA ... just figured out what we are doing differently. The
shale-dialog-basic library registers two resources (embedded in the jar
file) for the 1.0 and 1.1 DTDs of a dialog configuration resource. The
shale-dialog-scxml library
On 11/15/06, THOMAS, JAYANT (SBCSI) [EMAIL PROTECTED] wrote:
Thanks, That is what I want , say for example I might have a bunch of
higher level states from where at certain point I can navigate to child
states defined in another xml like popup.xml, it will be nice If I can
navigate from Wizard
, please ping the user list (Shale or
Commons, as you find appropriate). Thanks.
-Rahul
[1] http://people.apache.org/builds/shale/nightly/
[2] http://people.apache.org/builds/jakarta-commons/nightly/commons-scxml/
Thanks
Jayant
-Original Message-
From: Rahul Akolkar [mailto:[EMAIL PROTECTED
On 11/14/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 11/13/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
AHA ... just figured out what we are doing differently. The
shale-dialog-basic library registers two resources (embedded in the jar
file) for the 1.0 and 1.1 DTDs of a dialog
On 11/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Fri Nov 10 20:16:19 2006
New Revision: 473638
URL: http://svn.apache.org/viewvc?view=revrev=473638
Log:
Partial fix for cleaning up static resources at application shutdown
(SHALE-274) for the basic implementation.
(replying to dev, though I think these get picked up in JIRA eventually)
On 11/17/06, Craig McClanahan (JIRA) [EMAIL PROTECTED] wrote:
[ http://issues.apache.org/struts/browse/SHALE-337?page=all ]
Craig McClanahan resolved SHALE-337.
Fix
On 11/19/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
(replying to dev, though I think these get picked up in JIRA eventually)
On 11/17/06, Craig McClanahan (JIRA) [EMAIL PROTECTED] wrote:
[ http://issues.apache.org/struts/browse/SHALE-337?page=all ]
Craig McClanahan resolved SHALE-337
On 11/28/06, Niall Pemberton [EMAIL PROTECTED] wrote:
The Aquiring Shale section on the building page points to the Struts
download page (and mentions the struts subversion repository) for
checking out the source:
http://shale.apache.org/building.html
snip/
Thanks, should be fixed [1] by
On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Mon Dec 4 13:25:07 2006
New Revision: 482364
URL: http://svn.apache.org/viewvc?view=revrev=482364
Log:
First round of supporting events when DialogContextManager.create() or
DialogContextManager.remove() is called.
On 12/4/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/4/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 12/4/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Mon Dec 4 13:25:07 2006
New Revision: 482364
URL: http://svn.apache.org/viewvc?view=revrev=482364
On 12/13/06, Greg Reddin [EMAIL PROTECTED] wrote:
My project at work is finally in a place where we really need to use
Shale :-) The 1.0.3 release does not work out of the box for us
because we are using MyFaces 1.1.5 and Shale 1.0.3 depends on MyFaces
1.1.1. Shale 1.0.4-SNAPSHOT does not. So
On 12/15/06, Greg Reddin [EMAIL PROTECTED] wrote:
On Dec 15, 2006, at 10:38 AM, Rahul Akolkar wrote:
In terms of 1.0.4-SNAP JIRA issues, I will be fixing SHALE-348 this
weekend once I'm done traveling -- that leaves us with SHALE-61. I
dropped the ball on that, and ATM I don't think
On 12/15/06, Greg Reddin [EMAIL PROTECTED] wrote:
On Dec 15, 2006, at 10:38 AM, Rahul Akolkar wrote:
In terms of 1.0.4-SNAP JIRA issues, I will be fixing SHALE-348 this
weekend once I'm done traveling -- that leaves us with SHALE-61.
... also SHALE-211 [1]. I'm guessing we can close
On 12/15/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
Re: you guys tag teaming on RM for Shale ... +1! :-). The wiki has a
bunch of notes (mostly from Wendy) that I basically followed last time. A
couple of things to watch out for:
* The shale-master pom should be upversioned and
On 12/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Fri Dec 15 16:51:06 2006
New Revision: 487741
URL: http://svn.apache.org/viewvc?view=revrev=487741
Log:
Refine the dialog framework APIs as a foundation for improving handling of
browser navigation buttons:
*
Before we get to the master pom release:
Can we consider using scpexe:// URLs, or providing some way to do that?
As it stands, scp:// URLs don't work for me when I'm traveling (and
most of Dec. is travel). Background [1].
Before getting to the soution, it would help to get data points from
On 12/16/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/16/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
The subdialog issue doesn't exist in the Commons SCXML impl (its one
machine, rather than a stack of machines at runtime) -- ofcourse, the
downside is that IDs in the parent
On 12/16/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/16/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
Indeed, I think a common paradigm will be: do stuff on entry / undo on
exit. In which case, the onExit() from the previous view state and the
onEntry() into the new view state
On 12/16/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 12/16/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/16/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
Indeed, I think a common paradigm will be: do stuff on entry / undo on
exit. In which case, the onExit() from the previous
Figure we should get that going while we wrap up on 1.0.4 code,
otherwise a 72 hour buffer (at the least). I'm not aware of any
pending changes ATM, but if you have any, please go ahead.
Some procedural bits, yell if incorrect:
* I can't find the v1 tag (probably somewhere is Struts land, not
On 12/17/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/16/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Sounds like reasonable things to do :-) We even have a staging repo
defined in the master pom (thanks Wendy) which we should use for this.
By default if the version doesn't end in -SNAPSHOT
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote:
Just a question: are you keeping good notes as to what you're
doing? I'd like for the details of the process to end up on a wiki
page if they are not already there. After reading these messages I
have no clue what you are doing :-)
snip/
On 12/19/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/19/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
OK, if everyone's fine with that, I will create the 1.0 branch (called
SHALE_1_0_x unless there are better suggestions) when we get closer to
the release (after all 1.0.4-SNAP
On 12/19/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
* I like the habit I've seen Rahul and others do in Commons, of
adding contributor entries for those who have posted
patches. A quick scan of our issues might be useful.
snap/
This becomes hard after the fact. If we decide to
On 12/21/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/20/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Wed Dec 20 23:37:50 2006
New Revision: 489275
URL: http://svn.apache.org/viewvc?view=revrev=489275
Log:
Document the support for dealing with SHALE-61
On 12/22/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
This is a vote to release the tagged (and deployed) artifact above as version 2.
--8---
[X] +1
[ ] 0
[ ] -1, because ...
---
snap/
This vote is non-binding.
-Rahul
and participate.
-Rahul
On 12/22/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
In preparation for the framework release version 1.0.4, the Shale
Master POM has been updated:
http://tinyurl.com/ymy9ap (diff with v1)
tagged (long URLs below, may get fragmented):
http://svn.apache.org/repos/asf
On 12/26/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
Following a 24 hour buffer for reporting any counting errors, artifact
will be in the m2 rsync repo.
Thanks to those who took time to review and participate.
While I'm thinking of it... I
On 12/26/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
Back on track, will sign the pom, and will ask this list to verify it
before copying over. (BTW, is there a way to get m2 to sign?)
snap/
Done, I've added my signature to the master pom v2 in the staging
repo. My key is here [1
On 12/27/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
The md5 and sha1 checksums are fine. When I try to verify the signature,
though:
gpg --verify shale-master-2.pom.asc shale-master-2.pom
I get the Can't check signature: public
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
Yep ... that worked. I got the good signature and untrusted messages.
snap/
OK, so we're good to go on the master pom. Thanks.
I should have mentioned also what Wendy said ... we should follow the best
practice of maintaining
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/27/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 12/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Wed Dec 27 14:33:45 2006
New Revision: 490580
URL: http://svn.apache.org/viewvc?view=revrev=490580
Few thoughts:
1) Why is the dependencies section in the parent pom commented out?
Tempted to remove it.
2) We probably want to move designtime into a profile (can wait post 1.0.4).
3) There is some other cruft in the parent and remoting poms that I
intend to remove.
Objections to 1 or 3?
Branching tomorrow. Please speak up now if you want more time.
-Rahul
On 12/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/27/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
2) We probably want to move designtime into a profile (can wait post 1.0.4).
It should probably go back into the sandbox at the moment ... it's on my
list to work on in 2007
The permissions for the KEYS file [1] seem botched after being
restored from backup. Guess we'll need to ping #asfinfra ? (I'm never
on it though, anyone? TIA).
-Rahul
[1] http://www.apache.org/dist/shale/KEYS
For thread closure, this has been taken care of (thanks Craig).
-Rahul
On 12/28/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
The permissions for the KEYS file [1] seem botched after being
restored from backup. Guess we'll need to ping #asfinfra ? (I'm never
on it though, anyone? TIA).
-Rahul
On 12/28/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/28/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
Apps:
shale-blank-1.0.4.zip
shale-clay-usecases-1.0.4.zip
shale-mailreader-1.0.4.zip
shale-mailreader-jpa-1.0.4.zip
shale-sql-browser-1.0.4.zip
shale-usecases-1.0.4.zip
I'm done with changes to the release notes for now (commits@ list
seems to have a lag right now). Please jump in and improve them.
I have left one FIXME for any notable Clay changes that we may want to
list as was done for 1.0.3 (Gary?), but anything else worth mentioning
should go in section 3
On 12/29/06, Gary VanMatre [EMAIL PROTECTED] wrote:
From: Rahul Akolkar [EMAIL PROTECTED]
I'm done with changes to the release notes for now (commits@ list
seems to have a lag right now). Please jump in and improve them.
I have left one FIXME for any notable Clay changes that we may want
On 12/29/06, Gary VanMatre [EMAIL PROTECTED] wrote:
From: Rahul Akolkar [EMAIL PROTECTED]
On 12/29/06, Gary VanMatre wrote:
From: Rahul Akolkar
I'm done with changes to the release notes for now (commits@ list
seems to have a lag right now). Please jump in and improve them.
I
I did a dry run of the release artifacts (dry since its based on trunk
from earlier today, all versions are snaps):
http://people.apache.org/~rahul/shale/v104snap/ (m2 artifacts in repos)
If you get a chance, try inspecting a few artifacts, early feedback
would be great. Planning on using the
On 12/29/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 12/29/06, Wendy Smoak [EMAIL PROTECTED] wrote:
snip/
The first thing I notice is that there are no version numbers in the
filenames. I expected to see shale-framework-1.0.4-SNAPSHOT.zip, etc.
I manually removed the version number
No pending issues against 1.0.4 snap in JIRA ATM (the couple of open
ones are sufficiently addressed IMO), so pending ~24 hours for any
feedback on the dry run (let me know if you need more time), I will
move towards a final set of proposed artifacts (and a vote).
-Rahul
On 12/31/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/31/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
No pending issues against 1.0.4 snap in JIRA ATM (the couple of open
ones are sufficiently addressed IMO), so pending ~24 hours for any
feedback on the dry run (let me know if you need
The SHALE_1_0_X branch [1] has been created. Over the next day, it
will be used to prepare the proposed v1.0.4 artifacts and svn tag.
My preference would be to have no commits to the branch when releases
are being prepared and voted on (relevant commits to trunk that need
to be backported can
On 1/1/07, Craig McClanahan [EMAIL PROTECTED] wrote:
On 1/1/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
snip/
More generally, I propose we have the following procedure for future
releases:
(1) At the appropriate time, the RM declares a code freeze on the
relevant branch
(2) Development
On 1/1/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: craigmcc
Date: Mon Jan 1 14:58:04 2007
New Revision: 491671
URL: http://svn.apache.org/viewvc?view=revrev=491671
Log:
Advance trunk version numbers from 1.0.4-SNAPSHOT to 1.1.0-SNAPSHOT now that
1.0 has been branched. SHALE-383
On 1/4/07, Sean Schofield [EMAIL PROTECTED] wrote:
Thanks to Rahul for all the grunt work to pull this release together!
+1 for that sentiment!
Sorry I haven't been much help lately. I'm just getting my business
off the ground these days so I've been tied up with that and some
family stuff.
about what works together.
-= Gregg =-
Rahul Akolkar wrote:
On 12/29/06, Greg Reddin [EMAIL PROTECTED] wrote:
From: Rahul Akolkar [EMAIL PROTECTED]
Date: Thu, December 28, 2006 4:56 pm
To: commits@shale.apache.org
The above
On 1/5/07, Craig McClanahan [EMAIL PROTECTED] wrote:
snip/
What should also happen here is attribution in the NOTICE.txt file for
shale-tiger module too ... I'll look into the appropriate wording for that
and commit something soon.
snap/
OK, I will be cutting the new artifacts in ~8 hours
1 - 100 of 149 matches
Mail list logo
