[EMAIL PROTECTED] schrieb:
Jan Nielsen schrieb:
To get a bug fix into 1.1.6, I would like to recreate the Tomahawk
1.1.6 build. I grabbed the code at:
http://svn.apache.org/repos/asf/myfaces/tomahawk/tags/1_1_6
and tried to build that with "mvn -Djsf=12 -Dtomahawk=12 clean
package" but it fails to resolve the dependency on
myfaces-shared-tomahawk 2.0.6:
org.apache.myfaces.shared:myfaces-shared-tomahawk:jar:2.0.6
Reviewing a couple of repositories, it looks like 2.0.x releases are
there, /except/ for 2.0.6. I'm fine with building it myself but it
also looks like the 2.0.6 is missing from subversion:
http://svn.apache.org/repos/asf/myfaces/shared/tags
So, can the Tomahawk 1.1.6 build be reproduced? Is there a recipe, a
wiki, a script, or a spot in subversion from which the Tomahawk 1.1.6
release can be built?
Hmm..that is weird indeed. I'll check the email archives.
Tomahawk 1.1.6 does indeed depend on shared-2.0.6, and as you say
there appears to be neither a tag nor a released jar for shared-2.0.6.
The jsf1.2 "flavour" of tomahawk has only been added *after* the 1.1.6
tomahawk release. So the "-Djsf=12 -Dtomahawk=12" options are not
valid when building the 1.1.6 release. Note that normal tomahawk 1.1.x
runs fine on both JSF1.1 and JSF1.2. However there are some
optimisations that can be added by building against JSF1.2, hence the
new "flavour". But that doesn't change the fact that shared-2.0.6 is
missing.
I see there is a 2.0.6 dir in
http://svn.apache.org/repos/asf/myfaces/shared/branches
And the pom there has the released version number.
So I would guess that whoever did the release did a "mvn install" from
that branch dir, then build the final release of tomahawk but forgot to:
* move the branch to the tags dir
* deploy the shared jar to the release repo
So to rebuild tomahawk 1.1.6, you should be able to check out that
branch dir, do "mvn install" locally then build tomahawk 1.1.6.
In some ways it *is* a little odd to deploy the shared jar to the
release repo, as nobody will actually ever use it - except people like
yourself who want to rebuild the official release. But for tidiness it
probably *should* be done. And certainly an svn copy should have existed
in the tag dir, not just "branches" (although there is technically no
difference when using svn).
Regards,
Simon
