On Monday 19 April 2004 20:40, Jason van Zyl wrote:
> Huh? You don't want to share dependencies anywhere?
No. Just to say that
xerces -> 2.4.0
avalon-logkit -> 1.2
jakarta-bcel -> 5.2
log4j -> 1.2.1
and so on.
> > I want to have ONE place, where I can list the versions to use
> > for each artifact. Both the "used" ones as well as the "generated" ones.
>
> Sorry, what's the distinction wrt to Maven?
The 'generated ones' need to be 'injected' into pom.currentVersion, the
dependent ones needs to be 'injected' into 'pom.dependencies'.
> You realize that the deployment of a SNAPSHOT produces a timestamped
> version? You say you don't like the SNAPSHOT but again you don't say
> why.
One reason is that "those who used it" before my time didn't manage to get it
to work as it is supposed to, I guess. I.e. no timestamps. That is not
Maven's problem.
My 'disapproval' is that it consumes a lot of time connecting to the net. I am
sure you would say, use "-o"...
> > I haven't tried to manipulate the ${pom.currentVersion} directly from
> > such plugin. Would that work? If so, would that also mean that the plugin
> > could "fill-in" the versions for all the dependencies as well?
>
> The release plugin does this: manipulates the POMs, bumps versions and
> resolves SNAPSHOTS to their timestamped values before a release so you
> have real versions for everything before deploying.
Hmmm... I'll look into it.
Cheers
Niclas
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
