OpenVMS on Integrity latest version and patches.
And note:
I have already successfull built SQLJET and SVNKIT java libraries using
ant-1.7.0 under OpenVMS Itanium,
Now I want to build MAVEN-2.2.1 on OpenVMS from the tags / trunk sources
and I fail to execute the basic ANT build.xml process.
However, I know exactly how the basic bootstarp maven-2.2.1 build
process goes on
AND
I have built maven-x.x.x so many times successfully under Vista.
What can I do under OpenVMS with this ant build.xml script?
IA64>bash
bash$ export -p
declare -x CATALINA_BASE="/dkb3/apache/jakarta/tomcat"
declare -x CATALINA_HOME="/dkb3/apache/jakarta/tomcat"
declare -x HOME="/dkb3/stadelma"
declare -x HOSTTYPE="ia64"
declare -x JAVA_HOME="/jdk150/000000"
declare -x M2="/dkb3/apache-maven-2_2_1/bin"
declare -x M2_HOME="/dkb3/apache-maven-2_2_1"
declare -x M2_REPO="/dkb3/stadelma/.m2/"
declare -x OSTYPE="VMS"
declare -x
PATH="/dkb3/apache-maven-2_2_1:/dkb3/apache-maven-2_2_1/bin:/dkb3/stadel
ma:/bin:/gnu/bin:/GNU/BIN:/usr/bin:/usr/local/bin:."
declare -x SHELL="bash"
declare -x SHLVL="1"
declare -x TERM="vt102-132"
declare -x USER="STADELMA"
declare -x mvn="/dkb3/apache-maven-2_2_1/bin/mvn"
bash$ exit
exit
IA64>ant "-version"
Apache Ant version 1.7.0 compiled on February 22 2008
IA64> bash
bash$ ant -version
Unknown argument: -VERSION 1. Failure -VERSION is
returned in upper case. As such unknown! Why?
ant [options] [target [target2 [target3] ...]]
Options:
-help, -h print this message
-projecthelp, -p print project help information
-version print the version information and exit
-diagnostics print information that might be helpful to
diagnose or report problems.
-quiet, -q be extra quiet
-verbose, -v be extra verbose
-debug, -d print debugging information
-emacs, -e produce logging information without adornments
-lib <path> specifies a path to search for jars and classes
-logfile <file> use given file for log
-l <file> ''
-logger <classname> the class which is to perform logging
-listener <classname> add an instance of class as a project listener
-noinput do not allow interactive input
-buildfile <file> use given buildfile
-file <file> ''
-f <file> ''
-D<property>=<value> use value for given property
-keep-going, -k execute all targets that do not depend
on failed target(s)
-propertyfile <name> load all properties from file with -D
properties taking precedence
-inputhandler <class> the class which will handle input requests
-find <file> (s)earch for buildfile towards the root of
-s <file> the filesystem and use it
-nice number A niceness value for the main thread:
1 (lowest) to 10 (highest); 5 is the default
-nouserlib Run ant without using the jar files from
${user.home}/.ant/lib
-noclasspath Run ant without using CLASSPATH
-autoproxy Java1.5+: use the OS proxy settings
-main <class> override Ant's normal entry point
bash$
bash$ ant "-version"
Unknown argument: -VERSION 2. Failur: doubble quotes are
just eaten up
ant [options] [target [target2 [target3] ...]]
Options:
-help, -h print this message
-projecthelp, -p print project help information
-version print the version information and exit
-diagnostics print information that might be helpful to
diagnose or report problems.
-quiet, -q be extra quiet
-verbose, -v be extra verbose
-debug, -d print debugging information
-emacs, -e produce logging information without adornments
-lib <path> specifies a path to search for jars and classes
-logfile <file> use given file for log
-l <file> ''
-logger <classname> the class which is to perform logging
-listener <classname> add an instance of class as a project listener
-noinput do not allow interactive input
-buildfile <file> use given buildfile
-file <file> ''
-f <file> ''
-D<property>=<value> use value for given property
-keep-going, -k execute all targets that do not depend
on failed target(s)
-propertyfile <name> load all properties from file with -D
properties taking precedence
-inputhandler <class> the class which will handle input requests
-find <file> (s)earch for buildfile towards the root of
-s <file> the filesystem and use it
-nice number A niceness value for the main thread:
1 (lowest) to 10 (highest); 5 is the default
-nouserlib Run ant without using the jar files from
${user.home}/.ant/lib
-noclasspath Run ant without using CLASSPATH
-autoproxy Java1.5+: use the OS proxy settings
-main <class> override Ant's normal entry point
bash$
why do these these OpenVMS logicals not have effect on the case under
BASH?
"DECC$ARGV_PARSE_STYLE" = "enabel"
"DECC$EFS_CASE_PRESERVE" = "true"
"DECC$EFS_CASE_SPECIAL" = "true"
"DECC$EFS_CHARSET" = "true"
"DECC$FD_LOCKING" = "1"
Later on ....
IA64>ant "-f build.xml" "all" 4a. ANT gets File
build.xml and should build the "all" target
Buildfile: build.xml
clean-bootstrap:
initTaskDefs: 4b. maybe he likes to go
to the network and faisl on our proxy server firewall
[typedef] Could not load definitions from resource
org/apache/maven/artifact/ant/antlib.xml. It could not be found.
isMavenHomeSet:
BUILD FAILED 4c. what shal take place
here? Network access? If yes then I know why it failse here.
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/build.xml:55: You must set
the M2_HOME environment variable or specify a maven.home pro
perty to this Ant script
Total time: 10 seconds
IA64> 5. I have
M2_HOME and M2 defined as system logicals
IA64>show log M2_HOME
"M2_HOME" = "DKB3:[apache-maven-2_2_1]" (LNM$SYSTEM_TABLE)
IA64>
IA64>define M2_HOME "/dkb3/apache-maven-2_2_1" 5a. lets define it as
unix path and try again
IA64>ant "-f build.xml" "all"
Buildfile: build.xml
clean-bootstrap:
initTaskDefs:
[typedef] Could not load definitions from resource
org/apache/maven/artifact/ant/antlib.xml. It could not be found.
isMavenHomeSet:
BUILD FAILED
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/build.xml:55: You must set
the M2_HOME environment variable or specify a maven.home pro
perty to this Ant script
6. no lucke.
M2_HOME is exported by Bash and is set as system logical
Total time: 21 seconds lets pass maven.home as
property to the script
IA64>
IA64>ant "-Dmaven.home=/dkb3/apache-maven-2_2_1" "-f build.xml" "all"
Buildfile: build.xml
clean-bootstrap:
initTaskDefs:
[typedef] Could not load definitions from resource
org/apache/maven/artifact/ant/antlib.xml. It could not be found.
isMavenHomeSet: 7. OK now -lets see how
far we go ..
[echo] Using Maven home at: /dkb3/apache-maven-2_2_1
initLocalRepo: 8. OK too
[echo] Using the local repository at: /dkb3/stadelma/.m2/repository
init:
[echo] maven.home = /dkb3/apache-maven-2_2_1 9. OK
[echo] maven.assembly =
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/apache-maven/target/apache-
maven-2.2.1-bin.zip
read-poms:
BUILD FAILED 10. Guess what is not
working, maybe a network access
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/build.xml:72: Problem:
failed to create task or type urn:maven-artifact-ant:pom
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken
place.
Total time: 12 seconds
Now I can go on for a few more ant-targets defining pom.version and
skip.pull as properties for build.xml. But that is not how we shall
work. Somewhere ant atempts to upgrade the repository with artifacts
from the network, from an external repository, and that is why maven and
ant must operate properly using a proper Proxy Server Login to pass our
company firewall; and the proxy login shall not only provide for basic
authentication but must support authentication schemas like digfest,
ntlm, ntlmssp or better negotiate.
Now here is where the story building maven-2.2.1 on OpenVMS using ant
1.7 stops. To many issues. ANT under BASH would potentially help on some
spots to be able to go further, but that is just guessing unless the
basic problems with "double-quotes" or case sensitivity is fixed within
BASH. The best UNIX for sure - because it runs under VMS :-)
IA64>ant "-Dmaven.home=/dkb3/apache-maven-2_2_1" "-Dpom.version=2.2.1"
"-Dskip.pull=true" "all"
Buildfile: build.xml
clean-bootstrap:
initTaskDefs:
[typedef] Could not load definitions from resource
org/apache/maven/artifact/ant/antlib.xml. It could not be found.
isMavenHomeSet:
[echo] Using Maven home at: /dkb3/apache-maven-2_2_1
initLocalRepo:
[echo] Using the local repository at: /dkb3/stadelma/.m2/repository
init:
[echo] maven.home = /dkb3/apache-maven-2_2_1
[echo] maven.assembly =
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/apache-maven/target/apache-
maven-2.2.1-bin.
zip
read-poms:
pull:
generate-sources:
[mkdir] Created dir:
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/bootstrap/target
[mkdir] Created dir:
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/bootstrap/target/generated-
sources
[modello] Generating sources for maven-model/src/main/mdo/maven.mdo
BUILD FAILED
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/build.xml:147: The
following error occurred while executing this line:
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/build.xml:141: The
following error occurred while executing this line:
/dkb3/sw-projekte/asf/maven/tags/maven-2.2.1/build.xml:123: Reference
modello.pathid not found.
Total time: 15 seconds
IA64>
End of - it is for craying out ... :-(
mfG
Josef.Stadelmann@axa-winterthur.ch
(alias Sepp)