So I've just noticed that while we're installing snapshots, if you don't
explicitly tell maven to NOT use a unique snapshot number AND you have
say 4 generated artifacts you're installing, the metadata reflects the
last one installed.

 

For example, if you have a project that generates:

 

1 - a jar file

2 - a sources jar

3 - a zip file

4 - a war file

 

When you start using deploy:deploy-file, the metadata file in the
repository gets something like this:

 

  <versioning>

    <snapshot>

      <buildNumber>1</buildNumber>

      <timestamp>20080822.153306</timestamp>

    </snapshot>

 

But when you go through all four items, buildNumber becomes 4.  THEN -
when you have some other module that depends on these artifacts, it
fails to build because it's looking for buildNumber 4 for the jar file
and that doesn't exist.  How do you install all the modules and keep the
uniqueness?  Do you have to have them all bound/attached such that when
you do the regular mvn install, they're all accounted for and use
deploy:deploy?

 

Color me confused.

Reply via email to