On 4/20/06, Don Brown <[EMAIL PROTECTED]> wrote:
> Can we require these snapshot plugins in our POM somehow?
> I'm fine with working with snapshots, but their download and
> use should be automatic.
When the Javadoc plugin gets fixed, yes. For now, the released
versions are working (you just don'
Author: wsmoak
Date: Thu Apr 20 23:04:51 2006
New Revision: 395790
URL: http://svn.apache.org/viewcvs?rev=395790&view=rev
Log:
Added JXR plugin for source cross-reference.
Checkstyle config added, but commented out as it causes an error.
Modified:
struts/action/trunk/pom.xml
Modified: struts
Author: wsmoak
Date: Thu Apr 20 22:00:02 2006
New Revision: 395779
URL: http://svn.apache.org/viewcvs?rev=395779&view=rev
Log:
Added surefire and checkstyle report config.
Added site location.
Modified:
struts/action/trunk/pom.xml
Modified: struts/action/trunk/pom.xml
URL:
http://svn.apache
Author: wsmoak
Date: Thu Apr 20 21:51:15 2006
New Revision: 395778
URL: http://svn.apache.org/viewcvs?rev=395778&view=rev
Log:
Added Maven 2 website configuration. Use 'mvn site:deploy' to publish.
Added:
struts/action/trunk/core/src/site/
struts/action/trunk/core/src/site/site.xml (wi
> Ideally not. It's already going to be painful to split up the core-library
> package (which now produces several JAR files) into separate modules solely
> because Maven likes one artifact per module.
>
> Shale publishes information on API stability (
> http://struts.apache.org/struts-shale/api-s
On Thu, Apr 20, 2006 at 04:14:19PM -0700, Don Brown wrote:
> Jeff Turner, who set this up, wanted separate instances, and in fact, he
> wants, IIRC, that to be how JIRA is used at
> Apache from now on. The separate instance allows each of our subprojects to
> have their own JIRA project, and he
OK well if that's how the infra people want it. For the record, you
can combine subprojects into a project "category." That is how we're
doing it for myfaces. This is fine though. I do get tired of the
lone instance of JIRA crashing all of the time.
Please upgrade my account (schof.)
Also, ar
At JavaOne, Patrick, Jason, and I will be presenting a session about Struts Action 2 (deceptively titled, "What's Up
with Struts Ti?") We definitely want to have something more concrete to talk about like at least an unstable release of
Struts Action 2. JavaOne runs May 16-19 and our session is
Jeff Turner, who set this up, wanted separate instances, and in fact, he wants, IIRC, that to be how JIRA is used at
Apache from now on. The separate instance allows each of our subprojects to have their own JIRA project, and helps
isolate problems so that one instance won't bring all projects d
Don,
I've been off the list for a while now but can you explain why this is
a completely separate JIRA instance from the other ASF projects? Why
not use the existing one at http://issues.apache.org/jira?
+1 (as always) for migrating to JIRA. I find Bugzilla to be
unbearable compared to JIRA. I
With our JIRA instance stood up, it is time to revisit our earlier decision to migration our Struts Bugzilla tickets to
JIRA.
http://issues.apache.org/struts
I believe most of this work can be done without bothering infrastructure, as the import can be done through JIRA's web
admin interface.
Can we require these snapshot plugins in our POM somehow? I'm fine with working with snapshots, but their download and
use should be automatic.
Don
Wendy Smoak wrote:
On 4/18/06, Don Brown <[EMAIL PROTECTED]> wrote:
We definitely need an action/src/site directory to contain
the root site.xm
Ted Husted wrote:
We might want to keep a straight-line mapping in the naming conventions, where
OpenSymphony -> Apache Struts
WebWork -> Action
A good reason to prefer "action-default.xml" to "struts-default.xml"
is that we want people to be able to use Struts Action 1 and Struts
Action 2 in t
The confluence migration is one of the remaining issues before Incubator
graduation, and here is the plan:
1. Export the data from OpenSymphony
2. Lock the OS WW wiki down to only the dev team for minor changes
3. Stand up a confluence instance, probably on my personal server, with the
expor
Following Don's comments... with Java Web Parts, we have taken to using
the Feature Requests feature at SourceForge for all work being done,
regardless of whether it is actually a "feature request" or not... since
you can open a ticket, assign it, prioritize, comment, etc., it gives us
all one plac
After thinking about this a little more, would it make sense to test
this under our svn so that the commit msgs are sent as usual and we
can keep an eye things. The term 'subversion shelves' comes to mind
[0].
I remember as Wendy (and others?) were working on the one over in the
test rep
Looking at it further, this could all be done with JIRA how, which would probably be an easier interface to use and have
the bonus of collecting comments and patches. Perhaps we could use the "Priority" value to signify the type of issue
much like that status file does for httpd?
The WebWork t
I like the httpd one, clearly organized into sections that would be very helpful for guiding development. I think this
is a great idea and vote we should adopt it too.
Will shale, action, and tiles each have one, or will there be one for the whole
project?
Don
Ted Husted wrote:
On 4/20/06,
On 4/20/06, Don Brown <[EMAIL PROTECTED]> wrote:
> The bottom line is, IMO, the Struts project hasn't been as good as it could
> be at sharing our roadmap and vision with the user community. It is a
> personal goal of mine to improve this, and to see the continued success of
> both projects.
One
Did you really mean to put it there? Or under 'current'?
--
James Mitchell
On Apr 20, 2006, at 2:08 PM, [EMAIL PROTECTED] wrote:
Author: husted
Date: Thu Apr 20 11:08:51 2006
New Revision: 395664
URL: http://svn.apache.org/viewcvs?rev=395664&view=rev
Log:
Move shared STATUS.txt file to pr
Author: husted
Date: Thu Apr 20 11:08:51 2006
New Revision: 395664
URL: http://svn.apache.org/viewcvs?rev=395664&view=rev
Log:
Move shared STATUS.txt file to project root
Added:
struts/STATUS.txt
- copied unchanged from r395662, struts/action/trunk/build/STATUS.txt
Removed:
struts/a
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Peter Pilgrim
====
>
> Dear All
>
> The JAVAWUG (Java Web User Group) has rescheduled the BOF
> XVIII (Number
> 17) from Thursday 20th April to now Friday 20th April 2006.
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Struts Wiki" for change
notification.
The following page has been changed by GabrielZimmerman:
http://wiki.apache.org/struts/RoughSpots
--
*
>From: James Mitchell <[EMAIL PROTECTED]>
>
> We should probably do this over in a test repository and make sure it
> will do what we want. Similar to what was done for MyFaces and Action1.
>
> Your thoughts?
>
+1
> --
> James Mitchell
>
>
>
>
> On Apr 19, 2006, at 10:35 PM, Sean S
We should probably do this over in a test repository and make sure it
will do what we want. Similar to what was done for MyFaces and Action1.
Your thoughts?
--
James Mitchell
On Apr 19, 2006, at 10:35 PM, Sean Schofield wrote:
I'd love to see Shale move to M2. I'll try to help with the
Hi all,
Said plugin is available for eraly testing.
Snapshot version ( plugin-xwork-1.0.4-SNAPSHOT ) is
deployed on codehaus repository.
Tag and plugin domumentation is available on
http://xdoclet.codehaus.org/
Sources are in sourceforge project:
http://www.sourceforge.net/projects/xdoclet-
26 matches
Mail list logo
