Re: WOLips maven-wolifecycle-plugin bug?

From: Henrique Prange (hprang..mail.com)
Date: Wed Oct 15 2008 - 10:02:16 EDT

  • Next message: Lachlan Deck: "Re: Problems starting Maven based WOApplication in WOLips 3.4.5503 on Windows XP"

    Hi Lars,

    Could you try the 2.0.16-SNAPSHOT version of maven-wolifecycle-plugin?
    If the problem persists, could you run maven with -e option and attach
    the stack trace, please?

    Cheers,

    Henrique

    Lars Sonchocky-Helldorf wrote:
    > When trying to build a Maven based WOApplication project on Windows I
    > get the following error:
    >
    > [INFO] [woproject:define-woapplication-resources]
    > [INFO] Defining wo resources
    > [INFO] Defining wo resources: loading "resources.include.patternset"
    > [INFO] Defining wo resources: loading "resources.exclude.patternset"
    > [INFO] Defining wo resources: loading "wsresources.include.patternset"
    > [INFO] Defining wo resources: loading "wsresources.exclude.patternset"
    > [INFO] Copy webserverresources
    > [INFO] [resources:resources]
    > [INFO] Using default encoding to copy filtered resources.
    > [INFO] [compiler:compile]
    > [INFO] Compiling 126 source files to C:\Dokumente und
    > Einstellungen\cem\workspace\TankDiskAll\Applications\TankDiskServer\target\classes
    >
    > [INFO] [woproject:woapplication]
    >
    > initTaskDefs:
    >
    > test-pom:
    > [echo] Artifact ID = TankDiskServer
    > [echo] Artifact version = 1.0.5-SNAPSHOT
    >
    > woapplicationproperties:
    > [echo] classpath.localRepository.baseDir C:Dokumente und
    > Einstellungencem.m2
    > [echo] epository
    >
    > build-woapplication:
    > [echo] classpath.localRepository.baseDir C:Dokumente und
    > Einstellungencem.m2
    > [echo] epository
    > [woapplication] Installing TankDiskServer-1.0.5-SNAPSHOT in target
    > [INFO]
    > ------------------------------------------------------------------------
    > [ERROR] BUILD ERROR
    > [INFO]
    > ------------------------------------------------------------------------
    > [INFO] Failed to execute: Executing Ant script: /wolifecycle.build.xml
    > [build-woapplication]: Failed to execute.
    >
    > epository not found.stellungencem.m2
    > [INFO]
    > ------------------------------------------------------------------------
    > [INFO] For more information, run Maven with the -e switch
    > [INFO]
    > ------------------------------------------------------------------------
    > [INFO] Total time: 30 seconds
    > [INFO] Finished at: Tue Oct 14 12:45:47 CEST 2008
    > [INFO] Final Memory: 7M/28M
    > [INFO]
    > ------------------------------------------------------------------------
    >
    >
    >
    > the generated target/wobuild.properties looks like this:
    >
    > maven.localRepository.baseDir = C:/Dokumente und
    > Einstellungen/cem/.m2/repository
    >
    > while the generated target/classpath.properties has the same path in
    > Windows style:
    >
    > classpath.localRepository.baseDir C:\Dokumente und
    > Einstellungen\cem\.m2\repository
    >
    >
    >
    > Studying
    > https://svn.objectstyle.org/repos/woproject/tags/woproject-all-parent-2.0.15/maven2/maven-wolifecycle-plugin/src/main/scripts/wolifecycle.build.xml
    > tells me that target/wobuild.properties and target/classpath.properties
    > are both read and classpath.localRepository.baseDir is echoed to the
    > terminal. Since classpath.localRepository.baseDir contains backslashes
    > the path is totally mangled: all backslashes are missing (since
    > backslash is an escape character and there is even an carriage return in
    > it: \r from \repository. The result of this is then:
    >
    > [echo] classpath.localRepository.baseDir C:Dokumente und
    > Einstellungencem.m2
    > [echo] epository
    >
    > for the above windows style path
    >
    > While the windows style path is handled correctly for
    > target/wobuild.properties in
    > org.objectstyle.woproject.maven2.wolifecycle.DefineWOApplicationResourcesMojo.defineProperties()
    > by converting all backslashes using the
    > normalizedPath(localRepository.getBasedir())) method call this seems to
    > be not the case for target/classpath.properties which is IMHO the reason
    > for the build failure.
    >
    >
    >
    > Should I file a bug on this?
    >
    >
    > regards,
    >
    > Lars
    >
    >
    >
    >
    >



    This archive was generated by hypermail 2.0.0 : Wed Oct 15 2008 - 10:03:32 EDT