Do you have to be registered with the JCP as a corporation rather
than an individual to get that status?
On Jul 7, 2006, at 12:34 PM, James Mitchell wrote:
I sent in a request to be on the expert group under corporation,
since I am incorporated.
I would prefer to be a co-rep for Apache,
This looks good to me.
Greg
On Jul 17, 2006, at 12:57 AM, Craig McClanahan wrote:
As part of our transition to an Apache top level project (TLP), we are
obligated to submit a report to the ASF Board every month for the
first
three months, then quarterly thereafter. Here's what I am
I like that organization. Keep it as simple as possible and expand
on it if needed.
Greg
On Jul 17, 2006, at 10:11 PM, Wendy Smoak wrote:
On 7/16/06, Craig McClanahan [EMAIL PROTECTED] wrote:
Before doing so, it's probably worth spending some time figuring
out how we
want the source
On Jul 27, 2006, at 2:55 PM, Craig McClanahan wrote:
What do you think? Are we interested in putting this on our
roadmap? (And
following up +1s with code? :-)
+1. All I know about JSR-299 so far is that it is inspired by Seam.
All I know about Seam is what I heard from Gavin's
On Jul 29, 2006, at 7:30 PM, Sean Schofield wrote:
Is Shale a sourceforge project?
http://sourceforge.net/projects/shale
Looks like a graphical file mgr for Linux :-) And it appears to be
orphaned. At least there's nothing there.
Greg
On Aug 2, 2006, at 12:19 AM, Craig McClanahan wrote:
On 8/1/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 8/1/06, Craig McClanahan [EMAIL PROTECTED] wrote:
Somewhere in the changes over the last couple of days, the old
system
integration tests on apps like shale-blank (mvn -Pitest install)
, Greg Reddin [EMAIL PROTECTED] wrote:
+1. I was wanting to figure out what all that google open source
stuff was about anyway. But I'm cool with either google or
java.net.
I just set up shale-goodies for us at Google[1]. Note that you
must have
a GMail account to log in with for SVN
I think I prefer that too. shale.org doesn't appeal to me for some
reason I can't really put my finger on.
Greg
On Aug 4, 2006, at 2:03 PM, James Mitchell wrote:
I prefer com.google.shalegoodies
Your thoughts?
--
James Mitchell
678.910.8017
On Aug 4, 2006, at 11:30 AM, Sean
I'm cool with that too. It doesn't have to be a web address :-)
Greg
On Aug 4, 2006, at 2:47 PM, Wendy Smoak wrote:
On 8/4/06, Sean Schofield [EMAIL PROTECTED] wrote:
The only problem with com.google is if we move it from being
hosted on
google.com (a distinct possibility at this point.)
Attachment didn't seem to go through. Could you file a ticket? You
can send me the file directly I'll still have to open a ticket to
commit it.
Greg
On Aug 8, 2006, at 4:25 PM, David Geary wrote:
I've attached an HTML file that documents Shale Remoting. It would
be nice if some kind
On Aug 8, 2006, at 7:00 PM, Wendy Smoak wrote:
The space naming convention would probably give us SHLx___
Do we want to have just one space, and use it like we use Moin, or do
we want to push most of the project docs to the wiki?
I don't know anything about Confluence so I can't comment on
On Aug 30, 2006, at 6:26 PM, Sean Schofield wrote:
I agree with locking the page down. I don't have any problem with the
system as proposed but I think we should add a second round of voting.
Lets shorten the initial vote to 7 days. If you miss out on the
voting in the first round there's
On Aug 30, 2006, at 11:19 PM, James Mitchell wrote:
One thing that isn't 100% nailed down is the actual voting. Do we
want to post our votes to [EMAIL PROTECTED] Or [EMAIL PROTECTED] Or setup a quick web-
based poll to keep the votes hidden until the time expires.
I think all votes
+1
On Sep 28, 2006, at 8:41 PM, Craig McClanahan wrote:
The work we've done on the dialog support in the sandbox is showing
clear
earmarks of success. We can now support 100% of the functionality
that
actually works in the original implementation, plus have addressed
a number
of
On Oct 2, 2006, at 6:42 AM, Gregg Leichtman wrote:
I solved the problem. I ended up having to wrap all non JSF tags
within
each tile with verbatim tag pairs. This is definitely far from
elegant,
but I guess this is necessary until the JSF 1.2 version of MyFaces
emerges.
I was afraid
On Oct 18, 2006, at 5:46 PM, David Geary wrote:
If not working on it, I've been thinking about the homepage lately,
and it
strikes me that I don't really know how to spin Shale. We have so many
unrelated features that it's difficult to say Shale is The
addition of
JPA makes things even
://issues.apache.org/struts/browse/SHALE-321
Project: Shale
Issue Type: Bug
Components: Tiles
Affects Versions: 1.0.4-SNAPSHOT, 1.0.5-SNAPSHOT, 1.0.6-SNAPSHOT
Reporter: Greg Reddin
Assigned To: Greg Reddin
Priority: Blocker
Fix
On Nov 6, 2006, at 3:45 PM, Wendy Smoak wrote:
Well, no, since I just published a snapshot. :) IMO, the snapshot
repo should always have the latest-- Continuum ought to be publishing
a new one every time code is checked in, or at least nightly.
On [EMAIL PROTECTED], we've talked about
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 I started looking to see
where we stand on
On Dec 14, 2006, at 3:42 AM, Craig McClanahan wrote:
It's just what the POM says, but I don't know how to override it. In
1.1.1 MyFaces used the myfaces groupId and now they use
org.apache.myfaces. Because of this Maven doesn't know that my
dependency on MyFaces 1.1.5 should override Shale's
On Dec 14, 2006, at 8:53 AM, Niall Pemberton wrote:
As the shale-tiles module has no dependency on the rest of shale and
can be used in a vanilla JSF environment wouldn't it make more sense
to move this to the proposed Tiles project? I think the argument for
having JSF support in Tiles is
On Dec 14, 2006, at 9:22 AM, Wendy Smoak wrote:
Yes, shale-master is released independently. It has to be released in
advance of the framework so we don't have a snapshot as a parent.
Oh, I see. When I first looked at it I couldn't find a version number.
shale-parent.pom - The base POM
This issue appears to be fixed in Subversion.
https://issues.apache.org/struts/browse/SHALE-335
Is anything holding it up from being resolved?
Greg
On Dec 14, 2006, at 10:43 AM, Wendy Smoak wrote:
For the record, I'm for together. While there are some good
arguments for releasing components individually, and it might even be
easier from a technical standpoint, I think we'll have problems
explaining it to users. (I remember not wanting
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 there is any concrete
proposal towards it.
It looks like
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 that one. Any
objections?
Greg
[1]
On Dec 15, 2006, at 11:10 AM, Rahul Akolkar wrote:
... also SHALE-211 [1]. I'm guessing we can close that one. Any
objections?
snip/
Resolve it, at worst it will get re-opened. Its shouldn't affect the
release anyway, IMO.
Done :-)
Greg
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 :-)
Greg
On Dec 19, 2006, at 7:49 PM, Rahul Akolkar
On Dec 19, 2006, at 10:46 PM, Craig McClanahan wrote:
The updater
should be our long term direction, unless/until the Maven release
plugin
does all the stuff we need for staging votes.
What's missing in the release plugin? Just that there's no way to
stage a release? Do we use the
On Dec 20, 2006, at 2:51 PM, Craig McClanahan wrote:
* Since the trunk is being continuously built by Continuum,
trying to do our release cutting there (including removing
SNAPSHOT from the version numbers) would cause Continuum
to publish a release, with the real version number, before
we
The Shale project currently does not have a bylaws document. I
propose that we adopt the Struts bylaws[1] as the basis for our own
bylaws document and make changes in the following areas:
1. Change all instances of Struts to Shale.
2. Discuss the Subprojects section. Specifically, do we
On Dec 20, 2006, at 7:54 PM, Wendy Smoak wrote:
On 12/20/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote:
So the first thing we'd do when we decide to release is - after
finishing up business - start a branch for the release. Then we
work
On 12/31/06, Craig McClanahan [EMAIL PROTECTED] wrote:
We had talked earlier about the idea of doing quality rankings on the
individual packages separately, so that we'd have a chance to grant a GA
quality vote on some remaining portion other than shale-tiles. If we
still
feel this way, I'd
On 1/15/07, Kailas Lovlekar [EMAIL PROTECTED] wrote:
Shale is listed at version 1.1.0
All the pom.xml files show 1.1.0-SNAPSHOT, not sure how 1.0.4 was
derived for next release.
I believe it's just an iteration. When we got 1.0.4 ready we renamed the
trunk to 1.1.0-SNAPSHOT expecting that
On 6/22/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 6/22/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
hi,
are there any plans for 1.1.0 release ?
As an aside, IMO its worthwhile to have a v1.0.5 as well so we can
attempt to go GA in the 1.0.x line. Opinions?
Agreed. I've been
On 6/22/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
SCENARIO A:
1.0.x -- JSF 1.1, no new features beyond v1.0.4
1.1.x -- JSF 1.1, seeded from current trunk
1.2.x -- JSF 1.2
SCENARIO B:
1.0.x -- JSF 1.1, no new features beyond v1.0.4
1.1.x -- JSF 1.2, seeded from current trunk
I'd be happy
On 7/11/07, Wendy Smoak [EMAIL PROTECTED] wrote:
[X ] +1 - Let's accept the contribution
[ ] -1 - We should not accept it because...
Greg
On 10/20/07, Kito D. Mann [EMAIL PROTECTED] wrote:
I sent out an e-mail to the Shale mailing list a week or so ago about the
possibility of merging Shale with MyFaces. Development of Shale has become
somewhat stale, and I'd rather see MyFaces pickup the pieces than have the
code base atrophy
On 10/21/07, Niall Pemberton [EMAIL PROTECTED] wrote:
This is one class[1] and despite what the shale-tiles pom[2] declares,
it doesn't relate to/depend on any other parts of shale - just JSF and
Tiles. So it could just as easily be moved to the tiles TLP. Having
said that, I suggested this a
On 10/21/07, Craig McClanahan [EMAIL PROTECTED] wrote:
* Tiles Integration
See Clay.
+0 I'll abstain here and since I don't know much about the Tiles side of
things. Let's just say that I think Tiles integration should just work
in
MyFaces and Shale.
Likely relevant for
On Dec 19, 2007 4:32 PM, Rahul Akolkar [EMAIL PROTECTED] wrote:
Looks like the two remaining issues are the snapshot version of the
shale-master pom, and the Tiles dependency which is on an old
snapshot. Shale Tiles does not compile against any release of Tiles
2. Is anyone planning to
On Jan 2, 2008 6:25 PM, Gregg Leichtman [EMAIL PROTECTED] wrote:
Does the MyFaces view handler support JSF 1.2?
I'm ashamed to say I don't know what's changed in the ViewHandler API
between 1.1 and 1.2. If there are changes I suspect the current view
handler from MyFaces or Shale wouldn't be
On Jan 4, 2008 8:40 PM, Gregg Leichtman [EMAIL PROTECTED] wrote:
I consider this important, since I use Tiles and I want to and currently
am using JSF 1.2, since it resolves the interweaving problem among other
things. Granted, I could potentially move to Clay, but I came from
Struts and I am
On Feb 6, 2008 4:12 AM, samju [EMAIL PROTECTED] wrote:
* Seam similar architecture. Which Shale concepts did Seam implemented?
Was Shale created to elaborate JCreator?
Seam implements the annotations piece which is also in play for JSF
2.0. I think Seam also implements some of the concepts in
When I try to build shale at the root level (i.e. building all
subprojects) I get an error trying to build shale-core. It throws a
NoClassDefFoundError on ViewExpiredException (see error below). It
appears I'm somehow using a JSF 1.1 implementation. How should I go
about building with a JSF 1.2?
On Wed, Feb 20, 2008 at 4:37 PM, Greg Reddin [EMAIL PROTECTED] wrote:
When I try to build shale at the root level (i.e. building all
subprojects) I get an error trying to build shale-core. It throws a
NoClassDefFoundError on ViewExpiredException (see error below). It
appears I'm somehow
that his work has made it difficult for him to be as
involved as he once was. At his own request, Craig is now an emeritus
member of the Shale PMC.
Thank you,
Greg Reddin
Apache Shale PMC Member
On Wed, Feb 20, 2008 at 2:04 PM, Wendy Smoak [EMAIL PROTECTED] wrote:
On Wed, Feb 20, 2008 at 12:01 PM, Greg Reddin [EMAIL PROTECTED] wrote:
To get rid of the Tiles modules do you think it is sufficient to
simply remove the references from the POM or should we delete or move
the svn
I've fixed the build problems in the 1_0_X branch and completed the
extraction of the Tiles integration component. There are two
Clay-related tickets still posted to 1.0.5 [1] that don't seem
critical to me. I'd like to volunteer to be the RM for a 1.0.5 release
if everybody else is on board. I'm
Can someone doublecheck these two wiki pages and let me know if they
are out of date? Will I be ok using these as a guide? I noticed there
is no release plan page for 1.0.4. Was that intentional and/or should
I create one for 1.0.5?
http://wiki.apache.org/shale/ReleaseGuidelines
We got the mail three times - at least I did :-)
On Tue, Apr 1, 2008 at 1:37 AM, Torsten Krah
[EMAIL PROTECTED] wrote:
Something off-topic, i'll wrote the mail 3 times now and 2 got not delivered
because the list produces invalid mail headers (it inserts a reply-to header
instead of
On Mon, Mar 31, 2008 at 5:24 PM, Torsten Krah
[EMAIL PROTECTED] wrote:
I want to fix this bug 442 and want to ask some question here about doing
that, if thats ok, i'll hope so.
This is definitely the right place to discuss such fixes.
I'll fixed the decorator not to apply shales
This is the formal vote for the new Shale master POM version 3.
I would appreciate a thorough review of these artifacts since I am a
release manager newbie :-)
You can find the signed release candidate at [1].
Please vote
+1 if you reviewed the new master pom and approve of it
-1 if you found a
, 2008 at 11:29 AM, Greg Reddin [EMAIL PROTECTED] wrote:
On Wed, Apr 9, 2008 at 10:59 AM, Greg Reddin [EMAIL PROTECTED] wrote:
Please vote
+1 if you reviewed the new master pom and approve of it
-1 if you found a flaw or potential problem with the new master pom
I'll add my +1 as well
On Fri, Apr 18, 2008 at 6:58 PM, Rahul Akolkar [EMAIL PROTECTED] wrote:
I was hoping to just redo it. It has not been sync'ed yet so I'll just
svn rm the tag and the artifacts on the staging repo and to it over.
In case anyone's wondering, I'm still planning to continue the release
On Fri, May 2, 2008 at 10:42 AM, Paul Spencer [EMAIL PROTECTED] wrote:
Greg,
Thank you for the update.
For clarification, what are you artifacts are you planning on releasing in
the near future.
We are going to try to do a 1.0.5 release of the entire framework. But
there are a few changes
On Fri, May 2, 2008 at 2:02 PM, Rahul Akolkar [EMAIL PROTECTED] wrote:
I think the master pom is mostly ready for a vote (unless you're
having issues with the build due to any particular now-locked-down
plugin that you weren't having before).
No issues. I was just trying to decide whether
This is the formal vote for the new Shale master POM version 3. The
former vote for the same version was cancelled due to problems in the
POM. The POM was corrected and the release process was re-executed
since the previous release had not been copied to the main repository.
You can find the
On Mon, May 12, 2008 at 11:18 AM, Rahul Akolkar [EMAIL PROTECTED] wrote:
Its sometimes tedious to figure out why certain things are not
happening in the m2 build, but I think it'll be worthwhile spending
some time trying to fix this -- it will be a lot of work if you have
to manually sign
On Mon, May 12, 2008 at 10:48 AM, Greg Reddin [EMAIL PROTECTED] wrote:
Please vote
+1 if you reviewed the new master pom and approve of it
-1 if you found a flaw or potential problem with the new master pom
Here's my +1.
Anybody else care to vote on this one?
Greg
On Sat, May 17, 2008 at 11:44 AM, Wendy Smoak [EMAIL PROTECTED] wrote:
(I'm having trouble actually building Shale (test failures, problems
in the Tiger module, missing Cargo dependency?) but I see no reason to
hold up the master pom release.)
Is that occurring when building the trunk or the
The vote has passed with three binding +1s and no -1s. I will complete
the release process today and hopefully start on a 1.0.5 framework
release.
Thanks,
Greg
On Mon, May 19, 2008 at 9:03 AM, Greg Reddin [EMAIL PROTECTED] wrote:
On Sat, May 17, 2008 at 11:44 AM, Wendy Smoak [EMAIL PROTECTED
Just an update on the status of Release 1.0.5. I am unable to get the
apps to build unless I use the jsfri12 profile.
Using MyFaces doesn't seem to pull in all the needed Servlet/JSP
dependencies. We are back a version on MyFaces. I'll try to upgrade
that and see if it helps. If not, I can
On Thu, May 29, 2008 at 1:43 PM, Wendy Smoak [EMAIL PROTECTED] wrote:
I see that this is on a branch, is there also one on trunk? There
should be only one KEYS file for Shale, which is then published at
http://www.apache.org/dist/shale
Therre is a file on trunk and my key was already added
I just checked in a release notes document for the upcoming 1.0.5
release. Please let me know if you'd like changes to be made to it
before I proceed.
Thanks,
Greg
A set of artifacts for Shale 1.0.5 is now ready. Please review the
artifacts mentioned below and vote accordingly. Since this is my first
time as release manager I wouldn't be surprised if something is
missing or if I've included things that shouldn't be included, so I'd
appreciate as thorough a
On Wed, Jun 4, 2008 at 10:00 AM, Paul Spencer [EMAIL PROTECTED] wrote:
-1 The copyright date in the notice file is 2007 instead of 2008
Aside from the copyright date, noted above, I only verified that notice.txt,
manifest.mf and license.txt existed
I'll have a look at that.
The artifact
This is a resubmit of the Shale 1.0.5 release vote. (Sorry for the
delayed posting). I've modified the set of artifacts to the list below.
(1) The repository has been tagged here (I did not modify the tag):
http://svn.apache.org/repos/asf/shale/framework/tags/SHALE_1_0_5/
(2) The Maven
On Sat, Jun 7, 2008 at 10:44 PM, Greg Reddin [EMAIL PROTECTED] wrote:
--8
[X] +1 Release these artifacts as Shale 1.0.5
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released
On Mon, Jun 16, 2008 at 10:12 AM, Gary VanMatre [EMAIL PROTECTED] wrote:
+1 Release these artifacts as Shale 1.0.5
Assuming Rahul's +1 from the previous vote thread still holds the vote
passes and Shale 1.0.5 is ready to be released. As soon as I can find
the time I will complete the release
On Wed, Jun 25, 2008 at 11:39 AM, Paul Spencer [EMAIL PROTECTED] wrote:
Great!
I have not been able to test the current 1.0.5 release. Assuming the issues
I brought up in the prior 1.0.5 have been resolved, I would +1 this release.
IIRC your objections were related to a 2007 copyright date.
On Wed, Jun 25, 2008 at 2:37 PM, Rahul Akolkar [EMAIL PROTECTED] wrote:
Absolutely. All aboard, let 'er sail :-)
Sorry for disappearing for a few weeks. I have just copied the dist
artifacts to the dist directory and the Maven artifacts to the Maven
dist directory. I'll update the site
On Fri, Aug 29, 2008 at 11:11 PM, Kito D. Mann [EMAIL PROTECTED] wrote:
So, I see that the download link on the Shale home page actually points to
1.05, so that part is at least complete :-). I think the site and maven
artifacts still need to be pushed out, though...
That's right. THe site is
On Mon, Sep 29, 2008 at 6:22 PM, Kito Mann [EMAIL PROTECTED] wrote:
That's fine, but I don't really see _anyone_ driving releases :-). What's
the problem with letting Shale Test move somewhere else?
The problem, though, is that Shale Test is part of a project that has
stagnated. So,
Welcome, Paul! Glad to have you here.
Greg
On Thu, Oct 2, 2008 at 10:31 PM, Gary VanMatre [EMAIL PROTECTED] wrote:
Please join me in welcoming Paul Spencer as the newest Shale committer. Paul
has been very supportive of the Shale community over the past year. Paul is
also a member of the
On Mon, Oct 20, 2008 at 10:49 AM, Gary VanMatre [EMAIL PROTECTED] wrote:
I'd rather see the Shale community grow this library and the Shale project.
However, if the communities feel that the only way we can find volunteers to
contribute to its ongoing growth (seems a bit snobbish) is to
On Wed, Oct 22, 2008 at 10:45 AM, Simon Lessard
[EMAIL PROTECTED] wrote:
If the base
test classes don't get moved to MyFaces, then we're more or less condemning
MyFaces API to wait for RI to be released so that Shale-test can depend on
it to be updated to 2.0 API, or forcing MyFaces API to
If you have only 30 seconds to read this;
Join us in celebrating the ASF's 10th Anniversary at ApacheCon!
The Call for Papers is now open for ApacheCon US 2009, taking place 2-6
November in Oakland, California. Proposals are being accepted at
http://us.apachecon.com/c/acus2009/cfp/ and can be
On Tue, Dec 9, 2008 at 6:20 AM, Paul Spencer [EMAIL PROTECTED] wrote:
I am building Shale 1.1.0-SNAPSHOT with JDK 1.5.0_16-b06-284. The test on
Shale-Core are failing with the following error:
testPristine(org.apache.shale.util.TokenProcessorTestCase) Time elapsed:
0.038 sec ERROR!
The Travel Assistance Committee is now accepting applications for those
wanting to attend ApacheCon EU 2009 between the 23rd and 27th March 2009
in Amsterdam.
The Travel Assistance Committee is looking for people who would like to
be able to attend ApacheCon EU 2009 who need some financial
ApacheCon EU 2009 registration is now open!
23-27 March -- Mövenpick Hotel, Amsterdam, Netherlands
http://www.eu.apachecon.com/
Registration for ApacheCon Europe 2009 is now open - act before early
bird prices expire 6 February. Remember to book a room at the
://attic.apache.org.
You can follow the progress of the move at
https://issues.apache.org/jira/browse/ATTIC-2 if you so wish.
On behalf of the Apache Shale PMC, Thanks!
Greg Reddin
82 matches
Mail list logo
