Re: [struts1] STATUS - Version 1.3.5

[Ted Husted]

On 7/16/06, Dion Gillard <[EMAIL PROTECTED]> wrote:

Isn't the missing LICENSE/NOTICE very important?


That's been fixed.

And if it hadn't been fixed the in automatic build, I would have just
dropped the files into the archive myself before uploading it.

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [struts1] STATUS - Version 1.3.5

[Ted Husted]

On 7/15/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:

Fair enough.  Anything else that would improve the quality of 1.3.5, then?


One nit I'm having overall is that the project name isn't being
included in the page titles.

So, instead of a page title like "Struts Scripting - Welcome", ours
are just rendering as "Welcome".

This isn't a showstopper, but the Maven site appears to do this.

* http://maven.apache.org/

The "Maven - " prefix isn't in the source for the page, but "Maven"
happens to  be the value of project name in the site.xml.

* http://svn.apache.org/repos/asf/maven/site/trunk/src/site/xdoc/index.xml
* http://svn.apache.org/repos/asf/maven/site/trunk/src/site/site.xml

Is there a switch we need to flip someplace?

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Distribution Directories

[Ted Husted]

At

* http://people.apache.org/dist/struts/

I moved the v1 and scripting release from the action subdirectory up
to the struts directory, and then removed action.

Is this going to affect the mirroring, or any of that?

I don't see that we have any references from the website right now,
since there aren't any pending betas.

For the snapshots, we've been posting to

* http://people.apache.org/builds/struts/1.3.x/

Do we still want to use the "dist" folder for the 1.3.5 release?

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:

At

* http://people.apache.org/dist/struts/

I moved the v1 and scripting release from the action subdirectory up
to the struts directory, and then removed action.

Is this going to affect the mirroring, or any of that?


My impression is that only files under www.apache.org/dist are
mirrored (nothing on people.apache.org.)


For the snapshots, we've been posting to

* http://people.apache.org/builds/struts/1.3.x/

Do we still want to use the "dist" folder for the 1.3.5 release?


Based on the following links, I think it should be under /builds until
it becomes a release, then it can be moved to one of the 'dist'
directories depending on the quality.

* http://www.apache.org/dev/release.html#release-types
* http://www.apache.org/dev/release.html#build-directories

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Ted Husted]

The checklist mentions

* Deploy Test Build to cvs.apache.org/maven-snapshot-repository

Is there a Maven command for that?

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:


The checklist mentions

* Deploy Test Build to cvs.apache.org/maven-snapshot-repository

Is there a Maven command for that?


After you change all the version numbers to 1.3.5, 'mvn deploy' will do it.

Both / and
/ are pointed to the same
place (people.apache.org/maven-snapshot-repository) so no matter
whether the version number ends in -SNAPSHOT, it's going to get
deployed to the same place.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:


Both / and
/ are pointed to the same
place (people.apache.org/maven-snapshot-repository)


Just to avoid confusion:  right now on minotaur, /www/cvs.apache.org
is symlinked to /www/people.apache.org .

We should switch everything over to people.a.o eventually, but for the
moment it doesn't matter.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Ted Husted]

OK. I'll be going out for a bit soon, but I'll finish up on the tag
and roll later tonight.

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:

> The checklist mentions
>
> * Deploy Test Build to cvs.apache.org/maven-snapshot-repository
>
> Is there a Maven command for that?

After you change all the version numbers to 1.3.5, 'mvn deploy' will do it.

Both / and
/ are pointed to the same
place (people.apache.org/maven-snapshot-repository) so no matter
whether the version number ends in -SNAPSHOT, it's going to get
deployed to the same place.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Craig McClanahan]

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:


On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:

> Both / and
> / are pointed to the same
> place (people.apache.org/maven-snapshot-repository)

Just to avoid confusion:  right now on minotaur, /www/cvs.apache.org
is symlinked to /www/people.apache.org .

We should switch everything over to people.a.o eventually, but for the
moment it doesn't matter.



I can't guarantee that it's universal, but this *has* matterred for me in a
couple of cases ... particularly in trying to do builds of things like
MyFaces that have POMs pointing at a Maven repository on cvs.apache.org.  I
get timeouts on the Maven dependency downloads from this hostname, while
they work fine from people.apache.org.  I'd recommend that we at least get
the names correct in our own POMs before posting the release.

Craig

--

Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:


I can't guarantee that it's universal, but this *has* matterred for me in a
couple of cases ... particularly in trying to do builds of things like
MyFaces that have POMs pointing at a Maven repository on cvs.apache.org.  I
get timeouts on the Maven dependency downloads from this hostname, while
they work fine from people.apache.org.


There is a redirect in place from
http://cvs.apache.org/maven-snapshot-repository to
http://people.apache.org/maven-snapshot-repository.  Do you only have
trouble when you're behind a proxy?


I'd recommend that we at least get
the names correct in our own POMs before posting the release.


The Struts 1 parent pom does use people.apache.org in the
/, so it should be fine for downloads.

I was talking about deployment, where scp'ing something to
/www/cvs.apache.org or /www/people.apache.org is one and the same.
That () is defined in the struts-master pom,
and can be  fixed next time around in v4.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Craig McClanahan]

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:


On 7/16/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:

> I can't guarantee that it's universal, but this *has* matterred for me
in a
> couple of cases ... particularly in trying to do builds of things like
> MyFaces that have POMs pointing at a Maven repository on cvs.apache.org
.  I
> get timeouts on the Maven dependency downloads from this hostname, while
> they work fine from people.apache.org.

There is a redirect in place from
http://cvs.apache.org/maven-snapshot-repository to
http://people.apache.org/maven-snapshot-repository.  Do you only have
trouble when you're behind a proxy?



Previously, it was failing either with or without a proxy.  Just tried it
again, though, and it's working now ... so it might have been a transient
issue.


I'd recommend that we at least get
> the names correct in our own POMs before posting the release.

The Struts 1 parent pom does use people.apache.org in the
/, so it should be fine for downloads.

I was talking about deployment, where scp'ing something to
/www/cvs.apache.org or /www/people.apache.org is one and the same.
That () is defined in the struts-master pom,
and can be  fixed next time around in v4.



That also affects where Maven looks for dependencies, if you are *using*
Struts 1.3.5, right?  But as long as it doesn't mess anything up, I agree it
can wait for v4.

--

Wendy



Craig

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:



> I was talking about deployment, where scp'ing something to
> /www/cvs.apache.org or /www/people.apache.org is one and the same.
> That () is defined in the struts-master pom,
> and can be  fixed next time around in v4.

That also affects where Maven looks for dependencies, if you are *using*
Struts 1.3.5, right?  But as long as it doesn't mess anything up, I agree it
can wait for v4.


No,  controls the destination for 'mvn deploy'
and 'mvn site:deploy'.

It's / in the pom (or settings.xml) that
controls where Maven looks for dependencies.  And that is already
correct in the struts-parent pom.

Ted:  I'm testing strutsel-exercise-taglib -> el-example changes to
the assembly module now.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:

> The checklist mentions
>
> * Deploy Test Build to cvs.apache.org/maven-snapshot-repository
>
> Is there a Maven command for that?

After you change all the version numbers to 1.3.5, 'mvn deploy' will do it.


Actually... http://wiki.apache.org/struts/StrutsMavenRelease has
better instructions.

(I forgot to add -Ppre-assembly so it will build the -sources and
-javadoc jars.)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Ted Husted]

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:

Actually... http://wiki.apache.org/struts/StrutsMavenRelease has
better instructions.

(I forgot to add -Ppre-assembly so it will build the -sources and
-javadoc jars.)


OK, I'm rebuilding the assemblies against r422570 (with the -SNAPSHOT
qualifier removed).

But, I'd not sure what this line means

$ rm -rf $M2_REPO/org/apache/struts

Does it mean to clear our my refer to my local m2 repository as to o.a.s?

-T.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:


But, I'd not sure what this line means

 $ rm -rf $M2_REPO/org/apache/struts

Does it mean to clear our my refer to my local m2 repository as to o.a.s?


Yes, it's a good idea to clear your local repo before building a
release.  Maven deploys from the local repo, so if you had anything
old lying around (for example if you forgot to say -Papps) it might
get included in the assemblies.

It also makes sure that a completely clean build works, so that
someone downloading the distribution can build it starting with
nothing in the local repo.  (You'll see it retrieve the struts-master
pom each time.)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Ted Husted]

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:

> But, I'd not sure what this line means
>
>  $ rm -rf $M2_REPO/org/apache/struts
>
> Does it mean to clear our my refer to my local m2 repository as to o.a.s?

Yes, it's a good idea to clear your local repo before building a
release.  Maven deploys from the local repo, so if you had anything
old lying around (for example if you forgot to say -Papps) it might
get included in the assemblies.

It also makes sure that a completely clean build works, so that
someone downloading the distribution can build it starting with
nothing in the local repo.  (You'll see it retrieve the struts-master
pom each time.)


The other instructions say to do that at the beginning.

Do we need to do it twice?

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:


The other instructions say to do that at the beginning.

Do we need to do it twice?


Sorry, what two sets of instructions are in conflict?

I haven't done it for a while, but the steps here look good to me:
 http://wiki.apache.org/struts/StrutsMavenRelease

(Though I think they've been edited since an actual release was done,
so if they don't make sense in practice, let me know.)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Proposed Board Report

[Craig McClanahan]

As part of our transition to an Apache top level project (TLP), we are
obligated to submit a report to the ASF Board every month for the first
three months, then quarterly thereafter.  Here's what I am proposing to send
for July, which needs to be forwarded in a couple days.  (I'll also create a
"pmc" subdirectory in the repository to archive these things, since there is
nothing non-public we need to worry about).  Comments?

===

Apache Shale Board Report for July 2006
===


Overview


Per the Apache Board resolution at the June 2006 meeting, Apache Shale was
created as a top level project.  This is the first of the "every month for
the
first three months" status reports to the Board on activities within the
project.

All of the initial root and infrastructure requests have been completed.  We
are still de-tangling a few loose ends (wiki and JIRA instance shared with
the
Struts project), but these are not considered to be urgent.


PMC and Committer Changes
-

None.


Current Development Activities
--

As the creation of Shale as a TLP was coming to fruition, we had nearly
completed a migration to a Maven2 based build environment.  This work has
been substantially completed, and Shale is now completely M2 based for its
build infrastructure.  Nightly builds are still currently hosted on my
(Craig's) home desktop, but steps are underway to migrate this to a
Continuum
instance on Apache infrastructure.

We have initiated a contest to pick an official logo for the Apache Shale
project -- details are at .  The
entries so far have ranged from humorous to compelling ... it will be
interesting
to pick a final winner.

Current release activities are focused on a 1.0.3 release, which is still
likely
to be considered "beta" quality (due to dependence on unreleased components,
plus some outstanding bugs), but which has been requested by some downstream
users to avoid their need to depend on snapshots.


Submitted by,
Craig McClanahan

Re: [struts1] STATUS - Version 1.3.5 AVAILABLE

[Ted Husted]

Pursuant to the Struts 1.3.5 Release Plan

[http://wiki.apache.org/struts/StrutsActionRelease135]

a tagged build of 1.3.5 is now available

[http://people.apache.org/builds/struts/1.3.5]]

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Proposed Board Report

[Ted Husted]

Did you mean to send this to the Shale dev@, Craig?

On 7/17/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:

As part of our transition to an Apache top level project (TLP), we are
obligated to submit a report to the ASF Board every month for the first
three months, then quarterly thereafter.  Here's what I am proposing to send
for July, which needs to be forwarded in a couple days.  (I'll also create a
"pmc" subdirectory in the repository to archive these things, since there is
nothing non-public we need to worry about).  Comments?

===

Apache Shale Board Report for July 2006
===


Overview


Per the Apache Board resolution at the June 2006 meeting, Apache Shale was
created as a top level project.  This is the first of the "every month for
the
first three months" status reports to the Board on activities within the
project.

All of the initial root and infrastructure requests have been completed.  We
are still de-tangling a few loose ends (wiki and JIRA instance shared with
the
Struts project), but these are not considered to be urgent.


PMC and Committer Changes
-

None.


Current Development Activities
--

As the creation of Shale as a TLP was coming to fruition, we had nearly
completed a migration to a Maven2 based build environment.  This work has
been substantially completed, and Shale is now completely M2 based for its
build infrastructure.  Nightly builds are still currently hosted on my
(Craig's) home desktop, but steps are underway to migrate this to a
Continuum
instance on Apache infrastructure.

We have initiated a contest to pick an official logo for the Apache Shale
project -- details are at .  The
entries so far have ranged from humorous to compelling ... it will be
interesting
to pick a final winner.

Current release activities are focused on a 1.0.3 release, which is still
likely
to be considered "beta" quality (due to dependence on unreleased components,
plus some outstanding bugs), but which has been requested by some downstream
users to avoid their need to depend on snapshots.


Submitted by,
Craig McClanahan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Proposed Board Report

[Craig McClanahan]

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:


Did you mean to send this to the Shale dev@, Craig?



Yep ... sorry for the noise :-)

Craig


On 7/17/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:

> As part of our transition to an Apache top level project (TLP), we are
> obligated to submit a report to the ASF Board every month for the first
> three months, then quarterly thereafter.  Here's what I am proposing to
send
> for July, which needs to be forwarded in a couple days.  (I'll also
create a
> "pmc" subdirectory in the repository to archive these things, since
there is
> nothing non-public we need to worry about).  Comments?
>
>
===
>
> Apache Shale Board Report for July 2006
> ===
>
>
> Overview
> 
>
> Per the Apache Board resolution at the June 2006 meeting, Apache Shale
was
> created as a top level project.  This is the first of the "every month
for
> the
> first three months" status reports to the Board on activities within the
> project.
>
> All of the initial root and infrastructure requests have been
completed.  We
> are still de-tangling a few loose ends (wiki and JIRA instance shared
with
> the
> Struts project), but these are not considered to be urgent.
>
>
> PMC and Committer Changes
> -
>
> None.
>
>
> Current Development Activities
> --
>
> As the creation of Shale as a TLP was coming to fruition, we had nearly
> completed a migration to a Maven2 based build environment.  This work
has
> been substantially completed, and Shale is now completely M2 based for
its
> build infrastructure.  Nightly builds are still currently hosted on my
> (Craig's) home desktop, but steps are underway to migrate this to a
> Continuum
> instance on Apache infrastructure.
>
> We have initiated a contest to pick an official logo for the Apache
Shale
> project -- details are at .  The
> entries so far have ranged from humorous to compelling ... it will be
> interesting
> to pick a final winner.
>
> Current release activities are focused on a 1.0.3 release, which is
still
> likely
> to be considered "beta" quality (due to dependence on unreleased
components,
> plus some outstanding bugs), but which has been requested by some
downstream
> users to avoid their need to depend on snapshots.
>
>
> Submitted by,
> Craig McClanahan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Ted Husted]

After resetting my Maven repository, it took several restarts to get
it to build. The build would stall on a 503 error, but get past the
rror on that field, when restarted.

The same thing seems to be happening to me with deploy, but it still fails.

Does deploy update the maven-snapshot folder. Evidentally, that part
comes at the end.

Otherwise, it's tagged, rolled, and uploaded.

-Ted.

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:
>
> > The checklist mentions
> >
> > * Deploy Test Build to cvs.apache.org/maven-snapshot-repository
> >
> > Is there a Maven command for that?
>
> After you change all the version numbers to 1.3.5, 'mvn deploy' will do it.

Actually... http://wiki.apache.org/struts/StrutsMavenRelease has
better instructions.

(I forgot to add -Ppre-assembly so it will build the -sources and
-javadoc jars.)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
HTH, Ted.
* http://www.husted.com/struts/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Craig McClanahan]

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:



Otherwise, it's tagged, rolled, and uploaded.



+1 on the 1.3.5 bits.  A couple of notes below that I don't consider fatal
to the release:

* The "all" release (currently 40mb) is not really scalable to
 large numbers of sample apps, due to the duplication of
 dependency jars across the apps.  It might be worth considering
 a different release strategy for sample apps for 2.x, but that is
 not really relevant here.

* The "#1" struts-faces example app has embedded the storyboard
 stuff for the standard Struts mail reader app, which should really
 be updated for the differences with JSF (or simply deleted for now)

* The JAR files in the "lib" directory of the "all" distribution do not
 include the "X-*" source and target extension settings that are typical
 for recent Jakarta Commons releases (although "Build-Jdk" conveys
 some of that information).

-Ted.





Craig

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Ted Husted <[EMAIL PROTECTED]> wrote:


After resetting my Maven repository, it took several restarts to get
it to build. The build would stall on a 503 error, but get past the
rror on that field, when restarted.


I had to look up 503... Service Unavailable ?

When you say you reset your repository, did you delete the whole
thing, or just org/apache/struts?  What you're describing sounds like
the typical 'first build' that fails several times until all of the
transitive dependencies get downloaded to the local repo.


The same thing seems to be happening to me with deploy, but it still fails.


Can you run it with -X and redirect to a file so I can see the entire thing?


Does deploy update the maven-snapshot folder. Evidentally, that part
comes at the end.


Yes, 'mvn deploy -Ppre-assembly' should be uploading (via scp)
metadata and artifacts to people.apache.org/maven-snapshot-repository
as it builds each module.

I'm a little concerned because Maven rebuilds the jars during the
install phase, so the jars in the assembly are not going to be the
same ones that finally get deployed to the m2 repo. (But since there
is no date in the manifest, there is a chance they'll match exactly.)


Otherwise, it's tagged, rolled, and uploaded.


Thank you!

When you have time I'd like to hear your thoughts on the release
process.  For such a short checklist, it sure seems like a lot of
work.  After the last two I wondered if I was making it harder than
necessary.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Distribution Directories

[Wendy Smoak]

On 7/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:


... Maven rebuilds the jars during the install phase ...


s/install/package

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]