[
https://issues.apache.org/jira/browse/EXTVAL-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643362#action_12643362
]
Leonardo Uribe commented on EXTVAL-3:
-------------------------------------
This task has several points to be taken into account, that cause a lot of
confusion. It is better to list it, so we can check in the future
(Unfortunately I spent a lot of time trying generate a minimal site and find
those ugly maven site bugs!):
1. This project has an async release procedure. In other words, each module
could have its own release procedure and it has a separate parent pom where all
projects inherit. This does not play well with maven site plugin. For example,
execute:
mvn install
over trunk does not generate site xml to be published on local repository, but
if we do the same on parent module this file is generated.
2. If some change on site.xml is done, it is necessary to delete local
repository file. If not, the change is not added and when site is generated the
changes are not reflected.
3. For correct generation we can't execute:
mvn site:site
on trunk directly. By some reason parent site.xml is not taken into account for
child modules. Rather we must do site:site on parent module and then on each
module (like in buildtools myfaces maven plugins).
see http://jira.codehaus.org/browse/MSITE-364,
http://jira.codehaus.org/browse/MSITE-302
I hope this changes in the future but for now we should live with that three
ugly facts :-( .
> initial project site setup
> --------------------------
>
> Key: EXTVAL-3
> URL: https://issues.apache.org/jira/browse/EXTVAL-3
> Project: MyFaces Extensions Validator
> Issue Type: Task
> Affects Versions: 1.0.1-SNAPSHOT, 1.2.1-SNAPSHOT
> Reporter: Gerhard Petracek
> Assignee: Leonardo Uribe
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
