Re: [S2] Struts 2.0.2 status - Ready to roll
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 plugins and ran mvn install, then built again from the top. I thought we had decided not to have a combined Struts 2 jar, correct? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status - Ready to roll
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 the snapshot repository. (Matt, if you have that repo defined anywhere with releasesenabledtrue, please change it to false. Other than snapshots, there's nothing in it that is not also available in the central repo.) The automatic deploy tool didn't work for me, there's a problem with my key, and I won't have a chance to try it manually for several days. Ted, in your settings.xml, do you have the server and repository for struts-staging? There is an example here: http://wiki.apache.org/struts/StrutsMaintenanceMaven#head-4da186926f55ccb7da48cd77a8bf81a5d1a551eb It should have 'mvn deploy'ed to: http://people.apache.org/builds/struts/m2-staging-repository ... and then been moved underneath the directory with the assemblies. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Struts 2.0.2 status - Ready to roll
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 please fix the permissions?) They need to be moved so that the staging repo is empty for the next build. I'm not suggesting moving them into the rsynced repo, just into the same directory that holds the other things that need to be voted on: cd /www/people.apache.org/build/struts mv m2-staging-repository/ 2.0.2/ I'd also like to avoid people adding that repository to their poms, and moving things around for each build will help discourage that. Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tiles2] Tiles TLP next steps
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 and I'm not sure if we can do that or if it will need a svn admin. How about moving https://svn.apache.org/repos/asf/struts/sandbox/trunk/tiles/ to https://svn.apache.org/repos/asf/tiles/tiles2/trunk ? (When we did Shale, Ted mentioned that having repos/shale/shale would confuse ViewVC, that's why I suggested tiles/tiles2.) Is there anything else that needs to be moved over? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tiles2] Tiles TLP next steps
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 thinking there would be a sibling tiles/maven/trunk directory for a master pom, but that's just because every other project I work on has sub-projects. Then again, we might want tiles/sandbox. Thoughts? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tiles2] Tiles TLP next steps
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 way. . .that was just my first thought. We can always move things around later if needed. Okay, repos/asf/tiles/trunk it is. I'll have time later this afternoon, and will do the svn move then unless someone beats me to it. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where is last supported tiles.jar?
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 is identify a couple of revisions that work well with other frameworks such as Shale and Struts 2. Right now we're in the process of moving the code to its own top-level Apache project, after which there will be an announcement and (hopefully soon!) at least an alpha release. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tiles2] Tiles TLP next steps
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (TILES-3) Establish Tiles as a top-level Apache project
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 and switched the TILES project to it, so these should go to [EMAIL PROTECTED] now. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 status
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: http://people.apache.org/builds/struts/m2-staging-repository The directory may not exist, Maven will create it if necessary. Part of the release process should be to make sure the directory is not there (or empty) before you deploy. Then move m2-staging-repository underneath builds/struts/2.0.x, to keep things together and make way for staging the next release. Once the vote passes, the whole staging repo directory can be merged into the ibiblio-rsync repo. This is a change from staging releases in the snapshot repo, and a temporary thing while we wait for changes coming along from Maven. One day it will support release staging and we should be able to use the release plugin. Thanks, let me know if I can help. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven GPG plugin
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 done in settings.xml) If you have GPG installed and available on your path, this will sign all the jars, poms, and attached artifacts and deploy the signatures along with the artifacts. It works fine with Cygwin and GnuPG, I haven't tried it with the Windows version of GnuPG. (http://www.gnupg.org/download/) (http://jira.codehaus.org/browse/MGPG-1 is open, requesting that the plugin prompt for the passphrase instead of requiring it to be supplied in plain text.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 status
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 and personally wouldn't be opposed to a bit of revisionist history on the tag. :) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 status
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 mvn install I found that copying the WARs and JARs got past the error, and it seems to have signed the WARs too. Wendy, I'm deploying the maven artifacts again as a test. Could you look at them and tell me if they seem all right? I'm not sure what happened; I see the jars/wars and poms, but no -sources or -javadoc jars, nor any signatures: http://people.apache.org/builds/struts/m2-staging-repository/org/apache/struts/struts2-core/2.0.3/ -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 tag broken (was Re: struts-2.0.3-all.jar missing files?)
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 specify differently. It is a bug in Maven 2.0.4 which will only fetch new snapshots if they have 'unique versions' (timestamped snapshots). I can't recall which builds have uniqueVersionfalse, but it needs to be changed to true. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 tag broken (was Re: struts-2.0.3-all.jar missing files?)
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 familiar with the s2 build, but I'd suggest we tag and release struts-annotations. It's the same sort of thing we do with the struts-master pom. You don't have to tag all of maven/trunk, you can just tag the module you're interested in, over to maven/tags. In the tag for 2.0.3, I see this in the struts2-core pom.xml: dependency groupIdorg.apache.struts/groupId artifactIdstruts-annotations/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency Can someone fill me in on the details here? Is that jar really required at runtime? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 tag broken (was Re: struts-2.0.3-all.jar missing files?)
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 declares a dependency on struts2-core will pull the snapshot of struts-annotations into their webapp, because it is declared as a compile-time dependency. (It should be happening in the example apps now, in fact.) That jar should probably be in extensions instead of in dependencies. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Struts 2.0.3 and struts-annotations
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 core/pom.xml updated to the released version.) The struts-annotations release can be done along with 2.0.3, but it will require you to add the staging repo to your settings.xml so that Maven can find the released version of struts-annotations there. The alternative is to release struts-annotations in advance of s2, the same way we handle the struts-master pom. [1] http://svn.apache.org/viewvc?view=revrev=498071 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 and struts-annotations
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 if there are other problems. Sounds good. I'll work on getting struts-annotations released this week. So, to give 2.0.3 a try if you're using Maven, configure the staging repo with: repository idstruts-203-staging/id nameApache Struts 2.0.3 Staging Repository/name urlhttp://people.apache.org/builds/struts/2.0.3/m2-staging-repository/url /repository And then declare dependencies on the various 2.0.3 jars, for example: dependency groupIdorg.apache.struts/groupId artifactIdstruts2-core/artifactId version2.0.3/version /dependency -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Release struts-annotations?
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 it's missing? (While looking for that, I noticed that the Building With Maven page needs an update as well, it still talks about the 'extras' profile: http://struts.apache.org/2.x/docs/building-with-maven.html ) Other than documentation, is struts-annotations ready to go, or does anyone need more time? Thanks, Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release struts-annotations?
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 page... http://struts.apache.org/2.x/docs/building-with-maven.html I don't think there's a required template, just follow the style of the other pages. I'm also looking for a short description of the module (for the pom). -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 and struts-annotations
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 doesn't work, I need to see the commands you're typing, and the error you're getting. (If there is a lot of output, you can paste it on http://rafb.net/paste/ and link to it.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 and struts-annotations
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 AnnotationProcessorFactory, '
org.apache.struts.annotations.taglib.apt.TLDAnnotationProcessorFactory', not
found on search path.
warning: No annotation processors found but annotations present.
2 warnings
[INFO]
[INFO] BUILD SUCCESSFUL
Oops... I just noted that the build was successful and moved on. I
get the same thing.
I tried it with struts-annotations as a dependency of the Tobago
maven-apt-plugin, but that didn't work either. I don't know what the
search path for the plugin is, someone who is more familiar with it
will have to comment. How is Tobago using it?
As a workaround, we can move the dependency on struts-annotations back
to dependencies, but mark it 'optional'. That will put it on the
compile time classpath, but stop Maven from adding it as a transitive
dependency.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.3 and struts-annotations
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 one. I put struts-annotations back in compile scope, but marked it optional so it won't be considered a transitive dependency. And I asked on myfaces-dev to see why it won't work as a build extension or a dependency of the plugin itself. (I think it should if this is not something struts2-core itself depends on.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: quickstart archetype and dependencies
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 (duplicated reference). The problem with struts-annotations was taken care of by marking it optional (at least until the apt plugin can handle it as a plugin dependency or build extension.) Is tools.jar still getting pulled in or has that been resolved already? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Please fix permissions
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]
Re: Release struts-annotations?
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 release:perform to cooperate with the gpg plugin. (Just found the docs, I needed a profile in settings.xml, not a property on the command line...) I did manage to overwrite the struts.apache.org/2.x site because distributionManagementsite was wrong in pom.xml, but I re-published ( mvn site-deploy -Pall ) from struts2/trunk so it should be fine. The tag is here: http://svn.apache.org/repos/asf/struts/maven/tags/STRUTS_ANNOTATIONS_1_0_0/ And the repo is staged here: http://people.apache.org/builds/struts/struts-annotations-1.0.0/m2-staging-repository/ To try it out, temporarily add a repository to your pom.xml or settings.xml, and change the struts-annotations dependency version number. repository idstruts-annotations-100-staging/id nameStruts Annotations 1.0.0 Staging Repository/name urlhttp://people.apache.org/builds/struts/struts-annotations-1.0.0/m2-staging-repository//url /repository [1] with the exception of making too many changes to the pom, but I think that's fixed in svn. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release Struts Annotations 1.0.0
Struts Annotations 1.0.0 has been tagged and is available for testing in the following Maven repository: http://people.apache.org/builds/struts/struts-annotations-1.0.0/m2-staging-repository/ To test this build, temporarily add a repository to pom.xml or settings.xml, and change the struts-annotations dependency version number in the Struts2 build to 1.0.0. repository idstruts-annotations-100-staging/id nameStruts Annotations 1.0.0 Staging Repository/name urlhttp://people.apache.org/builds/struts/struts-annotations-1.0.0/m2-staging-repository//url /repository This is a build-time 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release struts-annotations?
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 check it carefully. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Struts Annotations 1.0.0
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. (It would also be nice to configure the jar plugin to add more info to the jar file manifest, it's nearly empty.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Struts Annotations 1.0.0
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 now it also means the individual jars because they are distributed in the Maven repo. This isn't a new requirement. I'm sure the 1.3.5 jars included them, and so should all the 2.x jars. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Struts Annotations 1.0.0
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 reason for a -1 vote in many days of voting, let's either retag 1.0.0 with the change or quickly run 1.0.1 and publish it immediately. I think we need a 2.0.4 release this weekend, and yes, I'm prepared to do it if necessary. No, it doesn't have to delay 2.0.4. We can stage builds for struts-annotations 1.0.1 and struts 2.0.4 together and vote on them at the same time. It's easier if all the dependencies are already in the central repo, but not required as long as they all end up in there eventually. To that end, struts-annotations 1.0.1 is staged here: http://people.apache.org/builds/struts/m2-staging-repository/ The release manager for Struts 2.0.4 will need to add a profile to settings.xml so that Maven can find the struts-annotations jar: [untested] settings ... profiles profile idstruts-annotations-101-staging/id repositories repository idstruts-annotations-101-staging/id urlhttp://people.apache.org/builds/struts/struts-annotations-1.0.1/m2-staging-repository/url snapshotsenabledfalse/enabled/snapshots releasesenabledtrue/enabled/releases /repository /repositories /profile ... /profiles activeProfiles activeProfilestruts-annotations-101-staging/activeProfile ... /activeProfiles /settings 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, and leaving them in causes problems in corporate environments. I'll be around on and off this weekend, let me know about when you're planning to do the release and I'll try to be available. Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Struts Annotations 1.0.0
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 likely to need to be reproducible for some reason, and it seems fairly likely that the struts-annotations-101-staging repository will not be around for ever. It's true that the staging repo will go away, but prior to that, the struts-annotations jar will be put into the central Maven repo. This does not affect the long term reproducibility of the struts 2.0.4 build. Nothing in the tagged/released struts poms will refer to the staging repo, it only goes in the release manager's settings.xml file temporarily. (Alternately, the RM could download and 'mvn install:install-file ...' the struts-annotations jar locally.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Struts Annotations 1.0.0
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 we have been tagging is present. I'm not sure what you mean. Is it causing a problem? You shouldn't need to activate that profile for the release, it's there so you can build the latest snapshot along with the struts 2 code, assuming you have checked out 'current'. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Struts Annotations 1.0.0
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, and leaving them in causes problems in corporate environments. You mean from the settings.xml ? No, I mean the snapshot repositories and pluginRepositories in the struts2-parent pom: http://svn.apache.org/repos/asf/struts/struts2/trunk/pom.xml Counting plugins, we have four snapshot dependencies. Tiles 2, we know about. HostedQA is for remote integration testing, the profile can be commented out during the release. The one in core is for the build itself, (unpacking xwork for the javadoc?) so I'm not going to argue for holding up a release over it. The one in assembly appears to be there to *exclude* that dependency by marking it provided. My guess is that plexus-container-default was incorrectly getting pulled in by some other dependency. The important thing is that when a user declares a dependency on struts2-core or another struts2 jar, no snapshot dependencies get pulled in. [Except tiles 2, for now.] Thanks for checking these before releasing, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Struts Annotations 1.0.0
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 other artifacts under maven? Are we sure we want a common maven folder? Paul asked, and Don answered a few days ago: http://www.nabble.com/-VOTE--Release-Struts-Annotations-1.0.0-t3084860.html#a8596388 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.5 status
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 2.0.4 vote? If not, please add it to the 2.0.5 vote so it can get into the central repository. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Struts 2.0.5 Quality
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 that in terms of a vote on a GA release, this means that the voter is using the bits in production (eating our own dog food). Yes, well _suggesting_ that is fine; making it a requirement is not. FWIW, the language in recent vote threads makes me less likely to take the time to test, since I don't have Struts apps in production anymore. I think we all have different roles to play, and that a vote based on exercising the example apps and examining the distribution for adherence to ASF release guidelines is just as valuable as a vote saying that it's working in a production system. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: archetype
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 -DremoteRepositories=http://people.apache.org/repo/m2-snapshot-repository I updated the starter archetype to use the released 2.0.5 jars, and deployed a new snapshot. Change to 2.0.5-SNAPSHOT in your command above, and try it again, mvn jetty:run worked for me. Is there a reason that Spring 1.2.8 is declared in the pom generated from the archetype, instead of letting the struts2-spring-plugin determine the version? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r505729 - in /struts/struts1/trunk/core/src/main: java/org/apache/struts/action/ActionServlet.java resources/org/apache/struts/resources/struts-config_1_3.dtd resources/org/apache/stru
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 that intentional? Also, instead of adding a new file for the 1.4 DTD, it would be better to copy the one from 1.3, preserving the history and making it easier to see what changed from 1.3 to 1.4. (Same for the tiles-config dtd in another commit.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r505729 - in /struts/struts1/trunk/core/src/main: java/org/apache/struts/action/ActionServlet.java resources/org/apache/struts/resources/struts-config_1_3.dtd resources/org/apache/stru
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 an SVN copy? I haven't used that command before, but is that what you're recommending? Yes. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Struts 2.0.5 Quality
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 or is it really missing? If you've confirmed it, please open an issue against 2.0.5. The file is probably missing from the assembly descriptor. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Struts 2.0.5 Quality
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 2.0.x branch. I could do any of these things today. If we do (3), I would first drop and recreate the 2.0.x tag from the 2.0.5 tag, so as to skip over the changes that broke the HEAD after 2.0.5 was tag. (Last time I branch the HEAD rather than a tag!) My vote goes to (3) including re-branching 2.0.x from the 2.0.5 tag. Another build issue is that the TLD is being rewritten during the assembly, I guess to reflect changes to the annotations. Should we be running an assembly before the tag first, to look for TLD updates, and checking those in, before continuing with the rest of the tag and roll? I'm not familiar enough with this to comment. Does this mean we're checking a generated file into svn? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[s2] Where do we put release plans?
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 PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Where do we put release plans?
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 things. They could be done with the Struts distribution, but it puts more work on the release manager. The archetypes need the Struts 2 version number hard coded in the pom.xml template, (src/main/resources/archetype-resources/pom.xml). Then they have to be tested with a clean local repo, meaning the non-snapshot jars have to be available in a Maven repo. So the archetypes have to be tested _after_ the build is staged. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Where do we put release plans?
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 and Struts 2. My suggestion would be to stage a quick vote to ratify the SA subproject and to create a Struts Annotations wiki space where we can keep the documentation, release notes, and such. IMO this is unnecessary... Struts Annotations is a build time dependency just like the struts-master pom and the checkstyle config file. If we have a new sub-project, it's Struts Maven where all the build-related stuff lives. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with apache website?
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 something seems to be down, check the status page: http://monitoring.apache.org/status/ . If it's listed there, someone has been notified. The infrastructure mailing list and irc channel are the next places to find info. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Users guide
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 source. Stay tuned. Did you find out what Spring uses? Docbook will certainly do it. There are two Maven plugins that I know of. There was a very nice pdf plugin for Maven 1, but so far nothing even close for m2. There's some work done in Doxia Book which uses iText, but I wasn't impressed with the output. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Status of 2.0.6 (Re: [VOTE] Struts 2.0.5 Quality)
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 the build lifecycle, then. What phase is the plugin execution bound to? We can change the output path to the target/class/META-INF, but maven doesn't create the META-INF folder if it is empty, so the annotations code fails to create the file. Is there anyway to force maven to create the META-INF folder? Shouldn't the plugin create the directory if it doesn't exist? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s1] Help to Initialize Commands
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 initialization in Struts. Why do you need to check for initialization? Without knowing more about the situation, (and it's been a long time since I worked with this,) I would suggest putting one-time initialization in a ServletContextListener. Then, later, the commands can simply assume that the setup has been done. (Usually, that something is available in application scope through the chain context.) If not, something has gone wrong, and you throw an exception or set an error message. (I never got very far with Spring + Commons Chain, but as Antonio suggests, that could be another option.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 jars are missing signatures in the Maven repo
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 something I can do on a regular basis. I'll fix 2.0.6, but, otherwise, this might have to be my last Maven distribution. Well, _that_ was certainly not my intent! You shouldn't have to sign them by hand -- there are far too many of them to make that a reasonable requirement. 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), but surely we have enough talent around here to convert it to a script that will work on Windows... Here's the signature part... # Recursively pgp sign files in a directory structure # Adapted from: http://gleamynode.net/wordpress/archives/129 echo -n PGP Key Password: stty -echo read PASSWORD stty echo echo for FILE in $(find . -name *.jar -or -name *.pom); do echo -n Signing: $FILE ... echo $PASSWORD | gpg --default-key $DEFAULT_KEY --detach-sign --armor --no-tty --yes --passphrase-fd 0 $FILE echo done. done Unfortunately, this isn't something another committer can volunteer for, the signatures really need to come from the person who built the jars. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 jars are missing signatures in the Maven repo
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), but surely we have enough talent around here to convert it to a script that will work on Windows... Oh, wait, I just noticed you mentioned Cygwin. :) When you have time, please post a message with the error you get about ssh keys so we can try to sort it out. I wonder if it's the need to manually create a .ssh directory which is described here: http://wiki.apache.org/struts/StrutsMaintenanceMaven#head-a50fcaa2d24d2668845a79e9371d91c30a320a39 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 jars are missing signatures in the Maven repo
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 did 'mvn install' rather than rather than 'mvn deploy'. Looking at [1] I think steps 5 and 6 need to be adjusted. The release profile and the passphrase need to be used with 'deploy'. (Step 5 is doing 'install' which is the default.) [1] http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 jars are missing signatures in the Maven repo
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 plugin, but I need to spend some time with it and make sure everything is in place before I suggest changing the release process, which is working well enough. Maven releases should be easier than this!) I use Cygwin exclusively, so I'm not having the back-and-forth issues that you describe... and that's going to be difficult to troubleshoot remotely. :( How about creating a ssh key with Cygwin, and appending it to to your authorized_keys on people.a.o? Paul, it sounds like the Struts 1 process is having a similar problem, because 'mvn deploy' with the gpg plugin configured should upload the signatures automatically along with the jars and poms. Thanks again to our release managers! I don't have time to take it on again right now, but I will make time to help if anyone else would like to learn the process. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 jars are missing signatures in the Maven repo
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. Paul is working on 1.3.8 and had a question about the gpg plugin, so I volunteered him to figure it out and then take a look at the Struts 2 release process. Thanks, Paul! http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html My theory is that 'mvn deploy' and '-Prelease' need to be in the same step, so that the signatures are both generated _and_ deployed. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 jars are missing signatures in the Maven repo
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 release,all,pre-assembly -Dpassphrase=$PASSPHRASE -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r514940 [1/3] - in /struts/struts2/trunk/plugins/dojo/src: main/java/org/apache/struts2/components/ main/java/org/apache/struts2/dojo/ main/java/org/apache/struts2/dojo/components/ mai
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, yet the commit message only mentions moving them. Were the changes intentional? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to publish s1?
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 artifacts in the Maven repo, you can copy them from the staging repo over to the same directory structure under people.apache.org/repo/m2-ibiblio-rsync-repository. (Copying breaks the repository metadata, but I'm not confident enough in the unreleased repositorytools project yet.) Publishing the release distribution is also a file copy, to the right place under www.apache.org/dist/struts. 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]. Please update the release instructions for the next person... -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to publish s1?
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 the current links. (Right now they're pointing at the 1.3.5 release.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to publish s1?
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 release process is good. :) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Bad file in SVN? - tabbledpanal.html
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 history (by one revision, the other has two,) and did not match the filename of the html file one directory above it. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: struts-annotations
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 to s2 to avoid a snapshot dependency. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: struts-annotations
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 struts-master pom, and it's the same situation. Struts 2 depends on struts-master, struts-annotations, and a bunch of other things. We need released versions of all those things because we are not supposed to release with snapshot dependencies. Unfortunately, until we start using Maven to do releases, checking for those snapshots is a manual process. I see that 2.0.6 went out with snapshot dependencies on both struts-annotations and maven-dependency-plugin. Luckily, those are build-time dependencies, so they won't affect anyone just *using* Struts 2. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: struts-annotations
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 more things that won't be discovered until someone tries it. For example, a dry run starts off this way: $ mvn release:prepare -DdryRun=true [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Struts 2 [INFO] Struts 2 Core [INFO] Searching repository for plugin with prefix: 'release'. [INFO] - --- [INFO] Building Struts 2 [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] - --- [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: e:\svn\struts\STRUTS_2_0_X [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : So, it will stop the release if it finds any snapshot dependencies. It also checks for local changes and won't proceed if you haven't checked in. Why can't they all be released together? They probably can, it's just a matter of someone moving them and making sure the whole thing builds again. My primary goal is no snapshot dependencies in released poms. (The struts-master pom doesn't belong to either Struts 1 or Struts 2. Eliminating it would mean duplicating the mailing lists, list of committers, etc., in each of the parent poms, but that's also doable.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: struts-annotations
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 have to wait for a 'core' release to get a new
released version of it.
Naaahhh... we're talking about whether to bring struts-annotations and
the archetypes into struts2/trunk (or the branch, I'm not entirely
sure).
I say go for it... my objection to bringing the archetypes in is not
technical, it's that the release manager will be required to manually
change the version numbers in the templates. Since the active release
manager is pushing for the change, that's not an issue. :)
Struts Annotations bothers me a little... you'll have to use
${version} in the struts2-core pom but again this is a build-time
thing, it won't break any users.
(I think we should leave struts-master out of it-- we've already got
the list of committers in three places that rarely match up--
STATUS.txt, pom.xml, volunteers.xml.)
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: when is struts 2.0.7 coming out ?
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 Ted's current plan is 2.0.7 on Monday, so keep an eye out for an announcement with the location of the test build. [1] http://www.nabble.com/Re%3A--s2--Struts-2.0.7-Status-p9522366.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 jars are missing signatures in the Maven repo
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 unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Struts 2 snapshot dependencies
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 assembly/pom.xml:version1.0-alpha-10-SNAPSHOT/version core/pom.xml:version2.0-alpha-1-SNAPSHOT/version core/pom.xml:version1.0-SNAPSHOT/version plugins/plexus/pom.xml:version1.0-alpha-10-SNAPSHOT/version plugins/tiles/pom.xml:version2.0-SNAPSHOT/version pom.xml: version1.0-SNAPSHOT/version Can any of these be removed in favor of released versions? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 snapshot dependencies
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 considers alphas and betas to be releases, and there is no ASF rule that excludes snapshot dependencies from releases. The dynamic is that is it unlikely that a PMC will vote a release GA when it has runtime beta dependencies. But if the PMC wanted to do that, it's our call. This isn't about ASF rules (or the lack thereof). Maven users do not expect to find snapshot dependencies in released artifacts. Builds are supposed to be reproducible, and that can't happen if you depend on a moving target. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 jars are missing signatures in the Maven repo
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 the list to experiment with and report back. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Struts 2.0.7 Status
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 something. The build lifecycle is explained here: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html Leaving some things out, it's compile - test - package - install - deploy. When you say 'mvn deploy', Maven executes all the things that belong in all the phases up to and including deploy. So 'mvn deploy' will compile the code, run the tests, package it up into jar/war artifacts, install them into your local repository, and deploy them to the appropriate remote repository based on whether the version number ends in -SNAPSHOT. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: s2 localization - want to chat
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 interface, but I don't think anyone is running one specifically for Freenode. Then again, I'm not entirely sure how that works, so maybe there is one somewhere. :) Martin has mentioned being able to get in through http. Thanks to Andy Williams, we do now have logs for the Freenode #struts channel: http://dev.rectang.com/logs/freenode/%23struts/ (As long as you see 'rhoid' in the channel, it's being logged.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2.0.7
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. http://www.nabble.com/-S2---VOTE--Struts-2.0.7-Quality-t3443816s177.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Rolling Struts 1.3.9 end of April
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 README.txt file explaining what it is and why it's not listed in pom.xml so it's clear to anyone looking around later. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Issues Closed: week of 2007-04-20
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 Closed: week of 2007-04-20 Thanks, Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PROPOSAL: s1 modules module
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 adding one new module called struts-spring, and see how things go from there. (It's not clear to me whether you want to add a jar called struts-modules which would have integration code with Spring and other third-party libraries, or whether modules is intended to be a directory structure like plugins in the s2 build.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PROPOSAL: s1 modules module
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? Add a directory, commit the new files, and then hook it up in the Maven pom (add a module) so it gets built. If you need help, ask a specific question. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 release plans
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 2.0.8-SNAPSHOT | grep -v .svn apps/pom.xml:version1.0-SNAPSHOT/version apps/pom.xml:version1.0-SNAPSHOT/version assembly/pom.xml:version1.0-alpha-10-SNAPSHOT/version core/pom.xml:version2.0-alpha-1-SNAPSHOT/version core/pom.xml:version1.0.2-SNAPSHOT/version plugins/plexus/pom.xml:version1.0-alpha-10-SNAPSHOT/version plugins/tiles/pom.xml:version2.0-SNAPSHOT/version pom.xml: version1.0-SNAPSHOT/version I'll take a closer look tomorrow and see if any of these have releases we can switch to. IIRC from prior Struts releases, some of them may be build time dependencies and won't affect downstream users. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Retrotranslator plugin version
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 plugin no, matter which version I use. Can someone please test and confirm that the released version of the plugin does the right thing? http://repo1.maven.org/maven2/org/codehaus/mojo/retrotranslator-maven-plugin/1.0-alpha-2/ http://snapshots.repository.codehaus.org/org/codehaus/mojo/retrotranslator-maven-plugin/1.0-SNAPSHOT/ Thanks, Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 2 release plans
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 a profile, so not a big deal. I don't see com.hostedqa in the central Maven repo. Patrick? Are these released somewhere? The one in 'core' is the dependency on struts-annotations, which will need to be released prior to or along with Struts 2.0.8. If you do it at the same time, release struts-annotations first, then add the staging repository to your settings.xml file if Maven complains about not being able to find the artifact. When you update all the version numbers to non-snapshot versions, please also comment out the snapshot repository definitions. Your corporate users who are behind firewalls and proxies will thank you. :) Hope that helps and that I didn't break anything! -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r542101 - /struts/struts1/branches/STRUTS_1_3_9/
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 PROTECTED] [EMAIL PROTECTED] wrote:
Author: pbenedict
Date: Sun May 27 20:58:09 2007
New Revision: 542101
URL: http://svn.apache.org/viewvc?view=revrev=542101
Log: (empty)
Added:
struts/struts1/branches/STRUTS_1_3_9/
- copied from r542100, struts/struts1/branches/STRUTS_1_3_BRANCH/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] [VOTE] Struts 2.0.8 Quality
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 Struts Annotations, how's that? It's staged here, but should probably have a separate vote as it wasn't mentioned in this one: http://people.apache.org/builds/struts/struts-annotations-1.0.2/ (Ranier mentioned this when he closed https://issues.apache.org/struts/browse/WW-1943.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XWork 2.0.3 missing from Maven's Central Repo
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: http://jira.codehaus.org/browse/MAVENUPLOAD-1609 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts 1/2 and Logging
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: http://www.nabble.com/commons-logging-and-static-log-members-t1244201.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Missing license headers in showcase
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 blocked a release. For this reason I think that we need to add the RAT plugin to see which files miss the header. Thoughts? Just go ahead and do it. :) Or if not, open an issue so whoever has time can take care of it. You may have to educate us on what exactly to do with the RAT plugin output, though. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] nightly builds
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 about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? The sticking point is usually permissions to get the files transferred to people.a.o. Infra isn't in favor of 'faceless' accounts, so that part needs to run as someone in particular. There is a shared Continuum instance on vmbuild.apache.org, I'm waiting to see how they solve the where to publish issue. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] [2.1.x] Bundled Plugins
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? How does Maven handle what? Ted seems to be talking about moving these plugins out of 'trunk' -- so presumably to sandbox or out to another place entirely. You'll need to take them out of the modules list, and adjust the assembly descriptors for the release distributions. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] [2.1.x] Bundled Plugins
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 of Struts 2. How does Maven ensure the support of popular plugins? There is a mojo project over at Codehaus, and Maven searches that groupId by default along with org.apache.maven.plugins. That covers most of the useful 'generic' plugins. Other projects and individuals are also releasing Maven plugins along with their stuff-- Jetty, MyFaces, Cargo, several Docbook plugins, etc. You can ask questions about any Maven plugin on [EMAIL PROTECTED], even if it's not a core plugin there's usually someone around who can either help or get you to the right place (Cargo users list, etc.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CI for Struts1
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 pondering whether to add Struts 1.3. I'd prefer [EMAIL PROTECTED], but I don't think we have one yet. If not that, then commits@ -- something that isn't intended for human conversations. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: s1: Proposal for plugins
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/PlugIn.html I went back and checked my email, but could not find a reference to plugin-in. I may have goofed and created a typo otherwise. I am talking about what you linked to. I wasn't picking on spelling, just trying to make sure this was the same concept. Does that mean struts-tiles1-plugin is the same as the current struts-tiles module? Another thing I've wondered... now that we have ServletContextListener, do we really need Struts Plugin at all? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xwork groupId change
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, that velocity is sometimes referred by group Id as org.apache.velocity or just velocity - when changing groups be carefull and check who uses it... This happens when a project changes groupIds without relocating the old versions in the repository. Maven has no way of knowing that 'velocity' and 'org.apache.velocity' are the same thing. There's a guide here: http://maven.apache.org/guides/mini/guide-relocation.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Home for orphan maven artifact
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 artifact? You can create an upload bundle and submit it to the central repository. There's a guide here: http://maven.apache.org/guides/mini/guide-central-repository-upload.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [S2] Release process for Struts 2.1.x
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 parameter so you can see what it's going to do (and then 'mvn release:clean' afterwards before doing it for real). The first time you do it, it will probably do some rearranging and reformatting in the pom, but after that the diffs will settle down to only the version number and scm connection elements changing. And just in general, we use the release plugin at Maven, have used it at MyFaces, and at work we use the release management feature in Continuum (which is based on the same thing). I admit it took a while before I trusted Maven to touch svn under my user id. :) Antonio, thanks for working on this! -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ApacheCon Roll Call
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. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.1.0 Build/Release Plan
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 proceed until all snapshot dependencies have been removed. (Tagged builds are supposed to be reproducible, and they can't be if they involve snapshots.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Source for plugins missing from 2.0.11?
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 seems odd that we have binaries in the source distro, rather than the source. Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Source for plugins missing from 2.0.11?
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 need to be revisited. Creating a distribution still requires manual intervention to achieve the desired result, where it should be an entirely automatic process. Okay, I'll see if I can take a look at it during hackathon. I've been reluctant to make changes because I'm not around very much, but you can always roll it back if it makes things worse. :) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Removing libraries from source distro (WAS: Re: Source for plugins missing from 2.0.11?)
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 distribution: since the preferred way of building Struts 2 is Maven, we can force using Maven for building from source. This way, we can remove the jars and let Maven download all the dependencies. There is a build.xml at the top. The dependencies might be for that... but, external dependencies only, we shouldn't include the released struts jars in the source distro. I looked at it, and we're still using an old version of the archetype plugin. It's just a few lines to get the plugin source included. One day maybe we can move to the latest archetype plugin release, but I there are lots of changes in the descriptor format. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release struts2-archetype-plugin and struts2-archetype-starter version 2.0.11
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 \ -DartifactId=tutorial \ -DarchetypeGroupId=org.apache.struts \ -DarchetypeArtifactId=struts2-archetype-starter \ -DarchetypeVersion=struts2-archetype-starter \ -DremoteRepositories=http://people.apache.org/repo/m2-snapshot-repository but Maven suggested that I install the artifact. I see that we have some binaries uploaded here: * http://people.apache.org/builds/struts/m2-staging-repository/org/apache/struts/ but I don't know enough about Maven to get those installed locally, without building it locally. Change remoteRepositories to use the repository that contains the staged archetype, (and fix the archetypeVersion). This worked: mvn archetype:create -DgroupId=tutorial -DartifactId=tutorial -DarchetypeGroupId=org.apache.struts -DarchetypeArtifactId=struts2-archetype-starter -DarchetypeVersion=2.0.11 -DremoteRepositories=http://people.apache.org/builds/struts/m2-staging-repository -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Googlecode Maven Repository for External Struts 2 Plugins
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 uploaded into the central repository. Instructions on how to use this repo for Struts 2 projects are at: http://code.google.com/p/struts2plugin-maven-repo/ On behalf of Maven users everywhere, please consider getting this synced with the central Maven repository. (I think that mostly works via rsync right now, but hopefully something can be arranged to handle svn.) Having to add an additional repository to your settings is a pain, and causes things like archetypes to not Just Work like they're supposed to. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One wiki?
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 for all of us. I don't think mixing the content is a good idea, and the Confluence space names already have 'S2' in them (well, besides WW which is left over.) Converting the s1 wiki to a new Confluence space is another option, if you'd rather use that than MoinMoin. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
