[
http://jira.codehaus.org/browse/MIDLJ-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier closed MIDLJ-9.
-------------------------------
Assignee: Arnaud Heritier
Resolution: Fixed
Fix Version/s: 1.1
> IDLJ fails on unix with absolute path if you don't have the right to write in
> a parent directory. Replace absolute paths in the command line by relative
> paths.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIDLJ-9
> URL: http://jira.codehaus.org/browse/MIDLJ-9
> Project: Maven 2.x CORBA IDL Compiler Plugin
> Issue Type: Bug
> Affects Versions: 1.0, 1.1
> Reporter: Arnaud Heritier
> Assignee: Arnaud Heritier
> Fix For: 1.1
>
>
> I have this error on the CI server
> {code}
> 12-Mar-2009 17:12:25 [INFO] [ERROR]
> com.sun.tools.corba.se.idl.InvalidArgument: Invalid argument: -td.
> 12-Mar-2009 17:12:25
> 12-Mar-2009 17:12:25 Compiler Usage:
> 12-Mar-2009 17:12:25
> 12-Mar-2009 17:12:25 java
> com.sun.tools.corba.se.idl.toJavaPortable.Compile [options] <idl file>
> 12-Mar-2009 17:12:25
> 12-Mar-2009 17:12:25 where <idl file> is the name of a file containing IDL
> definitions, and
> 12-Mar-2009 17:12:25 [options] is any combination of the options listed
> below. The options
> 12-Mar-2009 17:12:25 are optional and may appear in any order; <idl file> is
> required and
> 12-Mar-2009 17:12:25 must appear last.
> 12-Mar-2009 17:12:25
> 12-Mar-2009 17:12:25 Options:
> 12-Mar-2009 17:12:25 -d <symbol> This is equivalent to the
> following line in an
> 12-Mar-2009 17:12:25 IDL file: #define <symbol>
> 12-Mar-2009 17:12:25 -emitAll Emit all types, including
> those found in #included files.
> 12-Mar-2009 17:12:25 -f<side> Define what bindings to emit.
> <side> is one of client,
> 12-Mar-2009 17:12:25 server, all, serverTIE,
> allTIE. serverTIE and allTIE
> 12-Mar-2009 17:12:25 cause delegate model
> skeletons to be emitted. If this
> 12-Mar-2009 17:12:25 flag is not used, -fclient is
> assumed.
> 12-Mar-2009 17:12:25 -i <include path> By default, the current
> directory is scanned for
> 12-Mar-2009 17:12:25 included files. This option
> adds another directory.
> 12-Mar-2009 17:12:25 -keep If a file to be generated
> already exists, do not
> 12-Mar-2009 17:12:25 overwrite it. By default it
> is overwritten.
> 12-Mar-2009 17:12:25 -noWarn Suppress warnings.
> 12-Mar-2009 17:12:25 -oldImplBase Generate skeletons compatible
> with old (pre-1.4) JDK ORBs.
> 12-Mar-2009 17:12:25 -pkgPrefix <t> <prefix> When the type or module name
> <t> is encountered at
> 12-Mar-2009 17:12:25 file scope, begin the Java
> package name for all files
> 12-Mar-2009 17:12:25 generated for <t> with
> <prefix>.
> 12-Mar-2009 17:12:25 -pkgTranslate <t> <pkg> When the type or module name
> <t> in encountered, replace
> 12-Mar-2009 17:12:25 it with <pkg> in the
> generated java package. Note that
> 12-Mar-2009 17:12:25 pkgPrefix changes are made
> first. <t> must match the
> 12-Mar-2009 17:12:25 full package name exactly.
> Also, <t> must not be
> 12-Mar-2009 17:12:25 org, org.omg, or any
> subpackage of org.omg.
> 12-Mar-2009 17:12:25 -skeletonName <xxx%yyy> Name the skeleton according
> to the pattern.
> 12-Mar-2009 17:12:25 The defaults are:
> 12-Mar-2009 17:12:25 %POA for the POA base class
> (-fserver or -fall)
> 12-Mar-2009 17:12:25 _%ImplBase for the
> oldImplBase base class
> 12-Mar-2009 17:12:25 (-oldImplBase and (-fserver
> or -fall)).
> 12-Mar-2009 17:12:25 -td <dir> use <dir> for the output
> directory instead of
> 12-Mar-2009 17:12:25 the current directory.
> 12-Mar-2009 17:12:25 -tieName <xxx%yyy> Name the tie according to the
> pattern. The defaults are:
> 12-Mar-2009 17:12:25 %POATie for the POA tie
> (-fserverTie or -fallTie)
> 12-Mar-2009 17:12:25 %_Tie for the oldImplBase tie
> 12-Mar-2009 17:12:25 (-oldImplBase and
> (-fserverTie or -fallTie)).
> 12-Mar-2009 17:12:25 -v, -verbose Verbose mode.
> 12-Mar-2009 17:12:25 -version Display the version number
> and quit.
> {code}
> using debug mode I see that the directory in the command line exists
> If I launch manually the same command it fails too
> If I modify the command to use relative paths instead of the absolute one it
> passes
> The problem seems to occurs because the root directory doesn't allow my
> account to write in it.
> When we use the absolute path, Java checks from the root directory if we can
> write and it fails.
--
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
