Thanks for the reply.  I actually thought of this idea too so I had a hard 
time coming up with why it doesn't work or why it's hard.

I think we depend on CVS naturally because we use RAD as our environment 
and it's just easier to do so.

Anyways, the solution that you have come up with is hard because we have 
two applications.  So say both the applications are using the latest 
snapshot version of the utility project.  Then, one wants to stop using 
HEAD while the other application continues to use HEAD/snapshot.  So we 
release a version of the Utility project.  As a result of this release, we 
would have to manually update all the POMs dependent on the Utility 
project with the specific version number being released.  Then, we would 
have to manually update all the POMs from the other application that needs 
to depend on the new snapshot number since it is now incremented.  This 
means that we would have to coordinate between the two application teams 
while really it should only affect one team.

Do I make sense or am I missing something?

Thanks again for your reply.


_Mang Lau





"Siegmann Daniel, NY" <[EMAIL PROTECTED]> 
04/04/2006 10:36 AM
Please respond to
"Maven Users List" <[email protected]>


To
'Maven Users List' <[email protected]>
cc

Subject
RE: Shared projects and Maven best practice






I'm afraid I can't help with your problem exactly, but since you wanted to
spark a discussion...

> So really I guess that if there's a way to checkout an older 
> version of 
> the Utility project but HEAD of everything else, then I'm 
> fine.  Is there 
> a way to do this? Or am I using Maven incorrectly?  If I'm 
> unclear, please 
> ask and I'll try my best to clarify what I have.
> 
> Thanks so much.
> 
> 
> _Mang Lau

Why are you having your applications depend on CVS at all? I would think 
it
would be best to build Utility as its own jar, which would by deployed to
your central repository. Each release (tagged version) would exist as a 
jar
in your repository, and you could approximate CVS HEAD by deploying
snapshots. Then you can set the dependencies in your applications to
whichever versions you wish (an exact version for a tag, and a snapshot 
for
HEAD).

Unless I'm missing a reason why this wouldn't work?

--
Daniel Siegmann
FJA-US, Inc.
(212) 840-2618 ext. 139


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to