You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Assaf Arkin (JIRA)" <ji...@apache.org> on 2008/11/17 21:42:44 UTC

[jira] Commented: (BUILDR-217) separate 'type' from 'extension' in packages

    [ https://issues.apache.org/jira/browse/BUILDR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648314#action_12648314 ] 

Assaf Arkin commented on BUILDR-217:
------------------------------------

The package method uses the type argument to determine which packager to call, packager then decides how to apply the spec to the artifact, so it's entirely possible to have an :osgi packager creating a .jar artifact.

> separate 'type' from 'extension' in packages
> --------------------------------------------
>
>                 Key: BUILDR-217
>                 URL: https://issues.apache.org/jira/browse/BUILDR-217
>             Project: Buildr
>          Issue Type: Improvement
>          Components: Packaging
>    Affects Versions: 1.3.2
>            Reporter: Ittay Dror
>             Fix For: 1.3.4
>
>
> #package currently uses spec[:type] for both the 'type' of the artifact and the extension given to the file name.
> but sometimes files with the same extension may be of different types. in OSGI for example, the extension is always .jar, but they can be bundles or fragements. another example is source jars or zips. their type is 'source', regardless of the extension (as long as it is some sort of zip of course).
> in maven, ArtifactHandler separates between extension and 'packaging' i think it would be good for buildr to have the same

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.