You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by John Sisson <jr...@gmail.com> on 2006/04/04 16:30:38 UTC

Cannot build 1.1 on Windows - long file paths

I had issues relating to long file paths when building 1.1 from my 
C:\dev\asf\geronimo\branches\1.1 directory, so I tried building from a 
shorter directory ( C:\geronimo1.1 ) and still have issues (see below).

I haven't had a chance to look into this yet but I consider this to be a 
blocker.

Once we can build on windows we then need to test that Geronimo can be 
installed in common locations on windows (e.g. under C:\Program 
Files\Geronimo-1.1 ) without encountering file path length issues.

The following path (from the output below) is 317 bytes long:

C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class

See http://issues.apache.org/jira/browse/GERONIMO-1790 for more info on 
the long file path issue.

John

izpack:izpack-installer-build:
    [echo] IZPack installer build is running.
    [echo] IZPack Version is 3.8.0
    [java]
    [java] .::  IzPack - Version 3.8.0 ::.
    [java]
    [java] < compiler specifications version : 1.0 >
    [java]
    [java] - Copyright (C) 2001-2005 Julien Ponge
    [java] - Visit http://www.izforge.com/ for the latests releases
    [java] - Released under the terms of the Apache Software License 
version 2.0.
    [java]
    [java] -> Processing  : 
C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
    [java] -> Output      : 
C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-installer-1.1-SNAPSHOT.jar
    [java] -> Base path   : .
    [java] -> Kind        : standard
    [java] -> Compression : default
    [java] -> Compr. level: -1
    [java]
    [java] Adding resource: IzPack.uninstaller
    [java] Setting the installer information
    [java] Setting the GUI preferences
    [java] Adding langpack: eng
    [java] Adding resource: flag.eng
    [java] Adding resource: Installer.image
    [java] Adding resource: LicencePanel.licence
    [java] Adding resource: InfoPanel.info
    [java] Adding resource: userInputSpec.xml
    [java] Adding resource: ProcessPanel.Spec.xml
    [java] Adding resource: ImgPacksPanel.img.0
    [java] Adding resource: ImgPacksPanel.img.1
    [java] Adding resource: ImgPacksPanel.img.2
    [java] Adding resource: ImgPacksPanel.img.3
    [java] Adding resource: ImgPacksPanel.img.4
    [java] Adding resource: ImgPacksPanel.img.5
    [java] Adding resource: ImgPacksPanel.img.6
    [java] Adding resource: ImgPacksPanel.img.7
    [java] Adding resource: ImgPacksPanel.img.8
    [java] Adding resource: ImgPacksPanel.img.9
    [java] Adding resource: ImgPacksPanel.img.10
    [java] Adding resource: ImgPacksPanel.img.11
    [java] Adding resource: ImgPacksPanel.img.12
    [java] Adding resource: ImgPacksPanel.img.13
    [java] Adding resource: ImgPacksPanel.img.14
    [java] Adding resource: ImgPacksPanel.img.15
    [java] Adding resource: ImgPacksPanel.img.16
    [java] Adding resource: ImgPacksPanel.img.17
    [java] Adding resource: ImgPacksPanel.img.18
    [java] Adding resource: ImgPacksPanel.img.19
    [java] Adding resource: ImgPacksPanel.img.20
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
    [java] -> Fatal error :
    [java]    
C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: 
C:\geronimo1.1\assemblie
s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
hancerByCGLIB$$2ae63e1d.class
    [java] com.izforge.izpack.compiler.CompilerException: 
C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/gero
nimo-izpack.xml:96: 
C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\
1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\a
xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.parseError(CompilerConfig.java:1531)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:636)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:317)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.main(CompilerConfig.java:1847)
    [java]      at 
com.izforge.izpack.compiler.Compiler.main(Compiler.java:620)
    [java] Caused by: java.io.FileNotFoundException: 
C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronim
o-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
    [java]      at 
com.izforge.izpack.compiler.PackInfo.addFile(PackInfo.java:193)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:959)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:632)
    [java]      ... 3 more
    [java]
    [java] (tip : use -? to get the commmand line parameters)
    [java] [ERROR] Java Result: 1

BUILD FAILED
File...... C:\geronimo1.1\maven.xml
Element... maven:reactor
Line...... 63
Column.... -1
Unable to obtain goal [multiproject:install-callback] -- C:\Documents 
and Settings\sissonj\.geronimo-1.1.x-maven\cache\geronimo-izpa
ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning: Could not 
find file C:\geronimo1.1\assemblies\j2ee-installer\target\g
eronimo-installer-1.1-SNAPSHOT.jar to copy.
Total time   : 21 minutes 1 seconds
Finished at  : Tuesday, 4 April 2006 17:31:34



Re: Cannot build 1.1 on Windows - long file paths

Posted by Matt Hogstrom <ma...@hogstrom.org>.
Well, Windows does have some limites but 255 char file names is a bit onerous :-0

Jason Dillon wrote:
> Ugh... Why doesnt Microsoft fix this limitation in their whack filesystem?!
> 
> Sucks to have to muck up the build system to work around crazy windows problems. 
> 
> --jason
> 
> 
> -----Original Message-----
> From: John Sisson <jr...@gmail.com>
> Date: Wed, 05 Apr 2006 00:30:38 
> To:dev@geronimo.apache.org
> Subject: Cannot build 1.1 on Windows - long file paths
> 
> I had issues relating to long file paths when building 1.1 from my 
> C:\dev\asf\geronimo\branches\1.1 directory, so I tried building from a 
> shorter directory ( C:\geronimo1.1 ) and still have issues (see below).
> 
> I haven't had a chance to look into this yet but I consider this to be a 
> blocker.
> 
> Once we can build on windows we then need to test that Geronimo can be 
> installed in common locations on windows (e.g. under C:\Program 
> Files\Geronimo-1.1 ) without encountering file path length issues.
> 
> The following path (from the output below) is 317 bytes long:
> 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
> 
> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more info on 
> the long file path issue.
> 
> John
> 
> izpack:izpack-installer-build:
>     [echo] IZPack installer build is running.
>     [echo] IZPack Version is 3.8.0
>     [java]
>     [java] .::  IzPack - Version 3.8.0 ::.
>     [java]
>     [java] < compiler specifications version : 1.0 >
>     [java]
>     [java] - Copyright (C) 2001-2005 Julien Ponge
>     [java] - Visit http://www.izforge.com/ for the latests releases
>     [java] - Released under the terms of the Apache Software License 
> version 2.0.
>     [java]
>     [java] -> Processing  : 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>     [java] -> Output      : 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>     [java] -> Base path   : .
>     [java] -> Kind        : standard
>     [java] -> Compression : default
>     [java] -> Compr. level: -1
>     [java]
>     [java] Adding resource: IzPack.uninstaller
>     [java] Setting the installer information
>     [java] Setting the GUI preferences
>     [java] Adding langpack: eng
>     [java] Adding resource: flag.eng
>     [java] Adding resource: Installer.image
>     [java] Adding resource: LicencePanel.licence
>     [java] Adding resource: InfoPanel.info
>     [java] Adding resource: userInputSpec.xml
>     [java] Adding resource: ProcessPanel.Spec.xml
>     [java] Adding resource: ImgPacksPanel.img.0
>     [java] Adding resource: ImgPacksPanel.img.1
>     [java] Adding resource: ImgPacksPanel.img.2
>     [java] Adding resource: ImgPacksPanel.img.3
>     [java] Adding resource: ImgPacksPanel.img.4
>     [java] Adding resource: ImgPacksPanel.img.5
>     [java] Adding resource: ImgPacksPanel.img.6
>     [java] Adding resource: ImgPacksPanel.img.7
>     [java] Adding resource: ImgPacksPanel.img.8
>     [java] Adding resource: ImgPacksPanel.img.9
>     [java] Adding resource: ImgPacksPanel.img.10
>     [java] Adding resource: ImgPacksPanel.img.11
>     [java] Adding resource: ImgPacksPanel.img.12
>     [java] Adding resource: ImgPacksPanel.img.13
>     [java] Adding resource: ImgPacksPanel.img.14
>     [java] Adding resource: ImgPacksPanel.img.15
>     [java] Adding resource: ImgPacksPanel.img.16
>     [java] Adding resource: ImgPacksPanel.img.17
>     [java] Adding resource: ImgPacksPanel.img.18
>     [java] Adding resource: ImgPacksPanel.img.19
>     [java] Adding resource: ImgPacksPanel.img.20
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>     [java] -> Fatal error :
>     [java]    
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: 
> C:\geronimo1.1\assemblie
> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
> hancerByCGLIB$$2ae63e1d.class
>     [java] com.izforge.izpack.compiler.CompilerException: 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/gero
> nimo-izpack.xml:96: 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\
> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\a
> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.parseError(CompilerConfig.java:1531)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:636)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:317)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.main(CompilerConfig.java:1847)
>     [java]      at 
> com.izforge.izpack.compiler.Compiler.main(Compiler.java:620)
>     [java] Caused by: java.io.FileNotFoundException: 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronim
> o-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>     [java]      at 
> com.izforge.izpack.compiler.PackInfo.addFile(PackInfo.java:193)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:959)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:632)
>     [java]      ... 3 more
>     [java]
>     [java] (tip : use -? to get the commmand line parameters)
>     [java] [ERROR] Java Result: 1
> 
> BUILD FAILED
> File...... C:\geronimo1.1\maven.xml
> Element... maven:reactor
> Line...... 63
> Column.... -1
> Unable to obtain goal [multiproject:install-callback] -- C:\Documents 
> and Settings\sissonj\.geronimo-1.1.x-maven\cache\geronimo-izpa
> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning: Could not 
> find file C:\geronimo1.1\assemblies\j2ee-installer\target\g
> eronimo-installer-1.1-SNAPSHOT.jar to copy.
> Total time   : 21 minutes 1 seconds
> Finished at  : Tuesday, 4 April 2006 17:31:34
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Matt Hogstrom <ma...@hogstrom.org>.
Your so optimistic ;-P

I'm betting that Microsoft fixes it.  Just none of your old apps will work.

Jason Dillon wrote:
> Oooh... Will the next version actually fix this?
> 
> I'm guessing No.
> 
> --jason
> 
> 
> -----Original Message-----
> From: Matt Hogstrom <ma...@hogstrom.org>
> Date: Tue, 04 Apr 2006 17:39:25 
> To:dev@geronimo.apache.org
> Subject: Re: Cannot build 1.1 on Windows - long file paths
> 
> And how else are they going to sell the next version :)
> 
> Jason Dillon wrote:
> 
>>Ugh... Why doesnt Microsoft fix this limitation in their whack filesystem?!
>>
>>Sucks to have to muck up the build system to work around crazy windows problems. 
>>
>>--jason
>>
>>
>>-----Original Message-----
>>From: John Sisson <jr...@gmail.com>
>>Date: Wed, 05 Apr 2006 00:30:38 
>>To:dev@geronimo.apache.org
>>Subject: Cannot build 1.1 on Windows - long file paths
>>
>>I had issues relating to long file paths when building 1.1 from my 
>>C:\dev\asf\geronimo\branches\1.1 directory, so I tried building from a 
>>shorter directory ( C:\geronimo1.1 ) and still have issues (see below).
>>
>>I haven't had a chance to look into this yet but I consider this to be a 
>>blocker.
>>
>>Once we can build on windows we then need to test that Geronimo can be 
>>installed in common locations on windows (e.g. under C:\Program 
>>Files\Geronimo-1.1 ) without encountering file path length issues.
>>
>>The following path (from the output below) is 317 bytes long:
>>
>>C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>
>>See http://issues.apache.org/jira/browse/GERONIMO-1790 for more info on 
>>the long file path issue.
>>
>>John
>>
>>izpack:izpack-installer-build:
>>    [echo] IZPack installer build is running.
>>    [echo] IZPack Version is 3.8.0
>>    [java]
>>    [java] .::  IzPack - Version 3.8.0 ::.
>>    [java]
>>    [java] < compiler specifications version : 1.0 >
>>    [java]
>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>    [java] - Released under the terms of the Apache Software License 
>>version 2.0.
>>    [java]
>>    [java] -> Processing  : 
>>C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>>    [java] -> Output      : 
>>C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>>    [java] -> Base path   : .
>>    [java] -> Kind        : standard
>>    [java] -> Compression : default
>>    [java] -> Compr. level: -1
>>    [java]
>>    [java] Adding resource: IzPack.uninstaller
>>    [java] Setting the installer information
>>    [java] Setting the GUI preferences
>>    [java] Adding langpack: eng
>>    [java] Adding resource: flag.eng
>>    [java] Adding resource: Installer.image
>>    [java] Adding resource: LicencePanel.licence
>>    [java] Adding resource: InfoPanel.info
>>    [java] Adding resource: userInputSpec.xml
>>    [java] Adding resource: ProcessPanel.Spec.xml
>>    [java] Adding resource: ImgPacksPanel.img.0
>>    [java] Adding resource: ImgPacksPanel.img.1
>>    [java] Adding resource: ImgPacksPanel.img.2
>>    [java] Adding resource: ImgPacksPanel.img.3
>>    [java] Adding resource: ImgPacksPanel.img.4
>>    [java] Adding resource: ImgPacksPanel.img.5
>>    [java] Adding resource: ImgPacksPanel.img.6
>>    [java] Adding resource: ImgPacksPanel.img.7
>>    [java] Adding resource: ImgPacksPanel.img.8
>>    [java] Adding resource: ImgPacksPanel.img.9
>>    [java] Adding resource: ImgPacksPanel.img.10
>>    [java] Adding resource: ImgPacksPanel.img.11
>>    [java] Adding resource: ImgPacksPanel.img.12
>>    [java] Adding resource: ImgPacksPanel.img.13
>>    [java] Adding resource: ImgPacksPanel.img.14
>>    [java] Adding resource: ImgPacksPanel.img.15
>>    [java] Adding resource: ImgPacksPanel.img.16
>>    [java] Adding resource: ImgPacksPanel.img.17
>>    [java] Adding resource: ImgPacksPanel.img.18
>>    [java] Adding resource: ImgPacksPanel.img.19
>>    [java] Adding resource: ImgPacksPanel.img.20
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>    [java] Adding content of jar: 
>>file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
>>one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>    [java] -> Fatal error :
>>    [java]    
>>C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: 
>>C:\geronimo1.1\assemblie
>>s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
>>HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
>>hancerByCGLIB$$2ae63e1d.class
>>    [java] com.izforge.izpack.compiler.CompilerException: 
>>C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/gero
>>nimo-izpack.xml:96: 
>>C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\
>>1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\a
>>xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.parseError(CompilerConfig.java:1531)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:636)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:317)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.main(CompilerConfig.java:1847)
>>    [java]      at 
>>com.izforge.izpack.compiler.Compiler.main(Compiler.java:620)
>>    [java] Caused by: java.io.FileNotFoundException: 
>>C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
>>y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronim
>>o-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>    [java]      at 
>>com.izforge.izpack.compiler.PackInfo.addFile(PackInfo.java:193)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:959)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>>    [java]      at 
>>com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:632)
>>    [java]      ... 3 more
>>    [java]
>>    [java] (tip : use -? to get the commmand line parameters)
>>    [java] [ERROR] Java Result: 1
>>
>>BUILD FAILED
>>File...... C:\geronimo1.1\maven.xml
>>Element... maven:reactor
>>Line...... 63
>>Column.... -1
>>Unable to obtain goal [multiproject:install-callback] -- C:\Documents 
>>and Settings\sissonj\.geronimo-1.1.x-maven\cache\geronimo-izpa
>>ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning: Could not 
>>find file C:\geronimo1.1\assemblies\j2ee-installer\target\g
>>eronimo-installer-1.1-SNAPSHOT.jar to copy.
>>Total time   : 21 minutes 1 seconds
>>Finished at  : Tuesday, 4 April 2006 17:31:34
>>
>>

Re: Cannot build 1.1 on Windows - long file paths

Posted by Jason Dillon <ja...@planet57.com>.
Oooh... Will the next version actually fix this?

I'm guessing No.

--jason


-----Original Message-----
From: Matt Hogstrom <ma...@hogstrom.org>
Date: Tue, 04 Apr 2006 17:39:25 
To:dev@geronimo.apache.org
Subject: Re: Cannot build 1.1 on Windows - long file paths

And how else are they going to sell the next version :)

Jason Dillon wrote:
> Ugh... Why doesnt Microsoft fix this limitation in their whack filesystem?!
> 
> Sucks to have to muck up the build system to work around crazy windows problems. 
> 
> --jason
> 
> 
> -----Original Message-----
> From: John Sisson <jr...@gmail.com>
> Date: Wed, 05 Apr 2006 00:30:38 
> To:dev@geronimo.apache.org
> Subject: Cannot build 1.1 on Windows - long file paths
> 
> I had issues relating to long file paths when building 1.1 from my 
> C:\dev\asf\geronimo\branches\1.1 directory, so I tried building from a 
> shorter directory ( C:\geronimo1.1 ) and still have issues (see below).
> 
> I haven't had a chance to look into this yet but I consider this to be a 
> blocker.
> 
> Once we can build on windows we then need to test that Geronimo can be 
> installed in common locations on windows (e.g. under C:\Program 
> Files\Geronimo-1.1 ) without encountering file path length issues.
> 
> The following path (from the output below) is 317 bytes long:
> 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
> 
> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more info on 
> the long file path issue.
> 
> John
> 
> izpack:izpack-installer-build:
>     [echo] IZPack installer build is running.
>     [echo] IZPack Version is 3.8.0
>     [java]
>     [java] .::  IzPack - Version 3.8.0 ::.
>     [java]
>     [java] < compiler specifications version : 1.0 >
>     [java]
>     [java] - Copyright (C) 2001-2005 Julien Ponge
>     [java] - Visit http://www.izforge.com/ for the latests releases
>     [java] - Released under the terms of the Apache Software License 
> version 2.0.
>     [java]
>     [java] -> Processing  : 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>     [java] -> Output      : 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>     [java] -> Base path   : .
>     [java] -> Kind        : standard
>     [java] -> Compression : default
>     [java] -> Compr. level: -1
>     [java]
>     [java] Adding resource: IzPack.uninstaller
>     [java] Setting the installer information
>     [java] Setting the GUI preferences
>     [java] Adding langpack: eng
>     [java] Adding resource: flag.eng
>     [java] Adding resource: Installer.image
>     [java] Adding resource: LicencePanel.licence
>     [java] Adding resource: InfoPanel.info
>     [java] Adding resource: userInputSpec.xml
>     [java] Adding resource: ProcessPanel.Spec.xml
>     [java] Adding resource: ImgPacksPanel.img.0
>     [java] Adding resource: ImgPacksPanel.img.1
>     [java] Adding resource: ImgPacksPanel.img.2
>     [java] Adding resource: ImgPacksPanel.img.3
>     [java] Adding resource: ImgPacksPanel.img.4
>     [java] Adding resource: ImgPacksPanel.img.5
>     [java] Adding resource: ImgPacksPanel.img.6
>     [java] Adding resource: ImgPacksPanel.img.7
>     [java] Adding resource: ImgPacksPanel.img.8
>     [java] Adding resource: ImgPacksPanel.img.9
>     [java] Adding resource: ImgPacksPanel.img.10
>     [java] Adding resource: ImgPacksPanel.img.11
>     [java] Adding resource: ImgPacksPanel.img.12
>     [java] Adding resource: ImgPacksPanel.img.13
>     [java] Adding resource: ImgPacksPanel.img.14
>     [java] Adding resource: ImgPacksPanel.img.15
>     [java] Adding resource: ImgPacksPanel.img.16
>     [java] Adding resource: ImgPacksPanel.img.17
>     [java] Adding resource: ImgPacksPanel.img.18
>     [java] Adding resource: ImgPacksPanel.img.19
>     [java] Adding resource: ImgPacksPanel.img.20
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>     [java] -> Fatal error :
>     [java]    
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: 
> C:\geronimo1.1\assemblie
> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
> hancerByCGLIB$$2ae63e1d.class
>     [java] com.izforge.izpack.compiler.CompilerException: 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/gero
> nimo-izpack.xml:96: 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\
> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\a
> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.parseError(CompilerConfig.java:1531)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:636)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:317)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.main(CompilerConfig.java:1847)
>     [java]      at 
> com.izforge.izpack.compiler.Compiler.main(Compiler.java:620)
>     [java] Caused by: java.io.FileNotFoundException: 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronim
> o-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>     [java]      at 
> com.izforge.izpack.compiler.PackInfo.addFile(PackInfo.java:193)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:959)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:632)
>     [java]      ... 3 more
>     [java]
>     [java] (tip : use -? to get the commmand line parameters)
>     [java] [ERROR] Java Result: 1
> 
> BUILD FAILED
> File...... C:\geronimo1.1\maven.xml
> Element... maven:reactor
> Line...... 63
> Column.... -1
> Unable to obtain goal [multiproject:install-callback] -- C:\Documents 
> and Settings\sissonj\.geronimo-1.1.x-maven\cache\geronimo-izpa
> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning: Could not 
> find file C:\geronimo1.1\assemblies\j2ee-installer\target\g
> eronimo-installer-1.1-SNAPSHOT.jar to copy.
> Total time   : 21 minutes 1 seconds
> Finished at  : Tuesday, 4 April 2006 17:31:34
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Matt Hogstrom <ma...@hogstrom.org>.
And how else are they going to sell the next version :)

Jason Dillon wrote:
> Ugh... Why doesnt Microsoft fix this limitation in their whack filesystem?!
> 
> Sucks to have to muck up the build system to work around crazy windows problems. 
> 
> --jason
> 
> 
> -----Original Message-----
> From: John Sisson <jr...@gmail.com>
> Date: Wed, 05 Apr 2006 00:30:38 
> To:dev@geronimo.apache.org
> Subject: Cannot build 1.1 on Windows - long file paths
> 
> I had issues relating to long file paths when building 1.1 from my 
> C:\dev\asf\geronimo\branches\1.1 directory, so I tried building from a 
> shorter directory ( C:\geronimo1.1 ) and still have issues (see below).
> 
> I haven't had a chance to look into this yet but I consider this to be a 
> blocker.
> 
> Once we can build on windows we then need to test that Geronimo can be 
> installed in common locations on windows (e.g. under C:\Program 
> Files\Geronimo-1.1 ) without encountering file path length issues.
> 
> The following path (from the output below) is 317 bytes long:
> 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
> 
> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more info on 
> the long file path issue.
> 
> John
> 
> izpack:izpack-installer-build:
>     [echo] IZPack installer build is running.
>     [echo] IZPack Version is 3.8.0
>     [java]
>     [java] .::  IzPack - Version 3.8.0 ::.
>     [java]
>     [java] < compiler specifications version : 1.0 >
>     [java]
>     [java] - Copyright (C) 2001-2005 Julien Ponge
>     [java] - Visit http://www.izforge.com/ for the latests releases
>     [java] - Released under the terms of the Apache Software License 
> version 2.0.
>     [java]
>     [java] -> Processing  : 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>     [java] -> Output      : 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>     [java] -> Base path   : .
>     [java] -> Kind        : standard
>     [java] -> Compression : default
>     [java] -> Compr. level: -1
>     [java]
>     [java] Adding resource: IzPack.uninstaller
>     [java] Setting the installer information
>     [java] Setting the GUI preferences
>     [java] Adding langpack: eng
>     [java] Adding resource: flag.eng
>     [java] Adding resource: Installer.image
>     [java] Adding resource: LicencePanel.licence
>     [java] Adding resource: InfoPanel.info
>     [java] Adding resource: userInputSpec.xml
>     [java] Adding resource: ProcessPanel.Spec.xml
>     [java] Adding resource: ImgPacksPanel.img.0
>     [java] Adding resource: ImgPacksPanel.img.1
>     [java] Adding resource: ImgPacksPanel.img.2
>     [java] Adding resource: ImgPacksPanel.img.3
>     [java] Adding resource: ImgPacksPanel.img.4
>     [java] Adding resource: ImgPacksPanel.img.5
>     [java] Adding resource: ImgPacksPanel.img.6
>     [java] Adding resource: ImgPacksPanel.img.7
>     [java] Adding resource: ImgPacksPanel.img.8
>     [java] Adding resource: ImgPacksPanel.img.9
>     [java] Adding resource: ImgPacksPanel.img.10
>     [java] Adding resource: ImgPacksPanel.img.11
>     [java] Adding resource: ImgPacksPanel.img.12
>     [java] Adding resource: ImgPacksPanel.img.13
>     [java] Adding resource: ImgPacksPanel.img.14
>     [java] Adding resource: ImgPacksPanel.img.15
>     [java] Adding resource: ImgPacksPanel.img.16
>     [java] Adding resource: ImgPacksPanel.img.17
>     [java] Adding resource: ImgPacksPanel.img.18
>     [java] Adding resource: ImgPacksPanel.img.19
>     [java] Adding resource: ImgPacksPanel.img.20
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>     [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>     [java] -> Fatal error :
>     [java]    
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: 
> C:\geronimo1.1\assemblie
> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
> hancerByCGLIB$$2ae63e1d.class
>     [java] com.izforge.izpack.compiler.CompilerException: 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/gero
> nimo-izpack.xml:96: 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\
> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\a
> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.parseError(CompilerConfig.java:1531)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:636)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:317)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.main(CompilerConfig.java:1847)
>     [java]      at 
> com.izforge.izpack.compiler.Compiler.main(Compiler.java:620)
>     [java] Caused by: java.io.FileNotFoundException: 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronim
> o-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>     [java]      at 
> com.izforge.izpack.compiler.PackInfo.addFile(PackInfo.java:193)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:959)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
>     [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:632)
>     [java]      ... 3 more
>     [java]
>     [java] (tip : use -? to get the commmand line parameters)
>     [java] [ERROR] Java Result: 1
> 
> BUILD FAILED
> File...... C:\geronimo1.1\maven.xml
> Element... maven:reactor
> Line...... 63
> Column.... -1
> Unable to obtain goal [multiproject:install-callback] -- C:\Documents 
> and Settings\sissonj\.geronimo-1.1.x-maven\cache\geronimo-izpa
> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning: Could not 
> find file C:\geronimo1.1\assemblies\j2ee-installer\target\g
> eronimo-installer-1.1-SNAPSHOT.jar to copy.
> Total time   : 21 minutes 1 seconds
> Finished at  : Tuesday, 4 April 2006 17:31:34
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Jason Dillon <ja...@planet57.com>.
Ugh... Why doesnt Microsoft fix this limitation in their whack filesystem?!

Sucks to have to muck up the build system to work around crazy windows problems. 

--jason


-----Original Message-----
From: John Sisson <jr...@gmail.com>
Date: Wed, 05 Apr 2006 00:30:38 
To:dev@geronimo.apache.org
Subject: Cannot build 1.1 on Windows - long file paths

I had issues relating to long file paths when building 1.1 from my 
C:\dev\asf\geronimo\branches\1.1 directory, so I tried building from a 
shorter directory ( C:\geronimo1.1 ) and still have issues (see below).

I haven't had a chance to look into this yet but I consider this to be a 
blocker.

Once we can build on windows we then need to test that Geronimo can be 
installed in common locations on windows (e.g. under C:\Program 
Files\Geronimo-1.1 ) without encountering file path length issues.

The following path (from the output below) is 317 bytes long:

C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class

See http://issues.apache.org/jira/browse/GERONIMO-1790 for more info on 
the long file path issue.

John

izpack:izpack-installer-build:
    [echo] IZPack installer build is running.
    [echo] IZPack Version is 3.8.0
    [java]
    [java] .::  IzPack - Version 3.8.0 ::.
    [java]
    [java] < compiler specifications version : 1.0 >
    [java]
    [java] - Copyright (C) 2001-2005 Julien Ponge
    [java] - Visit http://www.izforge.com/ for the latests releases
    [java] - Released under the terms of the Apache Software License 
version 2.0.
    [java]
    [java] -> Processing  : 
C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
    [java] -> Output      : 
C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-installer-1.1-SNAPSHOT.jar
    [java] -> Base path   : .
    [java] -> Kind        : standard
    [java] -> Compression : default
    [java] -> Compr. level: -1
    [java]
    [java] Adding resource: IzPack.uninstaller
    [java] Setting the installer information
    [java] Setting the GUI preferences
    [java] Adding langpack: eng
    [java] Adding resource: flag.eng
    [java] Adding resource: Installer.image
    [java] Adding resource: LicencePanel.licence
    [java] Adding resource: InfoPanel.info
    [java] Adding resource: userInputSpec.xml
    [java] Adding resource: ProcessPanel.Spec.xml
    [java] Adding resource: ImgPacksPanel.img.0
    [java] Adding resource: ImgPacksPanel.img.1
    [java] Adding resource: ImgPacksPanel.img.2
    [java] Adding resource: ImgPacksPanel.img.3
    [java] Adding resource: ImgPacksPanel.img.4
    [java] Adding resource: ImgPacksPanel.img.5
    [java] Adding resource: ImgPacksPanel.img.6
    [java] Adding resource: ImgPacksPanel.img.7
    [java] Adding resource: ImgPacksPanel.img.8
    [java] Adding resource: ImgPacksPanel.img.9
    [java] Adding resource: ImgPacksPanel.img.10
    [java] Adding resource: ImgPacksPanel.img.11
    [java] Adding resource: ImgPacksPanel.img.12
    [java] Adding resource: ImgPacksPanel.img.13
    [java] Adding resource: ImgPacksPanel.img.14
    [java] Adding resource: ImgPacksPanel.img.15
    [java] Adding resource: ImgPacksPanel.img.16
    [java] Adding resource: ImgPacksPanel.img.17
    [java] Adding resource: ImgPacksPanel.img.18
    [java] Adding resource: ImgPacksPanel.img.19
    [java] Adding resource: ImgPacksPanel.img.20
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
    [java] Adding content of jar: 
file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal
one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
    [java] -> Fatal error :
    [java]    
C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: 
C:\geronimo1.1\assemblie
s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
hancerByCGLIB$$2ae63e1d.class
    [java] com.izforge.izpack.compiler.CompilerException: 
C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/gero
nimo-izpack.xml:96: 
C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\
1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\a
xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.parseError(CompilerConfig.java:1531)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:636)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:317)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.main(CompilerConfig.java:1847)
    [java]      at 
com.izforge.izpack.compiler.Compiler.main(Compiler.java:620)
    [java] Caused by: java.io.FileNotFoundException: 
C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronim
o-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
    [java]      at 
com.izforge.izpack.compiler.PackInfo.addFile(PackInfo.java:193)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:959)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969)
    [java]      at 
com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:632)
    [java]      ... 3 more
    [java]
    [java] (tip : use -? to get the commmand line parameters)
    [java] [ERROR] Java Result: 1

BUILD FAILED
File...... C:\geronimo1.1\maven.xml
Element... maven:reactor
Line...... 63
Column.... -1
Unable to obtain goal [multiproject:install-callback] -- C:\Documents 
and Settings\sissonj\.geronimo-1.1.x-maven\cache\geronimo-izpa
ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning: Could not 
find file C:\geronimo1.1\assemblies\j2ee-installer\target\g
eronimo-installer-1.1-SNAPSHOT.jar to copy.
Total time   : 21 minutes 1 seconds
Finished at  : Tuesday, 4 April 2006 17:31:34



Re: Cannot build 1.1 on Windows - long file paths

Posted by Dave Colasurdo <da...@earthlink.net>.
I tried with:

winzip - indicates an unzip error
infozip  - no error but omits the offending files
jar -xvf - gets the following exception

java.io.FileNotFoundException: 
geronimo-1.1-SNAPSHOT\repository\geronimo\daytrad
er-derby-tomcat\1.1-SNAPSHOT\daytrader-derby-tomcat-1.1-SNAPSHOT.car\daytrader-w
eb-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\
GenericServiceEndpointWrapper$$EnhancerByCGLIB$$6a6aebe.class (The 
system cannot
  find the path specified)
         at java.io.FileOutputStream.open(Native Method)
         at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
         at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
         at sun.tools.jar.Main.extractFile(Main.java:712)
         at sun.tools.jar.Main.extract(Main.java:678)
         at sun.tools.jar.Main.run(Main.java:190)
         at sun.tools.jar.Main.main(Main.java:904)

The problem isn't with the unzip program.. The problem is that the 
images have files with path lengths that exceed the current limit of 256 
for the windows platform..

-Dave-




Dain Sundstrom wrote:
> What if you unpack with jar -xf?
> 
> -dain
> 
> On Apr 6, 2006, at 1:07 PM, Dave Colasurdo wrote:
> 
>> The "long file path" problem on the windows platform isn't limited to 
>> building G1.1 on this platform.  The current images are incompatible 
>> with windows even when the images are generated on a different platform..
>>
>> Specifically, I built G1.1 on linux and then FTP'd the generated 
>> windows image (geronimo-tomcat-j2ee-1.1-SNAPSHOT.zip) to a windows 
>> machine..
>>
>> The resulting image can't unzip on the windows platform due to the 
>> path length problem.. :(
>>
>> e.g. 
>> C:\z\geronimo-1.1-SNAPSHOT\repository\geronimo\webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class 
>>
>>
>> Guess this is obvious in hindsight, though was thinking it was 
>> strictly a build issue..
>>
>> This absolutely needs to get fixed..
>>
>> -Dave-
>>
>>
>> Joe Bohn wrote:
>>> You beat me to it John .... I'm hitting the exact same problem.
>>> Joe
>>> John Sisson wrote:
>>>> I had issues relating to long file paths when building 1.1 from my 
>>>> C:\dev\asf\geronimo\branches\1.1 directory, so I tried building from 
>>>> a shorter directory ( C:\geronimo1.1 ) and still have issues (see 
>>>> below).
>>>>
>>>> I haven't had a chance to look into this yet but I consider this to 
>>>> be a blocker.
>>>>
>>>> Once we can build on windows we then need to test that Geronimo can 
>>>> be installed in common locations on windows (e.g. under C:\Program 
>>>> Files\Geronimo-1.1 ) without encountering file path length issues.
>>>>
>>>> The following path (from the output below) is 317 bytes long:
>>>>
>>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class 
>>>>
>>>>
>>>> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more info 
>>>> on the long file path issue.
>>>>
>>>> John
>>>>
>>>> izpack:izpack-installer-build:
>>>>    [echo] IZPack installer build is running.
>>>>    [echo] IZPack Version is 3.8.0
>>>>    [java]
>>>>    [java] .::  IzPack - Version 3.8.0 ::.
>>>>    [java]
>>>>    [java] < compiler specifications version : 1.0 >
>>>>    [java]
>>>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>>>    [java] - Released under the terms of the Apache Software License 
>>>> version 2.0.
>>>>    [java]
>>>>    [java] -> Processing  : 
>>>> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml 
>>>>
>>>>    [java] -> Output      : 
>>>> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-installer-1.1-SNAPSHOT.jar 
>>>>
>>>>    [java] -> Base path   : .
>>>>    [java] -> Kind        : standard
>>>>    [java] -> Compression : default
>>>>    [java] -> Compr. level: -1
>>>>    [java]
>>>>    [java] Adding resource: IzPack.uninstaller
>>>>    [java] Setting the installer information
>>>>    [java] Setting the GUI preferences
>>>>    [java] Adding langpack: eng
>>>>    [java] Adding resource: flag.eng
>>>>    [java] Adding resource: Installer.image
>>>>    [java] Adding resource: LicencePanel.licence
>>>>    [java] Adding resource: InfoPanel.info
>>>>    [java] Adding resource: userInputSpec.xml
>>>>    [java] Adding resource: ProcessPanel.Spec.xml
>>>>    [java] Adding resource: ImgPacksPanel.img.0
>>>>    [java] Adding resource: ImgPacksPanel.img.1
>>>>    [java] Adding resource: ImgPacksPanel.img.2
>>>>    [java] Adding resource: ImgPacksPanel.img.3
>>>>    [java] Adding resource: ImgPacksPanel.img.4
>>>>    [java] Adding resource: ImgPacksPanel.img.5
>>>>    [java] Adding resource: ImgPacksPanel.img.6
>>>>    [java] Adding resource: ImgPacksPanel.img.7
>>>>    [java] Adding resource: ImgPacksPanel.img.8
>>>>    [java] Adding resource: ImgPacksPanel.img.9
>>>>    [java] Adding resource: ImgPacksPanel.img.10
>>>>    [java] Adding resource: ImgPacksPanel.img.11
>>>>    [java] Adding resource: ImgPacksPanel.img.12
>>>>    [java] Adding resource: ImgPacksPanel.img.13
>>>>    [java] Adding resource: ImgPacksPanel.img.14
>>>>    [java] Adding resource: ImgPacksPanel.img.15
>>>>    [java] Adding resource: ImgPacksPanel.img.16
>>>>    [java] Adding resource: ImgPacksPanel.img.17
>>>>    [java] Adding resource: ImgPacksPanel.img.18
>>>>    [java] Adding resource: ImgPacksPanel.img.19
>>>>    [java] Adding resource: ImgPacksPanel.img.20
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>>>    [java] Adding content of jar: 
>>>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>>>
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>>>    [java] -> Fatal error :
>>>>    [java]    
>>>> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: 
>>>> C:\geronimo1.1\assemblie
>>>> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS 
>>>>
>>>> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En 
>>>>
>>>> hancerByCGLIB$$2ae63e1d.class
>>>>    [java] com.izforge.izpack.compiler.CompilerException: 
>>>> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/gero 
>>>>
>>>> nimo-izpack.xml:96: 
>>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\ 
>>>>
>>>> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\a 
>>>>
>>>> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.parseError(CompilerConfig.java:1531) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:636) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:317) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.main(CompilerConfig.java:1847) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.Compiler.main(Compiler.java:620)
>>>>    [java] Caused by: java.io.FileNotFoundException: 
>>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor 
>>>>
>>>> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronim 
>>>>
>>>> o-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.PackInfo.addFile(PackInfo.java:193)
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:959) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>>>
>>>>    [java]      at 
>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:632) 
>>>>
>>>>    [java]      ... 3 more
>>>>    [java]
>>>>    [java] (tip : use -? to get the commmand line parameters)
>>>>    [java] [ERROR] Java Result: 1
>>>>
>>>> BUILD FAILED
>>>> File...... C:\geronimo1.1\maven.xml
>>>> Element... maven:reactor
>>>> Line...... 63
>>>> Column.... -1
>>>> Unable to obtain goal [multiproject:install-callback] -- 
>>>> C:\Documents and 
>>>> Settings\sissonj\.geronimo-1.1.x-maven\cache\geronimo-izpa
>>>> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning: Could 
>>>> not find file C:\geronimo1.1\assemblies\j2ee-installer\target\g
>>>> eronimo-installer-1.1-SNAPSHOT.jar to copy.
>>>> Total time   : 21 minutes 1 seconds
>>>> Finished at  : Tuesday, 4 April 2006 17:31:34
>>>>
>>>>
>>>>
>>>>
> 
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Hernan Cunico <hc...@gmail.com>.
Hi Matt,
so far I have not found a way in windows to recursively "list" all directories and files with the 
alternate short name.   dir /X /s will not shrink recursively directory names

As for keeping the CARs JARed, I guess that will hide temporarily the problem. Windows still will 
need to get to those files, right. Isn't this the same issue Dave C is having? Isn't the application 
ruled by the OS limitations? if not, then using JARs instead may be an option.

Cheers!
Hernan

Matt Hogstrom wrote:
> So the file that is in Dave's example is 268 characters long.  Here are 
> a couple of questions that perhaps the folks using Windows can answer.
> 
> 1. What about long-name support in Windows.  I thought MS had some way 
> to shorten names...probably a Long Shot...but thought I'd try.
> 
> 2. Can we leave CARs JARed up?  I think this may be the only way to get 
> past the problem.
> 
> 3. The Maven jar naming convention is dramatically increasing the length 
> of the file name.  The groupId and artifacts are repeated as is the 
> version number.  For instance this takes up a lot of the realestate:
> 
> So this:
> \geronimo\webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class 
> 
> 
> becomes:
> \geronimo\10\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class 
> 
> 
> and we have an entrie like this in an index.properties:
> 10=webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\ 
> 
> 
> This would save 109 characters in the path name.
> 
> No matter what this is going to be a bit ugly.
> 
> Thoughts?
> 
> 
> Hernan Cunico wrote:
> 
>> I am having basically the same issue building directly on Windows. 
>> When the build gets to the izpack section it fails. I check the 
>> assemblies\j2ee-installer\target directory and it cascades 
>> recursively, in fact I am not able to delete that directory (yet).
>>
>> Any subsequent build attempts will also fail since maven will fail to 
>> delete the target directory.
>>
>> Cheers!
>> Hernan
>>
>> Dain Sundstrom wrote:
>>
>>> What if you unpack with jar -xf?
>>>
>>> -dain
>>>
>>> On Apr 6, 2006, at 1:07 PM, Dave Colasurdo wrote:
>>>
>>>> The "long file path" problem on the windows platform isn't limited  
>>>> to building G1.1 on this platform.  The current images are  
>>>> incompatible with windows even when the images are generated on a  
>>>> different platform..
>>>>
>>>> Specifically, I built G1.1 on linux and then FTP'd the generated  
>>>> windows image (geronimo-tomcat-j2ee-1.1-SNAPSHOT.zip) to a windows  
>>>> machine..
>>>>
>>>> The resulting image can't unzip on the windows platform due to the  
>>>> path length problem.. :(
>>>>
>>>> e.g. C:\z\geronimo-1.1-SNAPSHOT\repository\geronimo\webconsole- 
>>>> tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo- 
>>>> console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache 
>>>> \geronimo\console\securitymanager\realm\SecurityRealmPortlet 
>>>> $ExistingRealm.class
>>>>
>>>> Guess this is obvious in hindsight, though was thinking it was  
>>>> strictly a build issue..
>>>>
>>>> This absolutely needs to get fixed..
>>>>
>>>> -Dave-
>>>>
>>>>
>>>> Joe Bohn wrote:
>>>>
>>>>> You beat me to it John .... I'm hitting the exact same problem.
>>>>> Joe
>>>>> John Sisson wrote:
>>>>>
>>>>>> I had issues relating to long file paths when building 1.1 from  
>>>>>> my C:\dev\asf\geronimo\branches\1.1 directory, so I tried  
>>>>>> building from a shorter directory ( C:\geronimo1.1 ) and still  
>>>>>> have issues (see below).
>>>>>>
>>>>>> I haven't had a chance to look into this yet but I consider this  
>>>>>> to be a blocker.
>>>>>>
>>>>>> Once we can build on windows we then need to test that Geronimo  
>>>>>> can be installed in common locations on windows (e.g. under C: 
>>>>>> \Program Files\Geronimo-1.1 ) without encountering file path  
>>>>>> length issues.
>>>>>>
>>>>>> The following path (from the output below) is 317 bytes long:
>>>>>>
>>>>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1- 
>>>>>> SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT 
>>>>>> \daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1- 
>>>>>> SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis 
>>>>>> \client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>>> $2ae63e1d.class
>>>>>>
>>>>>> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more  
>>>>>> info on the long file path issue.
>>>>>>
>>>>>> John
>>>>>>
>>>>>> izpack:izpack-installer-build:
>>>>>>    [echo] IZPack installer build is running.
>>>>>>    [echo] IZPack Version is 3.8.0
>>>>>>    [java]
>>>>>>    [java] .::  IzPack - Version 3.8.0 ::.
>>>>>>    [java]
>>>>>>    [java] < compiler specifications version : 1.0 >
>>>>>>    [java]
>>>>>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>>>>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>>>>>    [java] - Released under the terms of the Apache Software  
>>>>>> License version 2.0.
>>>>>>    [java]
>>>>>>    [java] -> Processing  : C:\geronimo1.1\assemblies\j2ee- 
>>>>>> installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>>>>>>    [java] -> Output      : C:\geronimo1.1\assemblies\j2ee- 
>>>>>> installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>>>>>>    [java] -> Base path   : .
>>>>>>    [java] -> Kind        : standard
>>>>>>    [java] -> Compression : default
>>>>>>    [java] -> Compr. level: -1
>>>>>>    [java]
>>>>>>    [java] Adding resource: IzPack.uninstaller
>>>>>>    [java] Setting the installer information
>>>>>>    [java] Setting the GUI preferences
>>>>>>    [java] Adding langpack: eng
>>>>>>    [java] Adding resource: flag.eng
>>>>>>    [java] Adding resource: Installer.image
>>>>>>    [java] Adding resource: LicencePanel.licence
>>>>>>    [java] Adding resource: InfoPanel.info
>>>>>>    [java] Adding resource: userInputSpec.xml
>>>>>>    [java] Adding resource: ProcessPanel.Spec.xml
>>>>>>    [java] Adding resource: ImgPacksPanel.img.0
>>>>>>    [java] Adding resource: ImgPacksPanel.img.1
>>>>>>    [java] Adding resource: ImgPacksPanel.img.2
>>>>>>    [java] Adding resource: ImgPacksPanel.img.3
>>>>>>    [java] Adding resource: ImgPacksPanel.img.4
>>>>>>    [java] Adding resource: ImgPacksPanel.img.5
>>>>>>    [java] Adding resource: ImgPacksPanel.img.6
>>>>>>    [java] Adding resource: ImgPacksPanel.img.7
>>>>>>    [java] Adding resource: ImgPacksPanel.img.8
>>>>>>    [java] Adding resource: ImgPacksPanel.img.9
>>>>>>    [java] Adding resource: ImgPacksPanel.img.10
>>>>>>    [java] Adding resource: ImgPacksPanel.img.11
>>>>>>    [java] Adding resource: ImgPacksPanel.img.12
>>>>>>    [java] Adding resource: ImgPacksPanel.img.13
>>>>>>    [java] Adding resource: ImgPacksPanel.img.14
>>>>>>    [java] Adding resource: ImgPacksPanel.img.15
>>>>>>    [java] Adding resource: ImgPacksPanel.img.16
>>>>>>    [java] Adding resource: ImgPacksPanel.img.17
>>>>>>    [java] Adding resource: ImgPacksPanel.img.18
>>>>>>    [java] Adding resource: ImgPacksPanel.img.19
>>>>>>    [java] Adding resource: ImgPacksPanel.img.20
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>>>>>    [java] -> Fatal error :
>>>>>>    [java]    C:\geronimo1.1\assemblies\j2ee-installer/target/ 
>>>>>> geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: C:\geronimo1.1 
>>>>>> \assemblie
>>>>>> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo 
>>>>>> \daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
>>>>>> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated 
>>>>>> \org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
>>>>>> hancerByCGLIB$$2ae63e1d.class
>>>>>>    [java] com.izforge.izpack.compiler.CompilerException: C: 
>>>>>> \geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1- 
>>>>>> SNAPSHOT/gero
>>>>>> nimo-izpack.xml:96: C:\geronimo1.1\assemblies\j2ee-installer 
>>>>>> \target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby- 
>>>>>> jetty\
>>>>>> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader- 
>>>>>> web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache 
>>>>>> \geronimo\a
>>>>>> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>>> $2ae63e1d.class
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.parseError 
>>>>>> (CompilerConfig.java:1531)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>>> (CompilerConfig.java:636)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.executeCompiler 
>>>>>> (CompilerConfig.java:317)
>>>>>>    [java]      at com.izforge.izpack.compiler.CompilerConfig.main 
>>>>>> (CompilerConfig.java:1847)
>>>>>>    [java]      at com.izforge.izpack.compiler.Compiler.main 
>>>>>> (Compiler.java:620)
>>>>>>    [java] Caused by: java.io.FileNotFoundException: C:\geronimo1.1 
>>>>>> \assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
>>>>>> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby- 
>>>>>> jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF 
>>>>>> \geronim
>>>>>> o-generated\org\apache\geronimo\axis\client 
>>>>>> \GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>>>>>    [java]      at com.izforge.izpack.compiler.PackInfo.addFile 
>>>>>> (PackInfo.java:193)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:959)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>>> (CompilerConfig.java:632)
>>>>>>    [java]      ... 3 more
>>>>>>    [java]
>>>>>>    [java] (tip : use -? to get the commmand line parameters)
>>>>>>    [java] [ERROR] Java Result: 1
>>>>>>
>>>>>> BUILD FAILED
>>>>>> File...... C:\geronimo1.1\maven.xml
>>>>>> Element... maven:reactor
>>>>>> Line...... 63
>>>>>> Column.... -1
>>>>>> Unable to obtain goal [multiproject:install-callback] -- C: 
>>>>>> \Documents and Settings\sissonj\.geronimo-1.1.x-maven\cache 
>>>>>> \geronimo-izpa
>>>>>> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning:  
>>>>>> Could not find file C:\geronimo1.1\assemblies\j2ee-installer 
>>>>>> \target\g
>>>>>> eronimo-installer-1.1-SNAPSHOT.jar to copy.
>>>>>> Total time   : 21 minutes 1 seconds
>>>>>> Finished at  : Tuesday, 4 April 2006 17:31:34
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>
>>>
>>
>>
>>
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Matt Hogstrom <ma...@hogstrom.org>.
I think this is a band-aid and addresses the current bhaviour and not the underlying problem. 
Perhaps this should be added to help people out.

Prasad Kashyap wrote:
> Now I have my project root at c:\apache and that was too deep for the
> files in the target dir to be deleted.
> 
> How about, IF the clean:clean goal fails, moving the dir to be deleted
> to say c:\tmp and then delete it from there ?
> 
> 
> Cheers
> Prasad.
> 
> 
> On 4/6/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
> 
>>I think we should be able to JAR up our generated stuff and that
>>should get around the problem for now.  There will be some limit for
>>user path lengths, but they don't have to use archive names like
>>org.apache.geronimo/artifact/1.0-SNAPSHOT.ear/org.apache.geronimo.artifact-1.0-SNAPSHOT.war/...
>>
>>Thanks,
>>    Aaron
>>
>>On 4/6/06, Dain Sundstrom <da...@iq80.com> wrote:
>>
>>>Man I hate Windows....
>>>
>>>Anyway, if you have a real OS and list the files in an assembly, you
>>>will see that the problem is caused by the combination of two
>>>changes: we now keep configurations in the repository and we unpack
>>>them. If you look closer you will see that the big offenders are
>>>unpacked ears and wars.
>>>
>>>I believe the following are the longest paths in the server:
>>>
>>>(270)
>>>geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/1.1-
>>>SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-web-1.1-
>>>SNAPSHOT.war/META-INF/geronimo-generated/org/apache/geronimo/axis/
>>>client/GenericServiceEndpointWrapper$$EnhancerByCGLIB$$36344d29.class
>>>(264)
>>>geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-
>>>SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-
>>>standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/console/
>>>databasemanager/wizard/DatabasePoolPortlet$ResourceAdapterParams.class
>>>
>>>
>>>One thing to note here is that the longest paths are all classes
>>>generated by Geronimo, nested classes in wars or compiled JSP pages.
>>>Someone should look into makeing maven jar the latter two and
>>>Geronimo should be creating jars when generating classes (actually we
>>>should stop generating classes a head of time but that is another
>>>story).
>>>
>>>
>>>
>>>Breaking down the longest path, we have:
>>>
>>>GeronimoName (22)
>>>   geronimo-1.1-SNAPSHOT
>>>RepositoryPath (55)
>>>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
>>>FileName (39)
>>>   daytrader-derby-jetty-1.1-SNAPSHOT.car
>>>NestedPath (154)
>>>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/
>>>apache/geronimo/axis/client/GenericServiceEndpointWrapper$
>>>$EnhancerByCGLIB$$36344d29.class
>>>
>>>
>>>
>>>The first thing to note is if we simply replace "SNAPSHOT" with "0",
>>>we drop 28 characters which makes the longest path 242; not enough
>>>head room.  Of course, when we switch our groupId to the maven
>>>standard org.apache.geronimo we eat up 20 more characters.  If we are
>>>going to unpack war files there is very little we can do about the
>>>NestedPath, so we have very few choices left.  If we simply combine
>>>combine ${GeronimoName}/${FileName}/${NestedPath} we are up to 115
>>>characters leaving only 41 characters for anything else, but when you
>>>add back the 28 from "SNAPSHOT", you get to a more comfortable level.
>>>
>>>I think if we combine this problem with Sachin's request for a
>>>separate directory for applications, we could do something like this:
>>>
>>>${GeronimoName}/apps/${FileName}/${NestedPath}
>>>
>>>There are several problems with this.  I think users will confuse the
>>>hot-deploy directory "deploy" with the "apps" directory [1].  Then
>>>again, if you look at the problem configurations they are all apps
>>>the users may want to remove (sample apps and the console), so may be
>>>we should just put these in the hot-deploy directory.  Another
>>>problem is that it will be much more difficult to query a repository
>>>without a directory structure.  The server will basically have to
>>>read the configuration from these apps on startup to determine what
>>>they are, so again we may just want to use the hot-deploy directory.
>>>I'm not a fan of the hot-deploy directory, but I'm not sure there is
>>>a better solution.
>>>
>>>Again I renew my hate of Windows...
>>>/me shakes his fist at Bill Gates
>>>
>>>-dain
>>>
>>>
>>>[1] As a side issue, I prefer the name "apps" because it will be most
>>>familiar to tomcat users.
>>>
>>>
>>>
>>
> 
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Prasad Kashyap <go...@gmail.com>.
Now I have my project root at c:\apache and that was too deep for the
files in the target dir to be deleted.

How about, IF the clean:clean goal fails, moving the dir to be deleted
to say c:\tmp and then delete it from there ?


Cheers
Prasad.


On 4/6/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
> I think we should be able to JAR up our generated stuff and that
> should get around the problem for now.  There will be some limit for
> user path lengths, but they don't have to use archive names like
> org.apache.geronimo/artifact/1.0-SNAPSHOT.ear/org.apache.geronimo.artifact-1.0-SNAPSHOT.war/...
>
> Thanks,
>     Aaron
>
> On 4/6/06, Dain Sundstrom <da...@iq80.com> wrote:
> > Man I hate Windows....
> >
> > Anyway, if you have a real OS and list the files in an assembly, you
> > will see that the problem is caused by the combination of two
> > changes: we now keep configurations in the repository and we unpack
> > them. If you look closer you will see that the big offenders are
> > unpacked ears and wars.
> >
> > I believe the following are the longest paths in the server:
> >
> > (270)
> > geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/1.1-
> > SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-web-1.1-
> > SNAPSHOT.war/META-INF/geronimo-generated/org/apache/geronimo/axis/
> > client/GenericServiceEndpointWrapper$$EnhancerByCGLIB$$36344d29.class
> > (264)
> > geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-
> > SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-
> > standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/console/
> > databasemanager/wizard/DatabasePoolPortlet$ResourceAdapterParams.class
> >
> >
> > One thing to note here is that the longest paths are all classes
> > generated by Geronimo, nested classes in wars or compiled JSP pages.
> > Someone should look into makeing maven jar the latter two and
> > Geronimo should be creating jars when generating classes (actually we
> > should stop generating classes a head of time but that is another
> > story).
> >
> >
> >
> > Breaking down the longest path, we have:
> >
> > GeronimoName (22)
> >    geronimo-1.1-SNAPSHOT
> > RepositoryPath (55)
> >    repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
> > FileName (39)
> >    daytrader-derby-jetty-1.1-SNAPSHOT.car
> > NestedPath (154)
> >    daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/
> > apache/geronimo/axis/client/GenericServiceEndpointWrapper$
> > $EnhancerByCGLIB$$36344d29.class
> >
> >
> >
> > The first thing to note is if we simply replace "SNAPSHOT" with "0",
> > we drop 28 characters which makes the longest path 242; not enough
> > head room.  Of course, when we switch our groupId to the maven
> > standard org.apache.geronimo we eat up 20 more characters.  If we are
> > going to unpack war files there is very little we can do about the
> > NestedPath, so we have very few choices left.  If we simply combine
> > combine ${GeronimoName}/${FileName}/${NestedPath} we are up to 115
> > characters leaving only 41 characters for anything else, but when you
> > add back the 28 from "SNAPSHOT", you get to a more comfortable level.
> >
> > I think if we combine this problem with Sachin's request for a
> > separate directory for applications, we could do something like this:
> >
> > ${GeronimoName}/apps/${FileName}/${NestedPath}
> >
> > There are several problems with this.  I think users will confuse the
> > hot-deploy directory "deploy" with the "apps" directory [1].  Then
> > again, if you look at the problem configurations they are all apps
> > the users may want to remove (sample apps and the console), so may be
> > we should just put these in the hot-deploy directory.  Another
> > problem is that it will be much more difficult to query a repository
> > without a directory structure.  The server will basically have to
> > read the configuration from these apps on startup to determine what
> > they are, so again we may just want to use the hot-deploy directory.
> > I'm not a fan of the hot-deploy directory, but I'm not sure there is
> > a better solution.
> >
> > Again I renew my hate of Windows...
> > /me shakes his fist at Bill Gates
> >
> > -dain
> >
> >
> > [1] As a side issue, I prefer the name "apps" because it will be most
> > familiar to tomcat users.
> >
> >
> >
>

Re: Cannot build 1.1 on Windows - long file paths

Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I think we should be able to JAR up our generated stuff and that
should get around the problem for now.  There will be some limit for
user path lengths, but they don't have to use archive names like
org.apache.geronimo/artifact/1.0-SNAPSHOT.ear/org.apache.geronimo.artifact-1.0-SNAPSHOT.war/...

Thanks,
    Aaron

On 4/6/06, Dain Sundstrom <da...@iq80.com> wrote:
> Man I hate Windows....
>
> Anyway, if you have a real OS and list the files in an assembly, you
> will see that the problem is caused by the combination of two
> changes: we now keep configurations in the repository and we unpack
> them. If you look closer you will see that the big offenders are
> unpacked ears and wars.
>
> I believe the following are the longest paths in the server:
>
> (270)
> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/1.1-
> SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-web-1.1-
> SNAPSHOT.war/META-INF/geronimo-generated/org/apache/geronimo/axis/
> client/GenericServiceEndpointWrapper$$EnhancerByCGLIB$$36344d29.class
> (264)
> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-
> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-
> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/console/
> databasemanager/wizard/DatabasePoolPortlet$ResourceAdapterParams.class
>
>
> One thing to note here is that the longest paths are all classes
> generated by Geronimo, nested classes in wars or compiled JSP pages.
> Someone should look into makeing maven jar the latter two and
> Geronimo should be creating jars when generating classes (actually we
> should stop generating classes a head of time but that is another
> story).
>
>
>
> Breaking down the longest path, we have:
>
> GeronimoName (22)
>    geronimo-1.1-SNAPSHOT
> RepositoryPath (55)
>    repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
> FileName (39)
>    daytrader-derby-jetty-1.1-SNAPSHOT.car
> NestedPath (154)
>    daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/
> apache/geronimo/axis/client/GenericServiceEndpointWrapper$
> $EnhancerByCGLIB$$36344d29.class
>
>
>
> The first thing to note is if we simply replace "SNAPSHOT" with "0",
> we drop 28 characters which makes the longest path 242; not enough
> head room.  Of course, when we switch our groupId to the maven
> standard org.apache.geronimo we eat up 20 more characters.  If we are
> going to unpack war files there is very little we can do about the
> NestedPath, so we have very few choices left.  If we simply combine
> combine ${GeronimoName}/${FileName}/${NestedPath} we are up to 115
> characters leaving only 41 characters for anything else, but when you
> add back the 28 from "SNAPSHOT", you get to a more comfortable level.
>
> I think if we combine this problem with Sachin's request for a
> separate directory for applications, we could do something like this:
>
> ${GeronimoName}/apps/${FileName}/${NestedPath}
>
> There are several problems with this.  I think users will confuse the
> hot-deploy directory "deploy" with the "apps" directory [1].  Then
> again, if you look at the problem configurations they are all apps
> the users may want to remove (sample apps and the console), so may be
> we should just put these in the hot-deploy directory.  Another
> problem is that it will be much more difficult to query a repository
> without a directory structure.  The server will basically have to
> read the configuration from these apps on startup to determine what
> they are, so again we may just want to use the hot-deploy directory.
> I'm not a fan of the hot-deploy directory, but I'm not sure there is
> a better solution.
>
> Again I renew my hate of Windows...
> /me shakes his fist at Bill Gates
>
> -dain
>
>
> [1] As a side issue, I prefer the name "apps" because it will be most
> familiar to tomcat users.
>
>
>

Re: Cannot build 1.1 on Windows - long file paths

Posted by Dave Colasurdo <da...@earthlink.net>.
I believe it's important to keep the CARs expanded as I suspect users 
(in development mode) would want the ability to easily update JSPs and 
classes without redeploying.  I also think Dain's suggestion to shrink 
the path length is the right approach..  Other comments below..

-Dave-

Dain Sundstrom wrote:
> Man I hate Windows....
> 
> Anyway, if you have a real OS and list the files in an assembly, you 
> will see that the problem is caused by the combination of two changes: 
> we now keep configurations in the repository and we unpack them. If you 
> look closer you will see that the big offenders are unpacked ears and wars.
> 
> I believe the following are the longest paths in the server:
> 
> (270)
> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/apache/geronimo/axis/client/GenericServiceEndpointWrapper$$EnhancerByCGLIB$$36344d29.class 
> 
> (264)
> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/console/databasemanager/wizard/DatabasePoolPortlet$ResourceAdapterParams.class 
> 
> 
> 
> One thing to note here is that the longest paths are all classes 
> generated by Geronimo, nested classes in wars or compiled JSP pages.  
> Someone should look into makeing maven jar the latter two and Geronimo 
> should be creating jars when generating classes (actually we should stop 
> generating classes a head of time but that is another story).
> 
> 
> 
> Breaking down the longest path, we have:
> 
> GeronimoName (22)
>   geronimo-1.1-SNAPSHOT
> RepositoryPath (55)
>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
> FileName (39)
>   daytrader-derby-jetty-1.1-SNAPSHOT.car
> NestedPath (154)
>   
> daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/apache/geronimo/axis/client/GenericServiceEndpointWrapper$$EnhancerByCGLIB$$36344d29.class 
> 
> 
> 
> 
> The first thing to note is if we simply replace "SNAPSHOT" with "0", we 
> drop 28 characters which makes the longest path 242; not enough head 
> room.  Of course, when we switch our groupId to the maven standard 
> org.apache.geronimo we eat up 20 more characters.  If we are going to 
> unpack war files there is very little we can do about the NestedPath, so 
> we have very few choices left.  If we simply combine combine 
> ${GeronimoName}/${FileName}/${NestedPath} we are up to 115 characters 
> leaving only 41 characters for anything else, but when you add back the 
> 28 from "SNAPSHOT", you get to a more comfortable level.
> 
> I think if we combine this problem with Sachin's request for a separate 
> directory for applications, we could do something like this:
> 
> ${GeronimoName}/apps/${FileName}/${NestedPath}
> 
Are you suggesting removing the RepositoryPath from the actual directory 
structure?  If this is technically possible, I like the approach as I 
think it keeps with the idea of "providing an intuitive structure that 
users would expect" as opposed to an "obfuscated structure that is 
dictated by the technology".

As has been suggested by others.. perhaps we have two unique directory 
paths:

${GeronimoName}/sys-apps/${FileName}/${NestedPath}
${GeronimoName}/apps/${FileName}/${NestedPath}

sys-apps - would contain all of the geronimo internal apps and 
configurations (uddi, webconsole, activemq, etc.)

apps - would contain the welcome app, samples and end user applications


> There are several problems with this.  I think users will confuse the 
> hot-deploy directory "deploy" with the "apps" directory [1].  Then 

We can rename the deploy directory to hot-deploy for clarity..

> again, if you look at the problem configurations they are all apps the 
> users may want to remove (sample apps and the console), so may be we

Users can freely undeploy any of the apps in the apps directory.. This 
would be documented as a common thing to do.

Undeploying apps in the sys-apps directory is less common and while it 
is supported we document that this should only be done when users really 
know what they are doing.


> should just put these in the hot-deploy directory.  Another problem is 
> that it will be much more difficult to query a repository without a 
> directory structure.  The server will basically have to read the 
> configuration from these apps on startup to determine what they are, so 
> again we may just want to use the hot-deploy directory.  I'm not a fan 
> of the hot-deploy directory, but I'm not sure there is a better solution.
> 
> Again I renew my hate of Windows...
> /me shakes his fist at Bill Gates
> 
> -dain
> 
> 
> [1] As a side issue, I prefer the name "apps" because it will be most 
> familiar to tomcat users.
> 
> 
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Hernan Cunico <hc...@gmail.com>.
Hi All,
I agree with Matt, we need to find a common ground, something in between the very short, number 
based structure (and BTW not too meaningful) we had in the config-store and the "unnecessary" long 
directory structure and file names that we are having now.

Independently of the Windows limitation for handling long names, I personally think that having a 
structure as long (that potentially will keep growing) is unnecessary. What is the benefit of such a 
'very' verbose naming?  Sooner or later is going to become unpractical to browse through such a 
complex structure no matter what OS you are using.

Matt's alternative going back to the config-store sounds good (I would also suggest to limit the 
configId to a max number of chars) but we will still be facing the application naming area (222...). 
This is the are we have less control and, IMHO, where we should focus on.

Cheers!
Hernan

Matt Hogstrom wrote:
> Thinking about this some more I believe we need to make a good decision 
> here as having to revisit this issue in the future will cause users to 
> have to change how the server works.  I've been talking to a new user 
> that has a larger server farm and is very interested in the Geronimo 
> server as their new foundation.  However, they run a few thousand 
> servers and are VERY sensitive to changes in the behaviour of the server 
> in terms of how it impacts them.  Changes to the repsoistory will affect 
> their operational experience dramatically and they do run Windows (go 
> Bill Gates).  They are watching this thread with keen interest.  Their 
> biggest concern is changing how their build and distribution system 
> works and changes in this area is highly disruptive for them.
> 
> My view of the problem is that there are really three distinct areas of 
> a path.  They are the user area, the server area and the application 
> area.  Let me splain...
> 
> | 0000000000000000000000000000 | 
> 11111111111111111111111111111111111111111 | 2222222222222222222 ...
> C:\my\directory\before\geronimo\geronimo-1.1\repository\com.apache.geronimo\console-1.1\appArtifacts 
> 
> 
> The area in the 0's are controlled by the user and we need to leave more 
> headroom than a few characters so they can manage multiple deployments 
> of Geronimo; this could include multiple versions or multiple 
> deployments.  The users probably enjoy flexibility in naming as much as 
> we do.  We don't have control over this but we influence how much 
> headroom is available.
> 
> The 1's is really the area we have control over as this is the server 
> proper.  This includes the area from the top of the tree to the end of 
> where the files we create end.  So, for instance, this includes var, 
> repository, etc.  Since were currently experiencing this problem in the 
> respository I think we should focus on this area.
> 
> Finally, the 2's are the area that include the application and Maven 
> dependent information.  The Maven naming convention is verbose.  The 
> current implementation needs to be changed, the question is how and can 
> the change survive several releases so that our users are not forced to 
> change their deployments on each subsequent release.  *One immediate 
> thought I had was to place applications back into the config-store (or 
> equivalent name).  Rather than simply use a number as we did previously 
> perhaps the configId of the deployment would be appropriate.  Its human 
> readable and would be shorter than the current maven structure.*  I 
> highlighted the previous as I think this is the best option based on 
> what I know today.
> 
> Perhaps there some way to provide a Maven abstraction that would map 
> Maven dir names to an internal format for us.  I expect if we are 
> running into this its only a matter of time befoew other Maven users 
> experience the same issues.  For us its the nesting of Maven articacts / 
> configurations that is causing us the problem.  Jason, thoughts?
> 
> Whatever we decide we need to ensure that it is stable enough to work 
> for a period of time.
> 
> Matt
> 
> 
> Dain Sundstrom wrote:
> 
>> Man I hate Windows....
>>
>> Anyway, if you have a real OS and list the files in an assembly, you  
>> will see that the problem is caused by the combination of two  
>> changes: we now keep configurations in the repository and we unpack  
>> them. If you look closer you will see that the big offenders are  
>> unpacked ears and wars.
>>
>> I believe the following are the longest paths in the server:
>>
>> (270)
>> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/1.1- 
>> SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-web-1.1- 
>> SNAPSHOT.war/META-INF/geronimo-generated/org/apache/geronimo/axis/ 
>> client/GenericServiceEndpointWrapper$$EnhancerByCGLIB$$36344d29.class
>> (264)
>> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1- 
>> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console- 
>> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/console/ 
>> databasemanager/wizard/DatabasePoolPortlet$ResourceAdapterParams.class
>>
>>
>> One thing to note here is that the longest paths are all classes  
>> generated by Geronimo, nested classes in wars or compiled JSP pages.   
>> Someone should look into makeing maven jar the latter two and  
>> Geronimo should be creating jars when generating classes (actually we  
>> should stop generating classes a head of time but that is another  
>> story).
>>
>>
>>
>> Breaking down the longest path, we have:
>>
>> GeronimoName (22)
>>   geronimo-1.1-SNAPSHOT
>> RepositoryPath (55)
>>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
>> FileName (39)
>>   daytrader-derby-jetty-1.1-SNAPSHOT.car
>> NestedPath (154)
>>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/ 
>> apache/geronimo/axis/client/GenericServiceEndpointWrapper$ 
>> $EnhancerByCGLIB$$36344d29.class
>>
>>
>>
>> The first thing to note is if we simply replace "SNAPSHOT" with "0",  
>> we drop 28 characters which makes the longest path 242; not enough  
>> head room.  Of course, when we switch our groupId to the maven  
>> standard org.apache.geronimo we eat up 20 more characters.  If we are  
>> going to unpack war files there is very little we can do about the  
>> NestedPath, so we have very few choices left.  If we simply combine  
>> combine ${GeronimoName}/${FileName}/${NestedPath} we are up to 115  
>> characters leaving only 41 characters for anything else, but when you  
>> add back the 28 from "SNAPSHOT", you get to a more comfortable level.
>>
>> I think if we combine this problem with Sachin's request for a  
>> separate directory for applications, we could do something like this:
>>
>> ${GeronimoName}/apps/${FileName}/${NestedPath}
>>
>> There are several problems with this.  I think users will confuse the  
>> hot-deploy directory "deploy" with the "apps" directory [1].  Then  
>> again, if you look at the problem configurations they are all apps  
>> the users may want to remove (sample apps and the console), so may be  
>> we should just put these in the hot-deploy directory.  Another  
>> problem is that it will be much more difficult to query a repository  
>> without a directory structure.  The server will basically have to  
>> read the configuration from these apps on startup to determine what  
>> they are, so again we may just want to use the hot-deploy directory.   
>> I'm not a fan of the hot-deploy directory, but I'm not sure there is  
>> a better solution.
>>
>> Again I renew my hate of Windows...
>> /me shakes his fist at Bill Gates
>>
>> -dain
>>
>>
>> [1] As a side issue, I prefer the name "apps" because it will be most  
>> familiar to tomcat users.
>>
>>
>>
>>
>>
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Hernan Cunico <hc...@gmail.com>.
Hi All,
for those struggling with Windows file naming limitation. I found deleting those file is a royal 
pain as Windows can not point directly to the files already generated.

To delete those files and directories exceeding the 254 chars you can use the old DOS command 
"subst". This command will assign a drive letter to a directory, here is a example:

subst z: <geronimo_src>\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository

This temporary workaround worked just fine on my machine with Windows XP.

Cheers!
Hernan

Re: Cannot build 1.1 on Windows - long file paths

Posted by Hernan Cunico <hc...@gmail.com>.
Please, stay away from config/repos in DB :D  I've seen that before and I really hated it.
I can come up with a lond detailed list why we should not go that way ;)

Cheers!
Hernan

Jason Dillon wrote:
> Good time for everyone to go buy a Mac :-)
> 
> Is there any version of any windows fs that is not crippled with this  
> limitation?
> 
> Its a real pity that we have to work around muck like this... :-(
> 
>  * * *
> 
> What if the repo was not backed by a filesystem... but maybe a fast  
> database or something similar?  Then paths could be as long as we  want, 
> but the physical representation could be tailored for lame  operating 
> systems.
> 
> This would mean we need more tools to get at the data and to put in  the 
> data... but I think that would be generally a good thing anyways.
> 
> --jason
> 
> 
> On Apr 7, 2006, at 12:25 PM, Matt Hogstrom wrote:
> 
>> I'm not blaming the m2 structure.  One has to acknowledge that it  
>> accounts for more than 15% of the length (per your comment below).   
>> 15% is not insignificant but I'll concede that this is nowhere near  
>> the whole problem.  It is compunding of the length due to nesting  
>> modules.  Daytrader is a fair example of this.  This example is  from 
>> a build from this morning in branches/1.1.  I omitted the / 
>> Users/hogstrom/dev/geronimo/branches/1.1/assemblies/j2ee-tomcat/ 
>> target/ prefix.
>>
>> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-tomcat/ 
>> 1.1-SNAPSHOT/daytrader-derby-tomcat-1.1-SNAPSHOT.car/daytrader- 
>> web-1.1-SNAPSHOT.war/
>>
>> Repeated items like derby-tomcat-1.1-SNAPSHOT doesn't help :)
>>
>> BTW, Geronimo is not the only one to suffer from this issue.  The  
>> restriction is a problem on Windows I think we've been flirting  with 
>> it for sometime.  It has now just bit us hard.
>>
>> Dain Sundstrom wrote:
>>
>>> Please stop blaming the m2 repo structure for this problem.  The  m2  
>>> repo structure only increased the path of our longest path by  36  
>>> characters.  The true problem is that David and I moved the  
>>> unpacked  configurations into the repository.  We did this because  
>>> of the  chunkiness of the numbered directories in the config- store  
>>> directory.  The m2 repository structure makes querying the  
>>> repository  for version numbers possible and it is this querying  
>>> that makes  optional version numbers possible.
>>> I think we have two issues that both must be addressed:
>>> 1) The ears we generate in our build have very long internal  paths,  
>>> 154 characters.  This is just bad form, and vastly reduces  the user  
>>> path head room.
>>
>> >
>>
>>> 2) We need to move the unpacked ears our of the repository and  into 
>>> a  separate flat directory structure.
>>> I can look at the second one later today after fixing the  redeploy  
>>> command.  Can someone take a look at getting our build  to jar up 
>>> the  classes and compiled jsps in our build.  I'll fix  the 
>>> generated  classes in our build.
>>> -dain
>>> On Apr 7, 2006, at 6:50 AM, Matt Hogstrom wrote:
>>>
>>>> Thinking about this some more I believe we need to make a good   
>>>> decision here as having to revisit this issue in the future will   
>>>> cause users to have to change how the server works.  I've been   
>>>> talking to a new user that has a larger server farm and is very   
>>>> interested in the Geronimo server as their new foundation.    
>>>> However, they run a few thousand servers and are VERY sensitive  to  
>>>> changes in the behaviour of the server in terms of how it  impacts  
>>>> them.  Changes to the repsoistory will affect their  operational  
>>>> experience dramatically and they do run Windows (go  Bill Gates).   
>>>> They are watching this thread with keen interest.   Their biggest  
>>>> concern is changing how their build and  distribution system works  
>>>> and changes in this area is highly  disruptive for them.
>>>>
>>>> My view of the problem is that there are really three distinct   
>>>> areas of a path.  They are the user area, the server area and  the  
>>>> application area.  Let me splain...
>>>>
>>>> | 0000000000000000000000000000 |   
>>>> 11111111111111111111111111111111111111111 | 2222222222222222222 ...
>>>> C:\my\directory\before\geronimo\geronimo-1.1\repository  
>>>> \com.apache.geronimo\console-1.1\appArtifacts
>>>>
>>>> The area in the 0's are controlled by the user and we need to  
>>>> leave  more headroom than a few characters so they can manage  
>>>> multiple  deployments of Geronimo; this could include multiple  
>>>> versions or  multiple deployments.  The users probably enjoy  
>>>> flexibility in  naming as much as we do.  We don't have control  
>>>> over this but we  influence how much headroom is available.
>>>>
>>>> The 1's is really the area we have control over as this is the   
>>>> server proper.  This includes the area from the top of the tree  to  
>>>> the end of where the files we create end.  So, for instance,  this  
>>>> includes var, repository, etc.  Since were currently  experiencing  
>>>> this problem in the respository I think we should  focus on this area.
>>>>
>>>> Finally, the 2's are the area that include the application and   
>>>> Maven dependent information.  The Maven naming convention is   
>>>> verbose.  The current implementation needs to be changed, the   
>>>> question is how and can the change survive several releases so  
>>>> that  our users are not forced to change their deployments on  each  
>>>> subsequent release.  *One immediate thought I had was to  place  
>>>> applications back into the config-store (or equivalent  name).   
>>>> Rather than simply use a number as we did previously  perhaps the  
>>>> configId of the deployment would be appropriate.   Its human  
>>>> readable and would be shorter than the current maven  structure.*  
>>>> I  highlighted the previous as I think this is the  best option 
>>>> based  on what I know today.
>>>>
>>>> Perhaps there some way to provide a Maven abstraction that would   
>>>> map Maven dir names to an internal format for us.  I expect if  we  
>>>> are running into this its only a matter of time befoew other  Maven  
>>>> users experience the same issues.  For us its the nesting  of Maven  
>>>> articacts / configurations that is causing us the  problem.  Jason,  
>>>> thoughts?
>>>>
>>>> Whatever we decide we need to ensure that it is stable enough to   
>>>> work for a period of time.
>>>>
>>>> Matt
>>>>
>>>>
>>>> Dain Sundstrom wrote:
>>>>
>>>>> Man I hate Windows....
>>>>> Anyway, if you have a real OS and list the files in an  assembly,  
>>>>> you  will see that the problem is caused by the  combination of  
>>>>> two  changes: we now keep configurations in the  repository and we  
>>>>> unpack  them. If you look closer you will see  that the big  
>>>>> offenders are  unpacked ears and wars.
>>>>> I believe the following are the longest paths in the server:
>>>>> (270)
>>>>> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/  
>>>>> 1.1- SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-  
>>>>> web-1.1- SNAPSHOT.war/META-INF/geronimo-generated/org/apache/  
>>>>> geronimo/axis/ client/GenericServiceEndpointWrapper$  
>>>>> $EnhancerByCGLIB$$36344d29.class
>>>>> (264)
>>>>> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-   
>>>>> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-   
>>>>> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/  
>>>>> console/ databasemanager/wizard/DatabasePoolPortlet  
>>>>> $ResourceAdapterParams.class
>>>>> One thing to note here is that the longest paths are all  classes   
>>>>> generated by Geronimo, nested classes in wars or  compiled JSP  
>>>>> pages.   Someone should look into makeing maven  jar the latter 
>>>>> two  and  Geronimo should be creating jars when  generating 
>>>>> classes  (actually we  should stop generating classes  a head of 
>>>>> time but  that is another  story).
>>>>> Breaking down the longest path, we have:
>>>>> GeronimoName (22)
>>>>>   geronimo-1.1-SNAPSHOT
>>>>> RepositoryPath (55)
>>>>>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
>>>>> FileName (39)
>>>>>   daytrader-derby-jetty-1.1-SNAPSHOT.car
>>>>> NestedPath (154)
>>>>>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/ org/  
>>>>> apache/geronimo/axis/client/GenericServiceEndpointWrapper $  
>>>>> $EnhancerByCGLIB$$36344d29.class
>>>>> The first thing to note is if we simply replace "SNAPSHOT" with   
>>>>> "0",  we drop 28 characters which makes the longest path 242;  not  
>>>>> enough  head room.  Of course, when we switch our groupId  to the  
>>>>> maven  standard org.apache.geronimo we eat up 20 more  
>>>>> characters.   If we are  going to unpack war files there is very  
>>>>> little we can  do about the  NestedPath, so we have very few  
>>>>> choices left.  If we  simply combine  combine ${GeronimoName}/$ 
>>>>> {FileName}/${NestedPath}  we are up to 115  characters leaving  
>>>>> only 41 characters for  anything else, but when you  add back  the 
>>>>> 28 from "SNAPSHOT", you  get to a more comfortable level.
>>>>> I think if we combine this problem with Sachin's request for a    
>>>>> separate directory for applications, we could do something like  this:
>>>>> ${GeronimoName}/apps/${FileName}/${NestedPath}
>>>>> There are several problems with this.  I think users will  confuse  
>>>>> the  hot-deploy directory "deploy" with the "apps"  directory 
>>>>> [1].   Then  again, if you look at the problem  configurations they 
>>>>> are  all apps  the users may want to remove  (sample apps and the  
>>>>> console), so may be  we should just put  these in the hot-deploy  
>>>>> directory.  Another  problem is that it  will be much more  
>>>>> difficult to query a repository  without a  directory structure.   
>>>>> The server will basically have to  read  the configuration from  
>>>>> these apps on startup to determine what   they are, so again we 
>>>>> may  just want to use the hot-deploy  directory.   I'm not a fan of 
>>>>> the  hot-deploy directory, but I'm  not sure there is  a better 
>>>>> solution.
>>>>> Again I renew my hate of Windows...
>>>>> /me shakes his fist at Bill Gates
>>>>> -dain
>>>>> [1] As a side issue, I prefer the name "apps" because it will  be  
>>>>> most  familiar to tomcat users.
> 
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Jason Dillon <ja...@planet57.com>.
Good time for everyone to go buy a Mac :-)

Is there any version of any windows fs that is not crippled with this  
limitation?

Its a real pity that we have to work around muck like this... :-(

  * * *

What if the repo was not backed by a filesystem... but maybe a fast  
database or something similar?  Then paths could be as long as we  
want, but the physical representation could be tailored for lame  
operating systems.

This would mean we need more tools to get at the data and to put in  
the data... but I think that would be generally a good thing anyways.

--jason


On Apr 7, 2006, at 12:25 PM, Matt Hogstrom wrote:

> I'm not blaming the m2 structure.  One has to acknowledge that it  
> accounts for more than 15% of the length (per your comment below).   
> 15% is not insignificant but I'll concede that this is nowhere near  
> the whole problem.  It is compunding of the length due to nesting  
> modules.  Daytrader is a fair example of this.  This example is  
> from a build from this morning in branches/1.1.  I omitted the / 
> Users/hogstrom/dev/geronimo/branches/1.1/assemblies/j2ee-tomcat/ 
> target/ prefix.
>
> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-tomcat/ 
> 1.1-SNAPSHOT/daytrader-derby-tomcat-1.1-SNAPSHOT.car/daytrader- 
> web-1.1-SNAPSHOT.war/
>
> Repeated items like derby-tomcat-1.1-SNAPSHOT doesn't help :)
>
> BTW, Geronimo is not the only one to suffer from this issue.  The  
> restriction is a problem on Windows I think we've been flirting  
> with it for sometime.  It has now just bit us hard.
>
> Dain Sundstrom wrote:
>> Please stop blaming the m2 repo structure for this problem.  The  
>> m2  repo structure only increased the path of our longest path by  
>> 36  characters.  The true problem is that David and I moved the  
>> unpacked  configurations into the repository.  We did this because  
>> of the  chunkiness of the numbered directories in the config- 
>> store  directory.  The m2 repository structure makes querying the  
>> repository  for version numbers possible and it is this querying  
>> that makes  optional version numbers possible.
>> I think we have two issues that both must be addressed:
>> 1) The ears we generate in our build have very long internal  
>> paths,  154 characters.  This is just bad form, and vastly reduces  
>> the user  path head room.
> >
>> 2) We need to move the unpacked ears our of the repository and  
>> into a  separate flat directory structure.
>> I can look at the second one later today after fixing the  
>> redeploy  command.  Can someone take a look at getting our build  
>> to jar up the  classes and compiled jsps in our build.  I'll fix  
>> the generated  classes in our build.
>> -dain
>> On Apr 7, 2006, at 6:50 AM, Matt Hogstrom wrote:
>>> Thinking about this some more I believe we need to make a good   
>>> decision here as having to revisit this issue in the future will   
>>> cause users to have to change how the server works.  I've been   
>>> talking to a new user that has a larger server farm and is very   
>>> interested in the Geronimo server as their new foundation.    
>>> However, they run a few thousand servers and are VERY sensitive  
>>> to  changes in the behaviour of the server in terms of how it  
>>> impacts  them.  Changes to the repsoistory will affect their  
>>> operational  experience dramatically and they do run Windows (go  
>>> Bill Gates).   They are watching this thread with keen interest.   
>>> Their biggest  concern is changing how their build and  
>>> distribution system works  and changes in this area is highly  
>>> disruptive for them.
>>>
>>> My view of the problem is that there are really three distinct   
>>> areas of a path.  They are the user area, the server area and  
>>> the  application area.  Let me splain...
>>>
>>> | 0000000000000000000000000000 |   
>>> 11111111111111111111111111111111111111111 | 2222222222222222222 ...
>>> C:\my\directory\before\geronimo\geronimo-1.1\repository  
>>> \com.apache.geronimo\console-1.1\appArtifacts
>>>
>>> The area in the 0's are controlled by the user and we need to  
>>> leave  more headroom than a few characters so they can manage  
>>> multiple  deployments of Geronimo; this could include multiple  
>>> versions or  multiple deployments.  The users probably enjoy  
>>> flexibility in  naming as much as we do.  We don't have control  
>>> over this but we  influence how much headroom is available.
>>>
>>> The 1's is really the area we have control over as this is the   
>>> server proper.  This includes the area from the top of the tree  
>>> to  the end of where the files we create end.  So, for instance,  
>>> this  includes var, repository, etc.  Since were currently  
>>> experiencing  this problem in the respository I think we should  
>>> focus on this area.
>>>
>>> Finally, the 2's are the area that include the application and   
>>> Maven dependent information.  The Maven naming convention is   
>>> verbose.  The current implementation needs to be changed, the   
>>> question is how and can the change survive several releases so  
>>> that  our users are not forced to change their deployments on  
>>> each  subsequent release.  *One immediate thought I had was to  
>>> place  applications back into the config-store (or equivalent  
>>> name).   Rather than simply use a number as we did previously  
>>> perhaps the  configId of the deployment would be appropriate.   
>>> Its human  readable and would be shorter than the current maven  
>>> structure.*  I  highlighted the previous as I think this is the  
>>> best option based  on what I know today.
>>>
>>> Perhaps there some way to provide a Maven abstraction that would   
>>> map Maven dir names to an internal format for us.  I expect if  
>>> we  are running into this its only a matter of time befoew other  
>>> Maven  users experience the same issues.  For us its the nesting  
>>> of Maven  articacts / configurations that is causing us the  
>>> problem.  Jason,  thoughts?
>>>
>>> Whatever we decide we need to ensure that it is stable enough to   
>>> work for a period of time.
>>>
>>> Matt
>>>
>>>
>>> Dain Sundstrom wrote:
>>>
>>>> Man I hate Windows....
>>>> Anyway, if you have a real OS and list the files in an  
>>>> assembly,  you  will see that the problem is caused by the  
>>>> combination of  two  changes: we now keep configurations in the  
>>>> repository and we  unpack  them. If you look closer you will see  
>>>> that the big  offenders are  unpacked ears and wars.
>>>> I believe the following are the longest paths in the server:
>>>> (270)
>>>> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/  
>>>> 1.1- SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-  
>>>> web-1.1- SNAPSHOT.war/META-INF/geronimo-generated/org/apache/  
>>>> geronimo/axis/ client/GenericServiceEndpointWrapper$  
>>>> $EnhancerByCGLIB$$36344d29.class
>>>> (264)
>>>> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-   
>>>> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-   
>>>> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/  
>>>> console/ databasemanager/wizard/DatabasePoolPortlet  
>>>> $ResourceAdapterParams.class
>>>> One thing to note here is that the longest paths are all  
>>>> classes   generated by Geronimo, nested classes in wars or  
>>>> compiled JSP  pages.   Someone should look into makeing maven  
>>>> jar the latter two  and  Geronimo should be creating jars when  
>>>> generating classes  (actually we  should stop generating classes  
>>>> a head of time but  that is another  story).
>>>> Breaking down the longest path, we have:
>>>> GeronimoName (22)
>>>>   geronimo-1.1-SNAPSHOT
>>>> RepositoryPath (55)
>>>>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
>>>> FileName (39)
>>>>   daytrader-derby-jetty-1.1-SNAPSHOT.car
>>>> NestedPath (154)
>>>>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/ 
>>>> org/  apache/geronimo/axis/client/GenericServiceEndpointWrapper 
>>>> $  $EnhancerByCGLIB$$36344d29.class
>>>> The first thing to note is if we simply replace "SNAPSHOT" with   
>>>> "0",  we drop 28 characters which makes the longest path 242;  
>>>> not  enough  head room.  Of course, when we switch our groupId  
>>>> to the  maven  standard org.apache.geronimo we eat up 20 more  
>>>> characters.   If we are  going to unpack war files there is very  
>>>> little we can  do about the  NestedPath, so we have very few  
>>>> choices left.  If we  simply combine  combine ${GeronimoName}/$ 
>>>> {FileName}/${NestedPath}  we are up to 115  characters leaving  
>>>> only 41 characters for  anything else, but when you  add back  
>>>> the 28 from "SNAPSHOT", you  get to a more comfortable level.
>>>> I think if we combine this problem with Sachin's request for a    
>>>> separate directory for applications, we could do something like  
>>>> this:
>>>> ${GeronimoName}/apps/${FileName}/${NestedPath}
>>>> There are several problems with this.  I think users will  
>>>> confuse  the  hot-deploy directory "deploy" with the "apps"  
>>>> directory [1].   Then  again, if you look at the problem  
>>>> configurations they are  all apps  the users may want to remove  
>>>> (sample apps and the  console), so may be  we should just put  
>>>> these in the hot-deploy  directory.  Another  problem is that it  
>>>> will be much more  difficult to query a repository  without a  
>>>> directory structure.   The server will basically have to  read  
>>>> the configuration from  these apps on startup to determine what   
>>>> they are, so again we may  just want to use the hot-deploy  
>>>> directory.   I'm not a fan of the  hot-deploy directory, but I'm  
>>>> not sure there is  a better solution.
>>>> Again I renew my hate of Windows...
>>>> /me shakes his fist at Bill Gates
>>>> -dain
>>>> [1] As a side issue, I prefer the name "apps" because it will  
>>>> be  most  familiar to tomcat users.


Re: Cannot build 1.1 on Windows - long file paths

Posted by Jason Dillon <ja...@planet57.com>.
Um, I'm guessing this is one of the reasons why the windows registry  
isn't just a set of simple xml files too... no way that muck could be  
represented in their whacko filesystem.

--jason


On Apr 7, 2006, at 12:25 PM, Matt Hogstrom wrote:

> I'm not blaming the m2 structure.  One has to acknowledge that it  
> accounts for more than 15% of the length (per your comment below).   
> 15% is not insignificant but I'll concede that this is nowhere near  
> the whole problem.  It is compunding of the length due to nesting  
> modules.  Daytrader is a fair example of this.  This example is  
> from a build from this morning in branches/1.1.  I omitted the / 
> Users/hogstrom/dev/geronimo/branches/1.1/assemblies/j2ee-tomcat/ 
> target/ prefix.
>
> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-tomcat/ 
> 1.1-SNAPSHOT/daytrader-derby-tomcat-1.1-SNAPSHOT.car/daytrader- 
> web-1.1-SNAPSHOT.war/
>
> Repeated items like derby-tomcat-1.1-SNAPSHOT doesn't help :)
>
> BTW, Geronimo is not the only one to suffer from this issue.  The  
> restriction is a problem on Windows I think we've been flirting  
> with it for sometime.  It has now just bit us hard.
>
> Dain Sundstrom wrote:
>> Please stop blaming the m2 repo structure for this problem.  The  
>> m2  repo structure only increased the path of our longest path by  
>> 36  characters.  The true problem is that David and I moved the  
>> unpacked  configurations into the repository.  We did this because  
>> of the  chunkiness of the numbered directories in the config- 
>> store  directory.  The m2 repository structure makes querying the  
>> repository  for version numbers possible and it is this querying  
>> that makes  optional version numbers possible.
>> I think we have two issues that both must be addressed:
>> 1) The ears we generate in our build have very long internal  
>> paths,  154 characters.  This is just bad form, and vastly reduces  
>> the user  path head room.
> >
>> 2) We need to move the unpacked ears our of the repository and  
>> into a  separate flat directory structure.
>> I can look at the second one later today after fixing the  
>> redeploy  command.  Can someone take a look at getting our build  
>> to jar up the  classes and compiled jsps in our build.  I'll fix  
>> the generated  classes in our build.
>> -dain
>> On Apr 7, 2006, at 6:50 AM, Matt Hogstrom wrote:
>>> Thinking about this some more I believe we need to make a good   
>>> decision here as having to revisit this issue in the future will   
>>> cause users to have to change how the server works.  I've been   
>>> talking to a new user that has a larger server farm and is very   
>>> interested in the Geronimo server as their new foundation.    
>>> However, they run a few thousand servers and are VERY sensitive  
>>> to  changes in the behaviour of the server in terms of how it  
>>> impacts  them.  Changes to the repsoistory will affect their  
>>> operational  experience dramatically and they do run Windows (go  
>>> Bill Gates).   They are watching this thread with keen interest.   
>>> Their biggest  concern is changing how their build and  
>>> distribution system works  and changes in this area is highly  
>>> disruptive for them.
>>>
>>> My view of the problem is that there are really three distinct   
>>> areas of a path.  They are the user area, the server area and  
>>> the  application area.  Let me splain...
>>>
>>> | 0000000000000000000000000000 |   
>>> 11111111111111111111111111111111111111111 | 2222222222222222222 ...
>>> C:\my\directory\before\geronimo\geronimo-1.1\repository  
>>> \com.apache.geronimo\console-1.1\appArtifacts
>>>
>>> The area in the 0's are controlled by the user and we need to  
>>> leave  more headroom than a few characters so they can manage  
>>> multiple  deployments of Geronimo; this could include multiple  
>>> versions or  multiple deployments.  The users probably enjoy  
>>> flexibility in  naming as much as we do.  We don't have control  
>>> over this but we  influence how much headroom is available.
>>>
>>> The 1's is really the area we have control over as this is the   
>>> server proper.  This includes the area from the top of the tree  
>>> to  the end of where the files we create end.  So, for instance,  
>>> this  includes var, repository, etc.  Since were currently  
>>> experiencing  this problem in the respository I think we should  
>>> focus on this area.
>>>
>>> Finally, the 2's are the area that include the application and   
>>> Maven dependent information.  The Maven naming convention is   
>>> verbose.  The current implementation needs to be changed, the   
>>> question is how and can the change survive several releases so  
>>> that  our users are not forced to change their deployments on  
>>> each  subsequent release.  *One immediate thought I had was to  
>>> place  applications back into the config-store (or equivalent  
>>> name).   Rather than simply use a number as we did previously  
>>> perhaps the  configId of the deployment would be appropriate.   
>>> Its human  readable and would be shorter than the current maven  
>>> structure.*  I  highlighted the previous as I think this is the  
>>> best option based  on what I know today.
>>>
>>> Perhaps there some way to provide a Maven abstraction that would   
>>> map Maven dir names to an internal format for us.  I expect if  
>>> we  are running into this its only a matter of time befoew other  
>>> Maven  users experience the same issues.  For us its the nesting  
>>> of Maven  articacts / configurations that is causing us the  
>>> problem.  Jason,  thoughts?
>>>
>>> Whatever we decide we need to ensure that it is stable enough to   
>>> work for a period of time.
>>>
>>> Matt
>>>
>>>
>>> Dain Sundstrom wrote:
>>>
>>>> Man I hate Windows....
>>>> Anyway, if you have a real OS and list the files in an  
>>>> assembly,  you  will see that the problem is caused by the  
>>>> combination of  two  changes: we now keep configurations in the  
>>>> repository and we  unpack  them. If you look closer you will see  
>>>> that the big  offenders are  unpacked ears and wars.
>>>> I believe the following are the longest paths in the server:
>>>> (270)
>>>> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/  
>>>> 1.1- SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-  
>>>> web-1.1- SNAPSHOT.war/META-INF/geronimo-generated/org/apache/  
>>>> geronimo/axis/ client/GenericServiceEndpointWrapper$  
>>>> $EnhancerByCGLIB$$36344d29.class
>>>> (264)
>>>> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-   
>>>> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-   
>>>> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/  
>>>> console/ databasemanager/wizard/DatabasePoolPortlet  
>>>> $ResourceAdapterParams.class
>>>> One thing to note here is that the longest paths are all  
>>>> classes   generated by Geronimo, nested classes in wars or  
>>>> compiled JSP  pages.   Someone should look into makeing maven  
>>>> jar the latter two  and  Geronimo should be creating jars when  
>>>> generating classes  (actually we  should stop generating classes  
>>>> a head of time but  that is another  story).
>>>> Breaking down the longest path, we have:
>>>> GeronimoName (22)
>>>>   geronimo-1.1-SNAPSHOT
>>>> RepositoryPath (55)
>>>>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
>>>> FileName (39)
>>>>   daytrader-derby-jetty-1.1-SNAPSHOT.car
>>>> NestedPath (154)
>>>>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/ 
>>>> org/  apache/geronimo/axis/client/GenericServiceEndpointWrapper 
>>>> $  $EnhancerByCGLIB$$36344d29.class
>>>> The first thing to note is if we simply replace "SNAPSHOT" with   
>>>> "0",  we drop 28 characters which makes the longest path 242;  
>>>> not  enough  head room.  Of course, when we switch our groupId  
>>>> to the  maven  standard org.apache.geronimo we eat up 20 more  
>>>> characters.   If we are  going to unpack war files there is very  
>>>> little we can  do about the  NestedPath, so we have very few  
>>>> choices left.  If we  simply combine  combine ${GeronimoName}/$ 
>>>> {FileName}/${NestedPath}  we are up to 115  characters leaving  
>>>> only 41 characters for  anything else, but when you  add back  
>>>> the 28 from "SNAPSHOT", you  get to a more comfortable level.
>>>> I think if we combine this problem with Sachin's request for a    
>>>> separate directory for applications, we could do something like  
>>>> this:
>>>> ${GeronimoName}/apps/${FileName}/${NestedPath}
>>>> There are several problems with this.  I think users will  
>>>> confuse  the  hot-deploy directory "deploy" with the "apps"  
>>>> directory [1].   Then  again, if you look at the problem  
>>>> configurations they are  all apps  the users may want to remove  
>>>> (sample apps and the  console), so may be  we should just put  
>>>> these in the hot-deploy  directory.  Another  problem is that it  
>>>> will be much more  difficult to query a repository  without a  
>>>> directory structure.   The server will basically have to  read  
>>>> the configuration from  these apps on startup to determine what   
>>>> they are, so again we may  just want to use the hot-deploy  
>>>> directory.   I'm not a fan of the  hot-deploy directory, but I'm  
>>>> not sure there is  a better solution.
>>>> Again I renew my hate of Windows...
>>>> /me shakes his fist at Bill Gates
>>>> -dain
>>>> [1] As a side issue, I prefer the name "apps" because it will  
>>>> be  most  familiar to tomcat users.


Re: Cannot build 1.1 on Windows - long file paths

Posted by Matt Hogstrom <ma...@hogstrom.org>.
I'm not blaming the m2 structure.  One has to acknowledge that it accounts for more than 15% of the 
length (per your comment below).  15% is not insignificant but I'll concede that this is nowhere 
near the whole problem.  It is compunding of the length due to nesting modules.  Daytrader is a fair 
example of this.  This example is from a build from this morning in branches/1.1.  I omitted the 
/Users/hogstrom/dev/geronimo/branches/1.1/assemblies/j2ee-tomcat/target/ prefix.

geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-tomcat/1.1-SNAPSHOT/daytrader-derby-tomcat-1.1-SNAPSHOT.car/daytrader-web-1.1-SNAPSHOT.war/

Repeated items like derby-tomcat-1.1-SNAPSHOT doesn't help :)

BTW, Geronimo is not the only one to suffer from this issue.  The restriction is a problem on 
Windows I think we've been flirting with it for sometime.  It has now just bit us hard.

Dain Sundstrom wrote:
> Please stop blaming the m2 repo structure for this problem.  The m2  
> repo structure only increased the path of our longest path by 36  
> characters.  The true problem is that David and I moved the unpacked  
> configurations into the repository.  We did this because of the  
> chunkiness of the numbered directories in the config-store  directory.  
> The m2 repository structure makes querying the repository  for version 
> numbers possible and it is this querying that makes  optional version 
> numbers possible.
> 
> I think we have two issues that both must be addressed:
> 
> 1) The ears we generate in our build have very long internal paths,  154 
> characters.  This is just bad form, and vastly reduces the user  path 
> head room.
 >
> 2) We need to move the unpacked ears our of the repository and into a  
> separate flat directory structure.
> 
> I can look at the second one later today after fixing the redeploy  
> command.  Can someone take a look at getting our build to jar up the  
> classes and compiled jsps in our build.  I'll fix the generated  classes 
> in our build.
> 
> -dain
> 
> On Apr 7, 2006, at 6:50 AM, Matt Hogstrom wrote:
> 
>> Thinking about this some more I believe we need to make a good  
>> decision here as having to revisit this issue in the future will  
>> cause users to have to change how the server works.  I've been  
>> talking to a new user that has a larger server farm and is very  
>> interested in the Geronimo server as their new foundation.   However, 
>> they run a few thousand servers and are VERY sensitive to  changes in 
>> the behaviour of the server in terms of how it impacts  them.  Changes 
>> to the repsoistory will affect their operational  experience 
>> dramatically and they do run Windows (go Bill Gates).   They are 
>> watching this thread with keen interest.  Their biggest  concern is 
>> changing how their build and distribution system works  and changes in 
>> this area is highly disruptive for them.
>>
>> My view of the problem is that there are really three distinct  areas 
>> of a path.  They are the user area, the server area and the  
>> application area.  Let me splain...
>>
>> | 0000000000000000000000000000 |  
>> 11111111111111111111111111111111111111111 | 2222222222222222222 ...
>> C:\my\directory\before\geronimo\geronimo-1.1\repository 
>> \com.apache.geronimo\console-1.1\appArtifacts
>>
>> The area in the 0's are controlled by the user and we need to leave  
>> more headroom than a few characters so they can manage multiple  
>> deployments of Geronimo; this could include multiple versions or  
>> multiple deployments.  The users probably enjoy flexibility in  naming 
>> as much as we do.  We don't have control over this but we  influence 
>> how much headroom is available.
>>
>> The 1's is really the area we have control over as this is the  server 
>> proper.  This includes the area from the top of the tree to  the end 
>> of where the files we create end.  So, for instance, this  includes 
>> var, repository, etc.  Since were currently experiencing  this problem 
>> in the respository I think we should focus on this area.
>>
>> Finally, the 2's are the area that include the application and  Maven 
>> dependent information.  The Maven naming convention is  verbose.  The 
>> current implementation needs to be changed, the  question is how and 
>> can the change survive several releases so that  our users are not 
>> forced to change their deployments on each  subsequent release.  *One 
>> immediate thought I had was to place  applications back into the 
>> config-store (or equivalent name).   Rather than simply use a number 
>> as we did previously perhaps the  configId of the deployment would be 
>> appropriate.  Its human  readable and would be shorter than the 
>> current maven structure.*  I  highlighted the previous as I think this 
>> is the best option based  on what I know today.
>>
>> Perhaps there some way to provide a Maven abstraction that would  map 
>> Maven dir names to an internal format for us.  I expect if we  are 
>> running into this its only a matter of time befoew other Maven  users 
>> experience the same issues.  For us its the nesting of Maven  
>> articacts / configurations that is causing us the problem.  Jason,  
>> thoughts?
>>
>> Whatever we decide we need to ensure that it is stable enough to  work 
>> for a period of time.
>>
>> Matt
>>
>>
>> Dain Sundstrom wrote:
>>
>>> Man I hate Windows....
>>> Anyway, if you have a real OS and list the files in an assembly,  
>>> you  will see that the problem is caused by the combination of  two  
>>> changes: we now keep configurations in the repository and we  unpack  
>>> them. If you look closer you will see that the big  offenders are  
>>> unpacked ears and wars.
>>> I believe the following are the longest paths in the server:
>>> (270)
>>> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/ 1.1- 
>>> SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader- web-1.1- 
>>> SNAPSHOT.war/META-INF/geronimo-generated/org/apache/ geronimo/axis/ 
>>> client/GenericServiceEndpointWrapper$ $EnhancerByCGLIB$$36344d29.class
>>> (264)
>>> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-  
>>> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-  
>>> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/ 
>>> console/ databasemanager/wizard/DatabasePoolPortlet 
>>> $ResourceAdapterParams.class
>>> One thing to note here is that the longest paths are all classes   
>>> generated by Geronimo, nested classes in wars or compiled JSP  
>>> pages.   Someone should look into makeing maven jar the latter two  
>>> and  Geronimo should be creating jars when generating classes  
>>> (actually we  should stop generating classes a head of time but  that 
>>> is another  story).
>>> Breaking down the longest path, we have:
>>> GeronimoName (22)
>>>   geronimo-1.1-SNAPSHOT
>>> RepositoryPath (55)
>>>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
>>> FileName (39)
>>>   daytrader-derby-jetty-1.1-SNAPSHOT.car
>>> NestedPath (154)
>>>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/  
>>> apache/geronimo/axis/client/GenericServiceEndpointWrapper$  
>>> $EnhancerByCGLIB$$36344d29.class
>>> The first thing to note is if we simply replace "SNAPSHOT" with  
>>> "0",  we drop 28 characters which makes the longest path 242; not  
>>> enough  head room.  Of course, when we switch our groupId to the  
>>> maven  standard org.apache.geronimo we eat up 20 more characters.   
>>> If we are  going to unpack war files there is very little we can  do 
>>> about the  NestedPath, so we have very few choices left.  If we  
>>> simply combine  combine ${GeronimoName}/${FileName}/${NestedPath}  we 
>>> are up to 115  characters leaving only 41 characters for  anything 
>>> else, but when you  add back the 28 from "SNAPSHOT", you  get to a 
>>> more comfortable level.
>>> I think if we combine this problem with Sachin's request for a   
>>> separate directory for applications, we could do something like this:
>>> ${GeronimoName}/apps/${FileName}/${NestedPath}
>>> There are several problems with this.  I think users will confuse  
>>> the  hot-deploy directory "deploy" with the "apps" directory [1].   
>>> Then  again, if you look at the problem configurations they are  all 
>>> apps  the users may want to remove (sample apps and the  console), so 
>>> may be  we should just put these in the hot-deploy  directory.  
>>> Another  problem is that it will be much more  difficult to query a 
>>> repository  without a directory structure.   The server will 
>>> basically have to  read the configuration from  these apps on startup 
>>> to determine what  they are, so again we may  just want to use the 
>>> hot-deploy directory.   I'm not a fan of the  hot-deploy directory, 
>>> but I'm not sure there is  a better solution.
>>> Again I renew my hate of Windows...
>>> /me shakes his fist at Bill Gates
>>> -dain
>>> [1] As a side issue, I prefer the name "apps" because it will be  
>>> most  familiar to tomcat users.
> 
> 
> 
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Hernan Cunico <hc...@gmail.com>.
Hi All,
here  are some thoughts from my old IT Spec perspective :)

Maybe I'm smoking something but wouldn't it be easier for the end user if we just offer them a 
simpler directory structure for the applications !?!?!?

- This structure would be beneficial from a production stand point
<system_apps>/
here we put all the product applications. Very little end user updates here, maybe some 
customization at the initial build time if they are customizing Geronimo. We could keep all the apps 
JARed in this structure.

<user_apps>/
here we put all the user applications deployed via the deployer tool or the console. Here is where 
we have the bigger problem if the users use the same philosophy as we do with maven. I think here is 
where we need to focus.

<hot_deploy>/
this is within the <user_apps> dir. It will not be used too often in production, eitherway, most of 
the apps deployed here will be packaged as a jar or ear so we should not see any problems with the 
naming here.




- The same structure from a development/customization stand point
<system_apps>/
lots of updates from the end user. It might still be more convenient to maintain a short naming 
convention for easier browseability (hmmm, does that word actually exists!?). What is the problem 
using back the jars? repackaging? can we provide a tool (script, classloader!?) for updating the jar 
automatically?

<user_apps>/
not much end user interaction, most of the testing may be performed via hot deployment.

<hot_deploy>/
same as before, most of the apps deployed here will be packaged as a jar or ear so we should not see 
any problems with the naming here.

Cheers!
Hernan


David Jencks wrote:
> I've thought about not unpacking car files but rather flattening  
> everything in them and writing a classloader that can deal with  offsets 
> within a jar file.  This would completely solve the problem  except for 
> peoples desire to fiddle with jsp files on the fly.
> 
> For this, maybe we should allow a car file has the config.ser (in  xml 
> :-) as now but the rest of it is a map to the actual locations of  the 
> files?  I think it might be possible to include this in either a  second 
> "development-friendly" config store (in a special location) or  the 
> standard config store.
> 
> thanks
> david jencks
> 
> On Apr 7, 2006, at 10:29 AM, Dain Sundstrom wrote:
> 
>> Please stop blaming the m2 repo structure for this problem.  The m2  
>> repo structure only increased the path of our longest path by 36  
>> characters.  The true problem is that David and I moved the  unpacked 
>> configurations into the repository.  We did this because  of the 
>> chunkiness of the numbered directories in the config-store  
>> directory.  The m2 repository structure makes querying the  repository 
>> for version numbers possible and it is this querying  that makes 
>> optional version numbers possible.
>>
>> I think we have two issues that both must be addressed:
>>
>> 1) The ears we generate in our build have very long internal paths,  
>> 154 characters.  This is just bad form, and vastly reduces the user  
>> path head room.
>>
>> 2) We need to move the unpacked ears our of the repository and into  a 
>> separate flat directory structure.
>>
>> I can look at the second one later today after fixing the redeploy  
>> command.  Can someone take a look at getting our build to jar up  the 
>> classes and compiled jsps in our build.  I'll fix the generated  
>> classes in our build.
>>
>> -dain
>>
>> On Apr 7, 2006, at 6:50 AM, Matt Hogstrom wrote:
>>
>>> Thinking about this some more I believe we need to make a good  
>>> decision here as having to revisit this issue in the future will  
>>> cause users to have to change how the server works.  I've been  
>>> talking to a new user that has a larger server farm and is very  
>>> interested in the Geronimo server as their new foundation.   However, 
>>> they run a few thousand servers and are VERY sensitive to  changes in 
>>> the behaviour of the server in terms of how it impacts  them.  
>>> Changes to the repsoistory will affect their operational  experience 
>>> dramatically and they do run Windows (go Bill Gates).   They are 
>>> watching this thread with keen interest.  Their biggest  concern is 
>>> changing how their build and distribution system works  and changes 
>>> in this area is highly disruptive for them.
>>>
>>> My view of the problem is that there are really three distinct  areas 
>>> of a path.  They are the user area, the server area and the  
>>> application area.  Let me splain...
>>>
>>> | 0000000000000000000000000000 |  
>>> 11111111111111111111111111111111111111111 | 2222222222222222222 ...
>>> C:\my\directory\before\geronimo\geronimo-1.1\repository 
>>> \com.apache.geronimo\console-1.1\appArtifacts
>>>
>>> The area in the 0's are controlled by the user and we need to  leave 
>>> more headroom than a few characters so they can manage  multiple 
>>> deployments of Geronimo; this could include multiple  versions or 
>>> multiple deployments.  The users probably enjoy  flexibility in 
>>> naming as much as we do.  We don't have control  over this but we 
>>> influence how much headroom is available.
>>>
>>> The 1's is really the area we have control over as this is the  
>>> server proper.  This includes the area from the top of the tree to  
>>> the end of where the files we create end.  So, for instance, this  
>>> includes var, repository, etc.  Since were currently experiencing  
>>> this problem in the respository I think we should focus on this area.
>>>
>>> Finally, the 2's are the area that include the application and  Maven 
>>> dependent information.  The Maven naming convention is  verbose.  The 
>>> current implementation needs to be changed, the  question is how and 
>>> can the change survive several releases so  that our users are not 
>>> forced to change their deployments on each  subsequent release.  *One 
>>> immediate thought I had was to place  applications back into the 
>>> config-store (or equivalent name).   Rather than simply use a number 
>>> as we did previously perhaps the  configId of the deployment would be 
>>> appropriate.  Its human  readable and would be shorter than the 
>>> current maven structure.*   I highlighted the previous as I think 
>>> this is the best option  based on what I know today.
>>>
>>> Perhaps there some way to provide a Maven abstraction that would  map 
>>> Maven dir names to an internal format for us.  I expect if we  are 
>>> running into this its only a matter of time befoew other Maven  users 
>>> experience the same issues.  For us its the nesting of Maven  
>>> articacts / configurations that is causing us the problem.  Jason,  
>>> thoughts?
>>>
>>> Whatever we decide we need to ensure that it is stable enough to  
>>> work for a period of time.
>>>
>>> Matt
>>>
>>>
>>> Dain Sundstrom wrote:
>>>
>>>> Man I hate Windows....
>>>> Anyway, if you have a real OS and list the files in an assembly,  
>>>> you  will see that the problem is caused by the combination of  two  
>>>> changes: we now keep configurations in the repository and we  
>>>> unpack  them. If you look closer you will see that the big  
>>>> offenders are  unpacked ears and wars.
>>>> I believe the following are the longest paths in the server:
>>>> (270)
>>>> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/ 
>>>> 1.1- SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader- 
>>>> web-1.1- SNAPSHOT.war/META-INF/geronimo-generated/org/apache/ 
>>>> geronimo/axis/ client/GenericServiceEndpointWrapper$ 
>>>> $EnhancerByCGLIB$$36344d29.class
>>>> (264)
>>>> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-  
>>>> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-  
>>>> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/ 
>>>> console/ databasemanager/wizard/DatabasePoolPortlet 
>>>> $ResourceAdapterParams.class
>>>> One thing to note here is that the longest paths are all classes   
>>>> generated by Geronimo, nested classes in wars or compiled JSP  
>>>> pages.   Someone should look into makeing maven jar the latter  two 
>>>> and  Geronimo should be creating jars when generating classes  
>>>> (actually we  should stop generating classes a head of time but  
>>>> that is another  story).
>>>> Breaking down the longest path, we have:
>>>> GeronimoName (22)
>>>>   geronimo-1.1-SNAPSHOT
>>>> RepositoryPath (55)
>>>>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
>>>> FileName (39)
>>>>   daytrader-derby-jetty-1.1-SNAPSHOT.car
>>>> NestedPath (154)
>>>>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/  
>>>> apache/geronimo/axis/client/GenericServiceEndpointWrapper$  
>>>> $EnhancerByCGLIB$$36344d29.class
>>>> The first thing to note is if we simply replace "SNAPSHOT" with  
>>>> "0",  we drop 28 characters which makes the longest path 242; not  
>>>> enough  head room.  Of course, when we switch our groupId to the  
>>>> maven  standard org.apache.geronimo we eat up 20 more  characters.  
>>>> If we are  going to unpack war files there is very  little we can do 
>>>> about the  NestedPath, so we have very few  choices left.  If we 
>>>> simply combine  combine ${GeronimoName}/$ {FileName}/${NestedPath} 
>>>> we are up to 115  characters leaving  only 41 characters for 
>>>> anything else, but when you  add back the  28 from "SNAPSHOT", you 
>>>> get to a more comfortable level.
>>>> I think if we combine this problem with Sachin's request for a   
>>>> separate directory for applications, we could do something like  this:
>>>> ${GeronimoName}/apps/${FileName}/${NestedPath}
>>>> There are several problems with this.  I think users will confuse  
>>>> the  hot-deploy directory "deploy" with the "apps" directory  [1].  
>>>> Then  again, if you look at the problem configurations they  are all 
>>>> apps  the users may want to remove (sample apps and the  console), 
>>>> so may be  we should just put these in the hot-deploy  directory.  
>>>> Another  problem is that it will be much more  difficult to query a 
>>>> repository  without a directory structure.   The server will 
>>>> basically have to  read the configuration from  these apps on 
>>>> startup to determine what  they are, so again we  may just want to 
>>>> use the hot-deploy directory.   I'm not a fan of  the hot-deploy 
>>>> directory, but I'm not sure there is  a better  solution.
>>>> Again I renew my hate of Windows...
>>>> /me shakes his fist at Bill Gates
>>>> -dain
>>>> [1] As a side issue, I prefer the name "apps" because it will be  
>>>> most  familiar to tomcat users.
>>
>>
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by David Jencks <da...@yahoo.com>.
I've thought about not unpacking car files but rather flattening  
everything in them and writing a classloader that can deal with  
offsets within a jar file.  This would completely solve the problem  
except for peoples desire to fiddle with jsp files on the fly.

For this, maybe we should allow a car file has the config.ser (in  
xml :-) as now but the rest of it is a map to the actual locations of  
the files?  I think it might be possible to include this in either a  
second "development-friendly" config store (in a special location) or  
the standard config store.

thanks
david jencks

On Apr 7, 2006, at 10:29 AM, Dain Sundstrom wrote:

> Please stop blaming the m2 repo structure for this problem.  The m2  
> repo structure only increased the path of our longest path by 36  
> characters.  The true problem is that David and I moved the  
> unpacked configurations into the repository.  We did this because  
> of the chunkiness of the numbered directories in the config-store  
> directory.  The m2 repository structure makes querying the  
> repository for version numbers possible and it is this querying  
> that makes optional version numbers possible.
>
> I think we have two issues that both must be addressed:
>
> 1) The ears we generate in our build have very long internal paths,  
> 154 characters.  This is just bad form, and vastly reduces the user  
> path head room.
>
> 2) We need to move the unpacked ears our of the repository and into  
> a separate flat directory structure.
>
> I can look at the second one later today after fixing the redeploy  
> command.  Can someone take a look at getting our build to jar up  
> the classes and compiled jsps in our build.  I'll fix the generated  
> classes in our build.
>
> -dain
>
> On Apr 7, 2006, at 6:50 AM, Matt Hogstrom wrote:
>
>> Thinking about this some more I believe we need to make a good  
>> decision here as having to revisit this issue in the future will  
>> cause users to have to change how the server works.  I've been  
>> talking to a new user that has a larger server farm and is very  
>> interested in the Geronimo server as their new foundation.   
>> However, they run a few thousand servers and are VERY sensitive to  
>> changes in the behaviour of the server in terms of how it impacts  
>> them.  Changes to the repsoistory will affect their operational  
>> experience dramatically and they do run Windows (go Bill Gates).   
>> They are watching this thread with keen interest.  Their biggest  
>> concern is changing how their build and distribution system works  
>> and changes in this area is highly disruptive for them.
>>
>> My view of the problem is that there are really three distinct  
>> areas of a path.  They are the user area, the server area and the  
>> application area.  Let me splain...
>>
>> | 0000000000000000000000000000 |  
>> 11111111111111111111111111111111111111111 | 2222222222222222222 ...
>> C:\my\directory\before\geronimo\geronimo-1.1\repository 
>> \com.apache.geronimo\console-1.1\appArtifacts
>>
>> The area in the 0's are controlled by the user and we need to  
>> leave more headroom than a few characters so they can manage  
>> multiple deployments of Geronimo; this could include multiple  
>> versions or multiple deployments.  The users probably enjoy  
>> flexibility in naming as much as we do.  We don't have control  
>> over this but we influence how much headroom is available.
>>
>> The 1's is really the area we have control over as this is the  
>> server proper.  This includes the area from the top of the tree to  
>> the end of where the files we create end.  So, for instance, this  
>> includes var, repository, etc.  Since were currently experiencing  
>> this problem in the respository I think we should focus on this area.
>>
>> Finally, the 2's are the area that include the application and  
>> Maven dependent information.  The Maven naming convention is  
>> verbose.  The current implementation needs to be changed, the  
>> question is how and can the change survive several releases so  
>> that our users are not forced to change their deployments on each  
>> subsequent release.  *One immediate thought I had was to place  
>> applications back into the config-store (or equivalent name).   
>> Rather than simply use a number as we did previously perhaps the  
>> configId of the deployment would be appropriate.  Its human  
>> readable and would be shorter than the current maven structure.*   
>> I highlighted the previous as I think this is the best option  
>> based on what I know today.
>>
>> Perhaps there some way to provide a Maven abstraction that would  
>> map Maven dir names to an internal format for us.  I expect if we  
>> are running into this its only a matter of time befoew other Maven  
>> users experience the same issues.  For us its the nesting of Maven  
>> articacts / configurations that is causing us the problem.  Jason,  
>> thoughts?
>>
>> Whatever we decide we need to ensure that it is stable enough to  
>> work for a period of time.
>>
>> Matt
>>
>>
>> Dain Sundstrom wrote:
>>> Man I hate Windows....
>>> Anyway, if you have a real OS and list the files in an assembly,  
>>> you  will see that the problem is caused by the combination of  
>>> two  changes: we now keep configurations in the repository and we  
>>> unpack  them. If you look closer you will see that the big  
>>> offenders are  unpacked ears and wars.
>>> I believe the following are the longest paths in the server:
>>> (270)
>>> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/ 
>>> 1.1- SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader- 
>>> web-1.1- SNAPSHOT.war/META-INF/geronimo-generated/org/apache/ 
>>> geronimo/axis/ client/GenericServiceEndpointWrapper$ 
>>> $EnhancerByCGLIB$$36344d29.class
>>> (264)
>>> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-  
>>> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-  
>>> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/ 
>>> console/ databasemanager/wizard/DatabasePoolPortlet 
>>> $ResourceAdapterParams.class
>>> One thing to note here is that the longest paths are all classes   
>>> generated by Geronimo, nested classes in wars or compiled JSP  
>>> pages.   Someone should look into makeing maven jar the latter  
>>> two and  Geronimo should be creating jars when generating classes  
>>> (actually we  should stop generating classes a head of time but  
>>> that is another  story).
>>> Breaking down the longest path, we have:
>>> GeronimoName (22)
>>>   geronimo-1.1-SNAPSHOT
>>> RepositoryPath (55)
>>>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
>>> FileName (39)
>>>   daytrader-derby-jetty-1.1-SNAPSHOT.car
>>> NestedPath (154)
>>>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/  
>>> apache/geronimo/axis/client/GenericServiceEndpointWrapper$  
>>> $EnhancerByCGLIB$$36344d29.class
>>> The first thing to note is if we simply replace "SNAPSHOT" with  
>>> "0",  we drop 28 characters which makes the longest path 242; not  
>>> enough  head room.  Of course, when we switch our groupId to the  
>>> maven  standard org.apache.geronimo we eat up 20 more  
>>> characters.  If we are  going to unpack war files there is very  
>>> little we can do about the  NestedPath, so we have very few  
>>> choices left.  If we simply combine  combine ${GeronimoName}/$ 
>>> {FileName}/${NestedPath} we are up to 115  characters leaving  
>>> only 41 characters for anything else, but when you  add back the  
>>> 28 from "SNAPSHOT", you get to a more comfortable level.
>>> I think if we combine this problem with Sachin's request for a   
>>> separate directory for applications, we could do something like  
>>> this:
>>> ${GeronimoName}/apps/${FileName}/${NestedPath}
>>> There are several problems with this.  I think users will confuse  
>>> the  hot-deploy directory "deploy" with the "apps" directory  
>>> [1].  Then  again, if you look at the problem configurations they  
>>> are all apps  the users may want to remove (sample apps and the  
>>> console), so may be  we should just put these in the hot-deploy  
>>> directory.  Another  problem is that it will be much more  
>>> difficult to query a repository  without a directory structure.   
>>> The server will basically have to  read the configuration from  
>>> these apps on startup to determine what  they are, so again we  
>>> may just want to use the hot-deploy directory.   I'm not a fan of  
>>> the hot-deploy directory, but I'm not sure there is  a better  
>>> solution.
>>> Again I renew my hate of Windows...
>>> /me shakes his fist at Bill Gates
>>> -dain
>>> [1] As a side issue, I prefer the name "apps" because it will be  
>>> most  familiar to tomcat users.
>


Re: Cannot build 1.1 on Windows - long file paths

Posted by Dain Sundstrom <da...@iq80.com>.
Please stop blaming the m2 repo structure for this problem.  The m2  
repo structure only increased the path of our longest path by 36  
characters.  The true problem is that David and I moved the unpacked  
configurations into the repository.  We did this because of the  
chunkiness of the numbered directories in the config-store  
directory.  The m2 repository structure makes querying the repository  
for version numbers possible and it is this querying that makes  
optional version numbers possible.

I think we have two issues that both must be addressed:

1) The ears we generate in our build have very long internal paths,  
154 characters.  This is just bad form, and vastly reduces the user  
path head room.

2) We need to move the unpacked ears our of the repository and into a  
separate flat directory structure.

I can look at the second one later today after fixing the redeploy  
command.  Can someone take a look at getting our build to jar up the  
classes and compiled jsps in our build.  I'll fix the generated  
classes in our build.

-dain

On Apr 7, 2006, at 6:50 AM, Matt Hogstrom wrote:

> Thinking about this some more I believe we need to make a good  
> decision here as having to revisit this issue in the future will  
> cause users to have to change how the server works.  I've been  
> talking to a new user that has a larger server farm and is very  
> interested in the Geronimo server as their new foundation.   
> However, they run a few thousand servers and are VERY sensitive to  
> changes in the behaviour of the server in terms of how it impacts  
> them.  Changes to the repsoistory will affect their operational  
> experience dramatically and they do run Windows (go Bill Gates).   
> They are watching this thread with keen interest.  Their biggest  
> concern is changing how their build and distribution system works  
> and changes in this area is highly disruptive for them.
>
> My view of the problem is that there are really three distinct  
> areas of a path.  They are the user area, the server area and the  
> application area.  Let me splain...
>
> | 0000000000000000000000000000 |  
> 11111111111111111111111111111111111111111 | 2222222222222222222 ...
> C:\my\directory\before\geronimo\geronimo-1.1\repository 
> \com.apache.geronimo\console-1.1\appArtifacts
>
> The area in the 0's are controlled by the user and we need to leave  
> more headroom than a few characters so they can manage multiple  
> deployments of Geronimo; this could include multiple versions or  
> multiple deployments.  The users probably enjoy flexibility in  
> naming as much as we do.  We don't have control over this but we  
> influence how much headroom is available.
>
> The 1's is really the area we have control over as this is the  
> server proper.  This includes the area from the top of the tree to  
> the end of where the files we create end.  So, for instance, this  
> includes var, repository, etc.  Since were currently experiencing  
> this problem in the respository I think we should focus on this area.
>
> Finally, the 2's are the area that include the application and  
> Maven dependent information.  The Maven naming convention is  
> verbose.  The current implementation needs to be changed, the  
> question is how and can the change survive several releases so that  
> our users are not forced to change their deployments on each  
> subsequent release.  *One immediate thought I had was to place  
> applications back into the config-store (or equivalent name).   
> Rather than simply use a number as we did previously perhaps the  
> configId of the deployment would be appropriate.  Its human  
> readable and would be shorter than the current maven structure.*  I  
> highlighted the previous as I think this is the best option based  
> on what I know today.
>
> Perhaps there some way to provide a Maven abstraction that would  
> map Maven dir names to an internal format for us.  I expect if we  
> are running into this its only a matter of time befoew other Maven  
> users experience the same issues.  For us its the nesting of Maven  
> articacts / configurations that is causing us the problem.  Jason,  
> thoughts?
>
> Whatever we decide we need to ensure that it is stable enough to  
> work for a period of time.
>
> Matt
>
>
> Dain Sundstrom wrote:
>> Man I hate Windows....
>> Anyway, if you have a real OS and list the files in an assembly,  
>> you  will see that the problem is caused by the combination of  
>> two  changes: we now keep configurations in the repository and we  
>> unpack  them. If you look closer you will see that the big  
>> offenders are  unpacked ears and wars.
>> I believe the following are the longest paths in the server:
>> (270)
>> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/ 
>> 1.1- SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader- 
>> web-1.1- SNAPSHOT.war/META-INF/geronimo-generated/org/apache/ 
>> geronimo/axis/ client/GenericServiceEndpointWrapper$ 
>> $EnhancerByCGLIB$$36344d29.class
>> (264)
>> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1-  
>> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console-  
>> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/ 
>> console/ databasemanager/wizard/DatabasePoolPortlet 
>> $ResourceAdapterParams.class
>> One thing to note here is that the longest paths are all classes   
>> generated by Geronimo, nested classes in wars or compiled JSP  
>> pages.   Someone should look into makeing maven jar the latter two  
>> and  Geronimo should be creating jars when generating classes  
>> (actually we  should stop generating classes a head of time but  
>> that is another  story).
>> Breaking down the longest path, we have:
>> GeronimoName (22)
>>   geronimo-1.1-SNAPSHOT
>> RepositoryPath (55)
>>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
>> FileName (39)
>>   daytrader-derby-jetty-1.1-SNAPSHOT.car
>> NestedPath (154)
>>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/  
>> apache/geronimo/axis/client/GenericServiceEndpointWrapper$  
>> $EnhancerByCGLIB$$36344d29.class
>> The first thing to note is if we simply replace "SNAPSHOT" with  
>> "0",  we drop 28 characters which makes the longest path 242; not  
>> enough  head room.  Of course, when we switch our groupId to the  
>> maven  standard org.apache.geronimo we eat up 20 more characters.   
>> If we are  going to unpack war files there is very little we can  
>> do about the  NestedPath, so we have very few choices left.  If we  
>> simply combine  combine ${GeronimoName}/${FileName}/${NestedPath}  
>> we are up to 115  characters leaving only 41 characters for  
>> anything else, but when you  add back the 28 from "SNAPSHOT", you  
>> get to a more comfortable level.
>> I think if we combine this problem with Sachin's request for a   
>> separate directory for applications, we could do something like this:
>> ${GeronimoName}/apps/${FileName}/${NestedPath}
>> There are several problems with this.  I think users will confuse  
>> the  hot-deploy directory "deploy" with the "apps" directory [1].   
>> Then  again, if you look at the problem configurations they are  
>> all apps  the users may want to remove (sample apps and the  
>> console), so may be  we should just put these in the hot-deploy  
>> directory.  Another  problem is that it will be much more  
>> difficult to query a repository  without a directory structure.   
>> The server will basically have to  read the configuration from  
>> these apps on startup to determine what  they are, so again we may  
>> just want to use the hot-deploy directory.   I'm not a fan of the  
>> hot-deploy directory, but I'm not sure there is  a better solution.
>> Again I renew my hate of Windows...
>> /me shakes his fist at Bill Gates
>> -dain
>> [1] As a side issue, I prefer the name "apps" because it will be  
>> most  familiar to tomcat users.


Re: Cannot build 1.1 on Windows - long file paths

Posted by Matt Hogstrom <ma...@hogstrom.org>.
Thinking about this some more I believe we need to make a good decision here as having to revisit 
this issue in the future will cause users to have to change how the server works.  I've been talking 
to a new user that has a larger server farm and is very interested in the Geronimo server as their 
new foundation.  However, they run a few thousand servers and are VERY sensitive to changes in the 
behaviour of the server in terms of how it impacts them.  Changes to the repsoistory will affect 
their operational experience dramatically and they do run Windows (go Bill Gates).  They are 
watching this thread with keen interest.  Their biggest concern is changing how their build and 
distribution system works and changes in this area is highly disruptive for them.

My view of the problem is that there are really three distinct areas of a path.  They are the user 
area, the server area and the application area.  Let me splain...

| 0000000000000000000000000000 | 11111111111111111111111111111111111111111 | 2222222222222222222 ...
C:\my\directory\before\geronimo\geronimo-1.1\repository\com.apache.geronimo\console-1.1\appArtifacts

The area in the 0's are controlled by the user and we need to leave more headroom than a few 
characters so they can manage multiple deployments of Geronimo; this could include multiple versions 
or multiple deployments.  The users probably enjoy flexibility in naming as much as we do.  We don't 
have control over this but we influence how much headroom is available.

The 1's is really the area we have control over as this is the server proper.  This includes the 
area from the top of the tree to the end of where the files we create end.  So, for instance, this 
includes var, repository, etc.  Since were currently experiencing this problem in the respository I 
think we should focus on this area.

Finally, the 2's are the area that include the application and Maven dependent information.  The 
Maven naming convention is verbose.  The current implementation needs to be changed, the question is 
how and can the change survive several releases so that our users are not forced to change their 
deployments on each subsequent release.  *One immediate thought I had was to place applications back 
into the config-store (or equivalent name).  Rather than simply use a number as we did previously 
perhaps the configId of the deployment would be appropriate.  Its human readable and would be 
shorter than the current maven structure.*  I highlighted the previous as I think this is the best 
option based on what I know today.

Perhaps there some way to provide a Maven abstraction that would map Maven dir names to an internal 
format for us.  I expect if we are running into this its only a matter of time befoew other Maven 
users experience the same issues.  For us its the nesting of Maven articacts / configurations that 
is causing us the problem.  Jason, thoughts?

Whatever we decide we need to ensure that it is stable enough to work for a period of time.

Matt


Dain Sundstrom wrote:
> Man I hate Windows....
> 
> Anyway, if you have a real OS and list the files in an assembly, you  
> will see that the problem is caused by the combination of two  changes: 
> we now keep configurations in the repository and we unpack  them. If you 
> look closer you will see that the big offenders are  unpacked ears and 
> wars.
> 
> I believe the following are the longest paths in the server:
> 
> (270)
> geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/1.1- 
> SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-web-1.1- 
> SNAPSHOT.war/META-INF/geronimo-generated/org/apache/geronimo/axis/ 
> client/GenericServiceEndpointWrapper$$EnhancerByCGLIB$$36344d29.class
> (264)
> geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1- 
> SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console- 
> standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/console/ 
> databasemanager/wizard/DatabasePoolPortlet$ResourceAdapterParams.class
> 
> 
> One thing to note here is that the longest paths are all classes  
> generated by Geronimo, nested classes in wars or compiled JSP pages.   
> Someone should look into makeing maven jar the latter two and  Geronimo 
> should be creating jars when generating classes (actually we  should 
> stop generating classes a head of time but that is another  story).
> 
> 
> 
> Breaking down the longest path, we have:
> 
> GeronimoName (22)
>   geronimo-1.1-SNAPSHOT
> RepositoryPath (55)
>   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
> FileName (39)
>   daytrader-derby-jetty-1.1-SNAPSHOT.car
> NestedPath (154)
>   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/ 
> apache/geronimo/axis/client/GenericServiceEndpointWrapper$ 
> $EnhancerByCGLIB$$36344d29.class
> 
> 
> 
> The first thing to note is if we simply replace "SNAPSHOT" with "0",  we 
> drop 28 characters which makes the longest path 242; not enough  head 
> room.  Of course, when we switch our groupId to the maven  standard 
> org.apache.geronimo we eat up 20 more characters.  If we are  going to 
> unpack war files there is very little we can do about the  NestedPath, 
> so we have very few choices left.  If we simply combine  combine 
> ${GeronimoName}/${FileName}/${NestedPath} we are up to 115  characters 
> leaving only 41 characters for anything else, but when you  add back the 
> 28 from "SNAPSHOT", you get to a more comfortable level.
> 
> I think if we combine this problem with Sachin's request for a  separate 
> directory for applications, we could do something like this:
> 
> ${GeronimoName}/apps/${FileName}/${NestedPath}
> 
> There are several problems with this.  I think users will confuse the  
> hot-deploy directory "deploy" with the "apps" directory [1].  Then  
> again, if you look at the problem configurations they are all apps  the 
> users may want to remove (sample apps and the console), so may be  we 
> should just put these in the hot-deploy directory.  Another  problem is 
> that it will be much more difficult to query a repository  without a 
> directory structure.  The server will basically have to  read the 
> configuration from these apps on startup to determine what  they are, so 
> again we may just want to use the hot-deploy directory.   I'm not a fan 
> of the hot-deploy directory, but I'm not sure there is  a better solution.
> 
> Again I renew my hate of Windows...
> /me shakes his fist at Bill Gates
> 
> -dain
> 
> 
> [1] As a side issue, I prefer the name "apps" because it will be most  
> familiar to tomcat users.
> 
> 
> 
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Dain Sundstrom <da...@iq80.com>.
Man I hate Windows....

Anyway, if you have a real OS and list the files in an assembly, you  
will see that the problem is caused by the combination of two  
changes: we now keep configurations in the repository and we unpack  
them. If you look closer you will see that the big offenders are  
unpacked ears and wars.

I believe the following are the longest paths in the server:

(270)
geronimo-1.1-SNAPSHOT/repository/geronimo/daytrader-derby-jetty/1.1- 
SNAPSHOT/daytrader-derby-jetty-1.1-SNAPSHOT.car/daytrader-web-1.1- 
SNAPSHOT.war/META-INF/geronimo-generated/org/apache/geronimo/axis/ 
client/GenericServiceEndpointWrapper$$EnhancerByCGLIB$$36344d29.class
(264)
geronimo-1.1-SNAPSHOT/repository/geronimo/webconsole-jetty/1.1- 
SNAPSHOT/webconsole-jetty-1.1-SNAPSHOT.car/geronimo-console- 
standard-1.1-SNAPSHOT.war/WEB-INF/classes/org/apache/geronimo/console/ 
databasemanager/wizard/DatabasePoolPortlet$ResourceAdapterParams.class


One thing to note here is that the longest paths are all classes  
generated by Geronimo, nested classes in wars or compiled JSP pages.   
Someone should look into makeing maven jar the latter two and  
Geronimo should be creating jars when generating classes (actually we  
should stop generating classes a head of time but that is another  
story).



Breaking down the longest path, we have:

GeronimoName (22)
   geronimo-1.1-SNAPSHOT
RepositoryPath (55)
   repository/geronimo/daytrader-derby-jetty/1.1-SNAPSHOT
FileName (39)
   daytrader-derby-jetty-1.1-SNAPSHOT.car
NestedPath (154)
   daytrader-web-1.1-SNAPSHOT.war/META-INF/geronimo-generated/org/ 
apache/geronimo/axis/client/GenericServiceEndpointWrapper$ 
$EnhancerByCGLIB$$36344d29.class



The first thing to note is if we simply replace "SNAPSHOT" with "0",  
we drop 28 characters which makes the longest path 242; not enough  
head room.  Of course, when we switch our groupId to the maven  
standard org.apache.geronimo we eat up 20 more characters.  If we are  
going to unpack war files there is very little we can do about the  
NestedPath, so we have very few choices left.  If we simply combine  
combine ${GeronimoName}/${FileName}/${NestedPath} we are up to 115  
characters leaving only 41 characters for anything else, but when you  
add back the 28 from "SNAPSHOT", you get to a more comfortable level.

I think if we combine this problem with Sachin's request for a  
separate directory for applications, we could do something like this:

${GeronimoName}/apps/${FileName}/${NestedPath}

There are several problems with this.  I think users will confuse the  
hot-deploy directory "deploy" with the "apps" directory [1].  Then  
again, if you look at the problem configurations they are all apps  
the users may want to remove (sample apps and the console), so may be  
we should just put these in the hot-deploy directory.  Another  
problem is that it will be much more difficult to query a repository  
without a directory structure.  The server will basically have to  
read the configuration from these apps on startup to determine what  
they are, so again we may just want to use the hot-deploy directory.   
I'm not a fan of the hot-deploy directory, but I'm not sure there is  
a better solution.

Again I renew my hate of Windows...
/me shakes his fist at Bill Gates

-dain


[1] As a side issue, I prefer the name "apps" because it will be most  
familiar to tomcat users.



Re: Cannot build 1.1 on Windows - long file paths

Posted by Matt Hogstrom <ma...@hogstrom.org>.
I'll modify my options below:

John Sisson wrote:
> Matt Hogstrom wrote:
> 
>> So the file that is in Dave's example is 268 characters long.  Here 
>> are a couple of questions that perhaps the folks using Windows can 
>> answer.
>>
>> 1. What about long-name support in Windows.  I thought MS had some way 
>> to shorten names...probably a Long Shot...but thought I'd try.
>>
> I don't think it would be safe going down this path.  Some users turn 
> may have turned off short file name generation using the "fsutil 
> behaviour set disable8dot3 1" command.
> 
> http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx?mfr=true 
> 
> 
>> 2. Can we leave CARs JARed up?  I think this may be the only way to 
>> get past the problem.
>>
> I agree that this seems to be the only way to keep the file paths at a 
> reasonable length (also so other Windows programs can work with the 
> files without troubles).  Is there a reason why are we using expanded 
> CARs in the repository?

After thinking about this a bit more the expanded CARs is really better for development as 
developers could update JSPs , etc directly.  If we leave the CAR in an archive format developers 
would have to expand them, update them and then archive them (or something other than modifying the 
directly).  I think I'd prefer option 3 but it sounds oddly like the old config-store 
concept...perhaps there is a middle ground.
> 
> John
> 
>> 3. The Maven jar naming convention is dramatically increasing the 
>> length of the file name.  The groupId and artifacts are repeated as is 
>> the version number.  For instance this takes up a lot of the realestate:
>>
>> So this:
>> \geronimo\webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class 
>>
>>
>> becomes:
>> \geronimo\10\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class 
>>
>>
>> and we have an entrie like this in an index.properties:
>> 10=webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\ 
>>
>>
>> This would save 109 characters in the path name.
>>
>> No matter what this is going to be a bit ugly.
>>
>> Thoughts?
>>
>>
>> Hernan Cunico wrote:
>>
>>> I am having basically the same issue building directly on Windows. 
>>> When the build gets to the izpack section it fails. I check the 
>>> assemblies\j2ee-installer\target directory and it cascades 
>>> recursively, in fact I am not able to delete that directory (yet).
>>>
>>> Any subsequent build attempts will also fail since maven will fail to 
>>> delete the target directory.
>>>
>>> Cheers!
>>> Hernan
>>>
>>> Dain Sundstrom wrote:
>>>
>>>> What if you unpack with jar -xf?
>>>>
>>>> -dain
>>>>
>>>> On Apr 6, 2006, at 1:07 PM, Dave Colasurdo wrote:
>>>>
>>>>> The "long file path" problem on the windows platform isn't limited  
>>>>> to building G1.1 on this platform.  The current images are  
>>>>> incompatible with windows even when the images are generated on a  
>>>>> different platform..
>>>>>
>>>>> Specifically, I built G1.1 on linux and then FTP'd the generated  
>>>>> windows image (geronimo-tomcat-j2ee-1.1-SNAPSHOT.zip) to a windows  
>>>>> machine..
>>>>>
>>>>> The resulting image can't unzip on the windows platform due to the  
>>>>> path length problem.. :(
>>>>>
>>>>> e.g. C:\z\geronimo-1.1-SNAPSHOT\repository\geronimo\webconsole- 
>>>>> tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo- 
>>>>> console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache 
>>>>> \geronimo\console\securitymanager\realm\SecurityRealmPortlet 
>>>>> $ExistingRealm.class
>>>>>
>>>>> Guess this is obvious in hindsight, though was thinking it was  
>>>>> strictly a build issue..
>>>>>
>>>>> This absolutely needs to get fixed..
>>>>>
>>>>> -Dave-
>>>>>
>>>>>
>>>>> Joe Bohn wrote:
>>>>>
>>>>>> You beat me to it John .... I'm hitting the exact same problem.
>>>>>> Joe
>>>>>> John Sisson wrote:
>>>>>>
>>>>>>> I had issues relating to long file paths when building 1.1 from  
>>>>>>> my C:\dev\asf\geronimo\branches\1.1 directory, so I tried  
>>>>>>> building from a shorter directory ( C:\geronimo1.1 ) and still  
>>>>>>> have issues (see below).
>>>>>>>
>>>>>>> I haven't had a chance to look into this yet but I consider this  
>>>>>>> to be a blocker.
>>>>>>>
>>>>>>> Once we can build on windows we then need to test that Geronimo  
>>>>>>> can be installed in common locations on windows (e.g. under C: 
>>>>>>> \Program Files\Geronimo-1.1 ) without encountering file path  
>>>>>>> length issues.
>>>>>>>
>>>>>>> The following path (from the output below) is 317 bytes long:
>>>>>>>
>>>>>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1- 
>>>>>>> SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT 
>>>>>>> \daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1- 
>>>>>>> SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis 
>>>>>>> \client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>>>> $2ae63e1d.class
>>>>>>>
>>>>>>> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more  
>>>>>>> info on the long file path issue.
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> izpack:izpack-installer-build:
>>>>>>>    [echo] IZPack installer build is running.
>>>>>>>    [echo] IZPack Version is 3.8.0
>>>>>>>    [java]
>>>>>>>    [java] .::  IzPack - Version 3.8.0 ::.
>>>>>>>    [java]
>>>>>>>    [java] < compiler specifications version : 1.0 >
>>>>>>>    [java]
>>>>>>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>>>>>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>>>>>>    [java] - Released under the terms of the Apache Software  
>>>>>>> License version 2.0.
>>>>>>>    [java]
>>>>>>>    [java] -> Processing  : C:\geronimo1.1\assemblies\j2ee- 
>>>>>>> installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>>>>>>>    [java] -> Output      : C:\geronimo1.1\assemblies\j2ee- 
>>>>>>> installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>>>>>>>    [java] -> Base path   : .
>>>>>>>    [java] -> Kind        : standard
>>>>>>>    [java] -> Compression : default
>>>>>>>    [java] -> Compr. level: -1
>>>>>>>    [java]
>>>>>>>    [java] Adding resource: IzPack.uninstaller
>>>>>>>    [java] Setting the installer information
>>>>>>>    [java] Setting the GUI preferences
>>>>>>>    [java] Adding langpack: eng
>>>>>>>    [java] Adding resource: flag.eng
>>>>>>>    [java] Adding resource: Installer.image
>>>>>>>    [java] Adding resource: LicencePanel.licence
>>>>>>>    [java] Adding resource: InfoPanel.info
>>>>>>>    [java] Adding resource: userInputSpec.xml
>>>>>>>    [java] Adding resource: ProcessPanel.Spec.xml
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.0
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.1
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.2
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.3
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.4
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.5
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.6
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.7
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.8
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.9
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.10
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.11
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.12
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.13
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.14
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.15
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.16
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.17
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.18
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.19
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.20
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>>>>>>    [java] -> Fatal error :
>>>>>>>    [java]    C:\geronimo1.1\assemblies\j2ee-installer/target/ 
>>>>>>> geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: C:\geronimo1.1 
>>>>>>> \assemblie
>>>>>>> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo 
>>>>>>> \daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
>>>>>>> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated 
>>>>>>> \org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
>>>>>>> hancerByCGLIB$$2ae63e1d.class
>>>>>>>    [java] com.izforge.izpack.compiler.CompilerException: C: 
>>>>>>> \geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1- 
>>>>>>> SNAPSHOT/gero
>>>>>>> nimo-izpack.xml:96: C:\geronimo1.1\assemblies\j2ee-installer 
>>>>>>> \target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby- 
>>>>>>> jetty\
>>>>>>> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader- 
>>>>>>> web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache 
>>>>>>> \geronimo\a
>>>>>>> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>>>> $2ae63e1d.class
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.parseError 
>>>>>>> (CompilerConfig.java:1531)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>>>> (CompilerConfig.java:636)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.executeCompiler 
>>>>>>> (CompilerConfig.java:317)
>>>>>>>    [java]      at com.izforge.izpack.compiler.CompilerConfig.main 
>>>>>>> (CompilerConfig.java:1847)
>>>>>>>    [java]      at com.izforge.izpack.compiler.Compiler.main 
>>>>>>> (Compiler.java:620)
>>>>>>>    [java] Caused by: java.io.FileNotFoundException: 
>>>>>>> C:\geronimo1.1 
>>>>>>> \assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
>>>>>>> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby- 
>>>>>>> jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF 
>>>>>>> \geronim
>>>>>>> o-generated\org\apache\geronimo\axis\client 
>>>>>>> \GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>>>>>>    [java]      at com.izforge.izpack.compiler.PackInfo.addFile 
>>>>>>> (PackInfo.java:193)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:959)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>>>> (CompilerConfig.java:632)
>>>>>>>    [java]      ... 3 more
>>>>>>>    [java]
>>>>>>>    [java] (tip : use -? to get the commmand line parameters)
>>>>>>>    [java] [ERROR] Java Result: 1
>>>>>>>
>>>>>>> BUILD FAILED
>>>>>>> File...... C:\geronimo1.1\maven.xml
>>>>>>> Element... maven:reactor
>>>>>>> Line...... 63
>>>>>>> Column.... -1
>>>>>>> Unable to obtain goal [multiproject:install-callback] -- C: 
>>>>>>> \Documents and Settings\sissonj\.geronimo-1.1.x-maven\cache 
>>>>>>> \geronimo-izpa
>>>>>>> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning:  
>>>>>>> Could not find file C:\geronimo1.1\assemblies\j2ee-installer 
>>>>>>> \target\g
>>>>>>> eronimo-installer-1.1-SNAPSHOT.jar to copy.
>>>>>>> Total time   : 21 minutes 1 seconds
>>>>>>> Finished at  : Tuesday, 4 April 2006 17:31:34
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
> 
> 
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Paul McMahan <pa...@gmail.com>.
On 4/6/06, John Sisson <jr...@gmail.com> wrote:
> I think a reason why we are using expanded CARs could be so that users
> can edit web app files directly in the repository, as discussed in
> Sachin's recent "1.1 repo/configstore" thread.

Right -- I rely on this feature for editing JSPs without having to
restart the server, and for softlinking the web-inf/classes directory
to my project's target/classes directory so I can avoid redeploy
between code changes.  I would miss it if it were gone but realize of
course that the windows path problem is more important :-)

Best wishes,
Paul

Re: Cannot build 1.1 on Windows - long file paths

Posted by John Sisson <jr...@gmail.com>.

John Sisson wrote:
> Matt Hogstrom wrote:
>> So the file that is in Dave's example is 268 characters long.  Here 
>> are a couple of questions that perhaps the folks using Windows can 
>> answer.
>>
>> 1. What about long-name support in Windows.  I thought MS had some way 
>> to shorten names...probably a Long Shot...but thought I'd try.
>>
> I don't think it would be safe going down this path.  Some users turn 
> may have turned off short file name generation using the "fsutil 
> behaviour set disable8dot3 1" command.
> 
> http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx?mfr=true 
> 
> 
>> 2. Can we leave CARs JARed up?  I think this may be the only way to 
>> get past the problem.
>>
> I agree that this seems to be the only way to keep the file paths at a 
> reasonable length (also so other Windows programs can work with the 
> files without troubles).  Is there a reason why are we using expanded 
> CARs in the repository?

I think a reason why we are using expanded CARs could be so that users 
can edit web app files directly in the repository, as discussed in 
Sachin's recent "1.1 repo/configstore" thread.

John

> 
> John
>> 3. The Maven jar naming convention is dramatically increasing the 
>> length of the file name.  The groupId and artifacts are repeated as is 
>> the version number.  For instance this takes up a lot of the realestate:
>>
>> So this:
>> \geronimo\webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class 
>>
>>
>> becomes:
>> \geronimo\10\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class 
>>
>>
>> and we have an entrie like this in an index.properties:
>> 10=webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\ 
>>
>>
>> This would save 109 characters in the path name.
>>
>> No matter what this is going to be a bit ugly.
>>
>> Thoughts?
>>
>>
>> Hernan Cunico wrote:
>>> I am having basically the same issue building directly on Windows. 
>>> When the build gets to the izpack section it fails. I check the 
>>> assemblies\j2ee-installer\target directory and it cascades 
>>> recursively, in fact I am not able to delete that directory (yet).
>>>
>>> Any subsequent build attempts will also fail since maven will fail to 
>>> delete the target directory.
>>>
>>> Cheers!
>>> Hernan
>>>
>>> Dain Sundstrom wrote:
>>>
>>>> What if you unpack with jar -xf?
>>>>
>>>> -dain
>>>>
>>>> On Apr 6, 2006, at 1:07 PM, Dave Colasurdo wrote:
>>>>
>>>>> The "long file path" problem on the windows platform isn't limited  
>>>>> to building G1.1 on this platform.  The current images are  
>>>>> incompatible with windows even when the images are generated on a  
>>>>> different platform..
>>>>>
>>>>> Specifically, I built G1.1 on linux and then FTP'd the generated  
>>>>> windows image (geronimo-tomcat-j2ee-1.1-SNAPSHOT.zip) to a windows  
>>>>> machine..
>>>>>
>>>>> The resulting image can't unzip on the windows platform due to the  
>>>>> path length problem.. :(
>>>>>
>>>>> e.g. C:\z\geronimo-1.1-SNAPSHOT\repository\geronimo\webconsole- 
>>>>> tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo- 
>>>>> console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache 
>>>>> \geronimo\console\securitymanager\realm\SecurityRealmPortlet 
>>>>> $ExistingRealm.class
>>>>>
>>>>> Guess this is obvious in hindsight, though was thinking it was  
>>>>> strictly a build issue..
>>>>>
>>>>> This absolutely needs to get fixed..
>>>>>
>>>>> -Dave-
>>>>>
>>>>>
>>>>> Joe Bohn wrote:
>>>>>
>>>>>> You beat me to it John .... I'm hitting the exact same problem.
>>>>>> Joe
>>>>>> John Sisson wrote:
>>>>>>
>>>>>>> I had issues relating to long file paths when building 1.1 from  
>>>>>>> my C:\dev\asf\geronimo\branches\1.1 directory, so I tried  
>>>>>>> building from a shorter directory ( C:\geronimo1.1 ) and still  
>>>>>>> have issues (see below).
>>>>>>>
>>>>>>> I haven't had a chance to look into this yet but I consider this  
>>>>>>> to be a blocker.
>>>>>>>
>>>>>>> Once we can build on windows we then need to test that Geronimo  
>>>>>>> can be installed in common locations on windows (e.g. under C: 
>>>>>>> \Program Files\Geronimo-1.1 ) without encountering file path  
>>>>>>> length issues.
>>>>>>>
>>>>>>> The following path (from the output below) is 317 bytes long:
>>>>>>>
>>>>>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1- 
>>>>>>> SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT 
>>>>>>> \daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1- 
>>>>>>> SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis 
>>>>>>> \client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>>>> $2ae63e1d.class
>>>>>>>
>>>>>>> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more  
>>>>>>> info on the long file path issue.
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> izpack:izpack-installer-build:
>>>>>>>    [echo] IZPack installer build is running.
>>>>>>>    [echo] IZPack Version is 3.8.0
>>>>>>>    [java]
>>>>>>>    [java] .::  IzPack - Version 3.8.0 ::.
>>>>>>>    [java]
>>>>>>>    [java] < compiler specifications version : 1.0 >
>>>>>>>    [java]
>>>>>>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>>>>>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>>>>>>    [java] - Released under the terms of the Apache Software  
>>>>>>> License version 2.0.
>>>>>>>    [java]
>>>>>>>    [java] -> Processing  : C:\geronimo1.1\assemblies\j2ee- 
>>>>>>> installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>>>>>>>    [java] -> Output      : C:\geronimo1.1\assemblies\j2ee- 
>>>>>>> installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>>>>>>>    [java] -> Base path   : .
>>>>>>>    [java] -> Kind        : standard
>>>>>>>    [java] -> Compression : default
>>>>>>>    [java] -> Compr. level: -1
>>>>>>>    [java]
>>>>>>>    [java] Adding resource: IzPack.uninstaller
>>>>>>>    [java] Setting the installer information
>>>>>>>    [java] Setting the GUI preferences
>>>>>>>    [java] Adding langpack: eng
>>>>>>>    [java] Adding resource: flag.eng
>>>>>>>    [java] Adding resource: Installer.image
>>>>>>>    [java] Adding resource: LicencePanel.licence
>>>>>>>    [java] Adding resource: InfoPanel.info
>>>>>>>    [java] Adding resource: userInputSpec.xml
>>>>>>>    [java] Adding resource: ProcessPanel.Spec.xml
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.0
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.1
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.2
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.3
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.4
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.5
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.6
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.7
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.8
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.9
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.10
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.11
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.12
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.13
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.14
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.15
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.16
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.17
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.18
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.19
>>>>>>>    [java] Adding resource: ImgPacksPanel.img.20
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>>> standal
>>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>>>>>>    [java] -> Fatal error :
>>>>>>>    [java]    C:\geronimo1.1\assemblies\j2ee-installer/target/ 
>>>>>>> geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: C:\geronimo1.1 
>>>>>>> \assemblie
>>>>>>> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo 
>>>>>>> \daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
>>>>>>> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated 
>>>>>>> \org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
>>>>>>> hancerByCGLIB$$2ae63e1d.class
>>>>>>>    [java] com.izforge.izpack.compiler.CompilerException: C: 
>>>>>>> \geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1- 
>>>>>>> SNAPSHOT/gero
>>>>>>> nimo-izpack.xml:96: C:\geronimo1.1\assemblies\j2ee-installer 
>>>>>>> \target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby- 
>>>>>>> jetty\
>>>>>>> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader- 
>>>>>>> web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache 
>>>>>>> \geronimo\a
>>>>>>> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>>>> $2ae63e1d.class
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.parseError 
>>>>>>> (CompilerConfig.java:1531)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>>>> (CompilerConfig.java:636)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.executeCompiler 
>>>>>>> (CompilerConfig.java:317)
>>>>>>>    [java]      at com.izforge.izpack.compiler.CompilerConfig.main 
>>>>>>> (CompilerConfig.java:1847)
>>>>>>>    [java]      at com.izforge.izpack.compiler.Compiler.main 
>>>>>>> (Compiler.java:620)
>>>>>>>    [java] Caused by: java.io.FileNotFoundException: 
>>>>>>> C:\geronimo1.1 
>>>>>>> \assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
>>>>>>> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby- 
>>>>>>> jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF 
>>>>>>> \geronim
>>>>>>> o-generated\org\apache\geronimo\axis\client 
>>>>>>> \GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>>>>>>    [java]      at com.izforge.izpack.compiler.PackInfo.addFile 
>>>>>>> (PackInfo.java:193)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:959)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>>> (CompilerConfig.java:969)
>>>>>>>    [java]      at  
>>>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>>>> (CompilerConfig.java:632)
>>>>>>>    [java]      ... 3 more
>>>>>>>    [java]
>>>>>>>    [java] (tip : use -? to get the commmand line parameters)
>>>>>>>    [java] [ERROR] Java Result: 1
>>>>>>>
>>>>>>> BUILD FAILED
>>>>>>> File...... C:\geronimo1.1\maven.xml
>>>>>>> Element... maven:reactor
>>>>>>> Line...... 63
>>>>>>> Column.... -1
>>>>>>> Unable to obtain goal [multiproject:install-callback] -- C: 
>>>>>>> \Documents and Settings\sissonj\.geronimo-1.1.x-maven\cache 
>>>>>>> \geronimo-izpa
>>>>>>> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning:  
>>>>>>> Could not find file C:\geronimo1.1\assemblies\j2ee-installer 
>>>>>>> \target\g
>>>>>>> eronimo-installer-1.1-SNAPSHOT.jar to copy.
>>>>>>> Total time   : 21 minutes 1 seconds
>>>>>>> Finished at  : Tuesday, 4 April 2006 17:31:34
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by John Sisson <jr...@gmail.com>.
Matt Hogstrom wrote:
> So the file that is in Dave's example is 268 characters long.  Here 
> are a couple of questions that perhaps the folks using Windows can 
> answer.
>
> 1. What about long-name support in Windows.  I thought MS had some way 
> to shorten names...probably a Long Shot...but thought I'd try.
>
I don't think it would be safe going down this path.  Some users turn 
may have turned off short file name generation using the "fsutil 
behaviour set disable8dot3 1" command.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx?mfr=true

> 2. Can we leave CARs JARed up?  I think this may be the only way to 
> get past the problem.
>
I agree that this seems to be the only way to keep the file paths at a 
reasonable length (also so other Windows programs can work with the 
files without troubles).  Is there a reason why are we using expanded 
CARs in the repository?

John
> 3. The Maven jar naming convention is dramatically increasing the 
> length of the file name.  The groupId and artifacts are repeated as is 
> the version number.  For instance this takes up a lot of the realestate:
>
> So this:
> \geronimo\webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class 
>
>
> becomes:
> \geronimo\10\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class 
>
>
> and we have an entrie like this in an index.properties:
> 10=webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\ 
>
>
> This would save 109 characters in the path name.
>
> No matter what this is going to be a bit ugly.
>
> Thoughts?
>
>
> Hernan Cunico wrote:
>> I am having basically the same issue building directly on Windows. 
>> When the build gets to the izpack section it fails. I check the 
>> assemblies\j2ee-installer\target directory and it cascades 
>> recursively, in fact I am not able to delete that directory (yet).
>>
>> Any subsequent build attempts will also fail since maven will fail to 
>> delete the target directory.
>>
>> Cheers!
>> Hernan
>>
>> Dain Sundstrom wrote:
>>
>>> What if you unpack with jar -xf?
>>>
>>> -dain
>>>
>>> On Apr 6, 2006, at 1:07 PM, Dave Colasurdo wrote:
>>>
>>>> The "long file path" problem on the windows platform isn't limited  
>>>> to building G1.1 on this platform.  The current images are  
>>>> incompatible with windows even when the images are generated on a  
>>>> different platform..
>>>>
>>>> Specifically, I built G1.1 on linux and then FTP'd the generated  
>>>> windows image (geronimo-tomcat-j2ee-1.1-SNAPSHOT.zip) to a windows  
>>>> machine..
>>>>
>>>> The resulting image can't unzip on the windows platform due to the  
>>>> path length problem.. :(
>>>>
>>>> e.g. C:\z\geronimo-1.1-SNAPSHOT\repository\geronimo\webconsole- 
>>>> tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo- 
>>>> console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache 
>>>> \geronimo\console\securitymanager\realm\SecurityRealmPortlet 
>>>> $ExistingRealm.class
>>>>
>>>> Guess this is obvious in hindsight, though was thinking it was  
>>>> strictly a build issue..
>>>>
>>>> This absolutely needs to get fixed..
>>>>
>>>> -Dave-
>>>>
>>>>
>>>> Joe Bohn wrote:
>>>>
>>>>> You beat me to it John .... I'm hitting the exact same problem.
>>>>> Joe
>>>>> John Sisson wrote:
>>>>>
>>>>>> I had issues relating to long file paths when building 1.1 from  
>>>>>> my C:\dev\asf\geronimo\branches\1.1 directory, so I tried  
>>>>>> building from a shorter directory ( C:\geronimo1.1 ) and still  
>>>>>> have issues (see below).
>>>>>>
>>>>>> I haven't had a chance to look into this yet but I consider this  
>>>>>> to be a blocker.
>>>>>>
>>>>>> Once we can build on windows we then need to test that Geronimo  
>>>>>> can be installed in common locations on windows (e.g. under C: 
>>>>>> \Program Files\Geronimo-1.1 ) without encountering file path  
>>>>>> length issues.
>>>>>>
>>>>>> The following path (from the output below) is 317 bytes long:
>>>>>>
>>>>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1- 
>>>>>> SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT 
>>>>>> \daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1- 
>>>>>> SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis 
>>>>>> \client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>>> $2ae63e1d.class
>>>>>>
>>>>>> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more  
>>>>>> info on the long file path issue.
>>>>>>
>>>>>> John
>>>>>>
>>>>>> izpack:izpack-installer-build:
>>>>>>    [echo] IZPack installer build is running.
>>>>>>    [echo] IZPack Version is 3.8.0
>>>>>>    [java]
>>>>>>    [java] .::  IzPack - Version 3.8.0 ::.
>>>>>>    [java]
>>>>>>    [java] < compiler specifications version : 1.0 >
>>>>>>    [java]
>>>>>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>>>>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>>>>>    [java] - Released under the terms of the Apache Software  
>>>>>> License version 2.0.
>>>>>>    [java]
>>>>>>    [java] -> Processing  : C:\geronimo1.1\assemblies\j2ee- 
>>>>>> installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>>>>>>    [java] -> Output      : C:\geronimo1.1\assemblies\j2ee- 
>>>>>> installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>>>>>>    [java] -> Base path   : .
>>>>>>    [java] -> Kind        : standard
>>>>>>    [java] -> Compression : default
>>>>>>    [java] -> Compr. level: -1
>>>>>>    [java]
>>>>>>    [java] Adding resource: IzPack.uninstaller
>>>>>>    [java] Setting the installer information
>>>>>>    [java] Setting the GUI preferences
>>>>>>    [java] Adding langpack: eng
>>>>>>    [java] Adding resource: flag.eng
>>>>>>    [java] Adding resource: Installer.image
>>>>>>    [java] Adding resource: LicencePanel.licence
>>>>>>    [java] Adding resource: InfoPanel.info
>>>>>>    [java] Adding resource: userInputSpec.xml
>>>>>>    [java] Adding resource: ProcessPanel.Spec.xml
>>>>>>    [java] Adding resource: ImgPacksPanel.img.0
>>>>>>    [java] Adding resource: ImgPacksPanel.img.1
>>>>>>    [java] Adding resource: ImgPacksPanel.img.2
>>>>>>    [java] Adding resource: ImgPacksPanel.img.3
>>>>>>    [java] Adding resource: ImgPacksPanel.img.4
>>>>>>    [java] Adding resource: ImgPacksPanel.img.5
>>>>>>    [java] Adding resource: ImgPacksPanel.img.6
>>>>>>    [java] Adding resource: ImgPacksPanel.img.7
>>>>>>    [java] Adding resource: ImgPacksPanel.img.8
>>>>>>    [java] Adding resource: ImgPacksPanel.img.9
>>>>>>    [java] Adding resource: ImgPacksPanel.img.10
>>>>>>    [java] Adding resource: ImgPacksPanel.img.11
>>>>>>    [java] Adding resource: ImgPacksPanel.img.12
>>>>>>    [java] Adding resource: ImgPacksPanel.img.13
>>>>>>    [java] Adding resource: ImgPacksPanel.img.14
>>>>>>    [java] Adding resource: ImgPacksPanel.img.15
>>>>>>    [java] Adding resource: ImgPacksPanel.img.16
>>>>>>    [java] Adding resource: ImgPacksPanel.img.17
>>>>>>    [java] Adding resource: ImgPacksPanel.img.18
>>>>>>    [java] Adding resource: ImgPacksPanel.img.19
>>>>>>    [java] Adding resource: ImgPacksPanel.img.20
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>>> standal
>>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>>>>>    [java] -> Fatal error :
>>>>>>    [java]    C:\geronimo1.1\assemblies\j2ee-installer/target/ 
>>>>>> geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: C:\geronimo1.1 
>>>>>> \assemblie
>>>>>> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo 
>>>>>> \daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
>>>>>> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated 
>>>>>> \org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
>>>>>> hancerByCGLIB$$2ae63e1d.class
>>>>>>    [java] com.izforge.izpack.compiler.CompilerException: C: 
>>>>>> \geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1- 
>>>>>> SNAPSHOT/gero
>>>>>> nimo-izpack.xml:96: C:\geronimo1.1\assemblies\j2ee-installer 
>>>>>> \target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby- 
>>>>>> jetty\
>>>>>> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader- 
>>>>>> web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache 
>>>>>> \geronimo\a
>>>>>> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>>> $2ae63e1d.class
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.parseError 
>>>>>> (CompilerConfig.java:1531)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>>> (CompilerConfig.java:636)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.executeCompiler 
>>>>>> (CompilerConfig.java:317)
>>>>>>    [java]      at com.izforge.izpack.compiler.CompilerConfig.main 
>>>>>> (CompilerConfig.java:1847)
>>>>>>    [java]      at com.izforge.izpack.compiler.Compiler.main 
>>>>>> (Compiler.java:620)
>>>>>>    [java] Caused by: java.io.FileNotFoundException: 
>>>>>> C:\geronimo1.1 
>>>>>> \assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
>>>>>> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby- 
>>>>>> jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF 
>>>>>> \geronim
>>>>>> o-generated\org\apache\geronimo\axis\client 
>>>>>> \GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>>>>>    [java]      at com.izforge.izpack.compiler.PackInfo.addFile 
>>>>>> (PackInfo.java:193)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:959)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>>> (CompilerConfig.java:969)
>>>>>>    [java]      at  
>>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>>> (CompilerConfig.java:632)
>>>>>>    [java]      ... 3 more
>>>>>>    [java]
>>>>>>    [java] (tip : use -? to get the commmand line parameters)
>>>>>>    [java] [ERROR] Java Result: 1
>>>>>>
>>>>>> BUILD FAILED
>>>>>> File...... C:\geronimo1.1\maven.xml
>>>>>> Element... maven:reactor
>>>>>> Line...... 63
>>>>>> Column.... -1
>>>>>> Unable to obtain goal [multiproject:install-callback] -- C: 
>>>>>> \Documents and Settings\sissonj\.geronimo-1.1.x-maven\cache 
>>>>>> \geronimo-izpa
>>>>>> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning:  
>>>>>> Could not find file C:\geronimo1.1\assemblies\j2ee-installer 
>>>>>> \target\g
>>>>>> eronimo-installer-1.1-SNAPSHOT.jar to copy.
>>>>>> Total time   : 21 minutes 1 seconds
>>>>>> Finished at  : Tuesday, 4 April 2006 17:31:34
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>
>>>
>>
>>
>>
>


Re: Cannot build 1.1 on Windows - long file paths

Posted by Matt Hogstrom <ma...@hogstrom.org>.
So the file that is in Dave's example is 268 characters long.  Here are a couple of questions that 
perhaps the folks using Windows can answer.

1. What about long-name support in Windows.  I thought MS had some way to shorten names...probably a 
Long Shot...but thought I'd try.

2. Can we leave CARs JARed up?  I think this may be the only way to get past the problem.

3. The Maven jar naming convention is dramatically increasing the length of the file name.  The 
groupId and artifacts are repeated as is the version number.  For instance this takes up a lot of 
the realestate:

So this:
\geronimo\webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class

becomes:
\geronimo\10\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class

and we have an entrie like this in an index.properties:
10=webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\

This would save 109 characters in the path name.

No matter what this is going to be a bit ugly.

Thoughts?


Hernan Cunico wrote:
> I am having basically the same issue building directly on Windows. When 
> the build gets to the izpack section it fails. I check the 
> assemblies\j2ee-installer\target directory and it cascades recursively, 
> in fact I am not able to delete that directory (yet).
> 
> Any subsequent build attempts will also fail since maven will fail to 
> delete the target directory.
> 
> Cheers!
> Hernan
> 
> Dain Sundstrom wrote:
> 
>> What if you unpack with jar -xf?
>>
>> -dain
>>
>> On Apr 6, 2006, at 1:07 PM, Dave Colasurdo wrote:
>>
>>> The "long file path" problem on the windows platform isn't limited  
>>> to building G1.1 on this platform.  The current images are  
>>> incompatible with windows even when the images are generated on a  
>>> different platform..
>>>
>>> Specifically, I built G1.1 on linux and then FTP'd the generated  
>>> windows image (geronimo-tomcat-j2ee-1.1-SNAPSHOT.zip) to a windows  
>>> machine..
>>>
>>> The resulting image can't unzip on the windows platform due to the  
>>> path length problem.. :(
>>>
>>> e.g. C:\z\geronimo-1.1-SNAPSHOT\repository\geronimo\webconsole- 
>>> tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo- 
>>> console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache 
>>> \geronimo\console\securitymanager\realm\SecurityRealmPortlet 
>>> $ExistingRealm.class
>>>
>>> Guess this is obvious in hindsight, though was thinking it was  
>>> strictly a build issue..
>>>
>>> This absolutely needs to get fixed..
>>>
>>> -Dave-
>>>
>>>
>>> Joe Bohn wrote:
>>>
>>>> You beat me to it John .... I'm hitting the exact same problem.
>>>> Joe
>>>> John Sisson wrote:
>>>>
>>>>> I had issues relating to long file paths when building 1.1 from  my 
>>>>> C:\dev\asf\geronimo\branches\1.1 directory, so I tried  building 
>>>>> from a shorter directory ( C:\geronimo1.1 ) and still  have issues 
>>>>> (see below).
>>>>>
>>>>> I haven't had a chance to look into this yet but I consider this  
>>>>> to be a blocker.
>>>>>
>>>>> Once we can build on windows we then need to test that Geronimo  
>>>>> can be installed in common locations on windows (e.g. under C: 
>>>>> \Program Files\Geronimo-1.1 ) without encountering file path  
>>>>> length issues.
>>>>>
>>>>> The following path (from the output below) is 317 bytes long:
>>>>>
>>>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1- 
>>>>> SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT 
>>>>> \daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1- 
>>>>> SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis 
>>>>> \client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>> $2ae63e1d.class
>>>>>
>>>>> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more  
>>>>> info on the long file path issue.
>>>>>
>>>>> John
>>>>>
>>>>> izpack:izpack-installer-build:
>>>>>    [echo] IZPack installer build is running.
>>>>>    [echo] IZPack Version is 3.8.0
>>>>>    [java]
>>>>>    [java] .::  IzPack - Version 3.8.0 ::.
>>>>>    [java]
>>>>>    [java] < compiler specifications version : 1.0 >
>>>>>    [java]
>>>>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>>>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>>>>    [java] - Released under the terms of the Apache Software  
>>>>> License version 2.0.
>>>>>    [java]
>>>>>    [java] -> Processing  : C:\geronimo1.1\assemblies\j2ee- 
>>>>> installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>>>>>    [java] -> Output      : C:\geronimo1.1\assemblies\j2ee- 
>>>>> installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>>>>>    [java] -> Base path   : .
>>>>>    [java] -> Kind        : standard
>>>>>    [java] -> Compression : default
>>>>>    [java] -> Compr. level: -1
>>>>>    [java]
>>>>>    [java] Adding resource: IzPack.uninstaller
>>>>>    [java] Setting the installer information
>>>>>    [java] Setting the GUI preferences
>>>>>    [java] Adding langpack: eng
>>>>>    [java] Adding resource: flag.eng
>>>>>    [java] Adding resource: Installer.image
>>>>>    [java] Adding resource: LicencePanel.licence
>>>>>    [java] Adding resource: InfoPanel.info
>>>>>    [java] Adding resource: userInputSpec.xml
>>>>>    [java] Adding resource: ProcessPanel.Spec.xml
>>>>>    [java] Adding resource: ImgPacksPanel.img.0
>>>>>    [java] Adding resource: ImgPacksPanel.img.1
>>>>>    [java] Adding resource: ImgPacksPanel.img.2
>>>>>    [java] Adding resource: ImgPacksPanel.img.3
>>>>>    [java] Adding resource: ImgPacksPanel.img.4
>>>>>    [java] Adding resource: ImgPacksPanel.img.5
>>>>>    [java] Adding resource: ImgPacksPanel.img.6
>>>>>    [java] Adding resource: ImgPacksPanel.img.7
>>>>>    [java] Adding resource: ImgPacksPanel.img.8
>>>>>    [java] Adding resource: ImgPacksPanel.img.9
>>>>>    [java] Adding resource: ImgPacksPanel.img.10
>>>>>    [java] Adding resource: ImgPacksPanel.img.11
>>>>>    [java] Adding resource: ImgPacksPanel.img.12
>>>>>    [java] Adding resource: ImgPacksPanel.img.13
>>>>>    [java] Adding resource: ImgPacksPanel.img.14
>>>>>    [java] Adding resource: ImgPacksPanel.img.15
>>>>>    [java] Adding resource: ImgPacksPanel.img.16
>>>>>    [java] Adding resource: ImgPacksPanel.img.17
>>>>>    [java] Adding resource: ImgPacksPanel.img.18
>>>>>    [java] Adding resource: ImgPacksPanel.img.19
>>>>>    [java] Adding resource: ImgPacksPanel.img.20
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>>> standal
>>>>> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>>>>    [java] -> Fatal error :
>>>>>    [java]    C:\geronimo1.1\assemblies\j2ee-installer/target/ 
>>>>> geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: C:\geronimo1.1 
>>>>> \assemblie
>>>>> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo 
>>>>> \daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
>>>>> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated 
>>>>> \org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
>>>>> hancerByCGLIB$$2ae63e1d.class
>>>>>    [java] com.izforge.izpack.compiler.CompilerException: C: 
>>>>> \geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1- 
>>>>> SNAPSHOT/gero
>>>>> nimo-izpack.xml:96: C:\geronimo1.1\assemblies\j2ee-installer 
>>>>> \target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby- 
>>>>> jetty\
>>>>> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader- 
>>>>> web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache 
>>>>> \geronimo\a
>>>>> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>>> $2ae63e1d.class
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.parseError 
>>>>> (CompilerConfig.java:1531)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>> (CompilerConfig.java:636)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.executeCompiler 
>>>>> (CompilerConfig.java:317)
>>>>>    [java]      at com.izforge.izpack.compiler.CompilerConfig.main 
>>>>> (CompilerConfig.java:1847)
>>>>>    [java]      at com.izforge.izpack.compiler.Compiler.main 
>>>>> (Compiler.java:620)
>>>>>    [java] Caused by: java.io.FileNotFoundException: C:\geronimo1.1 
>>>>> \assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
>>>>> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby- 
>>>>> jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF 
>>>>> \geronim
>>>>> o-generated\org\apache\geronimo\axis\client 
>>>>> \GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>>>>    [java]      at com.izforge.izpack.compiler.PackInfo.addFile 
>>>>> (PackInfo.java:193)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:959)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>>> (CompilerConfig.java:969)
>>>>>    [java]      at  
>>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>>> (CompilerConfig.java:632)
>>>>>    [java]      ... 3 more
>>>>>    [java]
>>>>>    [java] (tip : use -? to get the commmand line parameters)
>>>>>    [java] [ERROR] Java Result: 1
>>>>>
>>>>> BUILD FAILED
>>>>> File...... C:\geronimo1.1\maven.xml
>>>>> Element... maven:reactor
>>>>> Line...... 63
>>>>> Column.... -1
>>>>> Unable to obtain goal [multiproject:install-callback] -- C: 
>>>>> \Documents and Settings\sissonj\.geronimo-1.1.x-maven\cache 
>>>>> \geronimo-izpa
>>>>> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning:  
>>>>> Could not find file C:\geronimo1.1\assemblies\j2ee-installer \target\g
>>>>> eronimo-installer-1.1-SNAPSHOT.jar to copy.
>>>>> Total time   : 21 minutes 1 seconds
>>>>> Finished at  : Tuesday, 4 April 2006 17:31:34
>>>>>
>>>>>
>>>>>
>>>>>
>>
>>
> 
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Hernan Cunico <hc...@gmail.com>.
I am having basically the same issue building directly on Windows. When the build gets to the izpack 
section it fails. I check the assemblies\j2ee-installer\target directory and it cascades 
recursively, in fact I am not able to delete that directory (yet).

Any subsequent build attempts will also fail since maven will fail to delete the target directory.

Cheers!
Hernan

Dain Sundstrom wrote:
> What if you unpack with jar -xf?
> 
> -dain
> 
> On Apr 6, 2006, at 1:07 PM, Dave Colasurdo wrote:
> 
>> The "long file path" problem on the windows platform isn't limited  to 
>> building G1.1 on this platform.  The current images are  incompatible 
>> with windows even when the images are generated on a  different 
>> platform..
>>
>> Specifically, I built G1.1 on linux and then FTP'd the generated  
>> windows image (geronimo-tomcat-j2ee-1.1-SNAPSHOT.zip) to a windows  
>> machine..
>>
>> The resulting image can't unzip on the windows platform due to the  
>> path length problem.. :(
>>
>> e.g. C:\z\geronimo-1.1-SNAPSHOT\repository\geronimo\webconsole- 
>> tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo- 
>> console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache 
>> \geronimo\console\securitymanager\realm\SecurityRealmPortlet 
>> $ExistingRealm.class
>>
>> Guess this is obvious in hindsight, though was thinking it was  
>> strictly a build issue..
>>
>> This absolutely needs to get fixed..
>>
>> -Dave-
>>
>>
>> Joe Bohn wrote:
>>
>>> You beat me to it John .... I'm hitting the exact same problem.
>>> Joe
>>> John Sisson wrote:
>>>
>>>> I had issues relating to long file paths when building 1.1 from  my 
>>>> C:\dev\asf\geronimo\branches\1.1 directory, so I tried  building 
>>>> from a shorter directory ( C:\geronimo1.1 ) and still  have issues 
>>>> (see below).
>>>>
>>>> I haven't had a chance to look into this yet but I consider this  to 
>>>> be a blocker.
>>>>
>>>> Once we can build on windows we then need to test that Geronimo  can 
>>>> be installed in common locations on windows (e.g. under C: \Program 
>>>> Files\Geronimo-1.1 ) without encountering file path  length issues.
>>>>
>>>> The following path (from the output below) is 317 bytes long:
>>>>
>>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1- 
>>>> SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT 
>>>> \daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1- 
>>>> SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis 
>>>> \client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ $2ae63e1d.class
>>>>
>>>> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more  
>>>> info on the long file path issue.
>>>>
>>>> John
>>>>
>>>> izpack:izpack-installer-build:
>>>>    [echo] IZPack installer build is running.
>>>>    [echo] IZPack Version is 3.8.0
>>>>    [java]
>>>>    [java] .::  IzPack - Version 3.8.0 ::.
>>>>    [java]
>>>>    [java] < compiler specifications version : 1.0 >
>>>>    [java]
>>>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>>>    [java] - Released under the terms of the Apache Software  License 
>>>> version 2.0.
>>>>    [java]
>>>>    [java] -> Processing  : C:\geronimo1.1\assemblies\j2ee- 
>>>> installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>>>>    [java] -> Output      : C:\geronimo1.1\assemblies\j2ee- 
>>>> installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>>>>    [java] -> Base path   : .
>>>>    [java] -> Kind        : standard
>>>>    [java] -> Compression : default
>>>>    [java] -> Compr. level: -1
>>>>    [java]
>>>>    [java] Adding resource: IzPack.uninstaller
>>>>    [java] Setting the installer information
>>>>    [java] Setting the GUI preferences
>>>>    [java] Adding langpack: eng
>>>>    [java] Adding resource: flag.eng
>>>>    [java] Adding resource: Installer.image
>>>>    [java] Adding resource: LicencePanel.licence
>>>>    [java] Adding resource: InfoPanel.info
>>>>    [java] Adding resource: userInputSpec.xml
>>>>    [java] Adding resource: ProcessPanel.Spec.xml
>>>>    [java] Adding resource: ImgPacksPanel.img.0
>>>>    [java] Adding resource: ImgPacksPanel.img.1
>>>>    [java] Adding resource: ImgPacksPanel.img.2
>>>>    [java] Adding resource: ImgPacksPanel.img.3
>>>>    [java] Adding resource: ImgPacksPanel.img.4
>>>>    [java] Adding resource: ImgPacksPanel.img.5
>>>>    [java] Adding resource: ImgPacksPanel.img.6
>>>>    [java] Adding resource: ImgPacksPanel.img.7
>>>>    [java] Adding resource: ImgPacksPanel.img.8
>>>>    [java] Adding resource: ImgPacksPanel.img.9
>>>>    [java] Adding resource: ImgPacksPanel.img.10
>>>>    [java] Adding resource: ImgPacksPanel.img.11
>>>>    [java] Adding resource: ImgPacksPanel.img.12
>>>>    [java] Adding resource: ImgPacksPanel.img.13
>>>>    [java] Adding resource: ImgPacksPanel.img.14
>>>>    [java] Adding resource: ImgPacksPanel.img.15
>>>>    [java] Adding resource: ImgPacksPanel.img.16
>>>>    [java] Adding resource: ImgPacksPanel.img.17
>>>>    [java] Adding resource: ImgPacksPanel.img.18
>>>>    [java] Adding resource: ImgPacksPanel.img.19
>>>>    [java] Adding resource: ImgPacksPanel.img.20
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>>> standal
>>>> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>>>    [java] -> Fatal error :
>>>>    [java]    C:\geronimo1.1\assemblies\j2ee-installer/target/ 
>>>> geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: C:\geronimo1.1 \assemblie
>>>> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo 
>>>> \daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
>>>> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated 
>>>> \org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
>>>> hancerByCGLIB$$2ae63e1d.class
>>>>    [java] com.izforge.izpack.compiler.CompilerException: C: 
>>>> \geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1- 
>>>> SNAPSHOT/gero
>>>> nimo-izpack.xml:96: C:\geronimo1.1\assemblies\j2ee-installer 
>>>> \target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby- 
>>>> jetty\
>>>> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader- 
>>>> web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache \geronimo\a
>>>> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>>> $2ae63e1d.class
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.parseError 
>>>> (CompilerConfig.java:1531)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>> (CompilerConfig.java:636)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.executeCompiler 
>>>> (CompilerConfig.java:317)
>>>>    [java]      at com.izforge.izpack.compiler.CompilerConfig.main 
>>>> (CompilerConfig.java:1847)
>>>>    [java]      at com.izforge.izpack.compiler.Compiler.main 
>>>> (Compiler.java:620)
>>>>    [java] Caused by: java.io.FileNotFoundException: C:\geronimo1.1 
>>>> \assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
>>>> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby- 
>>>> jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF \geronim
>>>> o-generated\org\apache\geronimo\axis\client 
>>>> \GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>>>    [java]      at com.izforge.izpack.compiler.PackInfo.addFile 
>>>> (PackInfo.java:193)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:959)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>>> (CompilerConfig.java:969)
>>>>    [java]      at  
>>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>>> (CompilerConfig.java:632)
>>>>    [java]      ... 3 more
>>>>    [java]
>>>>    [java] (tip : use -? to get the commmand line parameters)
>>>>    [java] [ERROR] Java Result: 1
>>>>
>>>> BUILD FAILED
>>>> File...... C:\geronimo1.1\maven.xml
>>>> Element... maven:reactor
>>>> Line...... 63
>>>> Column.... -1
>>>> Unable to obtain goal [multiproject:install-callback] -- C: 
>>>> \Documents and Settings\sissonj\.geronimo-1.1.x-maven\cache 
>>>> \geronimo-izpa
>>>> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning:  
>>>> Could not find file C:\geronimo1.1\assemblies\j2ee-installer \target\g
>>>> eronimo-installer-1.1-SNAPSHOT.jar to copy.
>>>> Total time   : 21 minutes 1 seconds
>>>> Finished at  : Tuesday, 4 April 2006 17:31:34
>>>>
>>>>
>>>>
>>>>
> 
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Dain Sundstrom <da...@iq80.com>.
What if you unpack with jar -xf?

-dain

On Apr 6, 2006, at 1:07 PM, Dave Colasurdo wrote:

> The "long file path" problem on the windows platform isn't limited  
> to building G1.1 on this platform.  The current images are  
> incompatible with windows even when the images are generated on a  
> different platform..
>
> Specifically, I built G1.1 on linux and then FTP'd the generated  
> windows image (geronimo-tomcat-j2ee-1.1-SNAPSHOT.zip) to a windows  
> machine..
>
> The resulting image can't unzip on the windows platform due to the  
> path length problem.. :(
>
> e.g. C:\z\geronimo-1.1-SNAPSHOT\repository\geronimo\webconsole- 
> tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo- 
> console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache 
> \geronimo\console\securitymanager\realm\SecurityRealmPortlet 
> $ExistingRealm.class
>
> Guess this is obvious in hindsight, though was thinking it was  
> strictly a build issue..
>
> This absolutely needs to get fixed..
>
> -Dave-
>
>
> Joe Bohn wrote:
>> You beat me to it John .... I'm hitting the exact same problem.
>> Joe
>> John Sisson wrote:
>>> I had issues relating to long file paths when building 1.1 from  
>>> my C:\dev\asf\geronimo\branches\1.1 directory, so I tried  
>>> building from a shorter directory ( C:\geronimo1.1 ) and still  
>>> have issues (see below).
>>>
>>> I haven't had a chance to look into this yet but I consider this  
>>> to be a blocker.
>>>
>>> Once we can build on windows we then need to test that Geronimo  
>>> can be installed in common locations on windows (e.g. under C: 
>>> \Program Files\Geronimo-1.1 ) without encountering file path  
>>> length issues.
>>>
>>> The following path (from the output below) is 317 bytes long:
>>>
>>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1- 
>>> SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT 
>>> \daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1- 
>>> SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis 
>>> \client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>> $2ae63e1d.class
>>>
>>> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more  
>>> info on the long file path issue.
>>>
>>> John
>>>
>>> izpack:izpack-installer-build:
>>>    [echo] IZPack installer build is running.
>>>    [echo] IZPack Version is 3.8.0
>>>    [java]
>>>    [java] .::  IzPack - Version 3.8.0 ::.
>>>    [java]
>>>    [java] < compiler specifications version : 1.0 >
>>>    [java]
>>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>>    [java] - Released under the terms of the Apache Software  
>>> License version 2.0.
>>>    [java]
>>>    [java] -> Processing  : C:\geronimo1.1\assemblies\j2ee- 
>>> installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml
>>>    [java] -> Output      : C:\geronimo1.1\assemblies\j2ee- 
>>> installer/target/geronimo-installer-1.1-SNAPSHOT.jar
>>>    [java] -> Base path   : .
>>>    [java] -> Kind        : standard
>>>    [java] -> Compression : default
>>>    [java] -> Compr. level: -1
>>>    [java]
>>>    [java] Adding resource: IzPack.uninstaller
>>>    [java] Setting the installer information
>>>    [java] Setting the GUI preferences
>>>    [java] Adding langpack: eng
>>>    [java] Adding resource: flag.eng
>>>    [java] Adding resource: Installer.image
>>>    [java] Adding resource: LicencePanel.licence
>>>    [java] Adding resource: InfoPanel.info
>>>    [java] Adding resource: userInputSpec.xml
>>>    [java] Adding resource: ProcessPanel.Spec.xml
>>>    [java] Adding resource: ImgPacksPanel.img.0
>>>    [java] Adding resource: ImgPacksPanel.img.1
>>>    [java] Adding resource: ImgPacksPanel.img.2
>>>    [java] Adding resource: ImgPacksPanel.img.3
>>>    [java] Adding resource: ImgPacksPanel.img.4
>>>    [java] Adding resource: ImgPacksPanel.img.5
>>>    [java] Adding resource: ImgPacksPanel.img.6
>>>    [java] Adding resource: ImgPacksPanel.img.7
>>>    [java] Adding resource: ImgPacksPanel.img.8
>>>    [java] Adding resource: ImgPacksPanel.img.9
>>>    [java] Adding resource: ImgPacksPanel.img.10
>>>    [java] Adding resource: ImgPacksPanel.img.11
>>>    [java] Adding resource: ImgPacksPanel.img.12
>>>    [java] Adding resource: ImgPacksPanel.img.13
>>>    [java] Adding resource: ImgPacksPanel.img.14
>>>    [java] Adding resource: ImgPacksPanel.img.15
>>>    [java] Adding resource: ImgPacksPanel.img.16
>>>    [java] Adding resource: ImgPacksPanel.img.17
>>>    [java] Adding resource: ImgPacksPanel.img.18
>>>    [java] Adding resource: ImgPacksPanel.img.19
>>>    [java] Adding resource: ImgPacksPanel.img.20
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>>    [java] Adding content of jar: file:/C:/Documents%20and% 
>>> 20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/ 
>>> standal
>>> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>>    [java] -> Fatal error :
>>>    [java]    C:\geronimo1.1\assemblies\j2ee-installer/target/ 
>>> geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: C:\geronimo1.1 
>>> \assemblie
>>> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo 
>>> \daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS
>>> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated 
>>> \org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En
>>> hancerByCGLIB$$2ae63e1d.class
>>>    [java] com.izforge.izpack.compiler.CompilerException: C: 
>>> \geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1- 
>>> SNAPSHOT/gero
>>> nimo-izpack.xml:96: C:\geronimo1.1\assemblies\j2ee-installer 
>>> \target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby- 
>>> jetty\
>>> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader- 
>>> web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache 
>>> \geronimo\a
>>> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$ 
>>> $2ae63e1d.class
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.parseError 
>>> (CompilerConfig.java:1531)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>> (CompilerConfig.java:636)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.executeCompiler 
>>> (CompilerConfig.java:317)
>>>    [java]      at com.izforge.izpack.compiler.CompilerConfig.main 
>>> (CompilerConfig.java:1847)
>>>    [java]      at com.izforge.izpack.compiler.Compiler.main 
>>> (Compiler.java:620)
>>>    [java] Caused by: java.io.FileNotFoundException: C:\geronimo1.1 
>>> \assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor
>>> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby- 
>>> jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF 
>>> \geronim
>>> o-generated\org\apache\geronimo\axis\client 
>>> \GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>>    [java]      at com.izforge.izpack.compiler.PackInfo.addFile 
>>> (PackInfo.java:193)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:959)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addRecursively 
>>> (CompilerConfig.java:969)
>>>    [java]      at  
>>> com.izforge.izpack.compiler.CompilerConfig.addPacks 
>>> (CompilerConfig.java:632)
>>>    [java]      ... 3 more
>>>    [java]
>>>    [java] (tip : use -? to get the commmand line parameters)
>>>    [java] [ERROR] Java Result: 1
>>>
>>> BUILD FAILED
>>> File...... C:\geronimo1.1\maven.xml
>>> Element... maven:reactor
>>> Line...... 63
>>> Column.... -1
>>> Unable to obtain goal [multiproject:install-callback] -- C: 
>>> \Documents and Settings\sissonj\.geronimo-1.1.x-maven\cache 
>>> \geronimo-izpa
>>> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning:  
>>> Could not find file C:\geronimo1.1\assemblies\j2ee-installer 
>>> \target\g
>>> eronimo-installer-1.1-SNAPSHOT.jar to copy.
>>> Total time   : 21 minutes 1 seconds
>>> Finished at  : Tuesday, 4 April 2006 17:31:34
>>>
>>>
>>>
>>>


Re: Cannot build 1.1 on Windows - long file paths

Posted by Dave Colasurdo <da...@earthlink.net>.
The "long file path" problem on the windows platform isn't limited to 
building G1.1 on this platform.  The current images are incompatible 
with windows even when the images are generated on a different platform..

Specifically, I built G1.1 on linux and then FTP'd the generated windows 
image (geronimo-tomcat-j2ee-1.1-SNAPSHOT.zip) to a windows machine..

The resulting image can't unzip on the windows platform due to the path 
length problem.. :(

e.g. 
C:\z\geronimo-1.1-SNAPSHOT\repository\geronimo\webconsole-tomcat\1.1-SNAPSHOT\webconsole-tomcat-1.1-SNAPSHOT.car\geronimo-console-standard-1.1-SNAPSHOT.war\WEB-INF\classes\org\apache\geronimo\console\securitymanager\realm\SecurityRealmPortlet$ExistingRealm.class

Guess this is obvious in hindsight, though was thinking it was strictly 
a build issue..

This absolutely needs to get fixed..

-Dave-


Joe Bohn wrote:
> 
> You beat me to it John .... I'm hitting the exact same problem.
> 
> Joe
> 
> John Sisson wrote:
>> I had issues relating to long file paths when building 1.1 from my 
>> C:\dev\asf\geronimo\branches\1.1 directory, so I tried building from a 
>> shorter directory ( C:\geronimo1.1 ) and still have issues (see below).
>>
>> I haven't had a chance to look into this yet but I consider this to be 
>> a blocker.
>>
>> Once we can build on windows we then need to test that Geronimo can be 
>> installed in common locations on windows (e.g. under C:\Program 
>> Files\Geronimo-1.1 ) without encountering file path length issues.
>>
>> The following path (from the output below) is 317 bytes long:
>>
>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class 
>>
>>
>> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more info 
>> on the long file path issue.
>>
>> John
>>
>> izpack:izpack-installer-build:
>>    [echo] IZPack installer build is running.
>>    [echo] IZPack Version is 3.8.0
>>    [java]
>>    [java] .::  IzPack - Version 3.8.0 ::.
>>    [java]
>>    [java] < compiler specifications version : 1.0 >
>>    [java]
>>    [java] - Copyright (C) 2001-2005 Julien Ponge
>>    [java] - Visit http://www.izforge.com/ for the latests releases
>>    [java] - Released under the terms of the Apache Software License 
>> version 2.0.
>>    [java]
>>    [java] -> Processing  : 
>> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml 
>>
>>    [java] -> Output      : 
>> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-installer-1.1-SNAPSHOT.jar 
>>
>>    [java] -> Base path   : .
>>    [java] -> Kind        : standard
>>    [java] -> Compression : default
>>    [java] -> Compr. level: -1
>>    [java]
>>    [java] Adding resource: IzPack.uninstaller
>>    [java] Setting the installer information
>>    [java] Setting the GUI preferences
>>    [java] Adding langpack: eng
>>    [java] Adding resource: flag.eng
>>    [java] Adding resource: Installer.image
>>    [java] Adding resource: LicencePanel.licence
>>    [java] Adding resource: InfoPanel.info
>>    [java] Adding resource: userInputSpec.xml
>>    [java] Adding resource: ProcessPanel.Spec.xml
>>    [java] Adding resource: ImgPacksPanel.img.0
>>    [java] Adding resource: ImgPacksPanel.img.1
>>    [java] Adding resource: ImgPacksPanel.img.2
>>    [java] Adding resource: ImgPacksPanel.img.3
>>    [java] Adding resource: ImgPacksPanel.img.4
>>    [java] Adding resource: ImgPacksPanel.img.5
>>    [java] Adding resource: ImgPacksPanel.img.6
>>    [java] Adding resource: ImgPacksPanel.img.7
>>    [java] Adding resource: ImgPacksPanel.img.8
>>    [java] Adding resource: ImgPacksPanel.img.9
>>    [java] Adding resource: ImgPacksPanel.img.10
>>    [java] Adding resource: ImgPacksPanel.img.11
>>    [java] Adding resource: ImgPacksPanel.img.12
>>    [java] Adding resource: ImgPacksPanel.img.13
>>    [java] Adding resource: ImgPacksPanel.img.14
>>    [java] Adding resource: ImgPacksPanel.img.15
>>    [java] Adding resource: ImgPacksPanel.img.16
>>    [java] Adding resource: ImgPacksPanel.img.17
>>    [java] Adding resource: ImgPacksPanel.img.18
>>    [java] Adding resource: ImgPacksPanel.img.19
>>    [java] Adding resource: ImgPacksPanel.img.20
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>>    [java] Adding content of jar: 
>> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
>>
>> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>>    [java] -> Fatal error :
>>    [java]    
>> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: 
>> C:\geronimo1.1\assemblie
>> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS 
>>
>> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En 
>>
>> hancerByCGLIB$$2ae63e1d.class
>>    [java] com.izforge.izpack.compiler.CompilerException: 
>> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/gero 
>>
>> nimo-izpack.xml:96: 
>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\ 
>>
>> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\a 
>>
>> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.parseError(CompilerConfig.java:1531) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:636) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:317) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.main(CompilerConfig.java:1847)
>>    [java]      at 
>> com.izforge.izpack.compiler.Compiler.main(Compiler.java:620)
>>    [java] Caused by: java.io.FileNotFoundException: 
>> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor 
>>
>> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronim 
>>
>> o-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.PackInfo.addFile(PackInfo.java:193)
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:959) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
>>
>>    [java]      at 
>> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:632) 
>>
>>    [java]      ... 3 more
>>    [java]
>>    [java] (tip : use -? to get the commmand line parameters)
>>    [java] [ERROR] Java Result: 1
>>
>> BUILD FAILED
>> File...... C:\geronimo1.1\maven.xml
>> Element... maven:reactor
>> Line...... 63
>> Column.... -1
>> Unable to obtain goal [multiproject:install-callback] -- C:\Documents 
>> and Settings\sissonj\.geronimo-1.1.x-maven\cache\geronimo-izpa
>> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning: Could 
>> not find file C:\geronimo1.1\assemblies\j2ee-installer\target\g
>> eronimo-installer-1.1-SNAPSHOT.jar to copy.
>> Total time   : 21 minutes 1 seconds
>> Finished at  : Tuesday, 4 April 2006 17:31:34
>>
>>
>>
>>
> 

Re: Cannot build 1.1 on Windows - long file paths

Posted by Joe Bohn <jo...@earthlink.net>.
You beat me to it John .... I'm hitting the exact same problem.

Joe

John Sisson wrote:
> I had issues relating to long file paths when building 1.1 from my 
> C:\dev\asf\geronimo\branches\1.1 directory, so I tried building from a 
> shorter directory ( C:\geronimo1.1 ) and still have issues (see below).
> 
> I haven't had a chance to look into this yet but I consider this to be a 
> blocker.
> 
> Once we can build on windows we then need to test that Geronimo can be 
> installed in common locations on windows (e.g. under C:\Program 
> Files\Geronimo-1.1 ) without encountering file path length issues.
> 
> The following path (from the output below) is 317 bytes long:
> 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class 
> 
> 
> See http://issues.apache.org/jira/browse/GERONIMO-1790 for more info on 
> the long file path issue.
> 
> John
> 
> izpack:izpack-installer-build:
>    [echo] IZPack installer build is running.
>    [echo] IZPack Version is 3.8.0
>    [java]
>    [java] .::  IzPack - Version 3.8.0 ::.
>    [java]
>    [java] < compiler specifications version : 1.0 >
>    [java]
>    [java] - Copyright (C) 2001-2005 Julien Ponge
>    [java] - Visit http://www.izforge.com/ for the latests releases
>    [java] - Released under the terms of the Apache Software License 
> version 2.0.
>    [java]
>    [java] -> Processing  : 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml 
> 
>    [java] -> Output      : 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-installer-1.1-SNAPSHOT.jar 
> 
>    [java] -> Base path   : .
>    [java] -> Kind        : standard
>    [java] -> Compression : default
>    [java] -> Compr. level: -1
>    [java]
>    [java] Adding resource: IzPack.uninstaller
>    [java] Setting the installer information
>    [java] Setting the GUI preferences
>    [java] Adding langpack: eng
>    [java] Adding resource: flag.eng
>    [java] Adding resource: Installer.image
>    [java] Adding resource: LicencePanel.licence
>    [java] Adding resource: InfoPanel.info
>    [java] Adding resource: userInputSpec.xml
>    [java] Adding resource: ProcessPanel.Spec.xml
>    [java] Adding resource: ImgPacksPanel.img.0
>    [java] Adding resource: ImgPacksPanel.img.1
>    [java] Adding resource: ImgPacksPanel.img.2
>    [java] Adding resource: ImgPacksPanel.img.3
>    [java] Adding resource: ImgPacksPanel.img.4
>    [java] Adding resource: ImgPacksPanel.img.5
>    [java] Adding resource: ImgPacksPanel.img.6
>    [java] Adding resource: ImgPacksPanel.img.7
>    [java] Adding resource: ImgPacksPanel.img.8
>    [java] Adding resource: ImgPacksPanel.img.9
>    [java] Adding resource: ImgPacksPanel.img.10
>    [java] Adding resource: ImgPacksPanel.img.11
>    [java] Adding resource: ImgPacksPanel.img.12
>    [java] Adding resource: ImgPacksPanel.img.13
>    [java] Adding resource: ImgPacksPanel.img.14
>    [java] Adding resource: ImgPacksPanel.img.15
>    [java] Adding resource: ImgPacksPanel.img.16
>    [java] Adding resource: ImgPacksPanel.img.17
>    [java] Adding resource: ImgPacksPanel.img.18
>    [java] Adding resource: ImgPacksPanel.img.19
>    [java] Adding resource: ImgPacksPanel.img.20
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/HelloPanel.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/LicencePanel.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/TargetPanel.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ImgPacksPanel.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ValidatePackSelections.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/InstallPanel.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/ProcessPanel.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/InfoPanel.jar
>    [java] Adding content of jar: 
> file:/C:/Documents%20and%20Settings/sissonj/.geronimo-1.1.x-maven/repository/geronimo/jars/standal 
> 
> one-compiler-custom-3.8.0.jar!/bin/panels/FinishPanel.jar
>    [java] -> Fatal error :
>    [java]    
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/geronimo-izpack.xml:96: 
> C:\geronimo1.1\assemblie
> s\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPS 
> 
> HOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$En 
> 
> hancerByCGLIB$$2ae63e1d.class
>    [java] com.izforge.izpack.compiler.CompilerException: 
> C:\geronimo1.1\assemblies\j2ee-installer/target/geronimo-1.1-SNAPSHOT/gero
> nimo-izpack.xml:96: 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repository\geronimo\daytrader-derby-jetty\ 
> 
> 1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronimo-generated\org\apache\geronimo\a 
> 
> xis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.parseError(CompilerConfig.java:1531) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:636) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:317) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.main(CompilerConfig.java:1847)
>    [java]      at 
> com.izforge.izpack.compiler.Compiler.main(Compiler.java:620)
>    [java] Caused by: java.io.FileNotFoundException: 
> C:\geronimo1.1\assemblies\j2ee-installer\target\geronimo-1.1-SNAPSHOT\repositor 
> 
> y\geronimo\daytrader-derby-jetty\1.1-SNAPSHOT\daytrader-derby-jetty-1.1-SNAPSHOT.car\daytrader-web-1.1-SNAPSHOT.war\META-INF\geronim 
> 
> o-generated\org\apache\geronimo\axis\client\GenericServiceEndpointWrapper$$EnhancerByCGLIB$$2ae63e1d.class 
> 
>    [java]      at 
> com.izforge.izpack.compiler.PackInfo.addFile(PackInfo.java:193)
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:959) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addRecursively(CompilerConfig.java:969) 
> 
>    [java]      at 
> com.izforge.izpack.compiler.CompilerConfig.addPacks(CompilerConfig.java:632) 
> 
>    [java]      ... 3 more
>    [java]
>    [java] (tip : use -? to get the commmand line parameters)
>    [java] [ERROR] Java Result: 1
> 
> BUILD FAILED
> File...... C:\geronimo1.1\maven.xml
> Element... maven:reactor
> Line...... 63
> Column.... -1
> Unable to obtain goal [multiproject:install-callback] -- C:\Documents 
> and Settings\sissonj\.geronimo-1.1.x-maven\cache\geronimo-izpa
> ck-plugin-1.1-SNAPSHOT\plugin.jelly:78:-1: <ant:copy> Warning: Could not 
> find file C:\geronimo1.1\assemblies\j2ee-installer\target\g
> eronimo-installer-1.1-SNAPSHOT.jar to copy.
> Total time   : 21 minutes 1 seconds
> Finished at  : Tuesday, 4 April 2006 17:31:34
> 
> 
> 
> 

-- 
Joe Bohn
joe.bohn at earthlink.net

"He is no fool who gives what he cannot keep, to gain what he cannot 
lose."   -- Jim Elliot