On 5/31/06, Gary VanMatre <[EMAIL PROTECTED]> wrote:
I have a couple more variations of the rolodex usecase example in the works. I
agree that it would be good to pull Clay out of the core usecases. What ever
it takes to let maven do it's magic.
I would also like to setup a Clay mail reader
>From: "Craig McClanahan" <[EMAIL PROTECTED]>
>
> On 5/31/06, Gary VanMatre wrote:
> >
> > >From: "Wendy Smoak"
> > >
> > > On 5/31/06, Sean Schofield wrote:
> > >
> > > > I think the ultimate answer depends on whether we know for sure that
> > > > we want separate releases. It doesn't soun
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
Why don't we just make a struts-shale-mvn directory in the real ASF
repo. Just copy the existing struts-shale? As long as there is
nothing pressing (next 10 days or so) to check in, we can just work in
the copy. Then when we're happy we cu
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> Sean, why don't you go ahead and check in what you've got, and don't
> worry too much about recording the commands it took to get there
> exactly. With the test repo as a reference, we'll be able to figure
> it out.
>
> I don't want to los
Sean, why don't you go ahead and check in what you've got, and don't
worry too much about recording the commands it took to get there
exactly. With the test repo as a reference, we'll be able to figure
it out.
I don't want to lose momentum, and it's easier to discuss the project
structure when t
On 5/31/06, Gary VanMatre <[EMAIL PROTECTED]> wrote:
>From: "Wendy Smoak" <[EMAIL PROTECTED]>
>
> On 5/31/06, Sean Schofield wrote:
>
> > I think the ultimate answer depends on whether we know for sure that
> > we want separate releases. It doesn't sound like we know for sure so
> > maybe we sho
>From: "Wendy Smoak" <[EMAIL PROTECTED]>
>
> On 5/31/06, Sean Schofield wrote:
>
> > I think the ultimate answer depends on whether we know for sure that
> > we want separate releases. It doesn't sound like we know for sure so
> > maybe we should just stick with one shale/trunk. For MyFaces we
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
I think the ultimate answer depends on whether we know for sure that
we want separate releases. It doesn't sound like we know for sure so
maybe we should just stick with one shale/trunk. For MyFaces we had
as a goal to break out tomahawk fr
Argh... just so no one thinks I forgot about this... I've had to work
from home all this week for various unforeseen reasons, and of course as
a pessimist like myself would expect, the mostly working code got lost
since this weekend. Thought there was a copy on my thumb drive, but of
course no
Using "main" works for me if we want to go this way.
I would stay away from main b/c we have src/main/java when following
the maven convention. I would suggest core (again if we go this way.)
But, does "apps" really belong underneath "main" (I can see the logic on the
rest of them)? And, do
On 5/31/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
Using "main" works for me if we want to go this way.
But, does "apps" really belong underneath "main" (I can see the logic on the
rest of them)?
It either goes there, or it gets its own trunk and a separate release
cycle. I was already
On 5/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> Well design time is inherently linked to core. It makes no sense to
> release one without the other. With shale-test, you might in fact
> release that separately from core so if it has it
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
Well design time is inherently linked to core. It makes no sense to
release one without the other. With shale-test, you might in fact
release that separately from core so if it has its own trunk and set
of branches, that is easier to do.
If
I'm lost, though, with what you did in designtime. First you
suggested separate trunks for everything, and now you want designtime
(but not spring or tiles) underneath core?
Well design time is inherently linked to core. It makes no sense to
release one without the other. With shale-test, you
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
Separate question. How are you running these scripts? They seem to
imply you have access to the actual svn server.
No, it's just a list of commands that I executed on a local checkout.
Maybe we should use svn move http://svn.apache.org
On 5/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 5/31/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On 5/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > Do you forsee us needing to release them separately? I think the
> > single distribution with one version number is less confusing
Separate question. How are you running these scripts? They seem to
imply you have access to the actual svn server. Maybe we should use
svn move http://svn.apache.org ... That would be less confusing to
me.
I have a bunch more changes to make. Should I wait for a new copy of
the test repo? I
I can see a reason to have Clay and Test Framework on separate trunks,
but I'm not so sure that spring and tiles really need a separate
release cycle from core.
Well if we don't split out tiles and spring, whenever you release a
new core, you are going to release a new spring and tiles jar wheth
> Why a sub-project of core? It's a separate, optional jar, like
> shale-tiger. I think it belongs in shale/designtime as its own
> module.
I agree ... and, if I understood you correctly, switching to a Maven build
will require not only this, but also splitting up core into separate modules
fo
On 5/31/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
On 5/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Do you forsee us needing to release them separately? I think the
> single distribution with one version number is less confusing for
> users. Separate releases are less work individua
On 5/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> I bet this makes the core stuff work in Creator. OK I moved it to be
> a subproject of core-library and for now, its not automatically being
> built when you build core-library (since we'r
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
I bet this makes the core stuff work in Creator. OK I moved it to be
a subproject of core-library and for now, its not automatically being
built when you build core-library (since we're missing the jars.) I
also moved one of the test cases t
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
PS.
core-library tests are now compiling although there are several failures
Good news ... on further review, the test module's compile time dependency
on core is really conceptual rather than actual ... there is no import that
requires t
PS.
core-library tests are now compiling although there are several failures
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I bet this makes the core stuff work in Creator. OK I moved it to be
a subproject of core-library and for now, its not automatically being
built when you build core-library (since we're missing the jars.) I
also moved one of the test cases to the proper location and modified
the script.
Suggest
I guess things depend on how often you envision the two modules
changing in the future. If test is more likely to change, you can
make the core ref in test be the
On 5/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> > You once explained how
This question is better suited for the User list.
-Ted.
On 5/31/06, Badrinath Punchagnula <[EMAIL PROTECTED]> wrote:
Hi,
Does Action Class uses Adapter patter?
Please explain me why it is Adapter patter?
I belive it is something to do with Business
Delegate patter.
Thanks
Badri
Hi,
Does Action Class uses Adapter patter?
Please explain me why it is Adapter patter?
I belive it is something to do with Business
Delegate patter.
Thanks
Badri
Send instant messages to your online friends http://in.messenger.yahoo.com
-
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> You once explained how you worked around something similar in MyFaces,
> any advice for this one?
Change the dependency in core-library to be a *released* version of shale-test.
That works, now that we have a released version. :) Thanks.
On 5/31/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
Is there any special reason for a designtime dir?
Can these be compiled with the source in src/main/java?
It's a separate artifact in the Ant build (shale-designtime.jar) so
it's a separate module in the Maven project structure. Is that wha
@Craig:
Is there any special reason for a designtime dir? Can these be
compiled with the source in src/main/java? If not, we can deviate
from m2 defaults and specify this additional source directory but
maven is happier if you stick with its standard layout.
Sean
On 5/30/06, Sean Schofield <[
No, I meant that they won't let me connect my laptop to the network,
even though there is a separate network line specifically for
contractors to use. Freaking paranoid PHB!!
So, I do my work on my MacBook Pro (using Eclipse WTP and Tomcat
5.5.17), then copy it over to a thumb drive, then
I got through most of the Action1 site last night, and will try to
make a final pass tonight.
On 5/30/06, Ted Husted <[EMAIL PROTECTED]> wrote:
OK, I'm on it.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
You once explained how you worked around something similar in MyFaces,
any advice for this one?
Change the dependency in core-library to be a *released* version of shale-test.
Wendy
Sean
-
To unsubscribe, e-mail: [EMAIL PRO
34 matches
Mail list logo
