You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Joe Germuska <Jo...@Germuska.com> on 2004/03/22 15:28:09 UTC

Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

>For me, the main discouraging thing about contributing to the 
>development of Struts has been the build process.  In the past, you 
>had to download all of jakarta-commons and spend a day or two 
>figuring out how to get that to build.  Recently, I tried to build 
>Struts and was successful using the Maven stuff.  Personally, I 
>don't mind using Maven, but I don't know that it should be 
>*required* to build a project from scratch.  I'd love to be able to 
>cvs co Struts, navigate to jakarta-struts and type "ant jar".
>
>I realize this is no easy thing to accomplish with a build file - 
>but it has been the most discouraging factor for me. ;-)

The only way we could accomplish something like that with a build 
file would be by including JARs in CVS, and if you ask me, there are 
enough reasons why that's a bad idea that I prefer the way it is, 
even though I'd very much like to see people feel more comfortable 
getting in and working on Struts source code.

When you say "I don't know that [Maven] should be *required*..." is 
your point that Ant is a widely accepted Java tool, while Maven has 
yet to cut a 1.0 release?  That's fair -- just want to make sure I 
understand you.

The build.xml file generated by 'maven ant' uses the ant 'get' task 
and the Maven iBiblio repository to download dependencies; we could 
perhaps look at copying some of that into our ant script to reduce 
build.properties to being more about configuration stuff and less 
about dependency stuff.

Joe

-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
       "Imagine if every Thursday your shoes exploded if you tied them 
the usual way.  This happens to us all the time with computers, and 
nobody thinks of complaining."
             -- Jef Raskin

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Michael McGrady <mi...@michaelmcgrady.com>.
I have a somewhat "nutty" suggestion.  I suggest that we have someone who 
is an "administrative" genius with a flair for teaching and simple 
statement be an available guide to assist new people in getting the proper 
builds to work on struts.  Such a person would, I predict, be worth 100 
times there weight in gold to this list.  How this should work is, of 
course, up for discussion.  Maybe, also, for some reason I don't know, this 
idea is a clunker.

Michael

At 06:28 AM 3/22/2004, you wrote:
>>For me, the main discouraging thing about contributing to the development 
>>of Struts has been the build process.  In the past, you had to download 
>>all of jakarta-commons and spend a day or two figuring out how to get 
>>that to build.  Recently, I tried to build Struts and was successful 
>>using the Maven stuff.  Personally, I don't mind using Maven, but I don't 
>>know that it should be *required* to build a project from scratch.  I'd 
>>love to be able to cvs co Struts, navigate to jakarta-struts and type 
>>"ant jar".
>>
>>I realize this is no easy thing to accomplish with a build file - but it 
>>has been the most discouraging factor for me. ;-)
>
>The only way we could accomplish something like that with a build file 
>would be by including JARs in CVS, and if you ask me, there are enough 
>reasons why that's a bad idea that I prefer the way it is, even though I'd 
>very much like to see people feel more comfortable getting in and working 
>on Struts source code.
>
>When you say "I don't know that [Maven] should be *required*..." is your 
>point that Ant is a widely accepted Java tool, while Maven has yet to cut 
>a 1.0 release?  That's fair -- just want to make sure I understand you.
>
>The build.xml file generated by 'maven ant' uses the ant 'get' task and 
>the Maven iBiblio repository to download dependencies; we could perhaps 
>look at copying some of that into our ant script to reduce 
>build.properties to being more about configuration stuff and less about 
>dependency stuff.
>
>Joe
>
>--
>Joe Germuska
>Joe@Germuska.com
>http://blog.germuska.com
>       "Imagine if every Thursday your shoes exploded if you tied them the 
> usual way.  This happens to us all the time with computers, and nobody 
> thinks of complaining."
>             -- Jef Raskin
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Michael McGrady <mi...@michaelmcgrady.com>.
I agree 100% with Matt and make the same prognostication.

At 06:46 AM 3/22/2004, you wrote:

>On Mar 22, 2004, at 7:28 AM, Joe Germuska wrote:
>
>>>For me, the main discouraging thing about contributing to the 
>>>development of Struts has been the build process.  In the past, you had 
>>>to download all of jakarta-commons and spend a day or two figuring out 
>>>how to get that to build.  Recently, I tried to build Struts and was 
>>>successful using the Maven stuff.  Personally, I don't mind using Maven, 
>>>but I don't know that it should be *required* to build a project from 
>>>scratch.  I'd love to be able to cvs co Struts, navigate to 
>>>jakarta-struts and type "ant jar".
>>>
>>>I realize this is no easy thing to accomplish with a build file - but it 
>>>has been the most discouraging factor for me. ;-)
>>
>>The only way we could accomplish something like that with a build file 
>>would be by including JARs in CVS, and if you ask me, there are enough 
>>reasons why that's a bad idea that I prefer the way it is, even though 
>>I'd very much like to see people feel more comfortable getting in and 
>>working on Struts source code.
>
>Right.  I include my JARs in CVS and I've been doing it for quite some 
>time with no issues.  To be honest, there doesn't seem to be much 
>difference in storing them in CVS vs. uploading them to a Maven 
>repository.  For me, it's often seemed easier to stick them in CVS.  Of 
>course, if I had managed to convert AppFuse to use Maven - maybe I 
>wouldn't be so bitter.  ;-)
>
>I do like to be able to checkout my CVS-based project and disconnect and 
>compile later though.  No internet dependency is a good thing.
>
>>
>>When you say "I don't know that [Maven] should be *required*..." is your 
>>point that Ant is a widely accepted Java tool, while Maven has yet to cut 
>>a 1.0 release?  That's fair -- just want to make sure I understand you.
>
>That's part of it - as well as Ant is easier to understand IMO.  I use 
>Maven on a couple projects, but I definitely prefer Ant - mainly b/c I 
>have an Ant build.xml file that I use on all my projects.
>
>>
>>The build.xml file generated by 'maven ant' uses the ant 'get' task and 
>>the Maven iBiblio repository to download dependencies; we could perhaps 
>>look at copying some of that into our ant script to reduce 
>>build.properties to being more about configuration stuff and less about 
>>dependency stuff.
>
>Whatever it takes to make Struts easier to build.  I guarantee that if you 
>can build Struts with an ANT_HOME (or MAVEN_HOME) and JAVA_HOME set - and 
>that's it - you'll get a lot more contributions.
>
>My $.02.
>
>Matt
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Matt Raible <li...@raibledesigns.com>.
On Mar 22, 2004, at 7:28 AM, Joe Germuska wrote:

>> For me, the main discouraging thing about contributing to the 
>> development of Struts has been the build process.  In the past, you 
>> had to download all of jakarta-commons and spend a day or two 
>> figuring out how to get that to build.  Recently, I tried to build 
>> Struts and was successful using the Maven stuff.  Personally, I don't 
>> mind using Maven, but I don't know that it should be *required* to 
>> build a project from scratch.  I'd love to be able to cvs co Struts, 
>> navigate to jakarta-struts and type "ant jar".
>>
>> I realize this is no easy thing to accomplish with a build file - but 
>> it has been the most discouraging factor for me. ;-)
>
> The only way we could accomplish something like that with a build file 
> would be by including JARs in CVS, and if you ask me, there are enough 
> reasons why that's a bad idea that I prefer the way it is, even though 
> I'd very much like to see people feel more comfortable getting in and 
> working on Struts source code.

Right.  I include my JARs in CVS and I've been doing it for quite some 
time with no issues.  To be honest, there doesn't seem to be much 
difference in storing them in CVS vs. uploading them to a Maven 
repository.  For me, it's often seemed easier to stick them in CVS.  Of 
course, if I had managed to convert AppFuse to use Maven - maybe I 
wouldn't be so bitter.  ;-)

I do like to be able to checkout my CVS-based project and disconnect 
and compile later though.  No internet dependency is a good thing.

>
> When you say "I don't know that [Maven] should be *required*..." is 
> your point that Ant is a widely accepted Java tool, while Maven has 
> yet to cut a 1.0 release?  That's fair -- just want to make sure I 
> understand you.

That's part of it - as well as Ant is easier to understand IMO.  I use 
Maven on a couple projects, but I definitely prefer Ant - mainly b/c I 
have an Ant build.xml file that I use on all my projects.

>
> The build.xml file generated by 'maven ant' uses the ant 'get' task 
> and the Maven iBiblio repository to download dependencies; we could 
> perhaps look at copying some of that into our ant script to reduce 
> build.properties to being more about configuration stuff and less 
> about dependency stuff.

Whatever it takes to make Struts easier to build.  I guarantee that if 
you can build Struts with an ANT_HOME (or MAVEN_HOME) and JAVA_HOME set 
- and that's it - you'll get a lot more contributions.

My $.02.

Matt


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


RE: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Gary D Ashley Jr." <Ga...@ToughGuy.net>.
> From: Matt Raible [mailto:lists@raibledesigns.com] 
> I don't care how things are partitioned in CVS, as long as everything 
> builds with one checkout and one command.

Along those lines, I'd like to suggest that a complete WAR and/or EAR of
examples be included as one command to checkout.  I'd even be happy to
roll up my sleeves and see about writing the maven/ant stuff to do it.
The idea behind this is to make it real simple for people to get the
example working to learn Struts.  By 1.  Download .war file.  2.  Place
in Tomcat deploy directory.  3.  See it work.  4.  Look at source
(bundled in war). 

The biggest complaint I get from my customers is they want a simple,
plain example of Struts to learn the basics.






---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Michael McGrady <mi...@michaelmcgrady.com>.
+1

At 03:15 AM 3/23/2004, you wrote:
>On Mon, 22 Mar 2004 23:49:31 -0800 (PST), Martin Cooper wrote:
> >> On the multi-repository projects I've worked on, we had a special
> >> repository  just for integration tasks like this.
> >
> > So we'd need yet another repo - say struts-integration - just for
> > this. Why is that better than just doing what we need within the
> > repo that we have already?
>
>Well, as you mentioned, another way to go would be for some one to write a 
>tool that could burst and rejar an arbitrary set of jars. (If one doesn't 
>already exist.) The source for such a tool could live in the core since 
>it's just something a volunteer would run offline and the upload. It 
>wouldn't be a true deliverable. And, I'm not convinced that we even need 
>to do such a thing. Even without a few extra JARs of our own, there are 
>still all the Commons JARs. (Though I suppose we could roll together those 
>too.) I'd tend to leave this for a end-user to do, say if there were 
>distributing a particular Struts distribution to several teams in an 
>enterprise. But it would be nice to provide a tool for this (if someone 
>had the itch to write it.) It really sounds like a job for Sun :)
>
>
>On Mon, 22 Mar 2004 20:50:24 -0800 (PST), Martin Cooper wrote:
> > I'd be open to it, but I think we have a lot of things we'd want to
> > do to get our own house in order before we actually take action on
> > this. I also think it might be a tricky issue in some respects. For
> > example, we'll be faced with making subjective decisions on
> > potentially substantial bodies of code, leading to the possibility
> > of "why not mine?" kinds of things. For larger code bases, we'd
> > also likely need to have some discussions with the incubator folks.
> >
> > But, as you say, let's get our own house in order first, and then
> > come back and talk about this some more.
>
>And in deciding how to renovate our house, let's keep in mind that we may 
>be having more children :)
>
>How about if we split the difference:
>
>core module:
>
>/core
>/site
>/apps
>
>opt-modules:
>
>* opt-taglib
>* opt-el
>* opt-faces
>* opt-dev ("sandbox")
>
>So, we'd go from seven to five.
>
>Then, later on, if we invite some of our friends to join us, and they move 
>in, we just add more opt modules.
>
>-Ted.
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-dev-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Joe Germuska <Jo...@Germuska.com>.
At 2:17 PM -0500 3/24/04, Ted Husted wrote:
>
>  >> \opt-el
>>>
>>  Hmm. This is also a taglib...
>
>But with different platform requirements. :)

Yes, but is there any reason not to treat them as a single 
deliverable?  They have interdependencies that would make this 
attractive, and if users use the correct TLD file, the platform 
dependencies should be invisible.

One wrinkle I see would be that from a compilation standpoint, it 
would be difficult to control the servletapi dependencies, so there 
would be some risk of building the base taglibs using Servlet 2.3 
features.

Even so, I think it's worth looking at making a single 
struts-taglib.jar that would integrate both forms.

Joe
-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
       "Imagine if every Thursday your shoes exploded if you tied them 
the usual way.  This happens to us all the time with computers, and 
nobody thinks of complaining."
             -- Jef Raskin

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Ted Husted <hu...@apache.org>.
On Wed, 24 Mar 2004 11:03:58 -0800 (PST), Martin Cooper wrote:
>> \opt-dev   (whiteboard or "sandbox")
>
> So 'dev', 'whiteboard' or 'sandbox'? ;-) I don't have a strong
> preference, although 'sandbox' is used by at least 4 Jakarta sub-
> projects. (In those, it's a separate repo, though. Do we want to do
> the same?)

Let's go for the brevity and consistency of opt-dev. If we're keeping everything in one module, then let's keep it all on one module :) 


>> \opt-taglib
>
> I still like the idea of pushing this down under a generic
> presentation directory, or at least under a JSP directory, so that
> we can move JSP specific stuff out of core and into this.

I would strongly prefer that we should tie the TLDs to specific deliverables and avoid taxonomies,

The "JSP specific stuff" should live with the taglibs or be refactored so that it's not JSP-specific :)

Obviously, I'm good with alternate presentation technologies, but they should be available as their own deliverables, and rooted in their own TLDs.


>> \opt-el
>>
> Hmm. This is also a taglib... 

But with different platform requirements. :)


-Ted.




---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Martin Cooper <ma...@apache.org>.
On Wed, 24 Mar 2004, Ted Husted wrote:

> On Tue, 23 Mar 2004 20:52:03 -0800 (PST), Martin Cooper wrote:
> > So, there are pros and cons both ways, of course. Now we just need
> > to make a decision and move on it. ;-)
>
> The consensus seems to be to use a single module with top-level-directories representing each subproject, so lets move forward with that.
>
> So I believe we're talking about something like this:
>
> \core        (including tiles and validator)
> \apps
> \site
> \opt-dev   (whiteboard or "sandbox")

So 'dev', 'whiteboard' or 'sandbox'? ;-) I don't have a strong preference,
although 'sandbox' is used by at least 4 Jakarta sub-projects. (In those,
it's a separate repo, though. Do we want to do the same?)

> \opt-taglib

I still like the idea of pushing this down under a generic presentation
directory, or at least under a JSP directory, so that we can move JSP
specific stuff out of core and into this.

> \opt-el

Hmm. This is also a taglib...

> \opt-faces
>
> The example applications we will have to juggle a bit:
>
> [apps]
> /src/example -> /mailreader/src/java
> /src/examples -> /examples/src/java
> /src/tiles-documentation -> /portal/src/java
>
> And the same for /web
> /web/{1}  ->  {1}/src/webapp/
>
> The other directory moving might go something like this:
>
> [opt-el]
> src/contrib/struts-el -> opt-el
>
> [opt-legacy]
> /src/contrib/struts-legacy -> opt-legacy
>
> [opt-faces]
> /src/contrib/struts-faces -> opt-faces
>
> [opt-dev]
> /src/contrib/ -> opt-dev
>
> [opt-taglib]
> src/share/o.a.s/taglib  ->  opt-taglib/src/java/o.a.s/taglib
> src/test/o.a.s/taglib    ->  opt-taglib/src/test/o.a.s/taglib
> doc/userGuide/dev_*.* -> opt-taglib/xdocs
> doc/userGuide/struts*.* -> opt-taglib/xdocs
>
> [site]
> /doc/ - site/xdocs
>
> [core]
> /src/share -> core/src/java
> /src/test -> core/src/test
> / -> /
>
> This is just a rough starting point. I'd want to try a dry-run offline first, and post it where people could browse it :)

+1. I was thinking along the same lines.

> One question is the packaging of Struts-el. Right now it's org.apache.strutsel. I'm thinking we might want that to be org.apache.struts.el instead.

Maybe either:

  org.apache.struts.taglib.el.${foo}
  org.apache.struts.taglib.${foo}.el

The latter just extends the original package names with ".el".

> We might also want to shuffle some things around in opt-faces to make it more Maven friendly. It's also sharing the UserDatabase package with the original example, and so we might want to break the UserDatabase out as a deliverable that multiple applications could share.
>
> Next question. In making changes like this, at what point do we start breaking the CVS history? I'd definitely want to keep it all for core and taglibs. The other components might be less important.

We can arrange to keep CVS history indefinitely. However, we'd want to
stop moving things around as soon as possible, really, and certainly not
move anything after we've created labels or branches in the new tree.

> ** Last but not least:  What else do we need to do for 1.2.1 ?  -- Just the three problem tickets  on the bugzilla list now?

Actually, contrary to your comment in the "Counting down" thread, I don't
have anything up my sleeve (unless I forgot something myself). ;-) It
would be nice to resolve the issue with the Cactus tests not stopping
properly on Tomcat 5.0, but I can live without that if necessary.

--
Martin Cooper


>
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Counting down to the 1.2.1 release (was RE: Making Struts Build Easier)

Posted by Ted Husted <hu...@apache.org>.
On Wed, 24 Mar 2004 12:11:01 -0800 (PST), Martin Cooper wrote:
> Do we want to wait for a Validator 1.1.2, or roll it with 1.1.1?

Well, we can't roll it with 1.1.1, since the report says the client validations won't work without the nightly build. 

It would be cool if we could roll Validator 1.1.2, and then roll Strut 1.2.1, and see if they both make the grade. 

We mostly expected 1.2.0 to wash-out, but 1.2.1 might actually be OK.

Meanwhile, we could branch 1.2.x and bring the Struts-Chain RP down from contrib. :) 

-Ted.



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Counting down to the 1.2.1 release (was RE: Making Struts Build Easier)

Posted by Martin Cooper <ma...@apache.org>.
On Wed, 24 Mar 2004, Ted Husted wrote:

> On Wed, 24 Mar 2004 11:03:58 -0800 (PST), Martin Cooper wrote:
> > Actually, contrary to your comment in the "Counting down" thread, I
> > don't have anything up my sleeve (unless I forgot something
> > myself). ;-) It would be nice to resolve the issue with the Cactus
> > tests not stopping properly on Tomcat 5.0, but I can live without
> > that if necessary.
>
> Well, if we get the problem tickets down to zero, and I update the release notes again, would we be up for rolling 1.2.1 this weekend?

I should be able to do that (although I'm going to have to get my taxes
done soon ;).

Do we want to wait for a Validator 1.1.2, or roll it with 1.1.1?

Regarding #26322, I'd be OK on flagging that one as LATER. I really think
this is a problem with WebLogic. We shouldn't have to (and we can't) make
*everything* serialisable.

--
Martin Cooper


>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Counting down to the 1.2.1 release (was RE: Making Struts Build Easier)

Posted by Ted Husted <hu...@apache.org>.
On Wed, 24 Mar 2004 11:03:58 -0800 (PST), Martin Cooper wrote:
> Actually, contrary to your comment in the "Counting down" thread, I
> don't have anything up my sleeve (unless I forgot something
> myself). ;-) It would be nice to resolve the issue with the Cactus
> tests not stopping properly on Tomcat 5.0, but I can live without
> that if necessary.

Well, if we get the problem tickets down to zero, and I update the release notes again, would we be up for rolling 1.2.1 this weekend?

-Ted.



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Counting down to the 1.2.1 release (was RE: Making Struts Build Easier)

Posted by David Graham <gr...@yahoo.com>.
--- Ted Husted <hu...@apache.org> wrote:
> On Wed, 24 Mar 2004 09:03:46 -0700, Matt Raible wrote:
> >> -----Original Message-----
> >> From: Ted Husted [mailto:husted@apache.org]
> >> Well, did-ja have anything to add to the list, Matt? :)
> >
> > Nope - release, release!!
> 
> The ones we have are resolvable,  but, I'm thinking Martin has something
> up his sleeve yet ...
> 
> Meanwhile, there's still the issue of our dependency on the Validator
> nightly
> 
> http://tinyurl.com/394ht
> 
> and how far we are from another Validator release ...

There have been a few additions since Validator 1.1.1 and IMO 1.1.2 can be
cut anytime.

David

> 
> -Ted.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 


__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Counting down to the 1.2.1 release (was RE: Making Struts Build Easier)

Posted by Ted Husted <hu...@apache.org>.
On Wed, 24 Mar 2004 09:03:46 -0700, Matt Raible wrote:
>> -----Original Message-----
>> From: Ted Husted [mailto:husted@apache.org]
>> Well, did-ja have anything to add to the list, Matt? :)
>
> Nope - release, release!!

The ones we have are resolvable,  but, I'm thinking Martin has something up his sleeve yet ... 

Meanwhile, there's still the issue of our dependency on the Validator nightly

http://tinyurl.com/394ht

and how far we are from another Validator release ...

-Ted.



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


RE: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Matt Raible <li...@raibledesigns.com>.

> -----Original Message-----
> From: Ted Husted [mailto:husted@apache.org] 
> > Personally, I'd like to see a 1.2 release before any CVS 
> changes are 
> > made.  I think the user community would agree.
> 
> Well, did-ja have anything to add to the list, Matt? :)
> 

Nope - release, release!! 



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Ted Husted <hu...@apache.org>.
On Wed, 24 Mar 2004 07:45:29 -0700, Matt Raible wrote:
>> ** Last but not least:  What else do we need to do for 1.2.1 ?  --
>>  Just the three problem tickets  on the bugzilla list now?
>>
>
> Personally, I'd like to see a 1.2 release before any CVS changes
> are made.  I think the user community would agree.

Well, did-ja have anything to add to the list, Matt? :)

http://tinyurl.com/yqxyk

If we can clear the outstanding problem tickets, along with any burning issues people haven't reported yet, we can roll 1.2.1.

-Ted.




---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Matt Raible <li...@raibledesigns.com>.
On Mar 24, 2004, at 4:19 AM, Ted Husted wrote:
>
> Next question. In making changes like this, at what point do we start 
> breaking the CVS history? I'd definitely want to keep it all for core 
> and taglibs. The other components might be less important.
>
> ** Last but not least:  What else do we need to do for 1.2.1 ?  -- 
> Just the three problem tickets  on the bugzilla list now?

Personally, I'd like to see a 1.2 release before any CVS changes are 
made.  I think the user community would agree.

Matt


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by David Graham <gr...@yahoo.com>.
--- Joe Germuska <Jo...@Germuska.com> wrote:
> >This makes it easy for the apps to extend a common Maven 
> >project.xml. We could still offer a single zip/tarball with all the 
> >applications WARs within.
> >
> >/apps
> >  - examples
> >  - mailreader
> >  - tilesPortal
> >  - userdb
> >
> >Now that I say it, the same approach might conceivably be used for 
> >el, taglibs, and faces.
> >
> >/taglibs
> >  - classic
> >  - el
> >  - faces
> >
> >But, the problem with binding the taglib packages too closely is 
> >that they would all have to be distribution-ready before we did a 
> >new roll of any. So, an ongoing refactoring in the "classic" taglibs 
> >could block a quick release of the "faces" taglib.
> >
> >I really want to try and avoid the hydraulic dependencies of the 1.1 
> >era, where we had to have everything ready to release all at once  :(
> 
> I think you've already made the case for not pushing all the taglibs 
> things together just because they are the same technology. 
> struts-faces should be its own thing, I'm pretty certain.
> 
> >Joe suggested combining opt-el with opt-taglibs, though we'd have to 
> >be careful which dependencies are used to build what. (Which makes 
> >me think they are not the same deliverable. el might just have a 
> >dependency on taglib.) I don't actually use either one much myself, 
> >so I have no preferences myself.
> 
> Whether the "classic" and "el" taglibs are one chunk or two isn't 
> hugely important to me either -- I would prefer that this decision be 
> made by developers who've done more work on that code to date. 
> However, I did find that when I patched 
> o.a.s.t.html.JavascriptValidator, I had to go and make a 
> corresponding change in the EL version.  I suspect that changes in 
> those two libraries are going to track pretty tightly.  But like I 
> said, I'm not pushing for this; just floating it...

Is there any reason that the EL tags wouldn't replace the existing tags
for Struts 2.0?  Also, IMO, many of the tags can be removed entirely for
2.0 because they've been replaced by more powerful counterparts in the
JSTL.

David

> 
> Joe
> -- 
> Joe Germuska            
> Joe@Germuska.com  
> http://blog.germuska.com    
>        "Imagine if every Thursday your shoes exploded if you tied them 
> the usual way.  This happens to us all the time with computers, and 
> nobody thinks of complaining."
>              -- Jef Raskin
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 


__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Joe Germuska <Jo...@Germuska.com>.
>This makes it easy for the apps to extend a common Maven 
>project.xml. We could still offer a single zip/tarball with all the 
>applications WARs within.
>
>/apps
>  - examples
>  - mailreader
>  - tilesPortal
>  - userdb
>
>Now that I say it, the same approach might conceivably be used for 
>el, taglibs, and faces.
>
>/taglibs
>  - classic
>  - el
>  - faces
>
>But, the problem with binding the taglib packages too closely is 
>that they would all have to be distribution-ready before we did a 
>new roll of any. So, an ongoing refactoring in the "classic" taglibs 
>could block a quick release of the "faces" taglib.
>
>I really want to try and avoid the hydraulic dependencies of the 1.1 
>era, where we had to have everything ready to release all at once  :(

I think you've already made the case for not pushing all the taglibs 
things together just because they are the same technology. 
struts-faces should be its own thing, I'm pretty certain.

>Joe suggested combining opt-el with opt-taglibs, though we'd have to 
>be careful which dependencies are used to build what. (Which makes 
>me think they are not the same deliverable. el might just have a 
>dependency on taglib.) I don't actually use either one much myself, 
>so I have no preferences myself.

Whether the "classic" and "el" taglibs are one chunk or two isn't 
hugely important to me either -- I would prefer that this decision be 
made by developers who've done more work on that code to date. 
However, I did find that when I patched 
o.a.s.t.html.JavascriptValidator, I had to go and make a 
corresponding change in the EL version.  I suspect that changes in 
those two libraries are going to track pretty tightly.  But like I 
said, I'm not pushing for this; just floating it...

Joe
-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
       "Imagine if every Thursday your shoes exploded if you tied them 
the usual way.  This happens to us all the time with computers, and 
nobody thinks of complaining."
             -- Jef Raskin

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Craig R. McClanahan" <cr...@apache.org>.
Quoting Ted Husted <hu...@apache.org>:

> On Wed, 24 Mar 2004 20:35:41 +0000, Peter A. Pilgrim wrote:
> > Are keeping the basic `src' and `web' main sub directory under each
> > top level directory?
> 
> I'd prefer we followed the Maven project layout recommendations for each
> deliverable. This will be the easiest for everyone to grok in the longrun. 
> 
> http://maven.apache.org/reference/dirlayout.html
> 
> So, under each top-level directory, we would find a layout like 
> 
> /src
>  - java
>  - test
>  - webapp
> 
> /xdocs 
> 
> /target (generated) 
> - *.jar
> - distributions
> - docs
> - site 
> - ...
> 
> 
> > May be it is worth putting `opt-legacy' and `opt-el' under a `view'
> > directory especially if they are all to do rendering the web user
> > interface
> 
> You might have meant opt-taglib and opt-el. Legacy is the old datasource
> implementation. 
> 
> I'd strongly prefer keeping a close relationship between
> top-level-directories and deliverables, and that we avoid taxonomies. 
> 
> Joe suggested combining opt-el with opt-taglibs, though we'd have to be
> careful which dependencies are used to build what. (Which makes me think they
> are not the same deliverable. el might just have a dependency on taglib.) I
> don't actually use either one much myself, so I have no preferences myself.
> 
> The example applications tree might be a tad different. Here I'd favor a
> master apps directory, with a directory for each application beneath that.
> This makes it easy for the apps to extend a common Maven project.xml. We
> could still offer a single zip/tarball with all the applications WARs within.
> 
> 
> /apps 
>  - examples
>  - mailreader
>  - tilesPortal
>  - userdb
> 
> Now that I say it, the same approach might conceivably be used for el,
> taglibs, and faces. 
> 
> /taglibs 
>  - classic
>  - el
>  - faces
> 
> But, the problem with binding the taglib packages too closely is that they
> would all have to be distribution-ready before we did a new roll of any. So,
> an ongoing refactoring in the "classic" taglibs could block a quick release
> of the "faces" taglib. 
> 

As I've mentioned before, JavaServer Faces is not just about JSP custom tags ...
the components and renderers in this package are just like Struts itself, in
that they're view technology independent.  Technologically, therefoe, "faces"
does not belong under "taglibs".

Further, I'd think the Struts developers would want to explore ways in which
other parts of Struts might benefit from some of the infrastructure features in
JSF, such as managed beans and programmatic expression evaluation.  They are
darned handy.

> I really want to try and avoid the hydraulic dependencies of the 1.1 era,
> where we had to have everything ready to release all at once  :(

Agreed.

> -Ted.

Craig


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Ted Husted <hu...@apache.org>.
On Wed, 24 Mar 2004 20:35:41 +0000, Peter A. Pilgrim wrote:
> Are keeping the basic `src' and `web' main sub directory under each
> top level directory?

I'd prefer we followed the Maven project layout recommendations for each deliverable. This will be the easiest for everyone to grok in the longrun. 

http://maven.apache.org/reference/dirlayout.html

So, under each top-level directory, we would find a layout like 

/src
 - java
 - test
 - webapp

/xdocs 

/target (generated) 
- *.jar
- distributions
- docs
- site 
- ...


> May be it is worth putting `opt-legacy' and `opt-el' under a `view'
> directory especially if they are all to do rendering the web user
> interface

You might have meant opt-taglib and opt-el. Legacy is the old datasource implementation. 

I'd strongly prefer keeping a close relationship between top-level-directories and deliverables, and that we avoid taxonomies. 

Joe suggested combining opt-el with opt-taglibs, though we'd have to be careful which dependencies are used to build what. (Which makes me think they are not the same deliverable. el might just have a dependency on taglib.) I don't actually use either one much myself, so I have no preferences myself.

The example applications tree might be a tad different. Here I'd favor a master apps directory, with a directory for each application beneath that. This makes it easy for the apps to extend a common Maven project.xml. We could still offer a single zip/tarball with all the applications WARs within. 

/apps 
 - examples
 - mailreader
 - tilesPortal
 - userdb

Now that I say it, the same approach might conceivably be used for el, taglibs, and faces. 

/taglibs 
 - classic
 - el
 - faces

But, the problem with binding the taglib packages too closely is that they would all have to be distribution-ready before we did a new roll of any. So, an ongoing refactoring in the "classic" taglibs could block a quick release of the "faces" taglib. 

I really want to try and avoid the hydraulic dependencies of the 1.1 era, where we had to have everything ready to release all at once  :(

-Ted.



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Peter A. Pilgrim" <pe...@xenonsoft.demon.co.uk>.
Ted Husted wrote:
> On Tue, 23 Mar 2004 20:52:03 -0800 (PST), Martin Cooper wrote:
> 
>> So, there are pros and cons both ways, of course. Now we just need to make a decision and
>> move on it. ;-)
> 
> 
> The consensus seems to be to use a single module with top-level-directories representing each
> subproject, so lets move forward with that.
> 
> So I believe we're talking about something like this:
> 
> \core        (including tiles and validator) \apps \site \opt-dev   (whiteboard or "sandbox")
>  \opt-taglib \opt-el \opt-faces
> 
> The example applications we will have to juggle a bit:
> 
> [apps] /src/example -> /mailreader/src/java /src/examples -> /examples/src/java 
> /src/tiles-documentation -> /portal/src/java
> 
> And the same for /web /web/{1}  ->  {1}/src/webapp/
> 
> The other directory moving might go something like this:
> 
> [opt-el] src/contrib/struts-el -> opt-el
> 
> [opt-legacy] /src/contrib/struts-legacy -> opt-legacy
> 
> [opt-faces] /src/contrib/struts-faces -> opt-faces
> 
> [opt-dev] /src/contrib/ -> opt-dev
> 
> [opt-taglib] src/share/o.a.s/taglib  ->  opt-taglib/src/java/o.a.s/taglib 
> src/test/o.a.s/taglib    ->  opt-taglib/src/test/o.a.s/taglib doc/userGuide/dev_*.* ->
> opt-taglib/xdocs doc/userGuide/struts*.* -> opt-taglib/xdocs
> 
> [site] /doc/ - site/xdocs
> 
> [core] /src/share -> core/src/java /src/test -> core/src/test / -> /

Are keeping the basic `src' and `web' main sub directory under each
top level directory?

May be it is worth putting `opt-legacy' and `opt-el' under a `view'
directory especially if they are all to do rendering the web user interface

> 
> This is just a rough starting point. I'd want to try a dry-run offline first, and post it
> where people could browse it :)
> 
> One question is the packaging of Struts-el. Right now it's org.apache.strutsel. I'm thinking
> we might want that to be org.apache.struts.el instead.
> 
> We might also want to shuffle some things around in opt-faces to make it more Maven friendly.
> It's also sharing the UserDatabase package with the original example, and so we might want to
> break the UserDatabase out as a deliverable that multiple applications could share.
> 
> Next question. In making changes like this, at what point do we start breaking the CVS
> history? I'd definitely want to keep it all for core and taglibs. The other components might
> be less important.
> 
> ** Last but not least:  What else do we need to do for 1.2.1 ?  -- Just the three problem
> tickets  on the bugzilla list now?
> 
> 
> -Ted.

Regards

-- 
Peter Pilgrim
            __ _____ _____ _____
           / //__  // ___// ___/   +  Serverside Java
          / /___/ // /__ / /__     +  Struts
         / // ___// ___// ___/     +  Expresso Committer
      __/ // /__ / /__ / /__       +  Independent Contractor
     /___//____//____//____/       +  Intrinsic Motivation
On Line Resume
    ||
    \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Ted Husted <hu...@apache.org>.
On Tue, 23 Mar 2004 20:52:03 -0800 (PST), Martin Cooper wrote:
> So, there are pros and cons both ways, of course. Now we just need
> to make a decision and move on it. ;-)

The consensus seems to be to use a single module with top-level-directories representing each subproject, so lets move forward with that. 

So I believe we're talking about something like this:

\core        (including tiles and validator)
\apps
\site
\opt-dev   (whiteboard or "sandbox")
\opt-taglib
\opt-el
\opt-faces

The example applications we will have to juggle a bit:

[apps]
/src/example -> /mailreader/src/java 
/src/examples -> /examples/src/java 
/src/tiles-documentation ->�/portal/src/java

And the same for /web
/web/{1}  ->� {1}/src/webapp/

The other directory moving might go something like this:

[opt-el]
src/contrib/struts-el ->�opt-el

[opt-legacy]
/src/contrib/struts-legacy ->�opt-legacy

[opt-faces]
/src/contrib/struts-faces ->�opt-faces

[opt-dev]
/src/contrib/ ->�opt-dev

[opt-taglib]
src/share/o.a.s/taglib  ->� opt-taglib/src/java/o.a.s/taglib
src/test/o.a.s/taglib    ->  opt-taglib/src/test/o.a.s/taglib
doc/userGuide/dev_*.* -> opt-taglib/xdocs
doc/userGuide/struts*.* -> opt-taglib/xdocs

[site]
/doc/ - site/xdocs

[core]
/src/share ->�core/src/java
/src/test -> core/src/test
/ ->�/

This is just a rough starting point. I'd want to try a dry-run offline first, and post it where people could browse it :)

One question is the packaging of Struts-el. Right now it's org.apache.strutsel. I'm thinking we might want that to be org.apache.struts.el instead. 

We might also want to shuffle some things around in opt-faces to make it more Maven friendly. It's also sharing the UserDatabase package with the original example, and so we might want to break the UserDatabase out as a deliverable that multiple applications could share. 

Next question. In making changes like this, at what point do we start breaking the CVS history? I'd definitely want to keep it all for core and taglibs. The other components might be less important. 

** Last but not least:  What else do we need to do for 1.2.1 ?  -- Just the three problem tickets  on the bugzilla list now?


-Ted.



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Martin Cooper <ma...@apache.org>.
On Tue, 23 Mar 2004, Ted Husted wrote:

> On Tue, 23 Mar 2004 18:16:53 +0000, Peter A. Pilgrim wrote:
> > 1) I think you should keep the same elementary structure
>
> Moving forward, we have already decided to use Maven as our build environment, which addresses a number of consistency and structural issues. We had also decided to distribute non-core components, like the taglibs, independantly. Independant releases lead to the idea of independant modules. Modules also seem like a good way to handle bringing on some of the more popular extensions.

As Joe mentioned, we would still need somewhere to put the shared files,
such as Maven's project.xml, the LICENSE and NOTICE files, the KEYS file,
etc. In a single-module world, those would live at the top level, just as
they do now. In a multi-module world, those should be in another module
solely for that purpose. (I certainly wouldn't want a build file that
knows about all the individual modules living in core, or any other
independently buildable module.)

> So, the "site" subproject would be an overview of the Struts project, and then link to the subprojects (including core) for more detail.
>
> A contributor mentioned wanting a single JAR. I don't think that's an itch any of Committers are desparate to scratch. And, if anyone did, it's been pointed out that Ant can be used to burst and combine JARs. Anyone could do that.
>
> I don't think anyone wants to build a single Struts WAR, especially since we already have multiple example applications in their own WARs.

I don't want a single jar or a single war, but I do want to be able to run
*one* build process to get all of the pieces to build. I also don't relish
the thought of having to maintain multiple Gump descriptors, either.

> At this point, we're down to whether to organize the subprojects (units of release) into multiple modules or around top-level-directories in a single module.

Yep, that's exactly where we are. ;-)

Here's what I think are the pros and cons of each approach:

One module, multiple directories:

+ One checkout grabs it all (but an alias can reference multiple modules).
+ Natural place (top level) for all cross-"module" files. (See above.)
+ Labelling and branching across "modules" is one CVS command.
+ Don't need CVS admin karma (i.e. Craig) to create new "modules".
- Harder (?) to check out only portions of the overall code base.

Multiple modules:

+ Easier (?) to check out only portions of the overall code base.
+ May scale better as we accumulate extensions.
- Need an extra module for cross-module files.
- Clutters up the Apache CVS repository.

The reason for the question marks is that this issue seems to have been
implied, but it's not really true. The difference is literally a single
character - 'cvs co struts-core' versus 'cvs co struts/core'.

The labelling issue is an interesting one. Someone (hi Ted! ;) is going to
argue that we'll want to label each "module" independently because we'll
want to release them independently, and I agree with that. But I also
think that there will be points in time that we'll want to label or branch
the entire code base, which will be easier to do across a single module.

So, there are pros and cons both ways, of course. Now we just need to
make a decision and move on it. ;-)

--
Martin Cooper


> My only feeling is that should we start inviting some of the popular extensions to join us, the module approach seems like it would scale better.
>
> -Ted.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Peter A. Pilgrim" <pe...@xenonsoft.demon.co.uk>.
Joe Germuska wrote:
>> I just to try build Struts with Maven, what am I doing wrong?
>> ...
>> Attempting to download commons-validator-1.1.2-dev.jar.
>> WARNING: Failed to download commons-validator-1.1.2-dev.jar.
>> The build cannot continue because of the following unsatisfied 
>> dependency:
> 
> 
> The problem is that the project.xml file declares a dependency on a 
> version of commons-validator which isn't in your local Maven repository 
> and which is not in the shared repository.
> 
> Maven looked here:
> http://ibiblio.org/maven/commons-validator/jars/
> 
> for
> commons-validator-1.1.2-dev.jar
> 
> and as you can see if you follow that URL, it isn't there.
> 
> You can control the versions that Maven uses for dependencies by 
> specifying certain properties.  (Full details at 
> http://maven.apache.org/reference/user-guide.html#Properties_Processing)
> 
> Probably the easiest way to set the properties would be to create or 
> edit build.properties in the root of your local Struts sandbox (same 
> directory where build.xml and project.xml are).  Add the following lines:
> 
> maven.jar.override=on
> maven.jar.commons-validator=1.1.1
> 
> That's a version of commons-validator that's on the shared Maven 
> repository, although I don't have time just at the minute to see if 
> Struts will still build against it!
> 
Yes the above did the trick. I have update the Struts Wiki page.
Ta also.

> You could also check out commons-validator and run "maven 
> jar:install-snapshot"  and use
> maven.jar.commons-validator=SNAPSHOT
> instead.
> 
> Hope that helps.  If we stick to our guns about avoiding dependencies on 
> unreleased software, this won't come up again... it's not Maven's fault!
> 
==////==

-- 
Peter Pilgrim
            __ _____ _____ _____
           / //__  // ___// ___/   +  Serverside Java
          / /___/ // /__ / /__     +  Struts
         / // ___// ___// ___/     +  Expresso Committer
      __/ // /__ / /__ / /__       +  Independent Contractor
     /___//____//____//____/       +  Intrinsic Motivation
On Line Resume
    ||
    \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Peter A. Pilgrim" <pe...@xenonsoft.demon.co.uk>.
Joe Germuska wrote:
>> java:jar-resources:
>> Copying 16 files to /new/peterp/jakarta-struts/m-target/classes
>>

==////==

>>     [style] 
>> new/peterp/jakarta-struts/doc/userGuide/struts-html.xml:1440:2: Fatal 
>> Error! The content of elements must consist of well-formed character 
>> data or markup.
>>     [style] Failed to process 
>> /new/peterp/jakarta-struts/doc/userGuide/struts-html.xml
> 
> 
> I don't think your problem is with XSLT (Xalan is defined as a 
> dependency in project.xml just for this purpose) -- from the logs it 
> looks as if struts-bean.xml is being styled correctly before 
> struts-html.xml fails.
> 
> It seems unlikely that this would be the problem, but are you sure you 
> have the head version of doc/userGuide/struts-html.xml?  I just did 
> "maven clean" followed by "maven jar" and didn't get any errors.
>

Thanks Joe

Running `maven jar' works now.

Looks like it was a CVS conflict with an older version. Purged all
the `doc' directory tree, then updated CVS to get latest deltas.

I got delta 1.76 for `doc/userGuide/struts-html.xml' too.

==////==

-- 
Peter Pilgrim
            __ _____ _____ _____
           / //__  // ___// ___/   +  Serverside Java
          / /___/ // /__ / /__     +  Struts
         / // ___// ___// ___/     +  Expresso Committer
      __/ // /__ / /__ / /__       +  Independent Contractor
     /___//____//____//____/       +  Intrinsic Motivation
On Line Resume
    ||
    \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Joe Germuska <Jo...@Germuska.com>.
>java:jar-resources:
>Copying 16 files to /new/peterp/jakarta-struts/m-target/classes
>
>     [style] Transforming into 
>/new/peterp/jakarta-struts/m-target/classes/META-INF/tlds
>     [style] Processing 
>/new/peterp/jakarta-struts/doc/userGuide/struts-bean.xml to 
>/new/peterp/jakarta-struts/m-target/classes/META-INF/tlds/struts-bean.tld
>     [style] Loading stylesheet 
>/new/peterp/jakarta-struts/doc/stylesheets/tld.xsl
>     [style] Processing 
>/new/peterp/jakarta-struts/doc/userGuide/struts-html.xml to 
>/new/peterp/jakarta-struts/m-target/classes/META-INF/tlds/struts-html.tld
>     [style] 
>new/peterp/jakarta-struts/doc/userGuide/struts-html.xml:1440:2: 
>Fatal Error! The content of elements must consist of well-formed 
>character data or markup.
>     [style] Failed to process 
>/new/peterp/jakarta-struts/doc/userGuide/struts-html.xml

I don't think your problem is with XSLT (Xalan is defined as a 
dependency in project.xml just for this purpose) -- from the logs it 
looks as if struts-bean.xml is being styled correctly before 
struts-html.xml fails.

It seems unlikely that this would be the problem, but are you sure 
you have the head version of doc/userGuide/struts-html.xml?  I just 
did "maven clean" followed by "maven jar" and didn't get any errors.

===========================
File: struts-html.xml   Status: Up-to-date

    Working revision:    1.76
    Repository revision: 1.76 
/home/cvs/jakarta-struts/doc/userGuide/struts-html.xml,v
    Sticky Tag:          (none)
    Sticky Date:         (none)
    Sticky Options:      (none)


It's possible that there's some other setting in my build.properties 
that I don't recognize, but I did a little searching and didn't see 
anything.  If you'd like to compare mine to yours, I could send it 
privately.

Joe


-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
       "Imagine if every Thursday your shoes exploded if you tied them 
the usual way.  This happens to us all the time with computers, and 
nobody thinks of complaining."
             -- Jef Raskin

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Peter A. Pilgrim" <pe...@xenonsoft.demon.co.uk>.
Joe Germuska wrote:
>> I just to try build Struts with Maven, what am I doing wrong?
>> ...
>> Attempting to download commons-validator-1.1.2-dev.jar.
>> WARNING: Failed to download commons-validator-1.1.2-dev.jar.
>> The build cannot continue because of the following unsatisfied 
>> dependency:
> 

I cannot seem to build the resource files. XSL Templates.

> peterp@orchard [266] > maven jar:install
...
java:prepare-filesystem:

java:compile:
     [echo] Compiling to m-target/classes

java:jar-resources:
Copying 16 files to /new/peterp/jakarta-struts/m-target/classes

     [style] Transforming into /new/peterp/jakarta-struts/m-target/classes/META-INF/tlds
     [style] Processing /new/peterp/jakarta-struts/doc/userGuide/struts-bean.xml to 
/new/peterp/jakarta-struts/m-target/classes/META-INF/tlds/struts-bean.tld
     [style] Loading stylesheet /new/peterp/jakarta-struts/doc/stylesheets/tld.xsl
     [style] Processing /new/peterp/jakarta-struts/doc/userGuide/struts-html.xml to 
/new/peterp/jakarta-struts/m-target/classes/META-INF/tlds/struts-html.tld
     [style] new/peterp/jakarta-struts/doc/userGuide/struts-html.xml:1440:2: Fatal Error! The 
content of elements must consist of well-formed character data or markup.
     [style] Failed to process /new/peterp/jakarta-struts/doc/userGuide/struts-html.xml

BUILD FAILED
File...... file:/new/peterp/jakarta-struts/
Element... ant:style
Line...... 29
Column.... 28
Fatal error during transformation
Total time: 16 seconds
Finished at: Wed Mar 24 01:14:25 GMT 2004

What are required `build.properties' for Xalan/Struts?

Many tia
-- 
Peter Pilgrim
            __ _____ _____ _____
           / //__  // ___// ___/   +  Serverside Java
          / /___/ // /__ / /__     +  Struts
         / // ___// ___// ___/     +  Expresso Committer
      __/ // /__ / /__ / /__       +  Independent Contractor
     /___//____//____//____/       +  Intrinsic Motivation
On Line Resume
    ||
    \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Joe Germuska <Jo...@Germuska.com>.
At 6:08 AM -0800 3/24/04, David Graham wrote:
>--- Joe Germuska <Jo...@Germuska.com> wrote:
><snip>
>
>>  Hope that helps.  If we stick to our guns about avoiding dependencies
>>  on unreleased software, this won't come up again... it's not Maven's
>>  fault!
>
>Commons Validator is a special case because it's mostly used with Struts.
>The standalone user population is significantly smaller than the Struts
>Validator users.  We decided that to get true testing of new Commons
>Validator versions we needed to distribute it with Struts builds.

Fair enough...  but there's still a snag between the apparently high 
demand for an easy-to-build Struts (based on the traffic in this 
thread) and using dependencies that aren't served from iBiblio.

Basically, the alternatives are to get all dependency versions on 
some repository server somewhere, or to try to better document the 
workarounds when they are necessary.  For a while, I had a comment 
block in project.xml explaining how to work around an unreleased 
validator dependency, but I took it out when the dependency version 
was one served from iBiblio.

In January, there was a thread on commons-dev about syncing Apache 
builds with iBiblio.  It suggested that there might be a secondary 
repository on cvs.apache.org for nightly builds, but it doesn't 
appear that it has been set up.  Don't know if it's stalled, or if it 
was vetoed.

http://thread.gmane.org/gmane.comp.jakarta.commons.devel/39462

It's conceptually easy to add alternative repositories in addition to 
ibiblio -- in fact, our project.properties file has a commented-out 
line from last time we were in this situation, but the repository 
indicated is 404.

I think the solution suggested by Mark Diggory in the commons-dev 
thread (a backup repo for nightly builds) is a pretty good idea; 
maybe we just have to push someone to get it actually set up?

Joe

-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
       "Imagine if every Thursday your shoes exploded if you tied them 
the usual way.  This happens to us all the time with computers, and 
nobody thinks of complaining."
             -- Jef Raskin

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by David Graham <gr...@yahoo.com>.
--- Joe Germuska <Jo...@Germuska.com> wrote:
<snip>

> Hope that helps.  If we stick to our guns about avoiding dependencies 
> on unreleased software, this won't come up again... it's not Maven's 
> fault!

Commons Validator is a special case because it's mostly used with Struts. 
The standalone user population is significantly smaller than the Struts
Validator users.  We decided that to get true testing of new Commons
Validator versions we needed to distribute it with Struts builds.

David

> 
> Joe
> 
> -- 
> Joe Germuska            
> Joe@Germuska.com  
> http://blog.germuska.com    
>        "Imagine if every Thursday your shoes exploded if you tied them 
> the usual way.  This happens to us all the time with computers, and 
> nobody thinks of complaining."
>              -- Jef Raskin
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 


__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Joe Germuska <Jo...@Germuska.com>.
>I just to try build Struts with Maven, what am I doing wrong?
>...
>Attempting to download commons-validator-1.1.2-dev.jar.
>WARNING: Failed to download commons-validator-1.1.2-dev.jar.
>The build cannot continue because of the following unsatisfied dependency:

The problem is that the project.xml file declares a dependency on a 
version of commons-validator which isn't in your local Maven 
repository and which is not in the shared repository.

Maven looked here:
http://ibiblio.org/maven/commons-validator/jars/

for
commons-validator-1.1.2-dev.jar

and as you can see if you follow that URL, it isn't there.

You can control the versions that Maven uses for dependencies by 
specifying certain properties.  (Full details at 
http://maven.apache.org/reference/user-guide.html#Properties_Processing)

Probably the easiest way to set the properties would be to create or 
edit build.properties in the root of your local Struts sandbox (same 
directory where build.xml and project.xml are).  Add the following 
lines:

maven.jar.override=on
maven.jar.commons-validator=1.1.1

That's a version of commons-validator that's on the shared Maven 
repository, although I don't have time just at the minute to see if 
Struts will still build against it!

You could also check out commons-validator and run "maven 
jar:install-snapshot"  and use
maven.jar.commons-validator=SNAPSHOT
instead.

Hope that helps.  If we stick to our guns about avoiding dependencies 
on unreleased software, this won't come up again... it's not Maven's 
fault!

Joe

-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
       "Imagine if every Thursday your shoes exploded if you tied them 
the usual way.  This happens to us all the time with computers, and 
nobody thinks of complaining."
             -- Jef Raskin

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Peter A. Pilgrim" <pe...@xenonsoft.demon.co.uk>.
Joe Germuska wrote:
> At 3:47 PM -0500 3/23/04, Ted Husted wrote:
> 
>> At this point, we're down to whether to organize the subprojects 
>> (units of release) into multiple modules or around 
>> top-level-directories in a single module.
>>
>> My only feeling is that should we start inviting some of the popular 
>> extensions to join us, the module approach seems like it would scale 
>> better.
> 
> 
> I don't have a very strong opinion about it.  However, from a Maven 
> perspective, if we want to share resources such as a common project.xml, 
> having multiple modules leaves us with no place to put the shared 
> project.  I've also had reasonably good results with the maven 
> "multiproject" goal for building a number of related projects, which 
> would also require a shared project.xml
> 

I just to try build Struts with Maven, what am I doing wrong?

> peterp@orchard [175] > maven java:compile
  __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc1-SNAPSHOT

Attempting to download commons-validator-1.1.2-dev.jar.
WARNING: Failed to download commons-validator-1.1.2-dev.jar.
The build cannot continue because of the following unsatisfied dependency:

commons-validator-1.1.2-dev.jar (try downloading from http://jakarta.apache.org/commons/validator/)

Total time: 6 seconds
Finished at: Tue Mar 23 22:11:19 GMT 2004


-- 
Peter Pilgrim
            __ _____ _____ _____
           / //__  // ___// ___/   +  Serverside Java
          / /___/ // /__ / /__     +  Struts
         / // ___// ___// ___/     +  Expresso Committer
      __/ // /__ / /__ / /__       +  Independent Contractor
     /___//____//____//____/       +  Intrinsic Motivation
On Line Resume
    ||
    \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Joe Germuska <Jo...@Germuska.com>.
At 3:47 PM -0500 3/23/04, Ted Husted wrote:
>At this point, we're down to whether to organize the subprojects 
>(units of release) into multiple modules or around 
>top-level-directories in a single module.
>
>My only feeling is that should we start inviting some of the popular 
>extensions to join us, the module approach seems like it would scale 
>better.

I don't have a very strong opinion about it.  However, from a Maven 
perspective, if we want to share resources such as a common 
project.xml, having multiple modules leaves us with no place to put 
the shared project.  I've also had reasonably good results with the 
maven "multiproject" goal for building a number of related projects, 
which would also require a shared project.xml

Plus even if infrastructure doesn't mind making new modules, we don't 
even have to ask if we want to add new module-like subdirectories 
under a main "struts" module.

I wouldn't veto a multiple module approach, but these seem like a few 
decent reasons for having a single CVS module.

Cocoon seems to coin new modules with each major version; is that a 
good approach?

Joe

-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
       "Imagine if every Thursday your shoes exploded if you tied them 
the usual way.  This happens to us all the time with computers, and 
nobody thinks of complaining."
             -- Jef Raskin

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Ted Husted <hu...@apache.org>.
On Tue, 23 Mar 2004 18:16:53 +0000, Peter A. Pilgrim wrote:
> 1) I think you should keep the same elementary structure

Moving forward, we have already decided to use Maven as our build environment, which addresses a number of consistency and structural issues. We had also decided to distribute non-core components, like the taglibs, independantly. Independant releases lead to the idea of independant modules. Modules also seem like a good way to handle bringing on some of the more popular extensions.

So, the "site" subproject would be an overview of the Struts project, and then link to the subprojects (including core) for more detail. 

A contributor mentioned wanting a single JAR. I don't think that's an itch any of Committers are desparate to scratch. And, if anyone did, it's been pointed out that Ant can be used to burst and combine JARs. Anyone could do that. 

I don't think anyone wants to build a single Struts WAR, especially since we already have multiple example applications in their own WARs.

At this point, we're down to whether to organize the subprojects (units of release) into multiple modules or around top-level-directories in a single module. 

My only feeling is that should we start inviting some of the popular extensions to join us, the module approach seems like it would scale better. 

-Ted.





---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Peter A. Pilgrim" <pe...@xenonsoft.demon.co.uk>.
Peter A. Pilgrim wrote:
> Ted Husted wrote:
> 
>> On Tue, 23 Mar 2004 10:07:55 +0000, Peter A. Pilgrim wrote:
>>
>>> In my experienc multiple CVS repositories can make a project much
>>> harder to manage. But are we singing from the same hymn sheet? Is a
>>> "multiple repository" equal ( or not equal) to a CVS module?
>>
>>
>>
>> We mean multiple CVS modules. The original idea being each module 
>> would generate a jar.  Product==JAR==Module==unit-of-release.
>> One list of potential products -- each with its own JAR, module, and 
>> release cycle -- would be:
>> * core (including tiles and validator)
>> * examples
>> * site
>> * whiteboard (or "sandbox")
>>
>> * opt-taglib
>> * opt-el
>> * opt-faces
>>
>> aka "the seven dwarfs" :)
>>
> 
> Now it clearer.
> 
> Well this is how Expresso CVS is laid out and an old investment bank
> project  which I was involved in a couple years ago was laid out like
> that as well.
> 
> I guess the hard part of copying jar and build a web app from CVS
> modules have already been discussed. Still it is the only way to
> go if you want to Struts to be modular. So +1 from me.
> 

Let me clarify my own post ( grabbing GNU Emacs  and picture-mode ).
The way it is organised under the current CVS module is `src' for Java source
and `web' file. So you could live with this structure.

1) I think you should keep the same elementary structure

Case#1

CVS Repository
     |
     + core (including tiles and validator)
     |  |
     |  +---web
     |  +---src
     |
     + examples
     |  |
     |  +---web
     |  +---src
     |
     + site
     |  |
     |  +---web
     |  +---src
     |
     + whiteboard (or "sandbox")
     |  |
     ...
     + opt-taglib
     |  |
     ...
     + opt-el
     |  |
     ...
     + opt-faces

2) Or you can remove all the `web' stuff and merge under one `web' (public_html)
module. But I have never liked this idea as a workable solution. I seen it once
long ago and I hated it then and now.

Case#2

CVS Repository
     |
     +--web
     |  |
     |  +-- examples
     |  +-- core
     |  +-- ...
     |
     + core (including tiles and validator)
     |  |
     |  +---src
     |
     + examples
     |  |
     |  +---src
     |
     + site
     |  |
     |  +---src
     |
     + whiteboard (or "sandbox")
     |  |
     ...
     + opt-taglib
     |  |
     ...
     + opt-el
     |  |
     ...
     + opt-faces

In any case in order to build a single WAR or EAR, can be quite hard on the
ANT XML build file. There is a lot of possible copying of files, JARing,
and/or JARing involved in order to build a release. In my limited
architectural experience you only need to get the initial build right once,
then you can forget about it, as long as other people developers understand
what is going on.

1) Developers have to understand the project directory structure and
standards in order to not to step on each other shoes.

e.g In order to build a WAR of all modules that runs out of the box,
you cannot have two different sub project developers, say from
`examples' and `site', each with a CVS file called

<CVS-MODULE>/web/some/foobar/acme.jsp.

Conflict of interest on files.

The same applies to source code and resources as well. Top level package
names must be agreed well in advanced. Of the course the current mapping

<CVS-MODULE>/src/shared/org/apache/struts/**

can be simplified to:

<CVS-MODULE>/src/org/apache/struts/**

in the new modular structure.

2) Organise fragments that are included into a larger configuration files.

e.g Each sub project may have TLD files, Properties files, i18n resources,
or Servlet Mappings and Servlet Paths that are merged into a final file.
Servlet mapping fragments are inserted into the final web.xml file.
Same goes for any Servlet filters.

NB: This is similar to using XML includes notation in order build a giant
`struts-config.xml', which shared by a large development team. I am
not sure if you need to do this as committers. Only I mention it if
you need to build a Struts Adventure Petstore demonstration
example in the far off future. Will properties file probably have to
merge them with ANT core tasks or some custom made build tool.

3) Agree to keep to a convention document so that the mythical `master'
build.xml does not blow up into smitherings.

4) Some one has to write standards & conventions document so that everybody
knows what time it is, and plays in a solid team.

5) Another other business obviously include JUnit, Struts documentation,
javadoc etc etc

It is starting resemble a big project with more 10+ developers working across
CVS modules. Having said all that I wish you great bundle of luck.

Regards
-- 
Peter Pilgrim
            __ _____ _____ _____
           / //__  // ___// ___/   +  Serverside Java
          / /___/ // /__ / /__     +  Struts
         / // ___// ___// ___/     +  Expresso Committer
      __/ // /__ / /__ / /__       +  Independent Contractor
     /___//____//____//____/       +  Intrinsic Motivation
On Line Resume
    ||
    \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Peter A. Pilgrim" <pe...@xenonsoft.demon.co.uk>.
Ted Husted wrote:
> On Tue, 23 Mar 2004 10:07:55 +0000, Peter A. Pilgrim wrote:
> 
>>In my experienc multiple CVS repositories can make a project much
>>harder to manage. But are we singing from the same hymn sheet? Is a
>>"multiple repository" equal ( or not equal) to a CVS module?
> 
> 
> We mean multiple CVS modules. The original idea being each module would generate a jar.  Product==JAR==Module==unit-of-release. 
> 
> One list of potential products -- each with its own JAR, module, and release cycle -- would be: 
> 
> * core (including tiles and validator)
> * examples
> * site
> * whiteboard (or "sandbox")
> 
> * opt-taglib
> * opt-el
> * opt-faces
> 
> aka "the seven dwarfs" :)
> 

Now it clearer.

Well this is how Expresso CVS is laid out and an old investment bank
project  which I was involved in a couple years ago was laid out like
that as well.

I guess the hard part of copying jar and build a web app from CVS
modules have already been discussed. Still it is the only way to
go if you want to Struts to be modular. So +1 from me.

-- 
Peter Pilgrim
            __ _____ _____ _____
           / //__  // ___// ___/   +  Serverside Java
          / /___/ // /__ / /__     +  Struts
         / // ___// ___// ___/     +  Expresso Committer
      __/ // /__ / /__ / /__       +  Independent Contractor
     /___//____//____//____/       +  Intrinsic Motivation
On Line Resume
    ||
    \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Ted Husted <hu...@apache.org>.
On Tue, 23 Mar 2004 10:07:55 +0000, Peter A. Pilgrim wrote:
> In my experienc multiple CVS repositories can make a project much
> harder to manage. But are we singing from the same hymn sheet? Is a
> "multiple repository" equal ( or not equal) to a CVS module?

We mean multiple CVS modules. The original idea being each module would generate a jar.  Product==JAR==Module==unit-of-release. 

One list of potential products -- each with its own JAR, module, and release cycle -- would be: 

* core (including tiles and validator)
* examples
* site
* whiteboard (or "sandbox")

* opt-taglib
* opt-el
* opt-faces

aka "the seven dwarfs" :)

-Ted.



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Peter A. Pilgrim" <pe...@xenonsoft.demon.co.uk>.
Martin Cooper wrote:
> On Mon, 22 Mar 2004, Craig R. McClanahan wrote:
> 
> 
>>Quoting Martin Cooper <ma...@apache.org>:
>>
>>
>>>On Mon, 22 Mar 2004, Ted Husted wrote:
>>>
>>>
>>>>On Mon, 22 Mar 2004 11:36:37 -0700, Matt Raible wrote:
>>>>
>>>>>While it's great to break out things into separate "modules" - I'd
>>>>>love to be able to get struts.jar w/ everything in it - including
>>>>>EL and tags.  I can live with all the commons-* JARs (even if it is
>>>>>annoying), but in general - the less JARs, the better.  It just
>>>>>simplifies things for the developer.
>>>>>
>>>>>I don't care how things are partitioned in CVS, as long as
>>>>>everything builds with one checkout and one command.
>>>>
>>>>If that were someone's itch, it could certainly be done. Ant doesn't know
>>>
>>>about the module partitions, and so someone could write a uber-build that did
>>>something like this.
>>>
>>>If we have all of the pieces in separate repositories, though, where would
>>>the files for such an uber-build be checked in? That's one of the problems
>>>I have with the multi-repository solution - there is no place for files
>>>that span those repositories. If we have one repository split into pieces,
>>>then we still have the top level for these things.
> 
>  > >
> 
>>On the multi-repository projects I've worked on, we had a special repository
>>just for integration tasks like this.
> 
> 
> So we'd need yet another repo - say struts-integration - just for this.
> Why is that better than just doing what we need within the repo that we
> have already?
> 

In my experienc multiple CVS repositories can make a project
much harder to manage. But are we singing from the same hymn sheet?
Is a "multiple repository" equal ( or not equal) to a CVS module?

> 
>>>>But, the problem with thinking of Struts as one monothic build is that
>>>
>>>every aspect of the framework has to be perfect, all at the same time, before
>>>we can call it a "general availability" ready-for-prime-time release.  One of
>>>the many reasons 1.1 took so long was that if there was any bug in any
>>>component anywhere in the framework, everything gridlocked.  :(  :(   :(
>>>
>>>That doesn't need to be true if we don't want it to. Recall that for a
>>>time we had a separtely built, separately distributed component called
>>>struts-legacy to handle the data source situation. There is no need for a
>>>one-to-one correlation between repositories and distributable entities.
>>>
>>>
>>>>What we want to do ... need to do ... is be able to release fixes to
>>>
>>>components like the taglibs independently of the core controller. Likewise,
>>>we need to release changes to Struts EL or Struts Faces (once it goes 1.0)
>>>without having to be sure every other component is ready to roll. We should
>>>also be able to release updates to the example applications without
>>>re-releasing the rest of the framework, if that's all we want to roll right
>>>now.
>>>
>>>Absolutely. And the number of repositories we have is entirely orthogonal
>>>to this.
>>>
>>
>>Ultimately true, although it's still somewhat easier to visualize if you have
>>separate repositories.
>>
>>
>>>>Some people may not like more JARs, but I know for certain that the single
>>>
>>>JAR approach is a momentum killer. It's made my life much more difficult, and
>>>I think it's chased away some Committers who became frustrated by having to
>>>"everything right" in order to one little feature into a formal release.
>>>
>>>For the people who want / need a single jar, it would be simple enough for
>>>us to provide an Ant target that explodes the desired individual jars and
>>>recombines them into a single jar. The only tricky part, I think, would be
>>>creating a manifest that identifies the versions of the individual pieces
>>>in that jar. That's assuming people want such a beast, of course. (I'm not
>>>in that camp myself, though, just as I'd never use the Commons Combo
>>>build.)
>>>
>>>
>>>>If we can get more code into the hands of more developers in less time,
>>>
>>>then a few more JARs seems like a small price to pay. :)
>>>
>>>+1
>>>
>>
>>Yep.
>>
>>
>>>>Here's something else to mull over:
>>>>
>>>>Now that Struts is a TLP, we might want to talk about whether we want to
>>>
>>>ask the most popular open source Struts extensions -- like Struts Menu,
>>>Workflow, Stxx, SSL, and TestCase -- whether they would like to donate their
>>>code to the ASF and live as Struts "opt" subprojects. This would be a
>>>continuation of what we started with Tiles, Validator, and Nested, which are
>>>all favorites with our community. People working on such packages might be
>>>brought on as Struts Committers, since they have proved they have what it
>>>takes to run a project, and after an appropriate period, later invited to
>>>join the Struts PMC.
>>>
>>>>IMHO, when people talk about JSF replacing Struts, they are unaware of the
>>>
>>>true breadth of the Struts platform. Perhaps it's time we made sure people
>>>know how much they are missing :)
>>>
>>>>A sad truth: In working with various teams managing larger projects, I've
>>>
>>>found a surprising reluctance to use extensions that were not distributed by
>>>the Struts project itself. By giving these very fine extensions "the nod", we
>>>can make them available to a greater number of Struts teams, to everyone's
>>>benefit. If we don't help make these extensions available to everyone, then
>>>we end up "hiding our light under a bushel".
>>>
>>>>Now, I haven't brought this idea up to any of the other Committers, and
>>>
>>>have no idea how any else will feel about it. But it is something that I
>>>would personally like to work towards -- once we have our existing code
>>>"rationalized". (First things first!)
>>>
>>>I'd be open to it, but I think we have a lot of things we'd want to do to
>>>get our own house in order before we actually take action on this. I also
>>>think it might be a tricky issue in some respects. For example, we'll be
>>>faced with making subjective decisions on potentially substantial bodies
>>>of code, leading to the possibility of "why not mine?" kinds of things.
>>>For larger code bases, we'd also likely need to have some discussions with
>>>the incubator folks.
>>>
>>>But, as you say, let's get our own house in order first, and then come
>>>back and talk about this some more.
>>>
>>>--
>>>Martin Cooper
>>>
>>>
>>>
>>>>-Ted.
>>>>
>>
>>Craig
>>
>>
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 
> 


-- 
Peter Pilgrim
            __ _____ _____ _____
           / //__  // ___// ___/   +  Serverside Java
          / /___/ // /__ / /__     +  Struts
         / // ___// ___// ___/     +  Expresso Committer
      __/ // /__ / /__ / /__       +  Independent Contractor
     /___//____//____//____/       +  Intrinsic Motivation
On Line Resume
    ||
    \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


RE: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Steve Raeburn <sr...@apache.org>.
FWIW I'm with Martin on this. I don't understand the advantage having
separate repositories will give us. Even under one top lever repository
directory, we can organize the Struts product(s) however we like.

The only advantage I can see in having separate repositories would be to
make it easier to grant different groups of committers access to
different areas. But that's not what we want to do anyway.

Another reason NOT to split into several top level directories is that
it adds more clutter to the already busy Apache repository. IMHO fewer
top level directories makes it easier for people to find what they need.

If there's a compelling reason to split into several top-level
repository directories that hasn't been stated (or I've missed), please
let me know, otherwise  I'd prefer to keep as few as possible.

But it's not a life or death issue either way :-)

Steve


> -----Original Message-----
> From: Martin Cooper [mailto:martinc@apache.org]
> Sent: March 22, 2004 11:50 PM
> To: Craig R. McClanahan
> Cc: Struts Developers List
> Subject: Re: Making Struts Build Easier (Re: "coming out" for JSF +
> Struts, was: Struts JSR?)
>
>
> On Mon, 22 Mar 2004, Craig R. McClanahan wrote:
>
> > Quoting Martin Cooper <ma...@apache.org>:
> >
> > > On Mon, 22 Mar 2004, Ted Husted wrote:
> > >
> > > > On Mon, 22 Mar 2004 11:36:37 -0700, Matt Raible wrote:
> > > > > While it's great to break out things into separate
> "modules" - I'd
> > > > > love to be able to get struts.jar w/ everything in it
> - including
> > > > > EL and tags.  I can live with all the commons-* JARs
> (even if it is
> > > > > annoying), but in general - the less JARs, the
> better.  It just
> > > > > simplifies things for the developer.
> > > > >
> > > > > I don't care how things are partitioned in CVS, as long as
> > > > > everything builds with one checkout and one command.
> > > >
> > > > If that were someone's itch, it could certainly be
> done. Ant doesn't know
> > > about the module partitions, and so someone could write a
> uber-build that did
> > > something like this.
> > >
> > > If we have all of the pieces in separate repositories,
> though, where would
> > > the files for such an uber-build be checked in? That's
> one of the problems
> > > I have with the multi-repository solution - there is no
> place for files
> > > that span those repositories. If we have one repository
> split into pieces,
> > > then we still have the top level for these things.
>  > >
> >
> > On the multi-repository projects I've worked on, we had a
> special repository
> > just for integration tasks like this.
>
> So we'd need yet another repo - say struts-integration - just
> for this.
> Why is that better than just doing what we need within the
> repo that we
> have already?
>
> > > > But, the problem with thinking of Struts as one
> monothic build is that
> > > every aspect of the framework has to be perfect, all at
> the same time, before
> > > we can call it a "general availability"
> ready-for-prime-time release.  One of
> > > the many reasons 1.1 took so long was that if there was
> any bug in any
> > > component anywhere in the framework, everything
> gridlocked.  :(  :(   :(
> > >
> > > That doesn't need to be true if we don't want it to.
> Recall that for a
> > > time we had a separtely built, separately distributed
> component called
> > > struts-legacy to handle the data source situation. There
> is no need for a
> > > one-to-one correlation between repositories and
> distributable entities.
> > >
> > > > What we want to do ... need to do ... is be able to
> release fixes to
> > > components like the taglibs independently of the core
> controller. Likewise,
> > > we need to release changes to Struts EL or Struts Faces
> (once it goes 1.0)
> > > without having to be sure every other component is ready
> to roll. We should
> > > also be able to release updates to the example
> applications without
> > > re-releasing the rest of the framework, if that's all we
> want to roll right
> > > now.
> > >
> > > Absolutely. And the number of repositories we have is
> entirely orthogonal
> > > to this.
> > >
> >
> > Ultimately true, although it's still somewhat easier to
> visualize if you have
> > separate repositories.
> >
> > > > Some people may not like more JARs, but I know for
> certain that the single
> > > JAR approach is a momentum killer. It's made my life much
> more difficult, and
> > > I think it's chased away some Committers who became
> frustrated by having to
> > > "everything right" in order to one little feature into a
> formal release.
> > >
> > > For the people who want / need a single jar, it would be
> simple enough for
> > > us to provide an Ant target that explodes the desired
> individual jars and
> > > recombines them into a single jar. The only tricky part,
> I think, would be
> > > creating a manifest that identifies the versions of the
> individual pieces
> > > in that jar. That's assuming people want such a beast, of
> course. (I'm not
> > > in that camp myself, though, just as I'd never use the
> Commons Combo
> > > build.)
> > >
> > > > If we can get more code into the hands of more
> developers in less time,
> > > then a few more JARs seems like a small price to pay. :)
> > >
> > > +1
> > >
> >
> > Yep.
> >
> > > > Here's something else to mull over:
> > > >
> > > > Now that Struts is a TLP, we might want to talk about
> whether we want to
> > > ask the most popular open source Struts extensions --
> like Struts Menu,
> > > Workflow, Stxx, SSL, and TestCase -- whether they would
> like to donate their
> > > code to the ASF and live as Struts "opt" subprojects.
> This would be a
> > > continuation of what we started with Tiles, Validator,
> and Nested, which are
> > > all favorites with our community. People working on such
> packages might be
> > > brought on as Struts Committers, since they have proved
> they have what it
> > > takes to run a project, and after an appropriate period,
> later invited to
> > > join the Struts PMC.
> > > >
> > > > IMHO, when people talk about JSF replacing Struts, they
> are unaware of the
> > > true breadth of the Struts platform. Perhaps it's time we
> made sure people
> > > know how much they are missing :)
> > > >
> > > > A sad truth: In working with various teams managing
> larger projects, I've
> > > found a surprising reluctance to use extensions that were
> not distributed by
> > > the Struts project itself. By giving these very fine
> extensions "the nod", we
> > > can make them available to a greater number of Struts
> teams, to everyone's
> > > benefit. If we don't help make these extensions available
> to everyone, then
> > > we end up "hiding our light under a bushel".
> > > >
> > > > Now, I haven't brought this idea up to any of the other
> Committers, and
> > > have no idea how any else will feel about it. But it is
> something that I
> > > would personally like to work towards -- once we have our
> existing code
> > > "rationalized". (First things first!)
> > >
> > > I'd be open to it, but I think we have a lot of things
> we'd want to do to
> > > get our own house in order before we actually take action
> on this. I also
> > > think it might be a tricky issue in some respects. For
> example, we'll be
> > > faced with making subjective decisions on potentially
> substantial bodies
> > > of code, leading to the possibility of "why not mine?"
> kinds of things.
> > > For larger code bases, we'd also likely need to have some
> discussions with
> > > the incubator folks.
> > >
> > > But, as you say, let's get our own house in order first,
> and then come
> > > back and talk about this some more.
> > >
> > > --
> > > Martin Cooper
> > >
> > >
> > > >
> > > > -Ted.
> > > >
> >
> > Craig
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Paul Speed <ps...@progeeks.com>.

Ted Husted wrote:

> On Mon, 22 Mar 2004 23:49:31 -0800 (PST), Martin Cooper wrote:
> 
> 
> Well, as you mentioned, another way to go would be for some one to write a tool that could burst and rejar an arbitrary set of jars. (If one doesn't already exist.) The source for such a tool could live in the core since it's just something a volunteer would run offline and the upload. It wouldn't be a true deliverable. And, I'm not convinced that we even need to do such a thing. Even without a few extra JARs of our own, there are still all the Commons JARs. (Though I suppose we could roll together those too.) I'd tend to leave this for a end-user to do, say if there were distributing a particular Struts distribution to several teams in an enterprise. But it would be nice to provide a tool for this (if someone had the itch to write it.) It really sounds like a job for Sun :)
> 

Did you need something beyond what ANT already provides?

An untested example:

     <target name="bundle.struts">
         <jar jarfile="lib/struts-all.jar">
             <zipgroupfileset dir="lib/struts">
                 <include name="**/*.jar" />
             </zipgroupfileset>
         </jar>
     </target>

-Paul


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Ted Husted <hu...@apache.org>.
On Mon, 22 Mar 2004 23:49:31 -0800 (PST), Martin Cooper wrote:
>> On the multi-repository projects I've worked on, we had a special
>> repository  just for integration tasks like this.
>
> So we'd need yet another repo - say struts-integration - just for
> this. Why is that better than just doing what we need within the
> repo that we have already?

Well, as you mentioned, another way to go would be for some one to write a tool that could burst and rejar an arbitrary set of jars. (If one doesn't already exist.) The source for such a tool could live in the core since it's just something a volunteer would run offline and the upload. It wouldn't be a true deliverable. And, I'm not convinced that we even need to do such a thing. Even without a few extra JARs of our own, there are still all the Commons JARs. (Though I suppose we could roll together those too.) I'd tend to leave this for a end-user to do, say if there were distributing a particular Struts distribution to several teams in an enterprise. But it would be nice to provide a tool for this (if someone had the itch to write it.) It really sounds like a job for Sun :)


On Mon, 22 Mar 2004 20:50:24 -0800 (PST), Martin Cooper wrote:
> I'd be open to it, but I think we have a lot of things we'd want to
> do to get our own house in order before we actually take action on
> this. I also think it might be a tricky issue in some respects. For
> example, we'll be faced with making subjective decisions on
> potentially substantial bodies of code, leading to the possibility
> of "why not mine?" kinds of things. For larger code bases, we'd
> also likely need to have some discussions with the incubator folks.
>
> But, as you say, let's get our own house in order first, and then
> come back and talk about this some more.

And in deciding how to renovate our house, let's keep in mind that we may be having more children :)

How about if we split the difference: 

core module:  

/core
/site
/apps

opt-modules:

* opt-taglib
* opt-el
* opt-faces
* opt-dev ("sandbox")

So, we'd go from seven to five. 

Then, later on, if we invite some of our friends to join us, and they move in, we just add more opt modules. 

-Ted.



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Martin Cooper <ma...@apache.org>.
On Mon, 22 Mar 2004, Craig R. McClanahan wrote:

> Quoting Martin Cooper <ma...@apache.org>:
>
> > On Mon, 22 Mar 2004, Ted Husted wrote:
> >
> > > On Mon, 22 Mar 2004 11:36:37 -0700, Matt Raible wrote:
> > > > While it's great to break out things into separate "modules" - I'd
> > > > love to be able to get struts.jar w/ everything in it - including
> > > > EL and tags.  I can live with all the commons-* JARs (even if it is
> > > > annoying), but in general - the less JARs, the better.  It just
> > > > simplifies things for the developer.
> > > >
> > > > I don't care how things are partitioned in CVS, as long as
> > > > everything builds with one checkout and one command.
> > >
> > > If that were someone's itch, it could certainly be done. Ant doesn't know
> > about the module partitions, and so someone could write a uber-build that did
> > something like this.
> >
> > If we have all of the pieces in separate repositories, though, where would
> > the files for such an uber-build be checked in? That's one of the problems
> > I have with the multi-repository solution - there is no place for files
> > that span those repositories. If we have one repository split into pieces,
> > then we still have the top level for these things.
 > >
>
> On the multi-repository projects I've worked on, we had a special repository
> just for integration tasks like this.

So we'd need yet another repo - say struts-integration - just for this.
Why is that better than just doing what we need within the repo that we
have already?

> > > But, the problem with thinking of Struts as one monothic build is that
> > every aspect of the framework has to be perfect, all at the same time, before
> > we can call it a "general availability" ready-for-prime-time release.  One of
> > the many reasons 1.1 took so long was that if there was any bug in any
> > component anywhere in the framework, everything gridlocked.  :(  :(   :(
> >
> > That doesn't need to be true if we don't want it to. Recall that for a
> > time we had a separtely built, separately distributed component called
> > struts-legacy to handle the data source situation. There is no need for a
> > one-to-one correlation between repositories and distributable entities.
> >
> > > What we want to do ... need to do ... is be able to release fixes to
> > components like the taglibs independently of the core controller. Likewise,
> > we need to release changes to Struts EL or Struts Faces (once it goes 1.0)
> > without having to be sure every other component is ready to roll. We should
> > also be able to release updates to the example applications without
> > re-releasing the rest of the framework, if that's all we want to roll right
> > now.
> >
> > Absolutely. And the number of repositories we have is entirely orthogonal
> > to this.
> >
>
> Ultimately true, although it's still somewhat easier to visualize if you have
> separate repositories.
>
> > > Some people may not like more JARs, but I know for certain that the single
> > JAR approach is a momentum killer. It's made my life much more difficult, and
> > I think it's chased away some Committers who became frustrated by having to
> > "everything right" in order to one little feature into a formal release.
> >
> > For the people who want / need a single jar, it would be simple enough for
> > us to provide an Ant target that explodes the desired individual jars and
> > recombines them into a single jar. The only tricky part, I think, would be
> > creating a manifest that identifies the versions of the individual pieces
> > in that jar. That's assuming people want such a beast, of course. (I'm not
> > in that camp myself, though, just as I'd never use the Commons Combo
> > build.)
> >
> > > If we can get more code into the hands of more developers in less time,
> > then a few more JARs seems like a small price to pay. :)
> >
> > +1
> >
>
> Yep.
>
> > > Here's something else to mull over:
> > >
> > > Now that Struts is a TLP, we might want to talk about whether we want to
> > ask the most popular open source Struts extensions -- like Struts Menu,
> > Workflow, Stxx, SSL, and TestCase -- whether they would like to donate their
> > code to the ASF and live as Struts "opt" subprojects. This would be a
> > continuation of what we started with Tiles, Validator, and Nested, which are
> > all favorites with our community. People working on such packages might be
> > brought on as Struts Committers, since they have proved they have what it
> > takes to run a project, and after an appropriate period, later invited to
> > join the Struts PMC.
> > >
> > > IMHO, when people talk about JSF replacing Struts, they are unaware of the
> > true breadth of the Struts platform. Perhaps it's time we made sure people
> > know how much they are missing :)
> > >
> > > A sad truth: In working with various teams managing larger projects, I've
> > found a surprising reluctance to use extensions that were not distributed by
> > the Struts project itself. By giving these very fine extensions "the nod", we
> > can make them available to a greater number of Struts teams, to everyone's
> > benefit. If we don't help make these extensions available to everyone, then
> > we end up "hiding our light under a bushel".
> > >
> > > Now, I haven't brought this idea up to any of the other Committers, and
> > have no idea how any else will feel about it. But it is something that I
> > would personally like to work towards -- once we have our existing code
> > "rationalized". (First things first!)
> >
> > I'd be open to it, but I think we have a lot of things we'd want to do to
> > get our own house in order before we actually take action on this. I also
> > think it might be a tricky issue in some respects. For example, we'll be
> > faced with making subjective decisions on potentially substantial bodies
> > of code, leading to the possibility of "why not mine?" kinds of things.
> > For larger code bases, we'd also likely need to have some discussions with
> > the incubator folks.
> >
> > But, as you say, let's get our own house in order first, and then come
> > back and talk about this some more.
> >
> > --
> > Martin Cooper
> >
> >
> > >
> > > -Ted.
> > >
>
> Craig
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Craig R. McClanahan" <cr...@apache.org>.
Quoting Martin Cooper <ma...@apache.org>:

> On Mon, 22 Mar 2004, Ted Husted wrote:
> 
> > On Mon, 22 Mar 2004 11:36:37 -0700, Matt Raible wrote:
> > > While it's great to break out things into separate "modules" - I'd
> > > love to be able to get struts.jar w/ everything in it - including
> > > EL and tags.  I can live with all the commons-* JARs (even if it is
> > > annoying), but in general - the less JARs, the better.  It just
> > > simplifies things for the developer.
> > >
> > > I don't care how things are partitioned in CVS, as long as
> > > everything builds with one checkout and one command.
> >
> > If that were someone's itch, it could certainly be done. Ant doesn't know
> about the module partitions, and so someone could write a uber-build that did
> something like this.
> 
> If we have all of the pieces in separate repositories, though, where would
> the files for such an uber-build be checked in? That's one of the problems
> I have with the multi-repository solution - there is no place for files
> that span those repositories. If we have one repository split into pieces,
> then we still have the top level for these things.
> 

On the multi-repository projects I've worked on, we had a special repository
just for integration tasks like this.

> > But, the problem with thinking of Struts as one monothic build is that
> every aspect of the framework has to be perfect, all at the same time, before
> we can call it a "general availability" ready-for-prime-time release.  One of
> the many reasons 1.1 took so long was that if there was any bug in any
> component anywhere in the framework, everything gridlocked.  :(  :(   :(
> 
> That doesn't need to be true if we don't want it to. Recall that for a
> time we had a separtely built, separately distributed component called
> struts-legacy to handle the data source situation. There is no need for a
> one-to-one correlation between repositories and distributable entities.
> 
> > What we want to do ... need to do ... is be able to release fixes to
> components like the taglibs independently of the core controller. Likewise,
> we need to release changes to Struts EL or Struts Faces (once it goes 1.0)
> without having to be sure every other component is ready to roll. We should
> also be able to release updates to the example applications without
> re-releasing the rest of the framework, if that's all we want to roll right
> now.
> 
> Absolutely. And the number of repositories we have is entirely orthogonal
> to this.
> 

Ultimately true, although it's still somewhat easier to visualize if you have
separate repositories.

> > Some people may not like more JARs, but I know for certain that the single
> JAR approach is a momentum killer. It's made my life much more difficult, and
> I think it's chased away some Committers who became frustrated by having to
> "everything right" in order to one little feature into a formal release.
> 
> For the people who want / need a single jar, it would be simple enough for
> us to provide an Ant target that explodes the desired individual jars and
> recombines them into a single jar. The only tricky part, I think, would be
> creating a manifest that identifies the versions of the individual pieces
> in that jar. That's assuming people want such a beast, of course. (I'm not
> in that camp myself, though, just as I'd never use the Commons Combo
> build.)
> 
> > If we can get more code into the hands of more developers in less time,
> then a few more JARs seems like a small price to pay. :)
> 
> +1
> 

Yep.

> > Here's something else to mull over:
> >
> > Now that Struts is a TLP, we might want to talk about whether we want to
> ask the most popular open source Struts extensions -- like Struts Menu,
> Workflow, Stxx, SSL, and TestCase -- whether they would like to donate their
> code to the ASF and live as Struts "opt" subprojects. This would be a
> continuation of what we started with Tiles, Validator, and Nested, which are
> all favorites with our community. People working on such packages might be
> brought on as Struts Committers, since they have proved they have what it
> takes to run a project, and after an appropriate period, later invited to
> join the Struts PMC.
> >
> > IMHO, when people talk about JSF replacing Struts, they are unaware of the
> true breadth of the Struts platform. Perhaps it's time we made sure people
> know how much they are missing :)
> >
> > A sad truth: In working with various teams managing larger projects, I've
> found a surprising reluctance to use extensions that were not distributed by
> the Struts project itself. By giving these very fine extensions "the nod", we
> can make them available to a greater number of Struts teams, to everyone's
> benefit. If we don't help make these extensions available to everyone, then
> we end up "hiding our light under a bushel".
> >
> > Now, I haven't brought this idea up to any of the other Committers, and
> have no idea how any else will feel about it. But it is something that I
> would personally like to work towards -- once we have our existing code
> "rationalized". (First things first!)
> 
> I'd be open to it, but I think we have a lot of things we'd want to do to
> get our own house in order before we actually take action on this. I also
> think it might be a tricky issue in some respects. For example, we'll be
> faced with making subjective decisions on potentially substantial bodies
> of code, leading to the possibility of "why not mine?" kinds of things.
> For larger code bases, we'd also likely need to have some discussions with
> the incubator folks.
> 
> But, as you say, let's get our own house in order first, and then come
> back and talk about this some more.
> 
> --
> Martin Cooper
> 
> 
> >
> > -Ted.
> >

Craig



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Martin Cooper <ma...@apache.org>.
On Mon, 22 Mar 2004, Ted Husted wrote:

> On Mon, 22 Mar 2004 11:36:37 -0700, Matt Raible wrote:
> > While it's great to break out things into separate "modules" - I'd
> > love to be able to get struts.jar w/ everything in it - including
> > EL and tags.  I can live with all the commons-* JARs (even if it is
> > annoying), but in general - the less JARs, the better.  It just
> > simplifies things for the developer.
> >
> > I don't care how things are partitioned in CVS, as long as
> > everything builds with one checkout and one command.
>
> If that were someone's itch, it could certainly be done. Ant doesn't know about the module partitions, and so someone could write a uber-build that did something like this.

If we have all of the pieces in separate repositories, though, where would
the files for such an uber-build be checked in? That's one of the problems
I have with the multi-repository solution - there is no place for files
that span those repositories. If we have one repository split into pieces,
then we still have the top level for these things.

> But, the problem with thinking of Struts as one monothic build is that every aspect of the framework has to be perfect, all at the same time, before we can call it a "general availability" ready-for-prime-time release.  One of the many reasons 1.1 took so long was that if there was any bug in any component anywhere in the framework, everything gridlocked.  :(  :(   :(

That doesn't need to be true if we don't want it to. Recall that for a
time we had a separtely built, separately distributed component called
struts-legacy to handle the data source situation. There is no need for a
one-to-one correlation between repositories and distributable entities.

> What we want to do ... need to do ... is be able to release fixes to components like the taglibs independently of the core controller. Likewise, we need to release changes to Struts EL or Struts Faces (once it goes 1.0) without having to be sure every other component is ready to roll. We should also be able to release updates to the example applications without re-releasing the rest of the framework, if that's all we want to roll right now.

Absolutely. And the number of repositories we have is entirely orthogonal
to this.

> Some people may not like more JARs, but I know for certain that the single JAR approach is a momentum killer. It's made my life much more difficult, and I think it's chased away some Committers who became frustrated by having to "everything right" in order to one little feature into a formal release.

For the people who want / need a single jar, it would be simple enough for
us to provide an Ant target that explodes the desired individual jars and
recombines them into a single jar. The only tricky part, I think, would be
creating a manifest that identifies the versions of the individual pieces
in that jar. That's assuming people want such a beast, of course. (I'm not
in that camp myself, though, just as I'd never use the Commons Combo
build.)

> If we can get more code into the hands of more developers in less time, then a few more JARs seems like a small price to pay. :)

+1

> Here's something else to mull over:
>
> Now that Struts is a TLP, we might want to talk about whether we want to ask the most popular open source Struts extensions -- like Struts Menu, Workflow, Stxx, SSL, and TestCase -- whether they would like to donate their code to the ASF and live as Struts "opt" subprojects. This would be a continuation of what we started with Tiles, Validator, and Nested, which are all favorites with our community. People working on such packages might be brought on as Struts Committers, since they have proved they have what it takes to run a project, and after an appropriate period, later invited to join the Struts PMC.
>
> IMHO, when people talk about JSF replacing Struts, they are unaware of the true breadth of the Struts platform. Perhaps it's time we made sure people know how much they are missing :)
>
> A sad truth: In working with various teams managing larger projects, I've found a surprising reluctance to use extensions that were not distributed by the Struts project itself. By giving these very fine extensions "the nod", we can make them available to a greater number of Struts teams, to everyone's benefit. If we don't help make these extensions available to everyone, then we end up "hiding our light under a bushel".
>
> Now, I haven't brought this idea up to any of the other Committers, and have no idea how any else will feel about it. But it is something that I would personally like to work towards -- once we have our existing code "rationalized". (First things first!)

I'd be open to it, but I think we have a lot of things we'd want to do to
get our own house in order before we actually take action on this. I also
think it might be a tricky issue in some respects. For example, we'll be
faced with making subjective decisions on potentially substantial bodies
of code, leading to the possibility of "why not mine?" kinds of things.
For larger code bases, we'd also likely need to have some discussions with
the incubator folks.

But, as you say, let's get our own house in order first, and then come
back and talk about this some more.

--
Martin Cooper


>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Struts TLP Sub-projects (RE: Making Struts Build Easier)

Posted by James Holmes <ja...@jamesholmes.com>.
+++++1 on this!!

You hit the nail on the head.  Many people (mostly managers) are reluctant
to adopt Struts add-ons because they are not perceived as having the same
"tried and true" stamp as the official Struts core.  I think doing this
would be a huge boon for Struts and would foster a lot of the development
interest that's been talked about over the past couple of days.

Also, +1 on having the creators of those projects become committers so long
as they've shown a protracted history in maintaining their respective
projects and have an interest to continue doing so.

-James
http://www.jamesholmes.com/struts/


-------------------------------------------------------------
Here's something else to mull over: 

Now that Struts is a TLP, we might want to talk about whether we want to ask
the most popular open source Struts extensions -- like Struts Menu,
Workflow, Stxx, SSL, and TestCase -- whether they would like to donate their
code to the ASF and live as Struts "opt" subprojects. This would be a
continuation of what we started with Tiles, Validator, and Nested, which are
all favorites with our community. People working on such packages might be
brought on as Struts Committers, since they have proved they have what it
takes to run a project, and after an appropriate period, later invited to
join the Struts PMC. 

IMHO, when people talk about JSF replacing Struts, they are unaware of the
true breadth of the Struts platform. Perhaps it's time we made sure people
know how much they are missing :)

A sad truth: In working with various teams managing larger projects, I've
found a surprising reluctance to use extensions that were not distributed by
the Struts project itself. By giving these very fine extensions "the nod",
we can make them available to a greater number of Struts teams, to
everyone's benefit. If we don't help make these extensions available to
everyone, then we end up "hiding our light under a bushel".

Now, I haven't brought this idea up to any of the other Committers, and have
no idea how any else will feel about it. But it is something that I would
personally like to work towards -- once we have our existing code
"rationalized". (First things first!)

-Ted.


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Ted Husted <hu...@apache.org>.
On Mon, 22 Mar 2004 11:36:37 -0700, Matt Raible wrote:
> While it's great to break out things into separate "modules" - I'd
> love to be able to get struts.jar w/ everything in it - including
> EL and tags.  I can live with all the commons-* JARs (even if it is
> annoying), but in general - the less JARs, the better.  It just
> simplifies things for the developer.
>
> I don't care how things are partitioned in CVS, as long as
> everything builds with one checkout and one command.

If that were someone's itch, it could certainly be done. Ant doesn't know about the module partitions, and so someone could write a uber-build that did something like this. 

But, the problem with thinking of Struts as one monothic build is that every aspect of the framework has to be perfect, all at the same time, before we can call it a "general availability" ready-for-prime-time release.  One of the many reasons 1.1 took so long was that if there was any bug in any component anywhere in the framework, everything gridlocked.  :(  :(   :(

What we want to do ... need to do ... is be able to release fixes to components like the taglibs independently of the core controller. Likewise, we need to release changes to Struts EL or Struts Faces (once it goes 1.0) without having to be sure every other component is ready to roll. We should also be able to release updates to the example applications without re-releasing the rest of the framework, if that's all we want to roll right now. 

Some people may not like more JARs, but I know for certain that the single JAR approach is a momentum killer. It's made my life much more difficult, and I think it's chased away some Committers who became frustrated by having to "everything right" in order to one little feature into a formal release. 

If we can get more code into the hands of more developers in less time, then a few more JARs seems like a small price to pay. :)

Here's something else to mull over: 

Now that Struts is a TLP, we might want to talk about whether we want to ask the most popular open source Struts extensions -- like Struts Menu, Workflow, Stxx, SSL, and TestCase -- whether they would like to donate their code to the ASF and live as Struts "opt" subprojects. This would be a continuation of what we started with Tiles, Validator, and Nested, which are all favorites with our community. People working on such packages might be brought on as Struts Committers, since they have proved they have what it takes to run a project, and after an appropriate period, later invited to join the Struts PMC. 

IMHO, when people talk about JSF replacing Struts, they are unaware of the true breadth of the Struts platform. Perhaps it's time we made sure people know how much they are missing :)

A sad truth: In working with various teams managing larger projects, I've found a surprising reluctance to use extensions that were not distributed by the Struts project itself. By giving these very fine extensions "the nod", we can make them available to a greater number of Struts teams, to everyone's benefit. If we don't help make these extensions available to everyone, then we end up "hiding our light under a bushel".

Now, I haven't brought this idea up to any of the other Committers, and have no idea how any else will feel about it. But it is something that I would personally like to work towards -- once we have our existing code "rationalized". (First things first!)

-Ted.



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Matt Raible <li...@raibledesigns.com>.
On Mar 22, 2004, at 11:28 AM, Ted Husted wrote:

> On Mon, 22 Mar 2004 09:53:02 -0800, Craig R. McClanahan wrote:
>> Yep ... that's why we need to finish the "how many repositories"
>> discussion so we can start migrating towards something that is
>> simpler.
>
> I continue to think that the easiest thing in the long run will be a 
> module for each product. Where a product is equivalent to a Maven 
> artifact or a deliverable with its own release cycle.
>
> So, if infrastructure doesn't care, and we can centralize the 
> permissions, I'd like to go back to something like
>
> * core (including tiles and validator)
> * examples
> * site
> * whiteboard (or "sandbox")
>
> * opt-taglib
> * opt-el
> * opt-faces
>
> -Ted.

While it's great to break out things into separate "modules" - I'd love 
to be able to get struts.jar w/ everything in it - including EL and 
tags.  I can live with all the commons-* JARs (even if it is annoying), 
but in general - the less JARs, the better.  It just simplifies things 
for the developer.

I don't care how things are partitioned in CVS, as long as everything 
builds with one checkout and one command.

My $0.02.

Matt


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Ted Husted <hu...@apache.org>.
On Mon, 22 Mar 2004 09:53:02 -0800, Craig R. McClanahan wrote:
> Yep ... that's why we need to finish the "how many repositories"
> discussion so we can start migrating towards something that is
> simpler.

I continue to think that the easiest thing in the long run will be a module for each product. Where a product is equivalent to a Maven artifact or a deliverable with its own release cycle. 

So, if infrastructure doesn't care, and we can centralize the permissions, I'd like to go back to something like

* core (including tiles and validator)
* examples
* site
* whiteboard (or "sandbox")

* opt-taglib
* opt-el
* opt-faces

-Ted.



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by "Craig R. McClanahan" <cr...@apache.org>.
Quoting David Graham <gr...@yahoo.com>:

> Personally, I find the Struts build files to be complex and confusing. 
> I've come to associate Maven with easy builds because building commons
> components (including the distro, website, tests, etc) is a snap compared
> to Struts.  I agree that storing jars in cvs isn't a good idea which is
> why using Maven is so nice; it downloads the correct jars automatically.  
> 

It's also possible to set up Maven with a local repository so that offline
builds still work, too.

> Anything we can do to make the build more straightforward, whether it's
> with Ant or Maven, is a good thing :-).
> 

Yep ... that's why we need to finish the "how many repositories" discussion so
we can start migrating towards something that is simpler.

> David

Craig

> 
> --- Joe Germuska <Jo...@Germuska.com> wrote:
> > >For me, the main discouraging thing about contributing to the 
> > >development of Struts has been the build process.  In the past, you 
> > >had to download all of jakarta-commons and spend a day or two 
> > >figuring out how to get that to build.  Recently, I tried to build 
> > >Struts and was successful using the Maven stuff.  Personally, I 
> > >don't mind using Maven, but I don't know that it should be 
> > >*required* to build a project from scratch.  I'd love to be able to 
> > >cvs co Struts, navigate to jakarta-struts and type "ant jar".
> > >
> > >I realize this is no easy thing to accomplish with a build file - 
> > >but it has been the most discouraging factor for me. ;-)
> > 
> > The only way we could accomplish something like that with a build 
> > file would be by including JARs in CVS, and if you ask me, there are 
> > enough reasons why that's a bad idea that I prefer the way it is, 
> > even though I'd very much like to see people feel more comfortable 
> > getting in and working on Struts source code.
> > 
> > When you say "I don't know that [Maven] should be *required*..." is 
> > your point that Ant is a widely accepted Java tool, while Maven has 
> > yet to cut a 1.0 release?  That's fair -- just want to make sure I 
> > understand you.
> > 
> > The build.xml file generated by 'maven ant' uses the ant 'get' task 
> > and the Maven iBiblio repository to download dependencies; we could 
> > perhaps look at copying some of that into our ant script to reduce 
> > build.properties to being more about configuration stuff and less 
> > about dependency stuff.
> > 
> > Joe
> > 
> > -- 
> > Joe Germuska            
> > Joe@Germuska.com  
> > http://blog.germuska.com    
> >        "Imagine if every Thursday your shoes exploded if you tied them 
> > the usual way.  This happens to us all the time with computers, and 
> > nobody thinks of complaining."
> >              -- Jef Raskin
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> > 
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance Tax Center - File online. File on time.
> http://taxes.yahoo.com/filing.html
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Joe Germuska <Jo...@Germuska.com>.
At 11:52 AM -0500 3/22/04, Mike Kienenberger wrote:
>Two weeks ago, I tried to build the struts 1.1 source package against
>commons-collections-3.0.jar in order to run the unit tests and insure struts
>still worked properly.  After several hours of trying to set it up and make
...
>  Like those who posted before me, I don't care if it's
>ant or maven, only that it works.

Do you have the energy to try again with Maven?  It should be as 
simple as adding a couple of lines to "build.properties" in your 
local Struts CVS sandbox:

maven.jar.override=on
maven.jar.commons-collections=3.0

Joe

-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
       "Imagine if every Thursday your shoes exploded if you tied them 
the usual way.  This happens to us all the time with computers, and 
nobody thinks of complaining."
             -- Jef Raskin

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by Mike Kienenberger <mk...@alaska.net>.
David Graham <gr...@yahoo.com> wrote:
> Personally, I find the Struts build files to be complex and confusing. 

Two weeks ago, I tried to build the struts 1.1 source package against 
commons-collections-3.0.jar in order to run the unit tests and insure struts 
still worked properly.  After several hours of trying to set it up and make 
it work, I finally gave up.  There is definitely room for improvement in the 
build/test process.  Like those who posted before me, I don't care if it's 
ant or maven, only that it works.

As a counter-example, on the Cayenne project we have 24 external jar files 
that are stored in "otherlib" on CVS, but at least the project builds and 
tests "out of the box."

-Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Re: Making Struts Build Easier (Re: "coming out" for JSF + Struts, was: Struts JSR?)

Posted by David Graham <gr...@yahoo.com>.
Personally, I find the Struts build files to be complex and confusing. 
I've come to associate Maven with easy builds because building commons
components (including the distro, website, tests, etc) is a snap compared
to Struts.  I agree that storing jars in cvs isn't a good idea which is
why using Maven is so nice; it downloads the correct jars automatically.  

Anything we can do to make the build more straightforward, whether it's
with Ant or Maven, is a good thing :-).

David

--- Joe Germuska <Jo...@Germuska.com> wrote:
> >For me, the main discouraging thing about contributing to the 
> >development of Struts has been the build process.  In the past, you 
> >had to download all of jakarta-commons and spend a day or two 
> >figuring out how to get that to build.  Recently, I tried to build 
> >Struts and was successful using the Maven stuff.  Personally, I 
> >don't mind using Maven, but I don't know that it should be 
> >*required* to build a project from scratch.  I'd love to be able to 
> >cvs co Struts, navigate to jakarta-struts and type "ant jar".
> >
> >I realize this is no easy thing to accomplish with a build file - 
> >but it has been the most discouraging factor for me. ;-)
> 
> The only way we could accomplish something like that with a build 
> file would be by including JARs in CVS, and if you ask me, there are 
> enough reasons why that's a bad idea that I prefer the way it is, 
> even though I'd very much like to see people feel more comfortable 
> getting in and working on Struts source code.
> 
> When you say "I don't know that [Maven] should be *required*..." is 
> your point that Ant is a widely accepted Java tool, while Maven has 
> yet to cut a 1.0 release?  That's fair -- just want to make sure I 
> understand you.
> 
> The build.xml file generated by 'maven ant' uses the ant 'get' task 
> and the Maven iBiblio repository to download dependencies; we could 
> perhaps look at copying some of that into our ant script to reduce 
> build.properties to being more about configuration stuff and less 
> about dependency stuff.
> 
> Joe
> 
> -- 
> Joe Germuska            
> Joe@Germuska.com  
> http://blog.germuska.com    
>        "Imagine if every Thursday your shoes exploded if you tied them 
> the usual way.  This happens to us all the time with computers, and 
> nobody thinks of complaining."
>              -- Jef Raskin
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 


__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org