You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Antony Stubbs (JIRA)" <ji...@codehaus.org> on 2008/08/28 05:47:49 UTC
[jira] Created: (MDEP-177) add target option to go-offline goal
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
[jira] Commented: (MDEP-177) add target option to go-offline goal
Posted by "Antony Stubbs (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146258#action_146258 ]
Antony Stubbs commented on MDEP-177:
------------------------------------
Blogged about this and it's work around and other things here:
http://stubbisms.wordpress.com/2008/08/28/maven-is-to-ant-as-a-nail-gun-is-to-hammer-and-nails-you-need-to-move-on/
> 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
[jira] Commented: (MDEP-177) add target option to go-offline goal
Posted by "Devin Reid (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MDEP-177) add target option to go-offline goal
Posted by "Falko Modler (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=303294#comment-303294 ]
Falko Modler commented on MDEP-177:
-----------------------------------
I just came accross this issue when trying to assembly a project which should be run completely offline.
My workaround is:
{code}
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<executions>
<execution>
<id>create-offline-repo</id>
<phase>prepare-package</phase>
<goals>
<goal>exec</goal>
</goals>
</execution>
</executions>
<configuration>
<executable>${maven.home}/bin/${mvn-script}</executable>
<commandlineArgs>"dependency:go-offline" "-Dmaven.repo.local=target/repo"</commandlineArgs>
</configuration>
</plugin>
{code}
${mvn-script} is set platform dependend (by profiles that are activated by os-family).
> add target option to go-offline goal
> ------------------------------------
>
> Key: MDEP-177
> URL: https://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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira