Grokbase Groups Struts dev March 2008
FAQ

[Struts-dev] 2.1 build

Musachy Barroso
Mar 26, 2008 at 6:49 pm
Hi all,

Any news on the 2.1 build? Is anyone looking into it?

regards
musachy

--
"Hey you! Would you help me to carry the stone?" Pink Floyd

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
reply

Search Discussions

65 responses

  • Pedro Herrera at Mar 28, 2008 at 10:35 am
    good question . . .



    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy

    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    View this message in context: http://www.nabble.com/2.1-build-tp16313177p16349017.html
    Sent from the Struts - Dev mailing list archive at Nabble.com.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Ted Husted at Mar 28, 2008 at 10:38 am
    Is there much to do beside tag it, build it, and sign it? I could help
    with that much, so long as other people are testing it.

    -Ted.

    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Musachy Barroso at Mar 28, 2008 at 5:52 pm
    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is about
    time we get a build out there.

    regards
    musachy
    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted wrote:
    Is there much to do beside tag it, build it, and sign it? I could help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Rainer Hermanns at Mar 28, 2008 at 6:19 pm
    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com
    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is about
    time we get a build out there.

    regards
    musachy
    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted wrote:
    Is there much to do beside tag it, build it, and sign it? I could help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Mar 29, 2008 at 2:58 am
    I'm available to perform a good chunk of testing.

    Ted, if you do it can you keep some notes on the tasks you perform? Or
    is there anything with more detail than [1] or a previously used release
    plan for 2.x?
    I'd hoped to perform a dry-run myself but don't see how I can do that
    without committing via mvn release:prepare.

    [1] http://struts.apache.org/dev/releases.html
    [2] http://wiki.apache.org/struts/StrutsMavenRelease

    Rainer Hermanns wrote:
    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com

    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is about
    time we get a build out there.

    regards
    musachy
    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted wrote:

    Is there much to do beside tag it, build it, and sign it? I could help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Wendy Smoak at Mar 29, 2008 at 3:05 am

    On Fri, Mar 28, 2008 at 7:57 PM, Jeromy Evans wrote:

    I'd hoped to perform a dry-run myself but don't see how I can do that
    without committing via mvn release:prepare.
    What do you mean by dry run? The release:prepare goal has a
    -DdryRun=true parameter... but AFAIK Struts does not use the release
    plugin. (Yet?) And the wiki page you linked to is probably for Struts
    1.

    --
    Wendy

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Mar 29, 2008 at 5:15 am

    Wendy Smoak wrote:
    On Fri, Mar 28, 2008 at 7:57 PM, Jeromy Evans
    wrote:

    I'd hoped to perform a dry-run myself but don't see how I can do that
    without committing via mvn release:prepare.
    What do you mean by dry run? The release:prepare goal has a
    -DdryRun=true parameter... but AFAIK Struts does not use the release
    plugin. (Yet?) And the wiki page you linked to is probably for Struts
    1.
    Hi Wendy, ok, I thought there was discussion about setting up the
    release plugin but can't find the thread. The release plugin is at
    least referenced by pluginManagement.

    As a new developer I don't have a good appreciation of the effort
    involved in performing a release. Judging by how quickly 2.0.11.1 was
    rolled out by Rene I presume it's easy if you've done it before. When I
    tried to work it out based on the guidelines I couldn't get far without
    risking screwing something up.

    ie. is it safe to execute the release goal with -DdryRun=true? or does
    this risk committing?

    At the moment we can only sit around hoping someone with enough
    experience has enough time to make a release, which is not good.

    cheers,
    Jeromy Evans

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Antonio Petrelli at Mar 29, 2008 at 9:33 am

    2008/3/29, Jeromy Evans <jeromy.evans@blueskyminds.com.au>:
    ie. is it safe to execute the release goal with -DdryRun=true? or does
    this risk committing?
    I suppose that you are referring to "release:prepare" goal.
    It is safe, since all the changes are made locally and not committed
    (tested with Tiles).

    Antonio

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Wendy Smoak at Mar 29, 2008 at 12:48 pm

    On Fri, Mar 28, 2008 at 10:14 PM, Jeromy Evans wrote:

    ie. is it safe to execute the release goal with -DdryRun=true? or does
    this risk committing?
    Yes, it's safe. As long as you don't misspell dryRun (I've missed the
    capital R before...)

    Even if you do accidentally commit, it's not *that* big of a deal.
    This history is always there in Subversion, we can roll back.
    At the moment we can only sit around hoping someone with enough
    experience has enough time to make a release, which is not good.
    Antonio pointed to the correct page. Looks like another improvement
    could be made to "attach" the assemblies so they don't have to be
    built separately, but it's definitely progress! It really should be
    as simple as 'mvn release:prepare; mvn release:perform'. Eventually.

    --
    Wendy

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Antonio Petrelli at Mar 29, 2008 at 7:03 pm

    2008/3/29, Wendy Smoak <wsmoak@gmail.com>:
    Looks like another improvement
    could be made to "attach" the assemblies so they don't have to be
    built separately
    In Tiles, the assemblies are attached and deployed to the Maven
    repository, but they are significantly smaller artifacts than Struts
    ones. And anyway, assembly upload must be done manually.
    It really should be
    as simple as 'mvn release:prepare; mvn release:perform'. Eventually.
    There are some problems with the profiles that need to be activated.
    It needs some investigation...

    Antonio

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Antonio Petrelli at Mar 29, 2008 at 9:31 am

    2008/3/29, Wendy Smoak <wsmoak@gmail.com>:
    What do you mean by dry run? The release:prepare goal has a
    -DdryRun=true parameter... but AFAIK Struts does not use the release
    plugin. (Yet?)
    In fact it does:
    http://cwiki.apache.org/WW/creating-and-signing-a-struts-21x-distribution.html

    Antonio

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Rainer Hermanns at Mar 31, 2008 at 9:05 pm
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer
    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com
    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is about
    time we get a build out there.

    regards
    musachy
    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted wrote:
    Is there much to do beside tag it, build it, and sign it? I could help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Ted Husted at Mar 31, 2008 at 10:25 pm
    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.
    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer


    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com
    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is about
    time we get a build out there.

    regards
    musachy
    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted wrote:
    Is there much to do beside tag it, build it, and sign it? I could help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Rainer Hermanns at Apr 1, 2008 at 11:22 am
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer
    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:

    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer


    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com
    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I
    could help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Ted Husted at Apr 3, 2008 at 12:21 pm
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.
    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:

    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.
    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns wrote:

    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer



    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com

    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is about
    time we get a build out there.

    regards
    musachy
    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted wrote:

    Is there much to do beside tag it, build it, and sign it? I could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Musachy Barroso at Apr 3, 2008 at 12:55 pm
    It would be easier to ask if anyone is working on something that needs
    to be included (SmartUrls?).

    regards
    musachy
    On Thu, Apr 3, 2008 at 8:20 AM, Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.


    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:

    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer



    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com

    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Brian Pontarelli at Apr 3, 2008 at 3:59 pm
    Yeah, I was hoping to have time to get the convention plugin into the
    main repository, but I just haven't had anytime at all. It will have to
    wait until 2.2 unless someone else wants to move it over. At this point
    I can't even recall the outstanding issues and design changes that were
    being discussed before. Anyone else remember those?

    -bp


    Musachy Barroso wrote:
    It would be easier to ask if anyone is working on something that needs
    to be included (SmartUrls?).

    regards
    musachy
    On Thu, Apr 3, 2008 at 8:20 AM, Ted Husted wrote:

    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.


    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:

    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer



    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com

    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Musachy Barroso at Apr 3, 2008 at 4:03 pm
    If it isn't ready I don't think we should wait for it at this point. A
    2.1 release is long "overdue" IMO.

    regards
    musachy
    On Thu, Apr 3, 2008 at 11:58 AM, Brian Pontarelli wrote:
    Yeah, I was hoping to have time to get the convention plugin into the main
    repository, but I just haven't had anytime at all. It will have to wait
    until 2.2 unless someone else wants to move it over. At this point I can't
    even recall the outstanding issues and design changes that were being
    discussed before. Anyone else remember those?

    -bp




    Musachy Barroso wrote:
    It would be easier to ask if anyone is working on something that needs
    to be included (SmartUrls?).

    regards
    musachy

    On Thu, Apr 3, 2008 at 8:20 AM, Ted Husted wrote:

    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.


    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:

    And, if we're ready to roll a Struts after that, I'd be happy to
    step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns
    <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer



    Hey there,

    I am working on the open issues for xwork 2.1.1 over the
    weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help
    to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the
    release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com

    I will help testing it (I don't have any application on
    production
    tho). Ted if you could do it, it would be great, I think it
    is about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted
    <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I
    could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    HTH, Ted
    http://husted.com/ted/blog/
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org





    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Piero Sartini at Apr 4, 2008 at 12:59 pm

    Am Donnerstag, 3. April 2008 17:58:41 schrieb Brian Pontarelli:
    Yeah, I was hoping to have time to get the convention plugin into the
    main repository, but I just haven't had anytime at all. It will have to
    wait until 2.2 unless someone else wants to move it over. At this point
    I can't even recall the outstanding issues and design changes that were
    being discussed before. Anyone else remember those?
    I told you about a minor issue some time ago. Just created WW-2576 :)

    Piero

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Bob Tiernay at Apr 6, 2008 at 2:38 pm
    I have been waiting and waiting for the convention plugin :( That's really
    the only reason I've been anticipating the 2.1 release. What's involved in
    "moving it over"?

    --------------------------------------------------
    From: "Brian Pontarelli" <brian@pontarelli.com>
    Sent: Thursday, April 03, 2008 11:58 AM
    To: "Struts Developers List" <dev@struts.apache.org>
    Subject: Re: 2.1 build
    Yeah, I was hoping to have time to get the convention plugin into the main
    repository, but I just haven't had anytime at all. It will have to wait
    until 2.2 unless someone else wants to move it over. At this point I can't
    even recall the outstanding issues and design changes that were being
    discussed before. Anyone else remember those?

    -bp


    Musachy Barroso wrote:
    It would be easier to ask if anyone is working on something that needs
    to be included (SmartUrls?).

    regards
    musachy
    On Thu, Apr 3, 2008 at 8:20 AM, Ted Husted wrote:

    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.



    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:

    And, if we're ready to roll a Struts after that, I'd be happy to
    step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns
    <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer



    Hey there,

    I am working on the open issues for xwork 2.1.1 over the
    weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help
    to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the
    release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com

    I will help testing it (I don't have any application on
    production
    tho). Ted if you could do it, it would be great, I think it
    is about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted
    <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I
    could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:
    good question . . .

    Musachy Barroso wrote:
    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    HTH, Ted
    http://husted.com/ted/blog/
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Apr 4, 2008 at 7:11 am
    Ted, I tried to get you started with a dryRun of release:prepare but I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt

    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    svn co https://svn.apache.org/repos/asf/struts/struts2/trunk STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>
    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>

    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to install:install-file
    xwork-2.1.1 into my localRepository, so I guess I have to wait a little
    longer for it to replicate?

    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.
    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns wrote:

    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:


    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer




    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com


    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:

    good question . . .

    Musachy Barroso wrote:

    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Rainer Hermanns at Apr 4, 2008 at 7:16 am
    Jeromy,

    that's strange... XWork 2.1.1 jars are all available from the central
    repository.
    See here: http://repo1.maven.org/maven2/com/opensymphony/xwork/2.1.1/

    cheers,
    Rainer
    Ted, I tried to get you started with a dryRun of release:prepare but I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt

    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    svn co https://svn.apache.org/repos/asf/struts/struts2/trunk
    STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>
    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>

    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to install:install-file
    xwork-2.1.1 into my localRepository, so I guess I have to wait a little
    longer for it to replicate?

    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.

    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:


    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer




    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com


    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:

    good question . . .

    Musachy Barroso wrote:

    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Apr 4, 2008 at 7:29 am
    I had a miror configured (http://mirrors.dotsrc.org/maven2). I've
    passed that hiccup using the central repository.

    Rainer Hermanns wrote:
    Jeromy,

    that's strange... XWork 2.1.1 jars are all available from the central
    repository.
    See here: http://repo1.maven.org/maven2/com/opensymphony/xwork/2.1.1/

    cheers,
    Rainer

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Antonio Petrelli at Apr 4, 2008 at 7:17 am
    2008/4/4, Jeromy Evans <jeromy.evans@blueskyminds.com.au>:
    Ted, I tried to get you started with a dryRun of release:prepare but I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt<http://people.apache.org/%7Ejeromy/buildlog1.txt>


    This is strange, the XWork 2.1.1 artifacts are in the central repository...
    http://repo1.maven.org/maven2/com/opensymphony/xwork/2.1.1/

    Antonio
  • Jeromy Evans at Apr 4, 2008 at 8:36 am
    Is the release of struts-annotations-1.0.3 a blocker? It's not in
    central yet.

    struts-annotations dependencies:
    ./core/pom.xml:425: <version>1.0.3-20080216.121126-3</version>
    ./plugins/dojo/pom.xml:261: <version>1.0.3-20080123.123514-2</version>
    ../maven/struts-annotations/pom.xml: <version>1.0.4-SNAPSHOT</version>

    Jeromy Evans wrote:
    Ted, I tried to get you started with a dryRun of release:prepare but
    I'm still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt

    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    svn co https://svn.apache.org/repos/asf/struts/struts2/trunk
    STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>

    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>


    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to
    install:install-file xwork-2.1.1 into my localRepository, so I guess I
    have to wait a little longer for it to replicate?

    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.

    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:


    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer




    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com


    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:

    good question . . .

    Musachy Barroso wrote:

    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Al Sutton at Apr 4, 2008 at 9:33 am
    As a side note there is a new freemarker version out (2.3.12, changenotes at
    http://www.freemarker.org/docs/versions_2_3_12.html), is it worth bumping
    the version in the core pom?

    Al.
    ----- Original Message -----
    From: "Jeromy Evans" <jeromy.evans@blueskyminds.com.au>
    To: "Struts Developers List" <dev@struts.apache.org>
    Sent: Friday, April 04, 2008 9:35 AM
    Subject: Re: 2.1 build

    Is the release of struts-annotations-1.0.3 a blocker? It's not in central
    yet.
    struts-annotations dependencies:
    ./core/pom.xml:425: <version>1.0.3-20080216.121126-3</version>
    ./plugins/dojo/pom.xml:261: <version>1.0.3-20080123.123514-2</version>
    ../maven/struts-annotations/pom.xml: <version>1.0.4-SNAPSHOT</version>

    Jeromy Evans wrote:
    Ted, I tried to get you started with a dryRun of release:prepare but I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt

    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    svn co https://svn.apache.org/repos/asf/struts/struts2/trunk
    STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>
    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>

    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to install:install-file
    xwork-2.1.1 into my localRepository, so I guess I have to wait a little
    longer for it to replicate?

    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.

    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:


    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer




    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com


    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:

    good question . . .

    Musachy Barroso wrote:

    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Matt.payne at Apr 4, 2008 at 6:06 pm
    probably worth it.

    Otherwise

    people should

    <dependency>
    <groupId>org.apache.struts</groupId>
    <artifactId>struts2-core</artifactId>
    <version>.....</version>
    <exclusions>
    <exclusion>
    <groupId>freemarker</groupId>
    <artifactId>freemarker</artifactId>
    </exclusion>
    </exclusions>
    </dependency>

    <dependency>
    <groupId>org.freemarker</groupId>
    <artifactId>freemarker</artifactId>
    <version>2.3.12</version>
    </dependency>


    Al Sutton wrote:
    As a side note there is a new freemarker version out (2.3.12, changenotes
    at
    http://www.freemarker.org/docs/versions_2_3_12.html), is it worth bumping
    the version in the core pom?

    Al.
    ----- Original Message -----
    From: "Jeromy Evans" <jeromy.evans@blueskyminds.com.au>
    To: "Struts Developers List" <dev@struts.apache.org>
    Sent: Friday, April 04, 2008 9:35 AM
    Subject: Re: 2.1 build

    Is the release of struts-annotations-1.0.3 a blocker? It's not in
    central
    yet.
    struts-annotations dependencies:
    ./core/pom.xml:425: <version>1.0.3-20080216.121126-3</version>
    ./plugins/dojo/pom.xml:261: <version>1.0.3-20080123.123514-2</version>
    ../maven/struts-annotations/pom.xml: <version>1.0.4-SNAPSHOT</version>

    Jeromy Evans wrote:
    Ted, I tried to get you started with a dryRun of release:prepare but I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt

    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    svn co https://svn.apache.org/repos/asf/struts/struts2/trunk
    STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>
    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>

    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly
    -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to install:install-file
    xwork-2.1.1 into my localRepository, so I guess I have to wait a little
    longer for it to replicate?

    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.

    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:


    And, if we're ready to roll a Struts after that, I'd be happy to step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns
    <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer




    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to
    get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com


    I will help testing it (I don't have any application on production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:

    good question . . .

    Musachy Barroso wrote:

    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    View this message in context: http://www.nabble.com/2.1-build-tp16313177p16495027.html
    Sent from the Struts - Dev mailing list archive at Nabble.com.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Rainer Hermanns at Apr 5, 2008 at 3:26 pm
    I am working on this update right now.

    cheers,
    Rainer
    probably worth it.

    Otherwise

    people should

    <dependency>
    <groupId>org.apache.struts</groupId>
    <artifactId>struts2-core</artifactId>
    <version>.....</version>
    <exclusions>
    <exclusion>
    <groupId>freemarker</groupId>
    <artifactId>freemarker</artifactId>
    </exclusion>
    </exclusions>
    </dependency>

    <dependency>
    <groupId>org.freemarker</groupId>
    <artifactId>freemarker</artifactId>
    <version>2.3.12</version>
    </dependency>


    Al Sutton wrote:
    As a side note there is a new freemarker version out (2.3.12,
    changenotes
    at
    http://www.freemarker.org/docs/versions_2_3_12.html), is it worth
    bumping
    the version in the core pom?

    Al.
    ----- Original Message -----
    From: "Jeromy Evans" <jeromy.evans@blueskyminds.com.au>
    To: "Struts Developers List" <dev@struts.apache.org>
    Sent: Friday, April 04, 2008 9:35 AM
    Subject: Re: 2.1 build

    Is the release of struts-annotations-1.0.3 a blocker? It's not in
    central
    yet.
    struts-annotations dependencies:
    ./core/pom.xml:425: <version>1.0.3-20080216.121126-3</version>
    ./plugins/dojo/pom.xml:261: <version>1.0.3-20080123.123514-2</version>
    ../maven/struts-annotations/pom.xml: <version>1.0.4-SNAPSHOT</version>

    Jeromy Evans wrote:
    Ted, I tried to get you started with a dryRun of release:prepare but
    I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt

    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    svn co https://svn.apache.org/repos/asf/struts/struts2/trunk
    STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>
    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>

    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly
    -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to
    install:install-file
    xwork-2.1.1 into my localRepository, so I guess I have to wait a
    little
    longer for it to replicate?

    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.

    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:


    And, if we're ready to roll a Struts after that, I'd be happy to
    step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns
    <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer




    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to
    get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com


    I will help testing it (I don't have any application on
    production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I
    could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:

    good question . . .

    Musachy Barroso wrote:

    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    View this message in context:
    http://www.nabble.com/2.1-build-tp16313177p16495027.html
    Sent from the Struts - Dev mailing list archive at Nabble.com.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Rainer Hermanns at Apr 5, 2008 at 4:42 pm
    done
    probably worth it.

    Otherwise

    people should

    <dependency>
    <groupId>org.apache.struts</groupId>
    <artifactId>struts2-core</artifactId>
    <version>.....</version>
    <exclusions>
    <exclusion>
    <groupId>freemarker</groupId>
    <artifactId>freemarker</artifactId>
    </exclusion>
    </exclusions>
    </dependency>

    <dependency>
    <groupId>org.freemarker</groupId>
    <artifactId>freemarker</artifactId>
    <version>2.3.12</version>
    </dependency>


    Al Sutton wrote:
    As a side note there is a new freemarker version out (2.3.12,
    changenotes
    at
    http://www.freemarker.org/docs/versions_2_3_12.html), is it worth
    bumping
    the version in the core pom?

    Al.
    ----- Original Message -----
    From: "Jeromy Evans" <jeromy.evans@blueskyminds.com.au>
    To: "Struts Developers List" <dev@struts.apache.org>
    Sent: Friday, April 04, 2008 9:35 AM
    Subject: Re: 2.1 build

    Is the release of struts-annotations-1.0.3 a blocker? It's not in
    central
    yet.
    struts-annotations dependencies:
    ./core/pom.xml:425: <version>1.0.3-20080216.121126-3</version>
    ./plugins/dojo/pom.xml:261: <version>1.0.3-20080123.123514-2</version>
    ../maven/struts-annotations/pom.xml: <version>1.0.4-SNAPSHOT</version>

    Jeromy Evans wrote:
    Ted, I tried to get you started with a dryRun of release:prepare but
    I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt

    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    svn co https://svn.apache.org/repos/asf/struts/struts2/trunk
    STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>
    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>

    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly
    -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to
    install:install-file
    xwork-2.1.1 into my localRepository, so I guess I have to wait a
    little
    longer for it to replicate?

    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.

    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:


    And, if we're ready to roll a Struts after that, I'd be happy to
    step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns
    <hermanns@aixcept.de>
    wrote:
    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer




    Hey there,

    I am working on the open issues for xwork 2.1.1 over the weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to
    get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com


    I will help testing it (I don't have any application on
    production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted <husted@apache.org>
    wrote:
    Is there much to do beside tag it, build it, and sign it? I
    could
    help
    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:

    good question . . .

    Musachy Barroso wrote:

    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    View this message in context:
    http://www.nabble.com/2.1-build-tp16313177p16495027.html
    Sent from the Struts - Dev mailing list archive at Nabble.com.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Ted Husted at Apr 4, 2008 at 11:00 am
    Yes, it is something we should do first. It's on the list, but I
    usually forget about it until the last minute ... :)

    Are you setup to digitally sign the releases, Jeromy? It's the
    one-time section of Creating and Signing a Distributiob

    * http://struts.apache.org/2.0.11.1/docs/creating-and-signing-a-distribution.html#CreatingandSigningaDistribution-Onetime

    For a "wet run" of the release, that's usually the blocker for people.
    After that, it's a bit of a bother, but not actually difficult to do.

    Since it seems like you've already done most of the work, would you
    like to add your name to the release plan as a co-manager (along with
    mine)?

    * http://struts.apache.org/2.0.11.1/docs/version-notes-211.html


    -Ted.

    On Fri, Apr 4, 2008 at 4:35 AM, Jeromy Evans
    wrote:
    Is the release of struts-annotations-1.0.3 a blocker? It's not in central
    yet.
    struts-annotations dependencies:
    ./core/pom.xml:425: <version>1.0.3-20080216.121126-3</version>
    ./plugins/dojo/pom.xml:261: <version>1.0.3-20080123.123514-2</version>
    ../maven/struts-annotations/pom.xml: <version>1.0.4-SNAPSHOT</version>



    Jeromy Evans wrote:
    Ted, I tried to get you started with a dryRun of release:prepare but I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt
    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>
    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>
    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to install:install-file
    xwork-2.1.1 into my localRepository, so I guess I have to wait a little
    longer for it to replicate?
    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.

    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns wrote:

    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:



    And, if we're ready to roll a Struts after that, I'd be happy to
    step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns
    <hermanns@aixcept.de>
    wrote:

    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer





    Hey there,

    I am working on the open issues for xwork 2.1.1 over the
    weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to
    get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the
    release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com



    I will help testing it (I don't have any application on
    production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted
    <husted@apache.org>
    wrote:

    Is there much to do beside tag it, build it, and sign it? I
    could
    help

    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:


    good question . . .

    Musachy Barroso wrote:


    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy


    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd


    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    HTH, Ted
    http://husted.com/ted/blog/
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org





    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Apr 4, 2008 at 1:25 pm

    Ted Husted wrote:
    Yes, it is something we should do first. It's on the list, but I
    usually forget about it until the last minute ... :)

    Are you setup to digitally sign the releases, Jeromy?
    I've started working my way through it now. I'll have to come back to
    it tomorrow as it's too late on a Friday night in my part of the world.

    Since it seems like you've already done most of the work, would you
    like to add your name to the release plan as a co-manager (along with
    mine)?
    I've only run through the easy stuff so far but I'll try to help where I
    can.



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Don Brown at Apr 6, 2008 at 12:29 pm
    FWIW, Struts Annotations 1.0.3 has been released and approved, but I
    haven't had time to finish it off by signing the jar and moving it to
    the official repo. I'll try to find some time in the next few days if
    no one beats me to it.

    Don
    On Fri, Apr 4, 2008 at 8:59 PM, Ted Husted wrote:
    Yes, it is something we should do first. It's on the list, but I
    usually forget about it until the last minute ... :)

    Are you setup to digitally sign the releases, Jeromy? It's the
    one-time section of Creating and Signing a Distributiob

    * http://struts.apache.org/2.0.11.1/docs/creating-and-signing-a-distribution.html#CreatingandSigningaDistribution-Onetime

    For a "wet run" of the release, that's usually the blocker for people.
    After that, it's a bit of a bother, but not actually difficult to do.

    Since it seems like you've already done most of the work, would you
    like to add your name to the release plan as a co-manager (along with
    mine)?

    * http://struts.apache.org/2.0.11.1/docs/version-notes-211.html


    -Ted.



    On Fri, Apr 4, 2008 at 4:35 AM, Jeromy Evans
    wrote:
    Is the release of struts-annotations-1.0.3 a blocker? It's not in central
    yet.
    struts-annotations dependencies:
    ./core/pom.xml:425: <version>1.0.3-20080216.121126-3</version>
    ./plugins/dojo/pom.xml:261: <version>1.0.3-20080123.123514-2</version>
    ../maven/struts-annotations/pom.xml: <version>1.0.4-SNAPSHOT</version>



    Jeromy Evans wrote:
    Ted, I tried to get you started with a dryRun of release:prepare but I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt
    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>
    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>
    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to install:install-file
    xwork-2.1.1 into my localRepository, so I guess I have to wait a little
    longer for it to replicate?
    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.

    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:



    And, if we're ready to roll a Struts after that, I'd be happy to
    step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns
    <hermanns@aixcept.de>
    wrote:

    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer





    Hey there,

    I am working on the open issues for xwork 2.1.1 over the
    weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to
    get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the
    release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com



    I will help testing it (I don't have any application on
    production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted
    <husted@apache.org>
    wrote:

    Is there much to do beside tag it, build it, and sign it? I
    could
    help

    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:


    good question . . .

    Musachy Barroso wrote:


    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy


    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd


    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    HTH, Ted
    http://husted.com/ted/blog/
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org





    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Ted Husted at Apr 6, 2008 at 12:46 pm
    Thanks, Don.

    BTW, getting setup for digital signing is harder than it sounds. Every
    committer should consider generating a signature and putting it on
    file with the foundation. Signing isn't hard, but it can be a
    stumblingblock when it comes to posting a release.

    * http://struts.apache.org/2.0.11.1/docs/creating-and-signing-a-distribution.html#CreatingandSigningaDistribution-Onetime

    Since ASF distributions are sometimes passed around, it's important
    that we sign them, so if a strange problem is reported with a
    distribution, we confirm whether it's one of ours, or a forgery.

    -Ted.
    On Sun, Apr 6, 2008 at 8:28 AM, Don Brown wrote:
    FWIW, Struts Annotations 1.0.3 has been released and approved, but I
    haven't had time to finish it off by signing the jar and moving it to
    the official repo. I'll try to find some time in the next few days if
    no one beats me to it.

    Don


    On Fri, Apr 4, 2008 at 8:59 PM, Ted Husted wrote:
    Yes, it is something we should do first. It's on the list, but I
    usually forget about it until the last minute ... :)

    Are you setup to digitally sign the releases, Jeromy? It's the
    one-time section of Creating and Signing a Distributiob

    * http://struts.apache.org/2.0.11.1/docs/creating-and-signing-a-distribution.html#CreatingandSigningaDistribution-Onetime

    For a "wet run" of the release, that's usually the blocker for people.
    After that, it's a bit of a bother, but not actually difficult to do.

    Since it seems like you've already done most of the work, would you
    like to add your name to the release plan as a co-manager (along with
    mine)?

    * http://struts.apache.org/2.0.11.1/docs/version-notes-211.html


    -Ted.



    On Fri, Apr 4, 2008 at 4:35 AM, Jeromy Evans
    wrote:
    Is the release of struts-annotations-1.0.3 a blocker? It's not in central
    yet.
    struts-annotations dependencies:
    ./core/pom.xml:425: <version>1.0.3-20080216.121126-3</version>
    ./plugins/dojo/pom.xml:261: <version>1.0.3-20080123.123514-2</version>
    ../maven/struts-annotations/pom.xml: <version>1.0.4-SNAPSHOT</version>



    Jeromy Evans wrote:
    Ted, I tried to get you started with a dryRun of release:prepare but I'm
    still missing xwork.jar:2.1.1. The mvn output is at
    http://people.apache.org/~jeromy/buildlog1.txt
    Other details:

    * JIRA: No open issues except the omnibus ticket
    (https://issues.apache.org/struts/browse/WW-2421)
    * Release Notes: reasonably up-to-date:
    http://cwiki.apache.org/confluence/display/WW/Version+Notes+2.1.1
    STRUTS_2.1.1
    svn info: Revision: 644624
    * check pom.xml repositories (I'm not sure values should be here)
    find . -name "pom.xml" -exec grep -i -H -n '<repository>' {}
    ./pom.xml:72
    <url>scp://people.apache.org/www/people.apache.org/builds/struts/${pom.version}/m2-staging-repository</url>
    ./apps/pom.xml:73 <url>http://repository.codehaus.org</url>
    find . -name "pom.xml" -exec grep -i -H -n '<snapshotRepository>' {}
    ./pom.xml
    <url>scp://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>
    * change mvn settings.xml to a clean localRepository and dryRun
    release:prepare
    mvn release:prepare -P release,all,alljars,j4,pre-assembly -DdryRun=true
    The mvn output is at http://people.apache.org/~jeromy/buildlog1.txt
    That's as far as I got because I shouldn't have to install:install-file
    xwork-2.1.1 into my localRepository, so I guess I have to wait a little
    longer for it to replicate?
    regards,
    Jeromy Evans

    Ted Husted wrote:
    I'm still heads-down, but I could run a build through the gauntlet.
    Can anyone confirm that everything else we want to do is done, and
    we're at the tag and roll point?

    -Ted.

    On Tue, Apr 1, 2008 at 7:21 AM, Rainer Hermanns <hermanns@aixcept.de>
    wrote:
    Ted, others,

    xwork 2.1.1 is out and should be in the repos shortly.
    So we should be ready for a Struts 2.1.1 release build now.

    thanks for waiting,
    Rainer



    On Apr 1, 2008, at 12:24 AM, Ted Husted wrote:



    And, if we're ready to roll a Struts after that, I'd be happy to
    step
    through the process Wednesday night.

    -Ted.

    On Mon, Mar 31, 2008 at 4:05 PM, Rainer Hermanns
    <hermanns@aixcept.de>
    wrote:

    Sorry, but I have to delay the xwork release until tomorrow.
    cheers,
    Rainer





    Hey there,

    I am working on the open issues for xwork 2.1.1 over the
    weekend,
    so that the release could be out on monday.
    Since lots of fixes and changes were done affecting S2.1 core
    features, testing S2.1 with latest xwork snapshots would help to
    get
    both codebases stablelized.

    Please report xwork errors to XWork Jira [1].

    Ted, if you have some time next week for getting out the
    release,
    that would be awesome.

    cheers,
    Rainer

    [1] http://jira.opensymphony.com



    I will help testing it (I don't have any application on
    production
    tho). Ted if you could do it, it would be great, I think it is
    about
    time we get a build out there.

    regards
    musachy

    On Fri, Mar 28, 2008 at 6:38 AM, Ted Husted
    <husted@apache.org>
    wrote:

    Is there much to do beside tag it, build it, and sign it? I
    could
    help

    with that much, so long as other people are testing it.

    -Ted.


    On Fri, Mar 28, 2008 at 5:35 AM, Pedro Herrera
    wrote:


    good question . . .

    Musachy Barroso wrote:


    Hi all,

    Any news on the 2.1 build? Is anyone looking into it?

    regards
    musachy


    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    "Hey you! Would you help me to carry the stone?" Pink Floyd


    ---------------------------------------------------------------------

    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    Rainer Hermanns
    aixcept
    Mariahilfstrasse 9
    52062 Aachen - Germany
    w: http://aixcept.de/
    t: +49-241-4012247
    m: +49-170-3432912
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org



    --
    HTH, Ted
    http://husted.com/ted/blog/
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org





    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org


    --
    HTH, Ted
    http://husted.com/ted/blog/

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Bob Tiernay at Apr 6, 2008 at 2:32 pm
    Does anyone know if there are plans to include the Scope plugin
    (http://cwiki.apache.org/S2PLUGINS/scope-plugin.html) in the core, and
    perhaps add some canned interceptor stacks that include it? I see this as
    missing core component that has offers a great value add to the framework
    and it's users.

    Bob


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Matt.payne at Apr 7, 2008 at 3:17 pm
    Agreed on excellent value. It is a tremendous help for wizard type actions.
    Is it mature enough though? I don't think scope interceptor looks at
    annotations in a super class.

    I tried to consolidate similar functionality into a super class. After I was
    finished the annotations in the super class had no effect.

    I would like to this become a part of the framework, but I am not sure about
    tucking it in just before the 2.1 build.

    Matt


    Bob Tiernay wrote:
    Does anyone know if there are plans to include the Scope plugin
    (http://cwiki.apache.org/S2PLUGINS/scope-plugin.html) in the core, and
    perhaps add some canned interceptor stacks that include it? I see this as
    missing core component that has offers a great value add to the framework
    and it's users.

    Bob


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    --
    View this message in context: http://www.nabble.com/2.1-build-tp16313177p16537502.html
    Sent from the Struts - Dev mailing list archive at Nabble.com.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Apr 8, 2008 at 6:55 am
    I've signed struts-annotations-1.0.3 using jeromy@apache.org and copied
    to [1].

    Can some please take a moment to check these? If they're okay I presume
    the artefacts then just need to be copied to the right location for
    rsync to ibiblio. Any other formalities for struts-annotations?

    [1] http://people.apache.org/builds/struts/struts-annotations/1.0.3/


    Don Brown wrote:
    FWIW, Struts Annotations 1.0.3 has been released and approved, but I
    haven't had time to finish it off by signing the jar and moving it to
    the official repo. I'll try to find some time in the next few days if
    no one beats me to it.

    Don
    On Fri, Apr 4, 2008 at 8:59 PM, Ted Husted wrote:

    Yes, it is something we should do first. It's on the list, but I
    usually forget about it until the last minute ... :)

    Are you setup to digitally sign the releases, Jeromy? It's the
    one-time section of Creating and Signing a Distributiob

    * http://struts.apache.org/2.0.11.1/docs/creating-and-signing-a-distribution.html#CreatingandSigningaDistribution-Onetime

    For a "wet run" of the release, that's usually the blocker for people.
    After that, it's a bit of a bother, but not actually difficult to do.

    Since it seems like you've already done most of the work, would you
    like to add your name to the release plan as a co-manager (along with
    mine)?

    * http://struts.apache.org/2.0.11.1/docs/version-notes-211.html


    -Ted.

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Apr 8, 2008 at 7:10 am

    Jeromy Evans wrote:
    I've signed struts-annotations-1.0.3 using jeromy@apache.org and
    copied to [1].

    Can some please take a moment to check these? If they're okay I
    presume the artefacts then just need to be copied to the right
    location for rsync to ibiblio. Any other formalities for
    struts-annotations?

    [1] http://people.apache.org/builds/struts/struts-annotations/1.0.3/
    I should mention I generated the key only a few hours ago (8Apr08). It's
    been posted it to the MIT keyserver and added it to struts KEYS file:
    http://pgp.mit.edu:11371/pks/lookup?search=jeromy&op=index
    http://www.apache.org/dist/struts/KEYS



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Martin Cooper at Apr 8, 2008 at 2:37 pm

    On Tue, Apr 8, 2008 at 12:09 AM, Jeromy Evans wrote:

    Jeromy Evans wrote:
    I've signed struts-annotations-1.0.3 using jeromy@apache.org and copied
    to [1].

    Can some please take a moment to check these? If they're okay I presume
    the artefacts then just need to be copied to the right location for rsync to
    ibiblio. Any other formalities for struts-annotations?

    [1] http://people.apache.org/builds/struts/struts-annotations/1.0.3/

    I should mention I generated the key only a few hours ago (8Apr08). It's
    been posted it to the MIT keyserver and added it to struts KEYS file:
    http://pgp.mit.edu:11371/pks/lookup?search=jeromy&op=index
    http://www.apache.org/dist/struts/KEYS

    Please do *not* edit that file directly. The KEYS file is maintained in SVN,
    so you need to update that and then refresh the file on the site from that.

    https://svn.apache.org/repos/asf/struts/maven/trunk/build/KEYS

    --
    Martin Cooper


    <http://www.apache.org/dist/struts/KEYS>



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Apr 9, 2008 at 12:11 am

    Martin Cooper wrote:
    Please do *not* edit that file directly. The KEYS file is maintained in SVN,
    so you need to update that and then refresh the file on the site from that.

    https://svn.apache.org/repos/asf/struts/maven/trunk/build/KEYS
    Fixed. I've updated the instructions:
    http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Distribution

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Martin Cooper at Apr 9, 2008 at 1:09 am

    On Tue, Apr 8, 2008 at 5:10 PM, Jeromy Evans wrote:

    Martin Cooper wrote:
    Please do *not* edit that file directly. The KEYS file is maintained in
    SVN,
    so you need to update that and then refresh the file on the site from
    that.

    https://svn.apache.org/repos/asf/struts/maven/trunk/build/KEYS

    Fixed. I've updated the instructions:
    http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Distribution

    Thanks, on both counts.

    I didn't see a commit message, though, so could one of the moderators check
    the queue, please, and 'allow' jeromy@a.o so that his commit messages show
    up? Ta.

    --
    Martin Cooper


    <http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Distribution>

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Wendy Smoak at Apr 8, 2008 at 7:22 pm

    On Tue, Apr 8, 2008 at 8:54 AM, Jeromy Evans wrote:

    I've signed struts-annotations-1.0.3 using jeromy@apache.org and copied to
    [1].
    Where/how did you sign them? Were the files re-built? Generally you
    only sign what you build yourself, while it's under your control on a
    machine you trust.

    I'm also not sure how the vote passed, if they were never signed originally.
    Can some please take a moment to check these? If they're okay I presume
    the artefacts then just need to be copied to the right location for rsync to
    ibiblio. Any other formalities for struts-annotations?

    [1] http://people.apache.org/builds/struts/struts-annotations/1.0.3/
    Is this the same as what's in
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/
    ?

    --
    Wendy

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Apr 9, 2008 at 12:31 am

    Wendy Smoak wrote:
    On Tue, Apr 8, 2008 at 8:54 AM, Jeromy Evans
    wrote:

    I've signed struts-annotations-1.0.3 using jeromy@apache.org and copied to
    [1].
    Where/how did you sign them? Were the files re-built? Generally you
    only sign what you build yourself, while it's under your control on a
    machine you trust.
    Thanks for looking at these Wendy. It's difficult to step-in part way
    through the process.

    I checked the source out from the struts-annotations-1.03 TAG.
    I packaged and signed them myself but DID NOT deploy to
    m2-staging-repository as that task was complete already
    From step 7 of Ref[1], I signed the build artifacts and copied them to
    Ref[2] as per step 8.

    [1]
    http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Distribution
    [2] http://people.apache.org/builds/struts/struts-annotations/1.0.3/
    I'm also not sure how the vote passed, if they were never signed originally.
    I see that you mentioned that during the vote.
    Can some please take a moment to check these? If they're okay I presume
    the artefacts then just need to be copied to the right location for rsync to
    ibiblio. Any other formalities for struts-annotations?

    [1] http://people.apache.org/builds/struts/struts-annotations/1.0.3/
    Is this the same as what's in
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/
    ?
    I think that is a problem isn't it? The files in the
    m2-staging-repository [3] were built and deployed by Don, not the files
    I built and signed [2]
    As the maven artefacts for ibiblio come from m2-staging-repository
    they'd be Don's binaries, not mine.
    I presume that means the process has to be started from scratch unless
    Don completes as only he can/should sign the binaries he created and
    voters tested?

    [3]
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Don Brown at Apr 9, 2008 at 1:25 am
    *sigh* is this all necessary? I mean, by using the Maven release
    plugin, the binaries are created off the tag. A quick SVN command can
    confirm the tag hasn't been modified, so I don't see any problem with
    Jeromy building new binaries and finishing the release. The vote had
    passed with the caveat that the binaries are signed, so if Jeromy
    built the same binaries, a new vote would be an exercise in useless
    bureaucracy, IMO.

    Don

    On Wed, Apr 9, 2008 at 10:30 AM, Jeromy Evans
    wrote:
    Wendy Smoak wrote:
    On Tue, Apr 8, 2008 at 8:54 AM, Jeromy Evans
    wrote:


    I've signed struts-annotations-1.0.3 using jeromy@apache.org and copied
    to
    [1].
    Where/how did you sign them? Were the files re-built? Generally you
    only sign what you build yourself, while it's under your control on a
    machine you trust.

    Thanks for looking at these Wendy. It's difficult to step-in part way
    through the process.

    I checked the source out from the struts-annotations-1.03 TAG.
    I packaged and signed them myself but DID NOT deploy to
    m2-staging-repository as that task was complete already
    From step 7 of Ref[1], I signed the build artifacts and copied them to
    Ref[2] as per step 8.

    [1]
    http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Distribution
    [2] http://people.apache.org/builds/struts/struts-annotations/1.0.3/


    I'm also not sure how the vote passed, if they were never signed
    originally.
    I see that you mentioned that during the vote.


    Can some please take a moment to check these? If they're okay I
    presume
    the artefacts then just need to be copied to the right location for
    rsync to
    I think that is a problem isn't it? The files in the m2-staging-repository
    [3] were built and deployed by Don, not the files I built and signed [2]
    As the maven artefacts for ibiblio come from m2-staging-repository they'd
    be Don's binaries, not mine. I presume that means the process has to be
    started from scratch unless Don completes as only he can/should sign the
    binaries he created and voters tested?

    [3]
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Martin Cooper at Apr 9, 2008 at 1:31 am

    On Tue, Apr 8, 2008 at 6:22 PM, Don Brown wrote:

    *sigh* is this all necessary? I mean, by using the Maven release
    plugin, the binaries are created off the tag. A quick SVN command can
    confirm the tag hasn't been modified, so I don't see any problem with
    Jeromy building new binaries and finishing the release. The vote had
    passed with the caveat that the binaries are signed, so if Jeromy
    built the same binaries, a new vote would be an exercise in useless
    bureaucracy, IMO.

    If the binaries Jeromy created are bit-for-bit identical to the ones you
    built, then I don't have a problem. If they're not, then what he has built
    is not the same as what was voted on.

    --
    Martin Cooper


    Don

    On Wed, Apr 9, 2008 at 10:30 AM, Jeromy Evans
    wrote:
    Wendy Smoak wrote:
    On Tue, Apr 8, 2008 at 8:54 AM, Jeromy Evans
    wrote:


    I've signed struts-annotations-1.0.3 using jeromy@apache.org and
    copied
    to
    [1].
    Where/how did you sign them? Were the files re-built? Generally you
    only sign what you build yourself, while it's under your control on a
    machine you trust.

    Thanks for looking at these Wendy. It's difficult to step-in part way
    through the process.

    I checked the source out from the struts-annotations-1.03 TAG.
    I packaged and signed them myself but DID NOT deploy to
    m2-staging-repository as that task was complete already
    From step 7 of Ref[1], I signed the build artifacts and copied them to
    Ref[2] as per step 8.

    [1]
    http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Distribution
    [2] http://people.apache.org/builds/struts/struts-annotations/1.0.3/


    I'm also not sure how the vote passed, if they were never signed
    originally.
    I see that you mentioned that during the vote.


    Can some please take a moment to check these? If they're okay I
    presume
    the artefacts then just need to be copied to the right location for
    rsync to
    ibiblio. Any other formalities for struts-annotations?

    [1]
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/
    Is this the same as what's in
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/
    ?
    I think that is a problem isn't it? The files in the
    m2-staging-repository
    [3] were built and deployed by Don, not the files I built and signed [2]
    As the maven artefacts for ibiblio come from m2-staging-repository they'd
    be Don's binaries, not mine. I presume that means the process has to be
    started from scratch unless Don completes as only he can/should sign the
    binaries he created and voters tested?

    [3]
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Martin Cooper at Apr 9, 2008 at 1:42 am
    On Tue, Apr 8, 2008 at 6:30 PM, Martin Cooper wrote:
    On Tue, Apr 8, 2008 at 6:22 PM, Don Brown wrote:

    *sigh* is this all necessary? I mean, by using the Maven release
    plugin, the binaries are created off the tag. A quick SVN command can
    confirm the tag hasn't been modified, so I don't see any problem with
    Jeromy building new binaries and finishing the release. The vote had
    passed with the caveat that the binaries are signed, so if Jeromy
    built the same binaries, a new vote would be an exercise in useless
    bureaucracy, IMO.

    If the binaries Jeromy created are bit-for-bit identical to the ones you
    built, then I don't have a problem. If they're not, then what he has built
    is not the same as what was voted on.
    And more to the point, actually, it's not what people tested before they
    voted.

    --
    Martin Cooper


    --
    Martin Cooper


    Don

    On Wed, Apr 9, 2008 at 10:30 AM, Jeromy Evans
    wrote:
    Wendy Smoak wrote:
    On Tue, Apr 8, 2008 at 8:54 AM, Jeromy Evans
    wrote:


    I've signed struts-annotations-1.0.3 using jeromy@apache.org and
    copied
    to
    [1].
    Where/how did you sign them? Were the files re-built? Generally
    you
    only sign what you build yourself, while it's under your control on
    a
    machine you trust.

    Thanks for looking at these Wendy. It's difficult to step-in part way
    through the process.

    I checked the source out from the struts-annotations-1.03 TAG.
    I packaged and signed them myself but DID NOT deploy to
    m2-staging-repository as that task was complete already
    From step 7 of Ref[1], I signed the build artifacts and copied them to
    Ref[2] as per step 8.

    [1]
    http://cwiki.apache.org/confluence/display/WW/Creating+and+Signing+a+Distribution
    [2] http://people.apache.org/builds/struts/struts-annotations/1.0.3/


    I'm also not sure how the vote passed, if they were never signed
    originally.
    I see that you mentioned that during the vote.


    Can some please take a moment to check these? If they're okay I
    presume
    the artefacts then just need to be copied to the right location
    for
    rsync to
    ibiblio. Any other formalities for struts-annotations?

    [1]
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/
    Is this the same as what's in
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/
    ?
    I think that is a problem isn't it? The files in the
    m2-staging-repository
    [3] were built and deployed by Don, not the files I built and signed [2]
    As the maven artefacts for ibiblio come from m2-staging-repository they'd
    be Don's binaries, not mine. I presume that means the process has to be
    started from scratch unless Don completes as only he can/should sign the
    binaries he created and voters tested?

    [3]
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Apr 9, 2008 at 1:58 am

    Martin Cooper wrote:

    If the binaries Jeromy created are bit-for-bit identical to the ones you
    built, then I don't have a problem. If they're not, then what he has built
    is not the same as what was voted on.
    And more to the point, actually, it's not what people tested before they
    voted.

    --
    Martin Cooper

    Understood. Can I sign and distribute Don's binaries[1] or *must* they
    be signed by the person that built them?

    I generally wouldn't do it, but consider struts-annotations-1.3 as
    low-risk because of its small scope and that these binaries built on
    17Feb08 passed a vote on 18Feb08.

    I'm trying to push ahead as struts-annotations-1.3 is blocking a release
    of struts-2.1.1.

    [1]
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Martin Cooper at Apr 9, 2008 at 2:40 am

    On Tue, Apr 8, 2008 at 6:57 PM, Jeromy Evans wrote:

    Martin Cooper wrote:
    If the binaries Jeromy created are bit-for-bit identical to the ones
    you
    built, then I don't have a problem. If they're not, then what he has
    built
    is not the same as what was voted on.

    And more to the point, actually, it's not what people tested before they
    voted.

    --
    Martin Cooper


    Understood. Can I sign and distribute Don's binaries[1] or *must* they be
    signed by the person that built them?

    I've lost track of why Don can't sign them himself, but I would consider it
    OK for you to do that if you use the following process:

    1) Have Don e-mail you the binaries or otherwise get them to you in a way
    that they could not be intercepted. (I don't consider you picking them up
    from the URL below to be acceptable because there is a chance, however slim,
    that those binaries could have been compromised. And yes, I realise that
    e-mail can in fact be intercepted as well, but if you guys coordinate
    time-wise, I think that is an acceptable risk.)

    2) You sign them, and mail the .asc files back to Don.

    3) Don verifies that the .asc files you sent him validate successfully
    against the binaries that he has.

    At this point, you (Jeromy) have the appropriate signatures for what Don
    originally built, as well as the binaries, and can take it from there.

    --
    Martin Cooper

    I generally wouldn't do it, but consider struts-annotations-1.3 as
    low-risk because of its small scope and that these binaries built on 17Feb08
    passed a vote on 18Feb08.

    I'm trying to push ahead as struts-annotations-1.3 is blocking a release
    of struts-2.1.1.

    [1]
    http://people.apache.org/builds/struts/struts-annotations/1.0.3/m2-staging-repository/org/apache/struts/struts-annotations/1.0.3/



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Jeromy Evans at Apr 9, 2008 at 3:16 am

    Martin Cooper wrote:
    On Tue, Apr 8, 2008 at 6:57 PM, Jeromy Evans <
    jeromy.evans@blueskyminds.com.au> wrote:

    Understood. Can I sign and distribute Don's binaries[1] or *must* they be
    signed by the person that built them?

    I've lost track of why Don can't sign them himself, but I would consider it
    OK for you to do that if you use the following process:

    1) Have Don e-mail you the binaries or otherwise get them to you in a way
    that they could not be intercepted. (I don't consider you picking them up
    from the URL below to be acceptable because there is a chance, however slim,
    that those binaries could have been compromised. And yes, I realise that
    e-mail can in fact be intercepted as well, but if you guys coordinate
    time-wise, I think that is an acceptable risk.)

    2) You sign them, and mail the .asc files back to Don.

    3) Don verifies that the .asc files you sent him validate successfully
    against the binaries that he has.

    At this point, you (Jeromy) have the appropriate signatures for what Don
    originally built, as well as the binaries, and can take it from there.
    Thanks Martin, That doesn't take Don out of the loop so it won't
    alleviate the issue that he's been too busy to sign and distribute the
    binaries.
    If he's able to validate the .asc against the original binaries he's
    able to generate them. It's less effort and risk to wait until Don has
    time to complete the task.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Don Brown at Apr 9, 2008 at 12:30 pm
    I don't know Martin, don't you think there is security-conscious and
    then there is over-doing it a bit? If Jeromy took the jars as I
    deployed to the staging repo, signed them, then released them to the
    mirrors, wouldn't that be sufficient? He can check the timestamp of
    the file and see it was I who created them and that they haven't been
    modified. Yes, I suppose an uber hacker could have rooted the server
    and manipulated the timestamps, but if that is the case, we have
    _much_ bigger problems then a malicious annotations jar that isn't
    even used in a production Struts 2 app.

    Don

    On Wed, Apr 9, 2008 at 1:15 PM, Jeromy Evans
    wrote:
    Martin Cooper wrote:
    On Tue, Apr 8, 2008 at 6:57 PM, Jeromy Evans <
    jeromy.evans@blueskyminds.com.au> wrote:



    Understood. Can I sign and distribute Don's binaries[1] or *must* they
    be
    signed by the person that built them?

    I've lost track of why Don can't sign them himself, but I would consider it
    OK for you to do that if you use the following process:

    1) Have Don e-mail you the binaries or otherwise get them to you in a way
    that they could not be intercepted. (I don't consider you picking them up
    from the URL below to be acceptable because there is a chance, however slim,
    that those binaries could have been compromised. And yes, I realise that
    e-mail can in fact be intercepted as well, but if you guys coordinate
    time-wise, I think that is an acceptable risk.)

    2) You sign them, and mail the .asc files back to Don.

    3) Don verifies that the .asc files you sent him validate successfully
    against the binaries that he has.

    At this point, you (Jeromy) have the appropriate signatures for what Don
    originally built, as well as the binaries, and can take it from there.
    Thanks Martin, That doesn't take Don out of the loop so it won't alleviate
    the issue that he's been too busy to sign and distribute the binaries.
    If he's able to validate the .asc against the original binaries he's able
    to generate them. It's less effort and risk to wait until Don has time to
    complete the task.




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org
  • Al Sutton at Apr 10, 2008 at 6:28 am
    Guys,

    I've just submitted a patch to bring the S1 plugin pom up to 1.3.8 and I'm
    getting the following compile error;

    D:\Struts2\Build\struts2\plugins\struts1\src\main\java\org\apache\struts2\s1\WrapperModuleConfig.java:[41,0]
    org.apache.struts2.s1.WrapperModuleConfig is not abstract and does not
    override abstract method findActionConfigId(java.lang.String) in
    org.apache.struts.config.ModuleConfig
    D:\Struts2\Build\struts2\plugins\struts1\src\main\java\org\apache\struts2\s1\WrapperModuleConfig.java:[41,0]
    org.apache.struts2.s1.WrapperModuleConfig is not abstract and does not
    override abstract method findActionConfigId(java.lang.String) in
    org.apache.struts.config.ModuleConfig

    Could this indicate a problem with the S1 plugin thats currently up for
    inclusion in S2.1.1?

    Al.

    ----- Original Message -----
    From: "Jeromy Evans" <jeromy.evans@blueskyminds.com.au>
    To: "Struts Developers List" <dev@struts.apache.org>
    Sent: Wednesday, April 09, 2008 4:15 AM
    Subject: Re: 2.1 build

    Martin Cooper wrote:
    On Tue, Apr 8, 2008 at 6:57 PM, Jeromy Evans <
    jeromy.evans@blueskyminds.com.au> wrote:

    Understood. Can I sign and distribute Don's binaries[1] or *must* they
    be
    signed by the person that built them?

    I've lost track of why Don can't sign them himself, but I would consider
    it
    OK for you to do that if you use the following process:

    1) Have Don e-mail you the binaries or otherwise get them to you in a way
    that they could not be intercepted. (I don't consider you picking them up
    from the URL below to be acceptable because there is a chance, however
    slim,
    that those binaries could have been compromised. And yes, I realise that
    e-mail can in fact be intercepted as well, but if you guys coordinate
    time-wise, I think that is an acceptable risk.)

    2) You sign them, and mail the .asc files back to Don.

    3) Don verifies that the .asc files you sent him validate successfully
    against the binaries that he has.

    At this point, you (Jeromy) have the appropriate signatures for what Don
    originally built, as well as the binaries, and can take it from there.
    Thanks Martin, That doesn't take Don out of the loop so it won't
    alleviate the issue that he's been too busy to sign and distribute the
    binaries.
    If he's able to validate the .asc against the original binaries he's able
    to generate them. It's less effort and risk to wait until Don has time to
    complete the task.


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
    For additional commands, e-mail: dev-help@struts.apache.org

Related Discussions