This is a good set of observations and if we can figure out why this
snapshot is not being used (or even returned despite the dependency
onit) I think we'd be good to go. If we're going to do that though I
think it's important to understand the cause of this behaviour and
not just the effect.
--
Jeremy
On Dec 4, 2006, at 12:31 AM, ant elder wrote:
I'm starting to wonder if the subject line is even more apt than we
realize
and we're just assuming this is a significant problem without
investigating.
AFAICT the only thing thats happening is what I originally reported
- you
see log messages about the AXIOM API SNAPSHOT when using the WS
samples...but it doesn't look like that SNAPSHOT jar is actually
getting
used by anything.
- If you delete if from your repository the samples run fine. You
can run
the samples in offline mode and not have that SNAPSHOT jar in your
repository and the samples still run fine.
- If you build the sample webapps with loadExtensionDependencies
set to true
then the SNAPSHOT jar is *not* included in the WAR repository and the
samples still run fine even in offline mode.
- If you make incompatible changes to classes in the SNAPSHOT jar
in your
local repository, eg change the OMElement interface to have no
methods, the
samples still run fine.
Additionally debugging in the MavenHelper class you can see the
SNAPSHOT
messages are coming from the artifactResolver.resolveTransitively
call on
line 264 but the ArtifactResolutionResult thats returned from the
call *does
not* include the axiom-api SNAPSHOT artifact.
Based on that it doesn't look like the SNAPSHOT jar is even added
to the
classpath used by the samples. Could anyone else confirm these
observations?
If this is true the I think we could safely cut the M2 release as-
is, maybe
just add a comment to the release notes about the SNAPSHOT messages.
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
