The bootstrap folder contains primarily Ivy jars, which is needed to pull down
the rest of the dependencies. The Ant build relies on those dependencies to
execute its tasks, one of which generates the TLD from XDoclet annotations.
Don
Ted Husted wrote:
On 7/18/06, Don Brown <[EMAIL PROTECTED
On 7/18/06, Don Brown <[EMAIL PROTECTED]> wrote:
I created a ticket that summarizes the current Ant build discussion and lays out
the tasks.
https://issues.apache.org/struts/browse/WW-1384
So we need what's in the "bootstrap" folder or taglib generation?
-Ted.
---
I created a ticket that summarizes the current Ant build discussion and lays out
the tasks.
https://issues.apache.org/struts/browse/WW-1384
Don
Ted Husted wrote:
Given the Maven build, do we still need the /lib/bootstrap folder?
* http://svn.apache.org/viewvc/struts/struts2/trunk/lib/bootstr
Given the Maven build, do we still need the /lib/bootstrap folder?
* http://svn.apache.org/viewvc/struts/struts2/trunk/lib/bootstrap/
I expect that we need to keep the Clover license JAR someplace, but
what about the rest?
-Ted.
-
This is great, Wendy, thanks! One somewhat unique requirement I think we'll
have is aggregated Javadocs not only including our modules, but also xwork.
Would that be possible?
Don
Wendy Smoak wrote:
A first pass at Struts 2 distribution assemblies has been checked in.
It builds with:
cd ~/s
On 7/14/06, Ted Husted <[EMAIL PROTECTED]> wrote:
But, why do we chant
$ mvn install site -Papp,pre-assembly
for s1, but only
$ mvn install
for s2?
We do this because for s2 we haven't yet
* split out the apps from the s2 default build. (-Papps, to make the
default build fast)
* set it up
On 7/14/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
A first pass at Struts 2 distribution assemblies has been checked in.
It builds with:
cd ~/svn/struts/current/struts2
mvn install; cd assembly; mvn assembly:assembly
WW-1378 is open if you have comments.
Very cool!
But, why do we chant
$ mv
A first pass at Struts 2 distribution assemblies has been checked in.
It builds with:
cd ~/svn/struts/current/struts2
mvn install; cd assembly; mvn assembly:assembly
WW-1378 is open if you have comments.
--
Wendy
-
To unsubscr
>
> Yes, we do seem to have a JAR bloat issue with Struts
> 2. On disk, the
> S2 applications run *twice* the size of comparable
> S1 applications.
> (Though, that does not mean the memory footprint is
> different!)
>
> Why is that? Are we sucking in any runtime
> dependencies that we don't
> ne
On 7/10/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote:
This is a good question. I've wrestled with this a lot with WebWork. A few
thoughts:
- Does documentation have to be included in the release, or is connectivity
good enough
these days to let us get away with just pointing users to the w
This is a good question. I've wrestled with this a lot with WebWork. A few
thoughts:
- Does documentation have to be included in the release, or is connectivity
good enough these days to let us get away with just pointing users to the wiki?
- If we are to include a war file for the sample app
I would really suggest a binary distro and a source distro... looking at
WW2.2.2, unzipped it's 86MB, 55MB of which is the src directory alone.
I dare say most people who download Struts are not immediately
interested in the source, so it seems wasteful (think bandwidth for
instance, time for a
For now, I'd suggest a WW2-like distribution, that includes
everything. We may want to add a library JAR distribution later, but
for a x.0.0 release, it doesn't need to be a priority.
One way or another, the S2 wiki will end up as static HTML. Pier's
plugin is looking good, but we need a slick wa
Any thoughts on what you want the Struts 2 distribution to look like?
The two examples I have to work from are
Struts 1, which has a combined source and binary distribution
(including the example apps) plus a companion "library" distribution
with only the jars and dependencies, and
Shale, which
14 matches
Mail list logo
