[
https://issues.apache.org/jira/browse/SLING-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607255#action_12607255
]
Jukka Zitting commented on SLING-555:
-------------------------------------
As noted by Bertrand on the mailing list, we could also instruct people to add
the incubating repository to the Maven configuration in ~/.m2/settings.xml.
> mvn install on svn checkout fails if sling-3-incubator is not available
> -----------------------------------------------------------------------
>
> Key: SLING-555
> URL: https://issues.apache.org/jira/browse/SLING-555
> Project: Sling
> Issue Type: Bug
> Components: General
> Reporter: Jukka Zitting
>
> Carsten recently (revision 670566) added the incubating repository to the
> parent POM in svn. But since many components refer to version 3-incubator
> (instead of 4-incubator-SNAPSHOT) as the parent POM, this repository
> reference is not picked up by the build.
> And if the 3-incubator version of the parent POM is not available in the
> local Maven repository, the build fails as Maven does not know where to
> download it from (since the components don't refer to 4-incubator-SNAPSHOT
> version of the parent POM...).
> Moving the repository reference to the reactor POM also won't help.
> The options I see are:
> 1) Make components use 4-incubator-SNAPSHOT as the parent POM version
> 2) Make the 3-incubator version of the parent POM explicitly available in
> svn
> 3) Add the incubator repository reference to all component POMs
> 4) Publish the 3-incubator version of the parent POM to the standard Maven
> repository
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
