2007/12/4, Tomislav Stojcevich <[EMAIL PROTECTED]>:
>
> I believe if you add the following 2 configuration items to the
> release plugin declaration in the section of
> the parent pom, you should be able to use release:prepare and
> release:perform
>
> clean install site
> -P all,alljars,pre-assem
Ok, you offered help, now you're in for it :)
I tried to build from the top-level directory I checked out to after a
fresh checkout and it didn't work. I'm at a loss any time I see a Maven
problem (which, in my experience, is any time I've tried to use it for
any project, but I digress), so I
Thanks, will do. Once I have things fleshed out a little I'll bring it
up for discussion here. I want to make sure *I* think the ideas are
good first, and have some actual code to show for it.
Frank
Paul Benedict wrote:
If I can help with anything, let me know!
On Dec 4, 2007 7:50 PM, Mart
Yep, that's it, thanks Martin! And yeah, I just took another look and
missed the obvious Source Code link... Typically I keep the text in my
browser bigger than usual, which makes the menu on the left of the site
a littler overlapping, so I just missed it. Thanks though, all set now.
Frank
If I can help with anything, let me know!
On Dec 4, 2007 7:50 PM, Martin Cooper <[EMAIL PROTECTED]> wrote:
> On Dec 4, 2007 5:24 PM, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
>
> > At The Ajax Experience back in October, Ted and I tossed around a few
> > ideas for new S1 features (Ajax only be
On Dec 4, 2007 5:24 PM, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> At The Ajax Experience back in October, Ted and I tossed around a few
> ideas for new S1 features (Ajax only being one, contrary to the location
> of the discussions!), and since I've just completed writing on my most
> recent
At The Ajax Experience back in October, Ted and I tossed around a few
ideas for new S1 features (Ajax only being one, contrary to the location
of the discussions!), and since I've just completed writing on my most
recent book I had some time and was hoping to test some things out.
But, I'm emb
I've attached a patch for WW-2294/XW-593, ported from Toby's work. With
Wes's fantastic work here I think that is the majority of the main WW
fixes done.
- Original message -
From: "Ted Husted" <[EMAIL PROTECTED]>
To: "Struts Developers List"
Date: Tue, 4 Dec 2007 15:56:59 -0500
Subject
Thanks, Wes. We appreciate the help!
-Ted.
On Dec 4, 2007 3:54 PM, Wes Wannemacher <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I took a look through the issues that have been resolved in the last
> few weeks over on webwork and found the following -
>
> webwork's WW-1476 and WW-1463 are non-issues in
Hello,
I took a look through the issues that have been resolved in the last
few weeks over on webwork and found the following -
webwork's WW-1476 and WW-1463 are non-issues in struts2 because the
webwork issues are related to components that were moved / updated to
be in the dojo plugin. Just to
I believe if you add the following 2 configuration items to the
release plugin declaration in the section of
the parent pom, you should be able to use release:prepare and
release:perform
clean install site
-P all,alljars,pre-assembly
On Dec 4, 2007 1:33 PM, Antonio Petrelli <[EMAIL PROTECTED]> w
I see you are using the gpg plugin to sign. I'm not familiar with
that particular plugin.
Just a guess, to avoid the multiple entries of the passphrase I think
you could set a property in your settings.xml file
$PASSPHRASE, that should avoid you having to
specify -Dpassphrase="$PASSPHRASE". It '
Tomislav, I configured the release plugin only for the trunk (the
future Struts 2.1.1, probably).
Antonio
2007/12/4, Tomislav Stojcevich <[EMAIL PROTECTED]>:
> It does, but from the looks of the release process at
> http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
> the
Ah, I see now. It's probably just the way it's setup in the poms.
I'm assuming it was converted from another build system (ant perhaps)
which isn't the easiest thing to do sometimes.
If I get a chance I'll take a look at the poms and see if I see
anything that stands out and submit a patch.
You
The crux of my problem is that automatic signing doesn't work, and I
have to enter the passcode multiple times during the build. (It's a
pain, but no one else seems to be available to roll the releases.) My
recollection is with the plugin, signing didn't work at all. I'm sure
the plugin is fine, th
This might help. The jar plugin can be configured to automatically
sign the jars when it creates them during the package phase.
http://maven.apache.org/plugins/maven-jar-plugin/usage.html
http://maven.apache.org/plugins/maven-jar-plugin/sign-mojo.html
---
I did try to use the plugin last time, but there's a problem with my
security setup, and the plugin doesn't work for me. I'd like to setup
a new workstation soon, but it probably won't happen this calendar
year.
The underlying problem is that the ASF expects us to sign all the
JARs, which complica
It does, but from the looks of the release process at
http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
the release plugin is not being used.
Even if it were, in the parent pom it has
false in the release plugin
configuration so it won't run with that profile for whatever
OK, for the next round, we can run it with the "alljars" parameter,
and see if that helps.
On Dec 4, 2007 3:00 AM, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> In fact I did not fix anything, I only fixed the wiki!
> the "alljars" needs to be activated when deploying.
> I cannot do it myself sinc
2007/12/3, Ted Husted <[EMAIL PROTECTED]>:
>
>
> Personally, I think that the Java web community should be ashamed.
> Struts has generated millions of dollars of revenue for consultants,
> training centers, and publishers, the world over, and saved tens of
> thousands of companies the expense of d
2007/12/3, Ted Husted <[EMAIL PROTECTED]>:
> Unfortunately, I have no idea how to fix it. My setup here isn't quite
> right, and it might have something do with it. The exact steps we
> follow are here:
>
> * http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
>
> I know Ant
21 matches
Mail list logo
