On May 30, 2009, at 11:03 AM, Jason Warner wrote:
Hi David,
Do we have an estimated date for when trunk will be able to build
cleanly again? It's difficult to change the AHP builds to build
other projects first, and I don't really want to do that unless
these requirements are going to be around for a while.
If there is any flexibility at all about how the AHP builds work then
I'd set up a nexus repo to supply all the external artifacts and add,
temporarily, a hosted repo you can deploy genesis into and also add
the staging repo as a proxied repo. If this seems plausible I might
be able to help set it up.
In terms of actual solutions.... assuming that the build can work with
a snapshot parent that isn't in the local repo already then deploying
the genesis snapshot relies on
nexus space for geronimo and xbean:
https://issues.apache.org/jira/browse/INFRA-2066
nexus access for me:
https://issues.apache.org/jira/browse/INFRA-2076
we could go back to assembly plugin beta-3 if someone figures out the
problem I'm having with beta-4. Hopefully beta-4 will be released on
monday at 4:41 EST so I kinda expect that problem will disappear first.
thanks
david jencks
Thanks,
~Jason Warner
On Sat, May 30, 2009 at 10:55 AM, David Jencks
<[email protected]> wrote:
I saw some odd behavior with the release candidate for the assembly
plugin beta-4 (source archives are being built twice) so I committed
changes in genesis that rely on this version to make it easier for
people to reproduce.
So if you want to build genesis trunk (needed for g. trunk) you need
to make the staging repo available such as by adding it to your
nexus repo list and released group.
https://repository.apache.org/content/repositories/maven-staging-035
thanks
david jencks
