[ 
http://jira.codehaus.org/browse/MWAS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198675#action_198675
 ] 

Jim Solderitsch commented on MWAS-57:
-------------------------------------

I see that the generated ant goal is better:

    <wsAdmin wasHome="/home/jjs/IBM/WebSphere/AppServer" profileName="AppSrv01" 
script="'/home/jjs/netcds/netcdsPubWAS/Ear/bindsharedlibrary.py'" lang="jython" 
conntype="SOAP" host="jjscentos" jvmMaxMemory="256M" failonerror="true"/> 

But for CentOS, the extra double quotes still cause problems -- I get a file 
not found error. If I do an ls for the file with the path as written (wrapped 
in double and single quotes combined) from a terminal, this fails. If I leave 
off the double quotes, so that the path is wrapped in only single quotes, ls 
works. Also, if it is wrapped only in double quotes, ls works as well

So it seems it is the double wrapping here that matters. CentOS handles a 
single wrapping but not a double wrapping.


> Script elements for wsadmin goal have extra quote marks
> -------------------------------------------------------
>
>                 Key: MWAS-57
>                 URL: http://jira.codehaus.org/browse/MWAS-57
>             Project: Maven 2.x WebSphere 6 Plugin
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>         Environment: CentOS 5.3, Websphere 6.1.0.27
>            Reporter: Jim Solderitsch
>            Assignee: David J. M. Karlsen
>             Fix For: 1.2
>
>         Attachments: bad quot.jpg
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Here is what my pom fragment looks like:
>                     <plugin>
>                         <groupId>org.codehaus.mojo</groupId>
>                         <artifactId>was6-maven-plugin</artifactId>
>                         <version>1.2-SNAPSHOT</version>
>                         <executions>
>                           <execution>
>                             <id>deploy</id>
>                             <phase>validate</phase>
>                             <goals>
>                               <goal>wsAdmin</goal>
>                             </goals>
>                           </execution>
>                         </executions>
>                         <configuration>
>                           <wasHome>/opt/IBM/SDP/runtimes/base_v61</
> wasHome>
>                           <profileName>WTE_APPSRV61_FEP1</profileName>
>                           <conntype>SOAP</conntype>
>                           <script>bindsharedlibrary.jacl</script>
>                           <language>jacl</language>
>                           <host>jjscentos</host>
>                           <user>foo</user>
>                           <password>bar</password>
>                         </configuration>
>                     </plugin>
> The buildfile that gets generated puts a &quot; around the script path
> that gets generated from the script element;
> For example:
>    <wsAdmin wasHome="/opt/IBM/SDP/runtimes/base_v61"
> profileName="WTE_APPSRV61_FEP1" script="&quot;/home/jjs/netcds/
> netcdsPubWAS/Ear/bindsharedlibrary.jacl&quot;" lang="jacl"
> conntype="SOAP" host="jjscentos" user="foo" password="bar"
> jvmMaxMemory="256M" failonerror="true"/>
> This leads to wsadmin complaining that the file can't be found.
> The file exists without the &quot; around the name -- the plugin is adding 
> the quote marks.
> What can I do about this?

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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to