continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johnson, Jonathan" <jjohn...@454.com>
Subject RE: ContinuumBuildExecutorException: Could not find Maven project descriptor
Date Thu, 26 Jan 2006 17:37:01 GMT
>> 1. You can provide some patches for docs ;-)

I don't know where other people get all the time.  ;-)

>> don't need to specify scm part in all modules

Again, you are correct.  Just defining the scm in the parent pom.xml of the  multi-module
structure does the trick.



-----Original Message-----
From: Emmanuel Venisse [mailto:emmanuel@venisse.net] 
Sent: Thursday, January 26, 2006 12:07 PM
To: continuum-users@maven.apache.org
Subject: Re: ContinuumBuildExecutorException: Could not find Maven project descriptor

1. You can provide some patches for docs ;-)

2. In multi-module, you don't need to specify scm part in all modules if your parent pom is
in 
parent directory of your child, if not, you actually need to add it.

If your directory structue is like this :
project_root
    - pom.xml
    - child
        - pom.xml

scm url can be define in pom.xml in project_root like this : 
scm:cvs:pserver:jjohnson@serverx:/home/Repository:your_cvs_module/..../project_root/
and you have nothing in your pom.xml in child project, so it will be resolve to : 
scm:cvs:pserver:jjohnson@serverx:/home/Repository:your_cvs_module/..../project_root/child/

Emmanuel

Johnson, Jonathan a écrit :
> Emmanuel,
> 
> Your advice was superb.  That fixed the problem.  Once I added the working directory
and path to the module in the scm url it all worked.  The reasons for my problems were this:
> 
> 1.  I did not understand what a working directory was and therefore skipped the configuration
setting for this.  It would be helpful if the web page for configuration has simple help text
explaining what these setting are.  The unfortunate term of 'working directory' is subjective
and a more descriptive term should have been used.  Something like 'project root directory'.
 Tooltip text should be added with further descriptions.  Build output directory term should
also be changed.  Its really should be "Build Log Directory'.  A new user might be misled
thinking that all the build artifacts (class, jar, Javadoc, etc) are being placed here.  
> 
> 2.  Did not understand that I had to add a scm element to every pom.xml even when I have
multi-module structure with a parent pom.  For continuum the scm in the parent pom.xml should
be sufficient for all the child poms in the module subdirectories.  Defining the scm in the
sub poms is redundant.
> 
> 
> 
> -----Original Message-----
> From: Emmanuel Venisse [mailto:emmanuel@venisse.net] 
> Sent: Thursday, January 26, 2006 9:58 AM
> To: continuum-users@maven.apache.org
> Subject: Re: ContinuumBuildExecutorException: Could not find Maven project descriptor
> 
> The 'working directory' is the directory where your files will be checkout 
> ($CONTINUUM_HOME/apps/continuum/working_directory/<projectId>). The pom.xml of
your project must be 
> there. If it isn't that, your scm url is wrong.
> 
> Your scm url is 'scm:cvs:pserver:jjohnson@serverx:/home/Repository:project' so you must
have your 
> pom.xml in /home/Repository/project in cvs.
> For your project, scm url must something like this : 
> scm:cvs:pserver:jjohnson@serverx:/home/Repository:project/..../modules/myproject
> 
> Emmanuel
> 
> Johnson, Jonathan a écrit :
> 
>>>>You don't have a pom.xml in your working directory.
>>
>>
>>What does 'working directory' mean.  How would one define it?  Is this a new pom.xml
just for continuum?  What has to be in it?  I do have a parent pom.xml one directory above
my myproject directory.  For the maven 2 parent element the default location for a parent
pom.xml is ../poml.xml.  My Maven 2 build works correctly. I have a pom.xml in the parent
directory and in every module directory as recommended by the maven multi-project directory
layout.  Below is a tree of my project.
>>
>>
>>
>>>>Check your scm url for your project.
>>
>>Also this error occurs without the <scm> tag that was included below, so I think
its unrelated to the exception.
>>
>>├───modules					<-- parent pom.xml here.
>>│   ├───Common				<-- pom.xml fo common here.
>>│   │   └───src
>>│   │       ├───main
>>│   │       │   └───java
>>│   │       │       └───com
>>│   │       │           └───...
>>│   │       └───test
>>│   │           └───java
>>│   │               └───com
>>│   │                   └───...
>>│   ├───myproject				<-- pom.xml fr myproject here.
>>│   │   └───src
>>│   │       └───main
>>│   │           ├───config
>>│   │           ├───java
>>│   │           │   └───com
>>│   │           │       └───...
>>│   │           └───resources
>>
>>-----Original Message-----
>>From: Emmanuel Venisse [mailto:emmanuel@venisse.net] 
>>Sent: Thursday, January 26, 2006 4:08 AM
>>To: continuum-users@maven.apache.org
>>Subject: Re: ContinuumBuildExecutorException: Could not find Maven project descriptor
>>
>>You don't have a pom.xml in your working directory. Check your scm url for your project.
>>
>>Emmanuel
>>
>>Johnson, Jonathan a écrit :
>>
>>
>>>I'm getting an exception and not sure why it means.
>>>
>>>
>>>
>>>Being new to Continuum I have yet to get it to build any of my modules. 
>>>
>>>
>>>
>>>Here is my platform
>>>
>>>
>>>
>>>Red Hat
>>>
>>>Maven 2.0.2
>>>
>>>Continuum 1.0.2
>>>
>>>Java 1.5.0_06
>>>
>>>
>>>
>>>I'm getting this exception when running a build on a single, simple
>>>module within my multi-module structure.
>>>
>>>
>>>
>>>org.apache.maven.continuum.execution.ContinuumBuildExecutorException:
>>>Could not find Maven project descriptor.
>>>
>>>     at
>>>org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda
>>>teProjectFromCheckOut(MavenTwoBuildExecutor.java:111)
>>>
>>>     at
>>>org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectory
>>>ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction
>>>.java:62)
>>>
>>>     at
>>>org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(
>>>DefaultBuildController.java:169)
>>>
>>>     at
>>>org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec
>>>uteTask(BuildProjectTaskExecutor.java:53)
>>>
>>>     at
>>>org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut
>>>orRunnable.run(ThreadedTaskQueueExecutor.java:103)
>>>
>>>     at java.lang.Thread.run(Thread.java:595)
>>>
>>>     
>>>
>>>Most of the settings are supposed to come from the parent pom.  My Maven
>>>compile and package of the modules works correctly.  The pom.xml of the
>>>sub-module I am trying to execute is this.  
>>>
>>>
>>>
>>><project xmlns="http://maven.apache.org/POM/4.0.0"
>>>
>>>        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>
>>>        xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>>>http://maven.apache.org/maven-v4_0_0.xsd">
>>>
>>>   <modelVersion>4.0.0</modelVersion>
>>>
>>>   <groupId>com.fourfivefour.myproject</groupId>
>>>
>>>   <artifactId>myproject</artifactId>
>>>
>>>   <packaging>jar</packaging>
>>>
>>>   <version>0.9</version>
>>>
>>>   <name>myproject</name>
>>>
>>>   <description>todo</description>
>>>
>>>
>>>
>>>   <parent>
>>>
>>>       <groupId>com.fourfivefour</groupId>
>>>
>>>       <artifactId>AppJavaModules</artifactId>
>>>
>>>       <version>1.0</version>
>>>
>>>   </parent>
>>>
>>>
>>>
>>>   <dependencies>
>>>
>>>   </dependencies>
>>>
>>>
>>>
>>>   <scm>  <!-- Had to add this instead of relying on parent POM --->
>>>
>>>       <connection>
>>>
>>>
>>>scm:cvs:pserver:jjohnson@serverx:/home/Repository:project</connection>
>>>
>>>   </scm>
>>>
>>>
>>>
>>>   <build>
>>>
>>>       <plugins>
>>>
>>>       </plugins>
>>>
>>>   </build>
>>>
>>>
>>>
>>></project>
>>>
>>>
>>>
>>>
>>>LEGAL NOTICE:
>>>Unless expressly stated otherwise, this message is confidential and may be privileged.
It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the contents or any action taken
(or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee,
please inform the sender immediately.
>>>
>>>
>>>
>>
>>
> 
> 
> LEGAL NOTICE:
> Unless expressly stated otherwise, this message is confidential and may be privileged.
It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the contents or any action taken
(or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee,
please inform the sender immediately.
> 
> 
> 
> 
> 

Mime
View raw message