You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Adam Young (JIRA)" <ji...@apache.org> on 2010/04/16 22:59:25 UTC

[jira] Updated: (BUILDR-424) Buildr should support JPackage style remote file:// repositories

     [ https://issues.apache.org/jira/browse/BUILDR-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Young updated BUILDR-424:
------------------------------

    Attachment: buildr-pathmunge.patch

This patch provides the absolute minimun extension to buildr in order to provide run time extension repository code.  The localbuild.rb file is an example that shows how it could be used.  I'll post a working version shortly that does the JPP transform

> Buildr should support JPackage style remote file:// repositories
> ----------------------------------------------------------------
>
>                 Key: BUILDR-424
>                 URL: https://issues.apache.org/jira/browse/BUILDR-424
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Dependency management
>         Environment: Fedora and RPM based systems
>            Reporter: Adam Young
>         Attachments: buildr-pathmunge.patch
>
>
> A build system needs a more controlled environment to produce reproduceable builds than the Maven dependency resolution mechanism currently provides.   For JPackage, they have modified Maven to look in a local repository for builds:  /usr/share/maven and also to use a mapping file to produce much shorter paths.
> This is relatively trivial to implement in buildr, and would provide a great path forward for people that are currently using maven to build their projects.
> It would require an injection in artifact.rb's download function where a repository would have an optional code block, that performes the same logic as 
>  path = "#{group_path}/#{id}/#{version}/#{File.basename(name)}"
>           URI.download repo_url + path, name
> But allows the munging of the pieces that make up the path, most specifically the group_path

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira