You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Jan Matèrne (JIRA)" <ji...@apache.org> on 2010/01/08 10:39:54 UTC

[jira] Created: (IVY-1158) Make ivy.xml available

Make ivy.xml <conf description> available
-----------------------------------------

                 Key: IVY-1158
                 URL: https://issues.apache.org/jira/browse/IVY-1158
             Project: Ivy
          Issue Type: New Feature
          Components: Ant
            Reporter: Jan Matèrne
            Priority: Minor


You can (an IMHO should) write an explanation of the configuration in the ivy file
<ivy-module version="2.0">
    <configurations>
        <conf name="runtime" description="Runtime Libraries"/>
    </configurations>
</ivy-module>

The Ant task <ivy:info/> makes the names names available, but not the descriptions. 
So the first RFE is making them available (accoding to 'infotest.configurations') as 'infotest.configuration.descriptions'.

Another RFE is enhanding <ivy:retrieve/> to create a describing file in the destination directory which contains this information.
E.e. with Ivy pattern lib/[conf]/[artifact].[ext] you would create with <ivy:retrieve descriptionfile="readme.txt"/> a file lib/runtime/readme.txt with content "Runtime Libraries".
(!! Recreate old files, but beware that multiple confs could result in the same dir if the ivy pattern doesnt contain a [conf]. )


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


[jira] Commented: (IVY-1158) Make ivy.xml available

Posted by "Jan Matèrne (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799145#action_12799145 ] 

Jan Matèrne commented on IVY-1158:
----------------------------------

Workaround with AntContrib and a little bit scripting

{code:xml title="Ant Buildfile"} 
<xmlproperty file="ivy.xml" prefix=".ivyconf" delimiter="@"/>
<script language="javascript"> <![CDATA[
    descriptions = project.getProperty(".ivyconf.ivy-module.configurations.conf(description)").split("@");
    confs        = project.getProperty(".ivyconf.ivy-module.configurations.conf(name)").split("@");
    for(i=0; i<confs.length; i++) {
        project.setNewProperty(".ivyconf.list." + (i+1) + ".conf", confs[i]);
        project.setNewProperty(".ivyconf.list." + (i+1) + ".desc", descriptions[i]);
    }
    project.setNewProperty(".ivyconf.list.length", confs.length);
]]></script>
<ac:for begin="1" end="${.ivyconf.list.length}" param="i">
    <sequential>
        <echo file="lib/${.ivyconf.list.@{i}.conf}/.readme.txt" message="${.ivyconf.list.@{i}.desc}"/>
    </sequential>
</ac:for>
{code} 

> Make ivy.xml <conf description> available
> -----------------------------------------
>
>                 Key: IVY-1158
>                 URL: https://issues.apache.org/jira/browse/IVY-1158
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Ant
>            Reporter: Jan Matèrne
>            Priority: Minor
>
> You can (an IMHO should) write an explanation of the configuration in the ivy file
> <ivy-module version="2.0">
>     <configurations>
>         <conf name="runtime" description="Runtime Libraries"/>
>     </configurations>
> </ivy-module>
> The Ant task <ivy:info/> makes the names names available, but not the descriptions. 
> So the first RFE is making them available (accoding to 'infotest.configurations') as 'infotest.configuration.descriptions'.
> Another RFE is enhanding <ivy:retrieve/> to create a describing file in the destination directory which contains this information.
> E.e. with Ivy pattern lib/[conf]/[artifact].[ext] you would create with <ivy:retrieve descriptionfile="readme.txt"/> a file lib/runtime/readme.txt with content "Runtime Libraries".
> (!! Recreate old files, but beware that multiple confs could result in the same dir if the ivy pattern doesnt contain a [conf]. )

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


[jira] Updated: (IVY-1158) Make ivy.xml available

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene updated IVY-1158:
-------------------------------

    Fix Version/s: 2.2.0-RC1
                       (was: trunk)

> Make ivy.xml <conf description> available
> -----------------------------------------
>
>                 Key: IVY-1158
>                 URL: https://issues.apache.org/jira/browse/IVY-1158
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Ant
>            Reporter: Jan Matèrne
>            Assignee: Maarten Coene
>            Priority: Minor
>             Fix For: 2.2.0-RC1
>
>
> You can (an IMHO should) write an explanation of the configuration in the ivy file
> <ivy-module version="2.0">
>     <configurations>
>         <conf name="runtime" description="Runtime Libraries"/>
>     </configurations>
> </ivy-module>
> The Ant task <ivy:info/> makes the names names available, but not the descriptions. 
> So the first RFE is making them available (accoding to 'infotest.configurations') as 'infotest.configuration.descriptions'.
> Another RFE is enhanding <ivy:retrieve/> to create a describing file in the destination directory which contains this information.
> E.e. with Ivy pattern lib/[conf]/[artifact].[ext] you would create with <ivy:retrieve descriptionfile="readme.txt"/> a file lib/runtime/readme.txt with content "Runtime Libraries".
> (!! Recreate old files, but beware that multiple confs could result in the same dir if the ivy pattern doesnt contain a [conf]. )

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


[jira] Resolved: (IVY-1158) Make ivy.xml available

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene resolved IVY-1158.
--------------------------------

       Resolution: Fixed
    Fix Version/s: trunk
         Assignee: Maarten Coene

I've implemented your first RFE in trunk.
After running the <ivy:info /> task, the descriptions are availabe as "ivy.configuration.[config name].desc".

Regarding your second RFE, I think this is too specific to add to Ivy. And you can easily do it with ant-contrib as you illustrated in your example build.xml, something like this:

{noformat}
<ivy:info file="ivy.xml" />
<ac:for list="${ivy.configurations}" param="conf">
    <sequential>
        <echo file="lib/@{conf}/.readme.txt" message="${ivy.configuration.@{conf}.desc}"/>
    </sequential>
</ac:for>
{noformat}

But please reopen if you don't agree...

Maarten

> Make ivy.xml <conf description> available
> -----------------------------------------
>
>                 Key: IVY-1158
>                 URL: https://issues.apache.org/jira/browse/IVY-1158
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Ant
>            Reporter: Jan Matèrne
>            Assignee: Maarten Coene
>            Priority: Minor
>             Fix For: trunk
>
>
> You can (an IMHO should) write an explanation of the configuration in the ivy file
> <ivy-module version="2.0">
>     <configurations>
>         <conf name="runtime" description="Runtime Libraries"/>
>     </configurations>
> </ivy-module>
> The Ant task <ivy:info/> makes the names names available, but not the descriptions. 
> So the first RFE is making them available (accoding to 'infotest.configurations') as 'infotest.configuration.descriptions'.
> Another RFE is enhanding <ivy:retrieve/> to create a describing file in the destination directory which contains this information.
> E.e. with Ivy pattern lib/[conf]/[artifact].[ext] you would create with <ivy:retrieve descriptionfile="readme.txt"/> a file lib/runtime/readme.txt with content "Runtime Libraries".
> (!! Recreate old files, but beware that multiple confs could result in the same dir if the ivy pattern doesnt contain a [conf]. )

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