Proposal on how we should handle syncing between stabilisation forests and always open 7u (original) (raw)
Alan Bateman Alan.Bateman at oracle.com
Sat Nov 5 03:57:05 PDT 2011
- Previous message: Proposal on how we should handle syncing between stabilisation forests and always open 7u
- Next message: Proposal on how we should handle syncing between stabilisation forests and always open 7u
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 04/11/2011 18:12, Florian Weimer wrote:
:
jdk7u2/jaxws doesn't built either (see my previous message), so I'm not sure if the issue at hand is merely lack of synchronization. It's really difficult to find a JDK 7 forest which builds and receives (security) updates. I just checked the various forests:
jdk7u/jdk7u2 and jdk7u/jdk7u have the latest security fixes but unfortunately neither forest builds because jaxws_src.bundle is set to a bundle that doesn't exist.
jdk7u/jdk7u-dev is the integration forest for jdk7u/jdk7u. It isn't quite up to date and so doesn't have the changeset that switches to the missing jaxws bundle. Unfortunately it doesn't build either because it doesn't have the fix for 7099017.
Edvard or Abhijit - this is all rather embarrassing, do you know what is going on with the JAX-WS bundle? If that can be fixed and jdk7u-dev sync'ed up then I think law and order can be restored.
-Alan.
- Previous message: Proposal on how we should handle syncing between stabilisation forests and always open 7u
- Next message: Proposal on how we should handle syncing between stabilisation forests and always open 7u
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]