[jira] Commented: (SLING-555) mvn install on svn checkout fails if sling-3-incubator is not available

["Alexander Klimetschek (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610612#action_12610612 ] 

Alexander Klimetschek commented on SLING-555:
---------------------------------------------

I experienced the same problem (in revision 673754) and would prefer that this is fixed in trunk and not by changing settings.xml. If things are deployed to the m2-incubating-repository (as a placeholder for the central repository as long as the project is not mature), that repository has to be fully referenced within the poms.

The changes I had to make are these:

1) Add the pluginRepository as noted by Jukka to the parent pom and

2) reference the newest parent pom (4-incubator-SNAPSHOT) in these projects:
    - samples/simple-demo/pom.xml
    - extensions/apt/servlet/pom.xml
    - launchpad/webapp/pom.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
>             Fix For: 2.1.0
>
>         Attachments: SLING-555.patch
>
>
> 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.