Browse Source

Fixes to the borland ejbjar component to get it to handle non-windows

builds. Make work with ejb-naming schemes

Submitted by:	Tom Palmer <tomp@uk.uu.net>


git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@269517 13f79535-47bb-0310-9956-ffa450edef68
master
Conor MacNeill 24 years ago
parent
commit
616dd57d1a
1 changed files with 2 additions and 2 deletions
  1. +2
    -2
      src/main/org/apache/tools/ant/taskdefs/optional/ejb/BorlandDeploymentTool.java

+ 2
- 2
src/main/org/apache/tools/ant/taskdefs/optional/ejb/BorlandDeploymentTool.java View File

@@ -110,7 +110,7 @@ public class BorlandDeploymentTool extends GenericDeploymentTool implements Exe
protected static final String BAS_DD = "ejb-inprise.xml";

/** Java2iiop executable **/
protected static final String JAVA2IIOP = "java2iiop.exe";
protected static final String JAVA2IIOP = "java2iiop";

/** Verify class */
protected static final String VERIFY = "com.inprise.ejb.util.Verify";
@@ -218,7 +218,7 @@ public class BorlandDeploymentTool extends GenericDeploymentTool implements Exe
File borlandDD = new File(getConfig().descriptorDir,BAS_DD);
if (borlandDD.exists()) {
log("Borland specific file found "+ borlandDD, Project.MSG_VERBOSE);
ejbFiles.put(META_DIR + BAS_DD, borlandDD);
ejbFiles.put(META_DIR + BAS_DD, ddPrefix + borlandDD);
}
else {
log("Unable to locate borland deployment descriptor. It was expected to be in " +


Loading…
Cancel
Save