[
https://issues.apache.org/jira/browse/SANDBOX-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12555213
]
Simon Kitching commented on SANDBOX-201:
----------------------------------------
Umm, Dennis, the point is that the commons-sandbox-parent-3-SNAPSHOT pom cannot
be located - because the snapshot repository is not enabled.
It's a circular problem - the pom that defines the snapshot repo is only
available if a user has the snapshot repo defined.
This is a general problem that bites anyone working on code direct from svn
trunk, if the component references a not-yet-released parent pom. A general
solution to this would be great - but it's a kind of bootstrap problem; how to
find info about the appropriate snapshot repositories for a project without
looking in any snapshot repositories.
For the specific cases of sandbox components, it seems reasonable to me to add
the snapshot repo definition. It could actually be done as standard practice in
every pom, but we would need to be careful to always take it out again before a
release. However as sandbox components never get released that isn't a problem.
> [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.
