On 12/31/06, Ted Husted [EMAIL PROTECTED] wrote:
I was leaving site out. Thanks!
I'm having trouble with 'mvn install -Pall' (svn trunk, with the
version set at 2.0.2.)
The struts-all build is failing because it can't find
'struts2-config-browser-plugin'. To make it work, I dropped into
On 1/3/07, Ted Husted [EMAIL PROTECTED] wrote:
On 1/3/07, mraible [EMAIL PROTECTED] wrote:
Any chance of getting this deployed to Apache's Snapshot Maven repo?
http://people.apache.org/maven-snapshot-repository/org/apache/struts/struts2-core/
We no longer stage tagged and numbered builds in
On 1/4/07, Ted Husted [EMAIL PROTECTED] wrote:
So, the Maven artifacts are in the staging directory, but should we be
moving them over prior to a vote of the PMC? At this point, it's just
a tagged test build; 2.0.2 is not a release.
(Ted, you own the files under m2-staging-repository, can you
On 1/14/07, Martin Cooper [EMAIL PROTECTED] wrote:
The SVN repo is now set up, so you should be all set. When you send an
announcement is up to you, but now that everything else is in the Tiles
TLP's hands, I'd say now would be fine.
We still need to move the code over to svn.apache.org/tiles
On 1/14/07, Martin Cooper [EMAIL PROTECTED] wrote:
How about moving
https://svn.apache.org/repos/asf/struts/sandbox/trunk/tiles/ to
https://svn.apache.org/repos/asf/tiles/tiles2/trunk ?
Is there a need for the extra tiles2 directory in there? Why not just
...asf/tiles/trunk?
I was
On 1/15/07, David H. DeWolf [EMAIL PROTECTED] wrote:
My initial thought was that we wouldn't need the duplicate tiles2
directory (tiles/trunk would suffice). I would think that a simple parent
pom would suffice for tiles and we may not need a parent and a master.
I don't really care either
On 1/15/07, Stone, Sam [EMAIL PROTECTED] wrote:
Where can I download the last supported version of standalone tiles.jar
(not tiles 2)?
Standalone Tiles was the original name for what we now call Tiles 2.
It hasn't been released yet, so there aren't really versions of it.
All we've done so far
On 1/15/07, Greg Reddin [EMAIL PROTECTED] wrote:
I'm cool with this plan. Let's move it first. Then we can decide how to
organize it after the fact.
Done. https://svn.apache.org/repos/asf/tiles/trunk
Now we should move to our own mailing lists. :)
--
Wendy
On 1/15/07, Wendy Smoak (JIRA) [EMAIL PROTECTED] wrote:
Wendy Smoak commented on TILES-3:
-
Website published at http://tiles.apache.org. Will sync in an hour or so, and
needs editing to remove Struts Sandbox references.
I made a new notification scheme
On 1/16/07, Ted Husted [EMAIL PROTECTED] wrote:
The 2.0.3 build is uploading now, and I'll post the Maven stuff later tonight.
Ted, just making sure you're okay with the changes since the last release.
When you 'mvn deploy' a non-snapshot version, it's going to deploy to:
I've added a 'release' profile with maven-gpg-plugin configuration to
both the struts1 and struts2 parent poms.
When you're deploying to the m2-staging-repository directory, activate
the profile with
-P release
and supply your passphrase with
-Dpassphrase=My Pass Phrase
(This can also be
On 1/17/07, Ted Husted [EMAIL PROTECTED] wrote:
Thanks, Wendy. Seems to have worked like a charm.
Great!
Then it looks like the only thing missing is signatures for all the
jars and poms in the repository. Let me know if you need help
scripting that... or, I posted about gpg plugin config
On 1/18/07, Ted Husted [EMAIL PROTECTED] wrote:
I'm still banging the rocks together when it comes to Maven, and I
don't know what command to use to install the plugin trunk.
For the record:
svn co http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-gpg-plugin/
cd maven-gpg-plugin
On 1/19/07, Joe Germuska [EMAIL PROTECTED] wrote:
Hm. I've been doing a lot of local development with M2 and Snapshots and
haven't noticed any problems with it grabbing new ones from the repo.
If that is happening, it's a bug in M2; it's supposed to always go look for
new snapshots unless you
On 1/19/07, Don Brown [EMAIL PROTECTED] wrote:
Yeah, that's an interesting problem, cause would we tag all of
struts/maven? Do we tag individual projects along side the regular core
tag? They have the same 2.0.3-SNAPSHOT version.
Wendy, what's the best way to handle this?
I'm not all that
On 1/19/07, Musachy Barroso [EMAIL PROTECTED] wrote:
It isn't required at runtime. It is used at compile time by the apt plugin
to generate the tld file and some html files.
Thanks. Ted, I see you just re-tagged, but this is pretty important.
The way the pom.xml now stands, anyone who
Unfortunately, I think Struts 2.0.3 needs one more try.
I've modified struts2/core/pom.xml to declare struts-annotations as a
build extension rather than a compile-time dependency [1].
In addition, struts-annotations needs to be tagged and released with a
non-snapshot version number. (And
On 1/20/07, Ted Husted [EMAIL PROTECTED] wrote:
At this point, I think we should let Struts 2.0.3 lie. If we need to
roll a Stuts 2.0.4 to go past beta, because of the Struts Annotation
tagging, then so be it. But, in the meantime, perhaps we can get some
people to take 2.0.3 for a spin to see
I'd like to release struts-annotations so there will be a non-snapshot
version available for the next Struts 2 test build.
I see documentation on the annotations themselves, but I can't find
anything explaining what this jar is or how to use it. Can someone
please point that out, or add it if
On 1/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
Is there any specific place where I should put the doc? or some kind of
template to use?
I thought perhaps on the Building With Maven page, since this seems to
be a compile-time thing. If you need more room, feel free to add
another
On 1/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
What do I need to do to compile? Apt keeps complaining that it cannot find
the processor factory (that's inside the annotations jar). My maven
knowledge nears zero :)
Try building struts-annotations locally, then building struts 2.
If that
On 1/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
Under core:
$ mvn -Dmaven.test.skip=true compile
...
[INFO] [compiler:compile]
Compiling 401 source files to /home/musachy/dev/struts/core/target/classes
[INFO] [apt:execute {execution: default}]
warning: Specified
On 1/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
the Tobago plugin instatiates the apt classes (if fork=true then it uses apt
from command line), and then invokes the compile method, so the classpath
must be the same classpath that the plugin is running under.
Thanks for catching this
On 1/19/07, Musachy Barroso [EMAIL PROTECTED] wrote:
Yesterday I created a project with the quickstart archetype, and after
creating the eclipse project for it, I found that the
struts-annotations jar was added to the build path(which shouldn't),
along with tools.jar, which eclipse doesn't like
Joe, please fix the permissions for the struts-annotations -sources
jar in the snapshot repo. (It needs g+w.)
Thanks,
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 1/21/07, Rene Gielen [EMAIL PROTECTED] wrote:
A little late, but:
I added a short description to the struts-annotations pom.
Not late, and thanks. :)
Since it was a single module, I tried out the Maven release plugin--
mvn release:prepare worked fine, [1] but I couldn't get
dependency for Struts 2, and there is no
distribution assembly, though source and javadoc jars are available in
the Maven repo.
Once you have had a chance to test this build, please vote on whether
to release it to the central Maven repository.
Thank you,
--
Wendy Smoak
On 1/24/07, Don Brown [EMAIL PROTECTED] wrote:
This is great, thanks for doing this Wendy.
You're welcome. The vote is open, so assuming it passes I'll plan to
get this into the central repo on Saturday evening.
I have *not* tested this, I just tagged and built what was there, so
please
On 1/24/07, Wendy Smoak [EMAIL PROTECTED] wrote:
Struts Annotations 1.0.0 has been tagged and is available for testing
...
Once you have had a chance to test this build, please vote on whether
to release it to the central Maven repository.
-1 -- The jar is missing LICENSE and NOTICE files
On 1/25/07, Don Brown [EMAIL PROTECTED] wrote:
I don't understand - all of the Struts jars are missing those files.
The only place I see it added is in the assembly tarballs.
LICENSE and NOTICE must be present in every distribution. At one
time, that just meant the .zip/.tar.gz files, but
On 1/26/07, Don Brown [EMAIL PROTECTED] wrote:
Arg!! So now we have to start this whole process again, pushing the
2.0.4 release off at least three more days? There has really got to be
a better way to handle these types of minor modifications. Since the
lack of these two files is the only
On 1/27/07, Joe Germuska [EMAIL PROTECTED] wrote:
At the risk of complicating things, isn't bad form, if nothing else, to cut
a release based on a transient repository location? One of the reasons to
use Maven is to have a reproducible build, and a release is the kind of
build which is more
On 1/28/07, Ted Husted [EMAIL PROTECTED] wrote:
What about this in the root POM?
profile
idstruts-annotations/id
modules
module../maven/struts-annotations/module
/modules
/profile
This stanza presumes that a folder below what
On 1/28/07, Ted Husted [EMAIL PROTECTED] wrote:
On 1/26/07, Wendy Smoak [EMAIL PROTECTED] wrote:
Please also comment out any _snapshot_ repository or pluginRepository
definitions before tagging 2.0.4. They are not necessary for a
release build that doesn't have snapshot dependencies
On 1/28/07, Ted Husted [EMAIL PROTECTED] wrote:
No, it's not causing problems yet. I'm able to build a clean assembly
from a checkout of the struts2 trunk in isolation. But I'm not clear
on why we even need a separate JAR and release series. Is Struts 1
using the annotations too? Do we share
On 2/3/07, Ted Husted [EMAIL PROTECTED] wrote:
Just a reminder that we plan to tag and roll Struts 2.0.5 tomorrow.
If anyone had a chance to look at any of the tickets marked for 2.0.5,
today's your chance.
I didn't call a separate vote on Struts Annotations 1.0.1, was it
mentioned in the
On 2/7/07, Martin Cooper [EMAIL PROTECTED] wrote:
On 2/7/07, Ted Husted [EMAIL PROTECTED] wrote:
* http://httpd.apache.org/dev/guidelines.html
which also mentions that On some issues, this vote is only binding if
the voter has tested the action on their own system(s). I would
suggest
On 2/9/07, Musachy Barroso [EMAIL PROTECTED] wrote:
Creating a project with the maven starter archetype:
mvn archetype:create -DgroupId=tutorial -DartifactId=tutorial
-DarchetypeGroupId=org.apache.struts
-DarchetypeArtifactId=struts2-archetype-starter
-DarchetypeVersion=2.0.3-SNAPSHOT
On 2/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: pbenedict
Date: Sat Feb 10 09:56:46 2007
New Revision: 505729
URL: http://svn.apache.org/viewvc?view=revrev=505729
Log:
STR-3004: Added 1.4 DTD
This commit made a change to the Struts 1.3 DTD, removing 'reset' and
'populate'. Was
On 2/10/07, Paul Benedict [EMAIL PROTECTED] wrote:
Wendy, the 1.3 change was reverting to the original 1.3 version. The
1.4 additions were wrongly made to 1.3, and so I rolled it back. reset
is still there, but populate is now exclusively in 1.4.
OK, thanks.
When you say copy, do you mean
On 2/10/07, Tom Schneider [EMAIL PROTECTED] wrote:
Umm, it looks like the spring plugin jar isn't included. Someone on
#struts mentioned this and I confirmed it by downloading
struts-2.0.5-all.zip from the website and it's not in the lib
directory. (All the other plugins are there) Am I crazy
On 2/11/07, Ted Husted [EMAIL PROTECTED] wrote:
Yes, both the Spring Plugin and Codebehind Plugin are missing from the
assembly POM.
Do we just want to
(1) note this as a known issue,
(2) branch on 2.0.5 and issue a 2.0.5.1 version of the lib and all
distributions.
(3) issue 2.0.6 from the
Where is the release plan for 2.0.5, so I know where to put the one
for the archetypes?
I see release plans for older versions in the 'WW' Confluence space,
but not the recent ones.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL
On 2/11/07, Ted Husted [EMAIL PROTECTED] wrote:
The archetypes are a little different since each is coupled to one of
the subprojects. Though, I don't understand why the archtetype can't
be made part of the regular distribution but plugins can.
The archetypes are more Maven things than Struts
On 2/11/07, Ted Husted [EMAIL PROTECTED] wrote:
Under the bylaws, the Struts Annotation subproject hasn't been
ratified. We've been voting on the release, but I don't remember a
concrete proposal that said Let's create a Struts Annotations
subproject that will be a separate entity from Struts 1
On 2/12/07, Michael Jouravlev [EMAIL PROTECTED] wrote:
About an hour ago I could not access http://struts.apache.org/1.3.5,
now I cannot access http://wiki.apache.org/struts/, returns 500
Internal Server Error. Is this a know issue, someone is working on
this?
It seems to be okay now. If
On 2/13/07, Paul Benedict [EMAIL PROTECTED] wrote:
I agree with Ted's comments on the S1 layout. I am going to try some
experimenting with the Struts 1 User Guide for the 1.4 release and what
else we can do with it. I'll just do it for fun and see if I can make
HTML and PDF documents from one
On 2/15/07, Musachy Barroso [EMAIL PROTECTED] wrote:
I think the problem is that when the TLD is generated into the META-INF
folder, maven already copied the resources to the target folder, so the new
TLD doesn't make it into the jar file.
Sounds like the TLD is getting generated too late in
On 2/21/07, Paul Benedict [EMAIL PROTECTED] wrote:
I can't even make that assumption in Struts? I should be able to assume
how the Struts Chain works for a Struts Command. But in terms of a
solution, what do you suggest? I find it implausible there is no way for
a command to perform first-time
On 2/25/07, Ted Husted [EMAIL PROTECTED] wrote:
I think I might have to step away from the release manager role. Or,
at least the deployment of the Maven artifacts. I have a lot of
trouble getting the Maven signing plugins or scripts to work. Signing
all these Maven artifacts by hand is not
On 2/25/07, Wendy Smoak [EMAIL PROTECTED] wrote:
Prior to the gpg plugin being available I used a script to recursively
sign the jars in my local repo, and then upload the signatures. I
think Paul just used it for the Struts 1.3.7 signatures. It's a bash
shell script (I use Cygwin
On 2/25/07, Ted Husted [EMAIL PROTECTED] wrote:
Actually, I do have the asc files in my local repository, with a
timestamp that indicates taht they were created when I released and
deployed the Maven artifacts. So the question is why where only these
files left behind?
That would happen if you
On 2/25/07, Ted Husted [EMAIL PROTECTED] wrote:
Could you specify the exact steps that we should be following then?
I added a TODO to review steps 5 and 6 on the wiki page. You
mentioned March 4th for Struts 2.0.7, so that gives me a few days.
(I'd like to see Struts start using the release
On 2/25/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 2/25/07, Ted Husted [EMAIL PROTECTED] wrote:
Could you specify the exact steps that we should be following then?
I added a TODO to review steps 5 and 6 on the wiki page. You
mentioned March 4th for Struts 2.0.7, so that gives me a few days
On 3/3/07, Paul Benedict [EMAIL PROTECTED] wrote:
I'll update the docs if I can get permissions. My confluence userid is
my email address. Please grant me permissions.
Thanks. I took another look, and combined the former steps 5 and 6.
This should do it:
mvn deploy -P
On 3/5/07, Musachy Barroso [EMAIL PROTECTED] wrote:
Sorry to spoil it, but I *did use svn move*:
http://svn.apache.org/viewvc?view=revrevision=514940
If it was simply a move, there shouldn't have been any diffs, just
the list of files.
Many of the files were copied, changed from r514939,
On 3/10/07, Paul Benedict [EMAIL PROTECTED] wrote:
There are three remaining steps to accomplish.
* Update main website pages
* Publish artifacts
* Release distribution
Niall is going to help with #1. Does anyone have directions on how to
accomplish the other 2?
Assuming you mean putting the
On 3/10/07, Wendy Smoak [EMAIL PROTECTED] wrote:
In addition, you need to
update the current links to point to the new version. I can't
remember whether you have to delete the old ones first, but it's
ln -s [target] [link-name].
Actually... Struts 2 has a GA release now, so I think that gets
On 3/11/07, Martin Cooper [EMAIL PROTECTED] wrote:
Now we are specifically being told to *not*
create symbolic links! In fact, the instructions seem to indicate that the
'current' links probably shouldn't be created any more.
Thanks, Martin. Let's delete them, then... one less step in the
On 3/11/07, Ted Husted [EMAIL PROTECTED] wrote:
I believe that these are generated Javadoc files that we checkin for
the benefit of the snippet plugin. So, the answer would be to build it
and find out, except that I can't a checkout to build :)
I deleted tabbedpanel.html, which had less
On 3/11/07, James Mitchell [EMAIL PROTECTED] wrote:
Why is struts-annotations under struts/maven if it is required in
core and dojo.
I'm sure I missed that discussion.
Yes. Check the archives. :) It's apparently not Struts 2 specific.
Also, like the master pom, it has to be released prior
On 3/11/07, Ted Husted [EMAIL PROTECTED] wrote:
It's still not clear to me why it needs to be released separately. The
justification for the archetypes almost makes sense, but creating a
separate distribution for Struts Annotations still seems like busy
work.
No one objects to releasing the
On 3/11/07, Ted Husted [EMAIL PROTECTED] wrote:
Unfortunately, until we start using Maven to do releases,
I don't know what that means. What else would we need to do?
Some variation on mvn release:prepare and mvn release:perform with
-P whatever-profiles-struts2-needs and probably a few
On 3/11/07, Martin Cooper [EMAIL PROTECTED] wrote:
Unless I'm missing something, it's because we want to be able to release
some pieces (e.g. plugins) without requiring a corresponding release of
'core'. If a plugin depends on an updated version of struts-annotations (or
whatever), it shouldn't
On 3/17/07, Pedro Herrera [EMAIL PROTECTED] wrote:
Past almost 1 month after 2.0.6GA release, several changes ocurred in Struts2
after that.
I´d like to use and test the next release(2.07beta or 2.1beta).
What are the plans, Master, for the next step?
Based on this thread [1] it looks like
On 3/20/07, Ted Husted [EMAIL PROTECTED] wrote:
Which Cygwin tool do we use to create a ssh key?
ssh-keygen, there's an example here:
http://rcsg-gsir.imsb-dsgi.nrc-cnrc.gc.ca/documents/internet/node31.html
--
Wendy
-
To
The snapshot dependencies in Struts 2 releases are causing comments...
http://jira.codehaus.org/browse/MEV-511
I just looked through the 2.0.7 tag and found:
apps/pom.xml:version1.0-SNAPSHOT/version
apps/pom.xml:version1.0-SNAPSHOT/version
On 3/21/07, Ted Husted [EMAIL PROTECTED] wrote:
Aside from what is already on the list, what else else we need to use
the fabled release plugin.
Time, as usual. :) Someone needs to try it, see what happens, and
work through any issues that come up.
It is important to note that the ASF
On 3/21/07, Ted Husted [EMAIL PROTECTED] wrote:
For some reason, from Cygwin, I can't ssh to people, even with the password.
Unless command-line ssh works, nothing else could be expected to.
I think some combination of PuTTY and scpexe:// urls (instead of
scp://) should work. I'll put it on
On 3/21/07, Ted Husted [EMAIL PROTECTED] wrote:
On 3/21/07, James Mitchell [EMAIL PROTECTED] wrote:
I was under the impression that I will be deploying my locally built
artifacts.
Yes, it's just not clear to me whether deploy creates the artifacts.
It seems to be building and testing
On 3/21/07, Ted Husted [EMAIL PROTECTED] wrote:
Is the WW chatroom still open? That would be a good a place as any.
Just try and post the transcript, so that it become part of the
regular development discussions. (If it didn't happen on the list, it
didn't happen.)
Codehaus irc has a web
On 4/8/07, Thiago Galbiatti Vespa [EMAIL PROTECTED] wrote:
How can I get the Struts 2.0.7 binary release?
There are links to the binaries in the vote thread. Based on the
discussion, it looks like it will remain a test build -- not a
release.
On 4/17/07, Paul Benedict [EMAIL PROTECTED] wrote:
It's not part of the POM and so I don't think it needs to be deleted.
What do others think?
If it's being developed on trunk and will not be released as part of
1.3, then I would delete it.
If you leave it in the 1.3 branch, please add a
On 20 Apr 2007 15:12:00 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Struts2 - Friday, April 20, 2007
11 closed in last 7 days
David, can you please add the project name to the subject line (so
GMail will keep them separate)?
Struts2 Issues Closed: week of 2007-04-20
Shale Issues
On 4/21/07, Paul Benedict [EMAIL PROTECTED] wrote:
I am proposing a new module for Struts 1.x called modules which would
contain integration classes into popular open source libraries. For
starters, it would contain a new command to let Spring wire up the CRP
using a command.
I would suggest
On 4/29/07, Paul Benedict [EMAIL PROTECTED] wrote:
Based on the emails, it sounds like having a module for various
integration libraries is preferred.
A separate module for each new integration library, yes.
Fine by me. How can we get the
proposal to out of the think tank and into SVN?
On 5/22/07, Wendy Smoak [EMAIL PROTECTED] wrote:
Let's make sure there are no snapshot dependencies in any of the poms
and that the snapshot repositories are commented out before releasing.
From the top of the 2_0_X branch, here are the poms with snapshots:
$ grep -r SNAPSHOT * | grep -v
The STRUTS_2_0_X branch had a dependency on
retrotranslator-maven-plugin version 1.0-SNAPSHOT.
The latest snapshot is dated Feb 6th, and there is a 1.0-alpha-2
release dated March 14th.
I changed to the released version in r541159, however I have problems
using the j4 profile which enables this
The list of snapshot dependencies is now down to this:
apps/pom.xml:version1.0-SNAPSHOT/version
apps/pom.xml:version1.0-SNAPSHOT/version
core/pom.xml:version1.0.2-SNAPSHOT/version
The ones in 'apps' are Hosted QA related and are in
Did you mean tags instead of branches?
You can fix the commit log message after the fact:
svn propedit --revprop -r12345 svn:log
('svn help propedit' for more info.)
Is there a release plan? I looked here:
http://wiki.apache.org/struts/StrutsReleasePlans
--
Wendy
On 5/27/07, [EMAIL
On 6/7/07, Antonio Petrelli [EMAIL PROTECTED] wrote:
2007/6/6, Rainer Hermanns [EMAIL PROTECTED]:
[X] Leave at test build
-1 (non binding, I am only a committer) to a release, because Struts
2.0.8 depends on Struts Annotations 1.0.2 that is not released.
In fact there isn't any release of
On 6/23/07, mraible [EMAIL PROTECTED] wrote:
Struts 2.0.8 depends on XWork 2.0.3, yet XWork 2.0.3 is missing from Maven's
Central repo:
http://repo1.maven.org/maven2/opensymphony/xwork/
Are there plans to fix this?
Looks like there's a question about the groupId and the OpenSymphony repo:
On 7/6/07, Paul Benedict [EMAIL PROTECTED] wrote:
Has anyone ever read this?
http://wiki.apache.org/jakarta-commons/Logging/StaticLog
Did you check the archives? Simon mentioned it well over a year ago,
with no replies:
On 7/20/07, Antonio Petrelli [EMAIL PROTECTED] wrote:
I noticed that Struts 2 showcase application misses license headers in JSP
and FTL files (I did not check the other sample applications, though).
I think that they need to be added, since in other cases (such as in Tiles
2) this problem
On 8/12/07, James Holmes [EMAIL PROTECTED] wrote:
We need to get a process setup for generating nightly builds for Struts 2.
I'm not familiar with all of the infrastructure involved with getting this
going, but am
willing to help get this in place.
I have spoken briefly to James Mitchell
On 8/19/07, Don Brown [EMAIL PROTECTED] wrote:
Agreed, Spring should be a first-tier plugin. I'm fine with spinning
off the others, but who would maintain them? If it will be the same
people, then perhaps we should keep them in the repository.
How does Maven handle this situation? Wendy?
On 8/19/07, Don Brown [EMAIL PROTECTED] wrote:
Sorry, what I meant was what has Maven learned about managing plugins?
As Martin pointed out, it can easily become scattered and confusing
for users, but on the other hand, opening up plugins for outside
contributions let's us focus on the core
On 8/20/07, Henri Yandell [EMAIL PROTECTED] wrote:
As an FYI, I've added Struts1 to Continuum:
http://vmbuild1.apache.org/continuum/projectGroupSummary.action?projectGroupId=33
Anyone know where I should send the notifications? [EMAIL PROTECTED], or is
there a different address?
I'm
On 8/25/07, Paul Benedict [EMAIL PROTECTED] wrote:
On 8/25/07, Wendy Smoak [EMAIL PROTECTED] wrote:
What do you mean by plugin-in? Is it something different from the
configuration plugins that Struts 1 has?
http://struts.apache.org/1.3.5/struts-core/apidocs/org/apache/struts/action
On 9/2/07, Konstantin Priblouda [EMAIL PROTECTED] wrote:
diffucult to tell. but recently ( friday )
I got velocity included in war twice with different
versions and that produced lot of weird errors
on classloading and resolving methods *sometimes*
(on different boxes)
it turned out,
On 9/2/07, Nils-Helge Garli [EMAIL PROTECTED] wrote:
I have created a maven artifact to support running the pluto portlet
container with the maven-jetty-plugin, and I was planning on using
this in tutorials and archetypes for the portlet plugin. Anybody have
suggestions on where to host this
On 9/7/07, Ted Husted [EMAIL PROTECTED] wrote:
I'm nervous since there doesn't seem to be a way to try a dry run on
2.1.x. Though, since there is no hurry for 2.0.10, if you have time to
apply the patch to the branch, we might as well try it there first.
Jim pointed out the -DdryRun=true
On 9/22/07, Ted Husted [EMAIL PROTECTED] wrote:
I was just wondering who was planning on attending ApacheCon this year.
I know Don has a talk on the 15th, and Mark and I have tutorials
scheduled earlier in the week.
Is anyone else going to drop by this year?
I'll be there all week.
--
On 10/1/07, Ted Husted [EMAIL PROTECTED] wrote:
We can create a build without moving to a release. I'd really like to
tap the keg on 2.1.x.
There was some talk of using the Maven Release Plugin for Struts 2.1,
did that get worked out?
Keep in mind that the release plugin will not let you
When I attempt to build 2.0.11 from the source distribution, mvn
install -P all fails because the source for the plugins isn't
included.
I do see the _jars_ for all the s2 plugins in the lib directory of the
source distribution, however.
Can someone explain how this is intended to work? It
On Nov 11, 2007 2:43 AM, Ted Husted [EMAIL PROTECTED] wrote:
The Maven build does seem to be broken in that respect. I don't know
enough about Maven to try and fix it myself right now. Please feel
free to open a issue ticket in case some one else wants to try.
The entire build process might
On Nov 12, 2007 3:54 AM, Antonio Petrelli [EMAIL PROTECTED] wrote:
In fact it is not so bad, it needs only some tweaks to make it work
(and removing some extra configuration :-) ).
I feel that I am very near to the solution, but I wonder what is the
sense of including jars in the source
On Nov 23, 2007 3:54 AM, Ted Husted [EMAIL PROTECTED] wrote:
I'd like to give these a try, but I don't know where to start.
We have an archetype page here:
* http://struts.apache.org/2.0.11/docs/struts-maven-archetypes.html
So, I tried running
mvn archetype:create -DgroupId=tutorial \
On 11/25/07, Tom Schneider [EMAIL PROTECTED] wrote:
Hey all,
I finally figured out a way to host a maven repository on googlecode.
This should greatly simplify using googlecode hosted plugins in Struts
2. For me, it's also much nicer to use maven to deploy than trying to
get a jar manually
On Dec 5, 2007 9:38 AM, Paul Benedict [EMAIL PROTECTED] wrote:
Any chance we can actually have one wiki for all of Struts? I know we're
using cwiki also to create Struts production documentation, but we can also
use it for development plans? I'd rather leave MoinMoin for a unified wiki
space
501 - 600 of 1121 matches
Mail list logo
