You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Savage (JIRA)" <ji...@apache.org> on 2009/07/14 13:57:14 UTC

[jira] Created: (FELIX-1359) sigil-ivy-plugin.jar should export ant tasks via properties file vs expecting user to track classes that implement tasks

sigil-ivy-plugin.jar should export ant tasks via properties file vs expecting user to track classes that implement tasks
------------------------------------------------------------------------------------------------------------------------

                 Key: FELIX-1359
                 URL: https://issues.apache.org/jira/browse/FELIX-1359
             Project: Felix
          Issue Type: Improvement
          Components: Sigil
            Reporter: David Savage
            Priority: Minor


There are currently lots of repeated entries in examples files like:

  <classpath file="${ivy.settings.dir}/../../../target/sigil-ivy-plugin.jar" />
  <typedef name="sigil-parser" classname="org.apache.felix.sigil.ivy.SigilParser" />
  <typedef name="sigil" classname="org.apache.felix.sigil.ivy.SigilResolver" />

Would be better to use the form of task def:

<project xmlns:sigil="sigillib:org.apache.felix.sigil">
     <taskdef uri="sigillib:org.apache.felix.sigil"
              resource="sigillib.properties"
              classpath="${ivy.settings.dir}/../../../target/sigil-ivy-plugin.jar"/>

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

[jira] Commented: (FELIX-1359) sigil-ivy-plugin.jar should export ant tasks via properties file vs expecting user to track classes that implement tasks

Posted by "Derek Baum (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730806#action_12730806 ] 

Derek Baum commented on FELIX-1359:
-----------------------------------

The above <classpath> and <typedef> are sub-elements of ivy-settings.
They cannot be replaced with ant <typedef>.

See: http://ant.apache.org/ivy/history/2.1.0-rc1/settings.html

Some of the examples are minor modifications to existing Ivy examples, so I didn't want to change them, except as required to use Sigil.



> sigil-ivy-plugin.jar should export ant tasks via properties file vs expecting user to track classes that implement tasks
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-1359
>                 URL: https://issues.apache.org/jira/browse/FELIX-1359
>             Project: Felix
>          Issue Type: Improvement
>          Components: Sigil
>            Reporter: David Savage
>            Priority: Minor
>
> There are currently lots of repeated entries in examples files like:
>   <classpath file="${ivy.settings.dir}/../../../target/sigil-ivy-plugin.jar" />
>   <typedef name="sigil-parser" classname="org.apache.felix.sigil.ivy.SigilParser" />
>   <typedef name="sigil" classname="org.apache.felix.sigil.ivy.SigilResolver" />
> Would be better to use the form of task def:
> <project xmlns:sigil="sigillib:org.apache.felix.sigil">
>      <taskdef uri="sigillib:org.apache.felix.sigil"
>               resource="sigillib.properties"
>               classpath="${ivy.settings.dir}/../../../target/sigil-ivy-plugin.jar"/>

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

[jira] Commented: (FELIX-1359) sigil-ivy-plugin.jar should export ant tasks via properties file vs expecting user to track classes that implement tasks

Posted by "David Savage (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730824#action_12730824 ] 

David Savage commented on FELIX-1359:
-------------------------------------

Ok, shame I just noticed I had to update a load of these during the package refactor. Possibly some ivy gurus out there may be able to suggest a way to make these configs less fragile to internal refactoring?

> sigil-ivy-plugin.jar should export ant tasks via properties file vs expecting user to track classes that implement tasks
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-1359
>                 URL: https://issues.apache.org/jira/browse/FELIX-1359
>             Project: Felix
>          Issue Type: Improvement
>          Components: Sigil
>            Reporter: David Savage
>            Priority: Minor
>
> There are currently lots of repeated entries in examples files like:
>   <classpath file="${ivy.settings.dir}/../../../target/sigil-ivy-plugin.jar" />
>   <typedef name="sigil-parser" classname="org.apache.felix.sigil.ivy.SigilParser" />
>   <typedef name="sigil" classname="org.apache.felix.sigil.ivy.SigilResolver" />
> Would be better to use the form of task def:
> <project xmlns:sigil="sigillib:org.apache.felix.sigil">
>      <taskdef uri="sigillib:org.apache.felix.sigil"
>               resource="sigillib.properties"
>               classpath="${ivy.settings.dir}/../../../target/sigil-ivy-plugin.jar"/>

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