[
http://jira.codehaus.org/browse/MDEP-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206032#action_206032
]
Devin Reid commented on MDEP-177:
---------------------------------
A feature like this would be extremely useful for projects that need to be
rebuilt offsite from normal development on secure networks.
> add target option to go-offline goal
> ------------------------------------
>
> Key: MDEP-177
> URL: http://jira.codehaus.org/browse/MDEP-177
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: go-offline
> Affects Versions: 2.0
> Reporter: Antony Stubbs
> Assignee: Brian Fox
>
> Say I want to make it so that maven can work completely offline, just from
> someone checking out the project from source control. That means all
> dependencies must be under source control.
> the only way to do this, as far as I know, is to rename your repository dir,
> run the go-offline goal, and then copy all contents of the repo into your
> project, add the repo location to you project pom and commit. The big problem
> with this of course is that maven has to go fetch everything from the net,
> and that its a pain to do more than once (i.e. when plugin versions change,
> as copy-dependencies already outputs to target/dependencies)
> What would be much nicer, and easier to maintain, would be if there was a
> target option for go-offline. That way, i could set the 'target' to
> /mavenProjectRepo and *everything* needed to run maven on the project would
> be installed into that dir, from the local maven repo, or downloaded if
> required.
> Hope I was clear, let me know if you want clarification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
