installing snapshots to an internal repository

[EJ Ciramella <ej...@upromise.com>]

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.

Re: installing snapshots to an internal repository

[Brett Porter <br...@gmail.com>]

You may need to elaborate on your set up, as you can see here it is
possible to deploy them together for build #2:
http://snapshots.repository.codehaus.org/org/codehaus/redback/redback-users-api/1.1-SNAPSHOT/

That was built using the release profile in this pom:
http://svn.codehaus.org/redback/redback/trunk/pom.xml

Cheers,
Brett

2008/8/23 EJ Ciramella <ej...@upromise.com>:
> 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.
>
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org