[
https://issues.apache.org/jira/browse/SANDBOX-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556011#action_12556011
]
Simon Kitching commented on SANDBOX-201:
----------------------------------------
Even checking out the parent directory might not be sufficient. If the parent
pom itself depends on a snapshot parent, you would need to have it available on
the local filesystem too.
Actually, what harm would it do to just add the definition for the snapshot
repository to every pom, as per the attached patch, and leave it in for
releases? The maven-release-plugin always reports an error if there is a
SNAPSHOT dependency anywhere. Does it cause problems if a pom in the main repo
defines a snapshot repo? If so, either the release pom rewriting process could
remove them, or maven core could be modified to ignore snapshot repos defined
in poms retrieved from non-snapshot repos.
Perhaps we should continue this discussion on the maven list?
> [PATCH] minor pom.xml tweak so folks can build this project by itself without
> any other sandbox components
> ----------------------------------------------------------------------------------------------------------
>
> Key: SANDBOX-201
> URL: https://issues.apache.org/jira/browse/SANDBOX-201
> Project: Commons Sandbox
> Issue Type: Improvement
> Components: CSV
> Reporter: james strachan
> Assignee: Dennis Lundberg
> Attachments: csv-pom-patch.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
