ting not to use snapshots at all. That appears
not to be the Maven and C.I. spirit, is it?
I'm probably mis-understanding you ...
--
View this message in context:
http://www.nabble.com/Snapshot-parent-tp18743503p18749742.html
Sent from the Maven - Users mailing list archive at Nabble.com.
On Thu, 31 Jul 2008 09:44:41 sverhagen wrote:
> In Continuous Integration spirit, we have snapshot dependencies between all
> our own components.
> We have also set components to use snapshots of their parents ( ...
> ...-SNAPSHOT).
> Is the latter good practice?
> It will mean that I can't release
't it?
All your help would be appreciated -- this is really twisting my brain.
--
View this message in context:
http://www.nabble.com/Snapshot-parent-tp18743503p18743503.html
Sent from the Maven - Users mailing list archive at
So the whole point of releases is "rebuild" -- i.e. given a release
label and the software repository, the system can be rebuilt.
Is that correct?
Thanks for your feedback,
Adrian.
Dan Tran wrote:
> that is not allowed since there is no guarantee you can rebuild the release
> with a dependent snap
that is not allowed since there is no guarantee you can rebuild the release
with a dependent snapshot ( ie parent )
-D
On 12/6/06, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
I am trying to release a module using the maven-release-plugin.
The module has a parent which was not released y
Hi all,
I am trying to release a module using the maven-release-plugin.
The module has a parent which was not released yet (its siblings are not
released also).
When running release:prepare on that module Maven complains that its
parent is a SNAPSHOT, so it cannot complete the release preparation
Hi all,
I am trying to release a module using the maven-release-plugin.
The module has a parent which was not released yet (its siblings are not
released also).
When running release:prepare on that module Maven complains that its
parent is a SNAPSHOT, so it cannot complete the release preparation
