On 11/3/05, James Mitchell <[EMAIL PROTECTED]> wrote:
> As far as distribution size (for releases), I suppose we could take
> an approach where we package the dependencies under a separate folder
> (similar to what Spring and JSF RI do), and provide a build.bat and
> build.sh file that can assemble
As far as distribution size (for releases), I suppose we could take
an approach where we package the dependencies under a separate folder
(similar to what Spring and JSF RI do), and provide a build.bat and
build.sh file that can assemble it on the other end.
--
James Mitchell
678.910.8017
Ted Husted wrote:
So let's go with this then:
* The Struts Core Library distribution can start out at 1.3_00, and
not increment again until all of its components are GA. When the
Struts Core subproject increments a major or minor number, then the
Library distribution will follow suit.
* When th
So let's go with this then:
* The Struts Core Library distribution can start out at 1.3_00, and
not increment again until all of its components are GA. When the
Struts Core subproject increments a major or minor number, then the
Library distribution will follow suit.
* When the new subprojects (S
On 11/3/05, Hubert Rabago <[EMAIL PROTECTED]> wrote:
>
> "Struts Classic" keeps making me think "That's not the version I want
> -- I want Struts Modern".
>
> On 11/3/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> > VW was making Bug/Beetle for 50 years or so, it acquired Classic
> > status som
"Struts Classic" keeps making me think "That's not the version I want
-- I want Struts Modern".
On 11/3/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> VW was making Bug/Beetle for 50 years or so, it acquired Classic
> status sometimes in 60-ies, before Golf/Rabbit was introduced ;-)
Well, no
On 11/3/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> Michael Jouravlev wrote:
> > I still don't get what is wrong with Struts Classic. Levi's 501 is
> > classic and looks much better than stupid baggy pants. Heinz Original
> > is better than some newer products. Can you reinvent ketchup? This
Michael Jouravlev wrote:
I still don't get what is wrong with Struts Classic. Levi's 501 is
classic and looks much better than stupid baggy pants. Heinz Original
is better than some newer products. Can you reinvent ketchup? This can
be an idea for a slogan ;-)
How can you have something that is
On 11/3/05, Laurie Harper <[EMAIL PROTECTED]> wrote:
> On the name, I agree with others that 'Struts Classic' gives the wrong
> impresion, but I'm not too keen on 'Struts Core Library'. That suggests
> that it's part of a larger set of libraries you need to download to use
> 'Struts' for those used
On 11/3/05, Ted Husted <[EMAIL PROTECTED]> wrote:
> At this point, my suggestion would be to just give the Library
> distribution a sequential counter. The first GA release could be _001,
> and the next _002, and so forth.
>
> * struts_core_library_001.zip
> * struts_core_library_002.zip
I like t
Wendy Smoak wrote:
The following page has been changed by TedHusted:
http://wiki.apache.org/struts/StrutsClassicRelease130
The comment on the change is:
Per discussions on dev@, phase in the "Struts Core Library" idea.
- * Download the Struts 1.3.0 distribution from
http://svn.apache.org/dist
On 11/3/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> >
> Would there be any value of not versioning the bundle at all, forcing
> people to refer to the versions of the individual components? The
> bundle could then represent the latest version of those components, for
> convenience in downloading, an
On 11/3/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
>
> On 11/3/05, Ted Husted <[EMAIL PROTECTED]> wrote:
> > Or, we could just forget the whole thing and have only the individual
> > subproject releases. The bundle isn't mission critical; it was only
> > meant as a convenience.
>
> Bundle is
On 11/3/05, Ted Husted <[EMAIL PROTECTED]> wrote:
> Or, we could just forget the whole thing and have only the individual
> subproject releases. The bundle isn't mission critical; it was only
> meant as a convenience.
Bundle is critical, it ensures communication between teams ("Works for
me... Whi
Ted Husted said:
> Or, we could just forget the whole thing and have only the
> individual subproject releases. The bundle isn't mission
> critical; it was only meant as a convenience.
Would there be any value of not versioning the bundle at all, forcing
people to refer to the versions of the in
On Nov 3, 2005, at 12:12 PM, Ted Husted wrote:
At this point, my suggestion would be to just give the Library
distribution a sequential counter. The first GA release could be _001,
and the next _002, and so forth.
* struts_core_library_001.zip
* struts_core_library_002.zip
Or, we could just f
On 11/3/05, Martin Cooper <[EMAIL PROTECTED]> wrote:
> they will. I think it's highly unlikely that we'll want to rev the bundled
> distribution without a rev of struts-core, since people can download updated
> add-ons without having to grab the entire bundle, so I don't foresee issues
> there. (An
On 11/3/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> > This way it's always clear which distro a none-core subproject release
> > works with.
> > (i.e. you can't be sure about using taglib-1.3.1.2 with core-1.3.0,
> > but you're sure that taglib-1.3.0.4 will work)
>
> I like this. 1.3.1 does
On 11/3/05, Hubert Rabago <[EMAIL PROTECTED]> wrote:
>
> What about this.
>
> Struts 1.3.0 Distro
> - struts-core-1.3.0
> - struts-taglib-1.3.0
> - struts-tiles-1.3.0
> - struts-el-1.3.0
> - struts-apps-1.3.0
> - struts-site-1.3.0
> - struts-extras-1.3.0
>
> Subprojects can have their own independe
On 11/3/05, Hubert Rabago <[EMAIL PROTECTED]> wrote:
> What about this.
>
> Struts 1.3.0 Distro
> - struts-core-1.3.0
> - struts-taglib-1.3.0
> - struts-tiles-1.3.0
> - struts-el-1.3.0
> - struts-apps-1.3.0
> - struts-site-1.3.0
> - struts-extras-1.3.0
>
> Subprojects can have their own independent
On 11/3/05, Greg Reddin <[EMAIL PROTECTED]> wrote:
> One queston: Will we ever release the distro again? Or will each
> subproject just release independently?
Right now, I'm thinking that there will be an initial "test"
distribution when the original seven dwarfs are ready for wider
testing. Afte
What about this.
Struts 1.3.0 Distro
- struts-core-1.3.0
- struts-taglib-1.3.0
- struts-tiles-1.3.0
- struts-el-1.3.0
- struts-apps-1.3.0
- struts-site-1.3.0
- struts-extras-1.3.0
Subprojects can have their own independent release numbers all being
1.3.0.x, with the "1.3.0" dictated by struts-cor
On 11/3/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>
> After five years, the concept of Struts as a product is not going to
> go away so easily.
>
> Whether we call it 'Classic' or 'Core Library' or something else, I
> really think it needs to have 1.3 in the name and contain the 1.3.x
> versions
On 11/3/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> I missed the decision to include BSF, Flow and Faces. I don't think
> they belong in this distribution-- they have declared dependencies on
> Struts 1.2.7 and prior.
The comment on the Release Plan means to say that any Apache Struts
extension
How Eclipse recommends their plugin versions, for RCP apps: a distro
such as 3.1 "can" have modules (plugins) that have different versions,
but the recommended way is to push the distro version to the plugins, so
whatever plugins were 3.1.4 or whatever become 3.2.0 in the next distro.
People un
On 11/2/05, Ted Husted <[EMAIL PROTECTED]> wrote:
> I started to do that, but the idea was to also include the new
> subprojects, like Scripting and Flow and Faces, which would start at a
> 1.0.0 release. It seemed consistant to start with 1.0.0.
I missed the decision to include BSF, Flow and Fac
I guess I long for simplicity. I'm cool with the way everything is
structured. I would prefer a version number on the distro. And to
me it seems more natural to start it with 1.3.0. That's what we're
doing with the Tiles subproject. Even though it's really release 0.1
of the Tiles subp
On 11/2/05, Ted Husted <[EMAIL PROTECTED]> wrote:
>
> It's not uncommon for branded products to use dates as an identifier.
> Microsoft does it all the time. Of course, whether they actually test
> those products, I won't venture to say. :)
Sun has tried that branding approach as well on occastio
It's not uncommon for branded products to use dates as an identifier.
Microsoft does it all the time. Of course, whether they actually test
those products, I won't venture to say. :)
On 11/2/05, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> *That* is the characteristic that a nightly build type
Ted Husted wrote:
As Martin has already explained, there is an experimental area called
the Sandbox, and that's where Ti lives now. Shale has already been
there and done that. Shale is not an experiment. Shale is a
first-class citizen of the Apache Struts project. Get used to it.
Yes, I underst
On 11/2/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> If there was an "experimentation" group, or a "Future Struts Proposals",
> or something along those lines, which could include Ti and others as
> well, then I believe that more accurately describes how these things
> relate to each other.
Whether "classic" has a bad flair or not, it is much closer to real
state of things, than Struts Core, which is not actually a core. Using
a fancier name (from the point of view of some marketing-affected
people) instead of cleaner and true name does not make much sense to
me. Neither as 2 calories
Ted Husted wrote:
On 11/2/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
Why wouldn't there simply be a distro called Struts that includes Core
(which happens to map to the core subproject) and the original seven
subprojects, plus the three new ones if you want?
There is. But, it is not na
On 11/2/05, Ted Husted <[EMAIL PROTECTED]> wrote:
> On 11/2/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > I like the new name, but have reservations about starting with version
> > 1.0.0.
> >
> > I know this is the first ever "Struts Core Library", but to most
> > people it's just Struts, and Str
On 11/2/05, Ted Husted <[EMAIL PROTECTED]> wrote:
>
> On 11/2/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> > Why wouldn't there simply be a distro called Struts that includes Core
> > (which happens to map to the core subproject) and the original seven
> > subprojects, plus the three new ones
On 11/2/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> Why wouldn't there simply be a distro called Struts that includes Core
> (which happens to map to the core subproject) and the original seven
> subprojects, plus the three new ones if you want?
There is. But, it is not named "Struts" becau
I for one would have no objection to dating. That's a good compromise.
I still think a version number would be better, but a date I could
certainly live with.
The naming I still would contend is confusing though.
Why wouldn't there simply be a distro called Struts that includes Core
(which
On 11/2/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> I expected to see a Struts distro that combined core and flow and
> scripting and whatever else that when combined formed what we know now
> as Struts. Anything else would be an extension.
By a distribution I mean that we zip up subprojec
I find this to be even more confusing on two counts...
First, the version numbers, I thought the idea was that subprojects
could develop independently of one another... in that case, it doesn't
really matter if they all start at 1.0.0 or not.
Second, I know we discussed this yesterday, but I
On 11/2/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> I like the new name, but have reservations about starting with version 1.0.0.
>
> I know this is the first ever "Struts Core Library", but to most
> people it's just Struts, and Struts already had a 1.0 release.
>
> Yes, it's a marketing thing. :
At 7:44 PM -0700 11/2/05, Wendy Smoak wrote:
> The following page has been changed by TedHusted:
http://wiki.apache.org/struts/StrutsClassicRelease130
The comment on the change is:
Per discussions on dev@, phase in the "Struts Core Library" idea.
- * Download the Struts 1.3.0 distributio
41 matches
Mail list logo
