[
https://issues.apache.org/jira/browse/JCRVLT-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139479#comment-17139479
]
Konrad Windszus commented on JCRVLT-398:
----------------------------------------
1) is fixed with
https://github.com/apache/jackrabbit-filevault/commit/05ca12a45a4d963e8aa4c92b07460b8686c47d0e
2) I cannot reproduce as the maven-enforcer is correctly configured in
https://github.com/apache/jackrabbit-filevault/blob/05ca12a45a4d963e8aa4c92b07460b8686c47d0e/parent/pom.xml#L296
and enabled for all modules. [~reschke] I guess the problem could be that your
build failed even earlier? Please share the error.
> Migrate Filevault to Git
> ------------------------
>
> Key: JCRVLT-398
> URL: https://issues.apache.org/jira/browse/JCRVLT-398
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Misc
> Affects Versions: 3.4.2, package-maven-plugin-1.0.4
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.4.6, package-maven-plugin-1.1.4
>
>
> As discussed in
> https://lists.apache.org/thread.html/8ea0d827d9e8488183648f2364ecd4e178b6d82e03193735aae6b5cd%40%3Coak-dev.jackrabbit.apache.org%3E
> we should migrate to Git.
> Good candidates are both repos for FileVault which should each get a
> dedicated Git repository.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
