As mentioned in the Struts-Annotations thread, there will be an issue
with building applications with Maven, in that it will pull down an
unnecessary snapshot of the struts-annotatios JAR.
For now, I think we should let Struts 2.0.3 lie as a test build. When
we sort out the build issues, we can
On 1/18/07, Wendy Smoak [EMAIL PROTECTED] wrote:
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/
Sorry, since it was a test, and
I've tagged, rolled, and uploaded 2.0.3 again, but the Maven sources
are not showing up in the deployment to the staging folder or in my
local repository . I don't know why the sources are not being built
for me. The steps I followed are at
*
On 1/19/07, Ted Husted [EMAIL PROTECTED] wrote:
I've tagged, rolled, and uploaded 2.0.3 again, but the Maven sources
are not showing up in the deployment to the staging folder or in my
local repository . I don't know why the sources are not being built
for me. The steps I followed are at
*
That seems to do it. I'll redeploy the Maven artifacts later and then
start the vote.
Thanks again, Rahul. Your posts are always helpful.
-Ted.
On 1/19/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 1/19/07, Ted Husted [EMAIL PROTECTED] wrote:
I've tagged, rolled, and uploaded 2.0.3 again,
I updated my local copy to the revision 497046, where we added the
release profile to Struts 2. When I ran from Cygwin
$ mvn -P release -Dpassphrase=***
It ran fine against the core and api packages. When I tried again with
$ mvn -P all,release -Dpassphrase=***
It ran fine for awhile, but
On 1/18/07, Ted Husted [EMAIL PROTECTED] wrote:
I updated my local copy to the revision 497046, where we added the
release profile to Struts 2. When I ran from Cygwin
$ mvn -P release -Dpassphrase=***
It ran fine against the core and api packages. When I tried again with
$ mvn -P all,release
I forgot that we needed to sign the Maven artificats separately before
the deploy step.
I haven't been able to get the other signing scripts to work, but
Wendy's new release gopal does seem to be doing the job for me.
Problem is, the new goal was checked in after the 2.0.3 tag. The
simplest
Nope, and it would be a good thing as I fixed the portlet example and a
few other minor bugs.
Don
Ted Husted wrote:
I forgot that we needed to sign the Maven artificats separately before
the deploy step.
I haven't been able to get the other signing scripts to work, but
Wendy's new release
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
Thanks, Wendy. Seems to have worked like a charm.
Downloading the docs worked just great too. Thanks again.
-Ted.
On 1/17/07, Wendy Smoak [EMAIL PROTECTED] wrote:
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.
http://people.apache.org/builds/struts/m2-staging-repository
The http://people.apache.org/builds/struts/2.0.3/ seems to be created
and populated, but is not accessible from the web.
- Erik
-
To unsubscribe, e-mail:
Try it now.
On 1/17/07, Erik Bertelsen [EMAIL PROTECTED] wrote:
The http://people.apache.org/builds/struts/2.0.3/ seems to be created
and populated, but is not accessible from the web.
- Erik
-
To unsubscribe, e-mail: [EMAIL
2007/1/17, Ted Husted [EMAIL PROTECTED]:
Try it now.
well, it gives:
wget http://people.apache.org/builds/struts/2.0.3/struts-2.0.3-lib.zip
--16:47:42-- http://people.apache.org/builds/struts/2.0.3/struts-2.0.3-lib.zip
= `struts-2.0.3-lib.zip'
Resolving people.apache.org...
For some reason, the permissions on the ZIP files were different than
the others, but they should all be world readable now.
On 1/17/07, Erik Bertelsen [EMAIL PROTECTED] wrote:
2007/1/17, Ted Husted [EMAIL PROTECTED]:
Try it now.
well, it gives:
wget
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
I'm still not setup to sign the Maven artifiacts. I'm preparing for a
trip, and I can't be sure that I'll have time to look at it before I
leave. If someone else could take care of it, that would be great.
Otherwise I'll figure it out when I get back on the 28th.
The major problem is that my SSL
I didn't see a branch for 2.0.x Are we going to create it right before
we commit big 2.1.x features? I like not having the branch for now, as
I'm mostly working on bug fixes that should go into 2.0.4
Don
Ted Husted wrote:
I'm still not setup to sign the Maven artifiacts. I'm preparing for
Someone wasn't paying attention. :)
If we need to do bug fixes on 2.0.3, we'll branch off the tag--otherwise
we won't create the branch. Trunk became 2.1.x after the 2.0.3 tag.
Tom
Don Brown wrote:
I didn't see a branch for 2.0.x Are we going to create it right
before we commit big 2.1.x
Well, considering most/all of the work in the next few weeks will be
going into bug fixes for 2.0.x, I'd really like to not have to remember
all of them and apply them to two places. Including the fact that many
fixes are applicable to WebWork 2.2.x, that would make it three places
the fix
We can always branch at 2.0.3 if we need a 2.0.4, or at whatever
revision if we haven't started on the 2.1.x features yet. I just
didn't see the point of creating the branch until we were sure we
needed it. If we want to constrain our efforts to the 2.0.x list, then
we could also swap the head
The 2.0.3 build is uploading now, and I'll post the Maven stuff later tonight.
-Ted.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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'll be tied up the rest of the week, but if no one beats me to it, I
can tag and roll Struts 2.0.3 on Sunday. If anyone had a chance to
look at the remaining Showcase examples, that would be helpful. It
could save us the trouble of a 2.0.4.
As discussed elsewhere, once 2.0.3 is tagged, we plan
I agree - let's branch at 2.0.3. Thanks for volunteering to roll the build.
Don
Ted Husted wrote:
I'll be tied up the rest of the week, but if no one beats me to it, I
can tag and roll Struts 2.0.3 on Sunday. If anyone had a chance to
look at the remaining Showcase examples, that would be
For the autocompleter tag we need to add this method:
@StrutsTagAttribute(description=Iteratable source to populate from.)
public void setList(String list) {
super.setList(list);
}
the problem is that list is required (required=true) on the base.
Conversion problem.
regards
Tests are passing now: http://opensource.bamboo.atlassian.com/browse/STRUTS
Don
Ted Husted wrote:
I checked out r493885 to continue testing the assembly against the
latest changes, but the buid is failing for a test failure. It wasn't
obvious to me which test is failing, so I built it without
27 matches
Mail list logo
