geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay D. McHugh" <jaydmch...@gmail.com>
Subject Re: Building 2.0.3
Date Thu, 23 Oct 2008 22:22:50 GMT
Thanks Donald,

It was the Maven version (grrrr).

I just got a second test build completed.  So, I am going to change the
pom.xml so that you have to use Maven between 2.0.5 and 2.0.7 so that
(hopefully) no one else runs into the same problems.

Jay



Donald Woods wrote:
> Which OS, JDK and Maven?
> 
> The 2.0 builds are using Maven 2.0.7 and Sun 1.5.0_16 on a Linux system.
> 
> It's been a week or so since I rebuilt branches/2.0, but the last I
> tried it worked for me with a clean repo on openSUSE 11.0 and MacOSX.
> 
> 
> -Donald
> 
> 
> Jay D. McHugh wrote:
>> Hello all,
>>
>> I know that we have the automated build going on.  And I have been
>> getting the emails daily saying that the build was successful for 2.0.3.
>>
>> But, when I started with a fresh checkout and an empty repo - I was
>> unable to build.
>>
>> Are there changes that were made on the automated build machine?  Is
>> there something special about the settings it is using?
>>
>> I have already fixed a couple of problems, but before I check them in -
>> I wanted to make sure that they are actually necessary.
>>
>> Has anyone tried to do a clean and fresh build of 2.0 recently?  Did you
>> need to do anything special?
>>
>> I am currently getting stuck with the following exception (tracing
>> enabled):
>> <console snip>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Geronimo :: System
>> [INFO]    task-segment: [install]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [enforcer:enforce {execution: default}]
>> [INFO] [remote-resources:process {execution: process}]
>> [INFO] [tools:copy-legal-files {execution: install-legal-files}]
>> [INFO] [antrun:run {execution: generate-dynamic-properties}]
>> [INFO] Executing tasks
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Error executing ant tasks
>>
>> Embedded error: Could not create task or type of type: propertyfile.
>>
>> Ant could not find the task or a class this task relies upon.
>>
>> This is common and has a number of causes; the usual
>> solutions are to read the manual pages then download and
>> install needed JAR files, or fix the build file:
>>  - You have misspelt 'propertyfile'.
>>    Fix: check your spelling.
>>  - The task needs an external JAR file to execute
>>      and this is not found at the right place in the classpath.
>>    Fix: check the documentation for dependencies.
>>    Fix: declare the task.
>>  - The task is an Ant optional task and the JAR file and/or libraries
>>      implementing the functionality were not found at the time you
>>      yourself built your installation of Ant from the Ant sources.
>>    Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
>>      task and make sure it contains more than merely a
>> META-INF/MANIFEST.MF.
>>      If all it contains is the manifest, then rebuild Ant with the needed
>>      libraries present in ${ant.home}/lib/optional/ , or alternatively,
>>      download a pre-built release version from apache.org
>>  - The build file was written for a later version of Ant
>>    Fix: upgrade to at least the latest release version of Ant
>>  - The task is not an Ant core or optional task
>>      and needs to be declared using <taskdef>.
>>  - You are attempting to use a task defined using
>>     <presetdef> or <macrodef> but have spelt wrong or not
>>    defined it at the point of use
>>
>> Remember that for JAR files to be visible to Ant tasks implemented
>> in ANT_HOME/lib, the files must be in the same directory or on the
>> classpath
>>
>> Please neither file bug reports on this problem, nor email the
>> Ant mailing lists, until all of these causes have been explored,
>> as this is not an Ant bug.
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: Error executing
>> ant tasks
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
>>
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>>
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>
>>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>         at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>>         at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>>         at java.lang.reflect.Method.invoke(Method.java:585)
>>         at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>         at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
>> executing ant tasks
>>         at
>> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:114)
>>
>>         at
>> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
>>         at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>
>>         at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>
>>         ... 16 more
>> Caused by: Could not create task or type of type: propertyfile.
>>
>> Ant could not find the task or a class this task relies upon.
>>
>> This is common and has a number of causes; the usual
>> solutions are to read the manual pages then download and
>> install needed JAR files, or fix the build file:
>>  - You have misspelt 'propertyfile'.
>>    Fix: check your spelling.
>>  - The task needs an external JAR file to execute
>>      and this is not found at the right place in the classpath.
>>    Fix: check the documentation for dependencies.
>>    Fix: declare the task.
>>  - The task is an Ant optional task and the JAR file and/or libraries
>>      implementing the functionality were not found at the time you
>>      yourself built your installation of Ant from the Ant sources.
>>    Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
>>      task and make sure it contains more than merely a
>> META-INF/MANIFEST.MF.
>>      If all it contains is the manifest, then rebuild Ant with the needed
>>      libraries present in ${ant.home}/lib/optional/ , or alternatively,
>>      download a pre-built release version from apache.org
>>  - The build file was written for a later version of Ant
>>    Fix: upgrade to at least the latest release version of Ant
>>  - The task is not an Ant core or optional task
>>      and needs to be declared using <taskdef>.
>>  - You are attempting to use a task defined using
>>     <presetdef> or <macrodef> but have spelt wrong or not
>>    defined it at the point of use
>>
>> Remember that for JAR files to be visible to Ant tasks implemented
>> in ANT_HOME/lib, the files must be in the same directory or on the
>> classpath
>>
>> Please neither file bug reports on this problem, nor email the
>> Ant mailing lists, until all of these causes have been explored,
>> as this is not an Ant bug.
>>         at
>> org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:493)
>>
>>         at
>> org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:391)
>>         at
>> org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:158)
>>
>>         at org.apache.tools.ant.Task.perform(Task.java:363)
>>         at org.apache.tools.ant.Target.execute(Target.java:341)
>>         at
>> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108)
>>
>>         ... 19 more
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 1 minute 47 seconds
>> [INFO] Finished at: Wed Oct 22 15:13:41 CDT 2008
>> [INFO] Final Memory: 81M/1018M
>> [INFO]
>> ------------------------------------------------------------------------
>> </console snip>
>>
>> Any hints on getting past this?
>>
>>
>> Jay
>>

Mime
View raw message