Am 2013-12-10 01:54, schrieb Hervé BOUTEMY:
Le mardi 10 décembre 2013 01:05:30 Michael-O a écrit :
Am 2013-12-10 00:58, schrieb Hervé BOUTEMY:
<content>${project.build.directory}/staging/${maven.site.path}</content>
is not really necessary here, since skins are never multi-module, then no
need to site:stage
that's not a blocking issue, since it will work: just need to do extra
site:stage step, not usually needed
I am aware of that. That change was intentional. It conforms to all
other POMs and to the procedure described in the docs. Nothing more,
nothing less.
not really what I wanted to express with "if the component has multiple
modules, locally stage the site:"
but staging in every situation has the advantage that instructions would not
be different for mono-module and multi-module
I don't know what you all prefer: simpler instructions for mono-module (but
require a little thinking to know in which situation a build is) or uniform
instructions (even if it is a little more complex than absolutely necessary
for mono-modules)
Personally, I preform uniformity, convention over configuration. There
is a proverb "Don't make me think". A RM should not care about a
mono-module or multi-module project, all he/she needs to know that if I
perform these steps, all should be fine. The relase docs are scattered
over several pages and references. I'd like to avoid another exception
to that.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
