://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
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 Möve
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 support
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
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 rev
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
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 t
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
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.
On Wed, Sep 24, 2008 at 2:53 PM, Kito Mann <[EMAIL PROTECTED]> wrote:
> Hello everyone,
>
> At JSFOne we were discussing Shale Test, and again the idea of moving it out
> of Shale popped up. With so little activity in the Shale project, I'd like
> to bring up the issue of migrating it to MyFaces pr
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
Where's the best place to manage the site? I noticed that the site
source in the trunk is different from that in the 1_0_X branch. I was
trying to get the site ready to deploy now that 1.0.5 is finished and
before I make an announcement. But I'm not sure whether to deploy the
trunk site or the bran
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 tomor
On Tue, Jul 22, 2008 at 12:06 PM, <[EMAIL PROTECTED]> wrote:
> Hi, I contacted Craig to know something about Shale 1.1. He talk about
> the 1.1 version is in the trunk. Is the same trunk you are using for
> version 1.0.5?
No, Shale 1.1 is in svn here:
http://svn.apache.org/repos/asf/shale/fr
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 d
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 p
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
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 artifacts
On Thu, Jun 5, 2008 at 2:53 PM, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> 1) The *test* artifacts aren't meant to be distributed via releases,
> or used for anything beyond local testing, IIRC. (the usecases apps
> are meant to demo features). I would prefer we leave them out, to
> avoid many diff
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 artifa
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 re
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
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
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 include
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 Smoa
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
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 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
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 signe
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 whe
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 ch
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 relea
On Fri, Apr 18, 2008 at 3:19 PM, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
>
> None, thanks for doing this. If the master pom v3 hasn't been sync'ed
> to central, I don't mind doing a take 2 on it (otherwise we can move
> on to v4).
I was hoping to just redo it. It has not been sync'ed yet so I'
, 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 th
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.
Just a note: I'm leaving
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
I'm preparing to call a vote to release the master POM. I started
manually doing things because there was a thread some time ago saying
the maven release plugin wasn't usable for this. I'm thinking maybe
that has changed. Should I back out my changes and use mvn release to
do the job or am I on the
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 val
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 rep
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
http://wik
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 n
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 P
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 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
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? I'
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 tree as well?
Greg
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 concept
Shale is an open source project. It will never *die* unless the ASF
dies or kills it and nobody copies the code over to some other
repository. That's one of the main reasons we like open source. It's
not dependent on the existence of any person, company, or
organization.
It's funny how the discuss
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 an
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 c
et in it :-)
Thanks,
Greg
On Jan 2, 2008 9:02 AM, Gary VanMatre <[EMAIL PROTECTED]> wrote:
> From: "Antonio Petrelli" <[EMAIL PROTECTED]>
>
> > 2007/12/26, Greg Reddin :
> > > I'd like to propose that we discontinue support for the Shale-Tiles
&g
I'd like to propose that we discontinue support for the Shale-Tiles
component. I've spent some time looking at the TilesViewHandler over
the last week or so and comparing it to the TilesTwoViewHandler that
is unreleased, but is part of the MyFaces Tomahawk project. The
conclusion I've come to is th
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 plan
On 10/22/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
>
> Tiles works with FreeMarker and Struts 2 too. And sincerely I think that
> it
> could be used for JSF users, if it only gets more support (don't look at
> me,
> I don't know anything about JSF :-) ).
It could be used, but I'm not sure
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.
>
> Like
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
If this is turning into a vote we should specify what +1 and -1 means. Does
-1 mean "no, don't port it" or "no we have to have this"? :-)
Greg
On 10/21/07, Gary VanMatre <[EMAIL PROTECTED]> wrote:
>
> > * Application Controller
> > Don't know. I thought action oriented frameworks are outdated, th
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 at
On 10/5/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>
> Then actually that sounds like we should get a 1.0.5 out with the
> fixes people are waiting for, and then you can commit the potentially
> breaking changes and sort out the Tiles stuff.
That sounds like a good idea.
WDYT? We should really
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 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
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 be
On 1/23/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
I am pretty fine with a 1.0.5 instead of 1.0.4.1 ;)
Me too :-)
Greg
On 1/18/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
Continuum being on a break and permissions being jammed, this isn't
getting out to the site. But the 1.0.4 build has been out there for
over a week now ( download link in release notes [1] ), so please give
it a whirl towards making a quality
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 t
On 1/5/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
--8<
[X ] +1 (Binding) for PMC members only
[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released
--
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 s
On 12/29/06, Gary VanMatre <[EMAIL PROTECTED]> wrote:
Sounds nice but I love the snow. We don't get as much of it as you would
think
here in Denver. We are having one of those freakish back-to-back weeks of
blizzards (not the QD kind).
He, he. The DQ kind is all we get here in Arkansas :-
> From: "Rahul Akolkar" <[EMAIL PROTECTED]>
> Date: Thu, December 28, 2006 4:56 pm
> To: commits@shale.apache.org
>
> The above "projected quality" paragraph needs to be updated to reflect
> the current sentiment. Of the two items in that list, 1.0.4 will
> address most of the dialog issues (so I'
On Dec 20, 2006, at 7:57 PM, Craig McClanahan wrote:
On 12/20/06, Greg Reddin <[EMAIL PROTECTED]> wrote:
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
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 fo
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,
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
On Dec 20, 2006, at 2:01 PM, Rahul Akolkar wrote:
On 12/19/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
I would have a mild preference for naming the branch SHALE_1_0 but
I'm not
going to choke if we go with what you proposed either. I'm also
presuming
we'll create a tag (SHALE_1_0_4)
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 re
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 wrote:
On Dec 16, 2006, at 8:18 PM, Rahul Akolkar wrote:
Before getting to the soution, it would help to get data points from
folks who work with scp:// (does scpexe:// work, is it slower etc.).
Sorry for the belated response, but it works for me on the Mac. As
to the performance I don't really n
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?
Resolve it, at worst it will get re-opened. Its shouldn't affect the
release anyway, IMO.
Done :-)
Greg
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] https://issues.ap
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 co
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
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 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 .
Oh, I see. When I first looked at it I couldn't find a version number.
shale-parent.pom - The base POM for sh
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 diffe
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 Shal
On Dec 13, 2006, at 5:47 PM, Craig McClanahan wrote:
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.
Is it actually a hard dependency or just what the Maven POM says.
Can't say
that I have actually tried
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 p
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 switchi
-321
URL: http://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
Priorit
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 eve
On Oct 3, 2006, at 7:01 PM, Gregg Leichtman wrote:
I'm in the process of setting up to test this. I should have an answer
to this by the end of the week. I was hoping not to have to move to
the
RI, because I wanted access to the MyFaces extensions.
Sorry for my ignorance, but it seems like
On Oct 2, 2006, at 10:28 PM, Craig McClanahan wrote:
In general I suspect we'll just do overall releases (a.b.c) as a
matter of
course -- but we could release an a.b.c.d version of a particular
library,
say, to fix a security vulnerability or something.
That was my big question (that I ra
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 that
+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 outstandi
I'm pretty sure that if I try to publish the site the permissions or
something else will be wrong. Could someone else do this for me?
Thanks,
Greg
On Sep 5, 2006, at 9:24 AM, [EMAIL PROTECTED] wrote:
Author: greddin
Date: Tue Sep 5 07:24:21 2006
New Revision: 440352
URL: http://svn.apache
+1
On Aug 31, 2006, at 9:47 PM, Wendy Smoak wrote:
The Jakarta Commons sandbox is open [1] to any Apache committer who
expresses an interest in working there, and the Maven developers are
discussing [2] the addition of an open sandbox area for plugin
development.
I propose that we do the same,
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 shoul
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 sti
On Aug 30, 2006, at 12:22 PM, Craig McClanahan wrote:
One thing we should investigate ... can we lock down the wiki page
(i.e. no
more modifications) after the cutoff? If not, we'll need to copy
the set of
images over to some controlled-access page so that things don't
change out
under t
8/31 is coming tomorrow and people will soon be asking about the Logo
Contest I'm sure :-) This is a proposal of one possible way to
handle the voting.
* Create and publish a page somewhere on people.apache.org that lists
each entry and gives it a number. Why not do this on the wiki?
B
1 - 100 of 123 matches
Mail list logo
