You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "willem Jiang (JIRA)" <ji...@apache.org> on 2007/06/13 12:01:33 UTC

[jira] Created: (CXF-727) make cxf sampel common build support more than one jar

make cxf sampel common build support more than one jar 
-------------------------------------------------------

                 Key: CXF-727
                 URL: https://issues.apache.org/jira/browse/CXF-727
             Project: CXF
          Issue Type: Improvement
    Affects Versions: 2.0-RC
            Reporter: willem Jiang
            Assignee: willem Jiang
             Fix For: 2.0


Changed the thirdparty.classpath property to be used  as a refid and not as location .
In this way we can setup more than one jar in the thirdparty.classpath 

So the thirdpath jar would be used in sample like this 

<property environment="env"/>
     <path id="sample.thirdpart.classpath">
         <pathelement location="thirdpart1.jar"/>
         <pathelement location="thirdpart2.jar"/>
    </path>
    <property name="thirdparty.classpath" refid="sample.thirdpart.classpath"/>
   <import file="../../common_build.xml"/> 

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


[jira] Closed: (CXF-727) make cxf sampel common build support more than one jar

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

willem Jiang closed CXF-727.
----------------------------

    Resolution: Fixed

> make cxf sampel common build support more than one jar 
> -------------------------------------------------------
>
>                 Key: CXF-727
>                 URL: https://issues.apache.org/jira/browse/CXF-727
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.0-RC
>            Reporter: willem Jiang
>            Assignee: willem Jiang
>             Fix For: 2.0
>
>
> Changed the thirdparty.classpath property to be used  as a refid and not as location .
> In this way we can setup more than one jar in the thirdparty.classpath 
> So the thirdpath jar would be used in sample like this 
> <property environment="env"/>
>      <path id="sample.thirdpart.classpath">
>          <pathelement location="thirdpart1.jar"/>
>          <pathelement location="thirdpart2.jar"/>
>     </path>
>     <property name="thirdparty.classpath" refid="sample.thirdpart.classpath"/>
>    <import file="../../common_build.xml"/> 

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


[jira] Updated: (CXF-727) make cxf sampel common build support more than one jar

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

willem Jiang updated CXF-727:
-----------------------------


It already implemented in current common-build.xml

> make cxf sampel common build support more than one jar 
> -------------------------------------------------------
>
>                 Key: CXF-727
>                 URL: https://issues.apache.org/jira/browse/CXF-727
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.0-RC
>            Reporter: willem Jiang
>            Assignee: willem Jiang
>             Fix For: 2.0
>
>
> Changed the thirdparty.classpath property to be used  as a refid and not as location .
> In this way we can setup more than one jar in the thirdparty.classpath 
> So the thirdpath jar would be used in sample like this 
> <property environment="env"/>
>      <path id="sample.thirdpart.classpath">
>          <pathelement location="thirdpart1.jar"/>
>          <pathelement location="thirdpart2.jar"/>
>     </path>
>     <property name="thirdparty.classpath" refid="sample.thirdpart.classpath"/>
>    <import file="../../common_build.xml"/> 

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