Ohh, I just observed that even in the commons project, if one jar had a dependency on another jar after the release now they are including version 1.0, instead of 1.1-snapshot for their dependency. Will I have to go through all pom-s and update them manually? That's going to hurt.
Ex: A/pom.xml -> has dependency on 1.0-SNAPSHOT version of B after release A/pom.xml snapshot-1.1 will have a dependency on version 1.0 B. I was expecting it would be a dependency on version 1.1-SNAPSHOT of B, since they are modules of the same pom.xml. Is there a way to avoid this? thanks, Attila --- Attila Mezei-Horvati <[EMAIL PROTECTED]> wrote: > I have two projects: commons and app. > Commons is a parent pom for all the commons > subprojects. At the end it creates about 10 jars. > > App is dependent on these 10. > > When working, we modify both code (commons and app). > So we need to use dependency on snapshots. However > when releasing, we can not depend on snapshots. > > This means I have to go and modify all dependencies > in > the app's pom manually. I need to set them to a > version number (latest release). Then, after > release, > set the dependencies back to snapshots. > > Seems a lot of manual work to have a release. Is > there > a way to avoid this? > > thanks, > Attila > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
