Re: problem configuring a maven 2 project
The problem is that the pom.xml is not a real xml document. Is is a html presentation of the xml file. Therefore the pom is not valid. I get this if I use the browse code function of javaforge and for tigris. If I use the url that tortoisesvn uses, continuum sais it is not a valid url. http://gridshoresample.tigris.org/source/browse/gridshoresample/trunk/sources/studentregistrations/pom.xml does not give a real xml file but an html page showing the xml (error - Cannot build maven project from D:\DOCUME~1\JETTRO~1.COE\LOCALS~1\Temp\continuum-25232.tmp.) http://gridshoresample.tigris.org/svn/gridshoresample/trunk/sources/studentregistrations/pom.xml response is : not a valid url This is all finding place when trying to install a new maven 2 project. thanks for the help On 2/1/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > What is your problems? > > http://maven.apache.org/continuum/guides/getting-started/index.html > > Emmanuel > > Jettro Coenradie a écrit : > > Hi all, > > I am trying continuum. I am having problems getting it to work with a > > project under tigris. Does anyone have experience with this? > > > > thanks is advance > > > >
Re: problem configuring a maven 2 project
Sometimes things are so simple and I feel so stupid, thank you Emmanuel On 2/1/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > You must use the "as plain text" link in web page: > > http://gridshoresample.tigris.org/source/browse/*checkout*/gridshoresample/trunk/sources/studentregistrations/pom.xml?content-type=text%2Fplain > without the revision at the end. > > Emmanuel > > Jettro Coenradie a écrit : > > The problem is that the pom.xml is not a real xml document. Is is a html > > presentation of the xml file. Therefore the pom is not valid. I get this > if > > I use the browse code function of javaforge and for tigris. If I use the > url > > that tortoisesvn uses, continuum sais it is not a valid url. > > > > > http://gridshoresample.tigris.org/source/browse/gridshoresample/trunk/sources/studentregistrations/pom.xml > > does not give a real xml file but an html page showing the xml (error - > > Cannot build maven project from > > D:\DOCUME~1\JETTRO~1.COE\LOCALS~1\Temp\continuum-25232.tmp.) > > > > > http://gridshoresample.tigris.org/svn/gridshoresample/trunk/sources/studentregistrations/pom.xml > > response is : not a valid url > > > > This is all finding place when trying to install a new maven 2 project. > > > > thanks for the help > > > > On 2/1/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > > >>What is your problems? > >> > >>http://maven.apache.org/continuum/guides/getting-started/index.html > >> > >>Emmanuel > >> > >>Jettro Coenradie a écrit : > >> > >>>Hi all, > >>>I am trying continuum. I am having problems getting it to work with a > >>>project under tigris. Does anyone have experience with this? > >>> > >>>thanks is advance > >>> > >> > >> > > > >
Re: Project dependencies with ANT projects
Has this feature implemented already in the development head? I may want to give it a try. Regards, Richard Li Emmanuel Venisse wrote: not yet. It will be available in 1.1 Emmanuel Richard C. L. Li a écrit : Hi, Is there any way to define project dependencies between ANT projects? Regards, Richard Li
Re: SPAM: looking at the maven site via continuum
Not possible actually directly. We are in discussion about it. Workaround, you can change the continuum working directory (in configuration screen) to a subdirectory of continuum/apps/continuum/webapp/, so it should be accessible via an url Emmanuel Jettro Coenradie a écrit : Hi all, I have another question. Is it possible to present the site generated by maven next to the build? It would be nice to be able to check the site from the continuum website. greetz Jettro
Re: Project dependencies with ANT projects
No. trunk (1.1) is unstable. continuum-1.0.X (1.0.3) branch is more stable but won't include it. Emmanuel Richard C. L. Li a écrit : Has this feature implemented already in the development head? I may want to give it a try. Regards, Richard Li Emmanuel Venisse wrote: not yet. It will be available in 1.1 Emmanuel Richard C. L. Li a écrit : Hi, Is there any way to define project dependencies between ANT projects? Regards, Richard Li
Re: SPAM: looking at the maven site via continuum
On 2/1/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > Not possible actually directly. We are in discussion about it. Whereabouts by the way? I can see a heading for it on the wiki page for 1.1 (well maybe; Report templating?), but no content. Nothing is jumping out of continuum-dev, but I could easily be failing to find the right search terms. Hen
RE: looking at the maven site via continuum
I agree. When I first though about using Continuum over CruiseControl I
read the statement that Continuums integrates well with the maven
architecture. A strong feature of Maven is the site generation, yet in
Continuum there is no way to see the site. Moreover the default
Continuum build ('clean install') does not build the site.
Even if you add 'site' as a build goal and then navigate to the Working
Copy then to the target/site directory you cannot open the HTML files in
continuum. Continuum lists the html as text.
Two things Continuum needs
1. Schedule builds based on scm commit activity (rather than fixed
scedules). CruiseControl has ability to launch builds soon after files
are commited to a repository and also has nice reporting facilities to
see the scm activity. (This feature is on future features list for
Continuum, I just want to put my vote in).
2. Provide support for Continuum to build and view the module site.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Jettro Coenradie
Sent: Wednesday, February 01, 2006 6:31 AM
To: continuum-users@maven.apache.org
Subject: looking at the maven site via continuum
Hi all,
I have another question. Is it possible to present the site generated by
maven next to the build? It would be nice to be able to check the site
from
the continuum website.
greetz Jettro
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.
Re: SPAM: looking at the maven site via continuum
Don't remeber exactly, probably in jira. I'll check. Emmanuel Henri Yandell a écrit : On 2/1/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: Not possible actually directly. We are in discussion about it. Whereabouts by the way? I can see a heading for it on the wiki page for 1.1 (well maybe; Report templating?), but no content. Nothing is jumping out of continuum-dev, but I could easily be failing to find the right search terms. Hen
Continuum build failure
I just incremented all my versions on a branch in continuum and expected that it would build automatically. It appears something is really wierd because when attempting to build the parent, it is trying to find itself in the repository. What's up with that? If I build manually, it's fine. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:120) 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:534) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExceptio n: Cannot build maven project from d:\builds\cont-work-dir\28\pom.xml. at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:268) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. mapMetadataToProject(DefaultMavenBuilderHelper.java:89) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:116) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'com.stchome.modules.applications.dsms:parent' not found in repository: Unable to download the artifact from any repository com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:423) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:955) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:586) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile( DefaultMavenProjectBuilder.java:298) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:283) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:260) ... 7 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:380) ... 12 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Defaul tWagonManager.java:260) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:124) ... 14 more
Re: looking at the maven site via continuum
Johnson, Jonathan a écrit :
I agree. When I first though about using Continuum over CruiseControl I
read the statement that Continuums integrates well with the maven
architecture. A strong feature of Maven is the site generation, yet in
Continuum there is no way to see the site. Moreover the default
Continuum build ('clean install') does not build the site.
Even if you add 'site' as a build goal and then navigate to the Working
Copy then to the target/site directory you cannot open the HTML files in
continuum. Continuum lists the html as text.
you can see the generated site if you deploy it in a server with site:deploy
Site generation isn't added by default because the basic of a continuous integration tool is to
build a project.
Two things Continuum needs
1. Schedule builds based on scm commit activity (rather than fixed
scedules). CruiseControl has ability to launch builds soon after files
are commited to a repository and also has nice reporting facilities to
see the scm activity. (This feature is on future features list for
Continuum, I just want to put my vote in).
How CruiseControl do it?
For scm activity, we already have a report like changelog report
2. Provide support for Continuum to build and view the module site.
You can already do it with a site deploy.
Emmanuel
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Jettro Coenradie
Sent: Wednesday, February 01, 2006 6:31 AM
To: continuum-users@maven.apache.org
Subject: looking at the maven site via continuum
Hi all,
I have another question. Is it possible to present the site generated by
maven next to the build? It would be nice to be able to check the site
from
the continuum website.
greetz Jettro
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.
Re: multi-module maven 2 project
Johnson, Jonathan a écrit : Emmanuel, I was hoping that Continuum would preserve the parent-child relationship of a parent and child poms. It would be nice to force a build on either a child or the parent. Forcing a build on the parent pom would build its child modules. Building dependant projects is a planned feature. As it stands now I can use the parent pom.xml to load all the sub-modules in Continuum, then I can remove the parent project since it is not necessary. This is confusing. As it stands now if you try to run the parent project it just reports a success without doing anything. I would expect an error saying it can't build the sub-modules or it builds the sub-modules. If you are saying that the parent pom.xml is not needed then shouldn't Continuum just add the child modules and not the parent. Why it isn't needed? You need it for submodule, at least to install it in local repo because sub-modules depends on it. Also, What if you add three parent pom.xml to Continuum. The flat list of modules looses the project groupings. Perhaps adding a tree or grouping concept for the Continuum Projects list would be a helpful addition. Project grouping is a planned features for 1.1 Emmanuel - Jonathan -Original Message- From: Stevenson, Chris [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 01, 2006 6:27 AM To: 'continuum-users@maven.apache.org' Subject: RE: multi-module maven 2 project Thanks for your responses gents. I was under wrong the impression that continuum didn't support multi module builds. Now I know it does I will definitely be using them more. Cheers, Chris -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 31 January 2006 08:46 To: continuum-users@maven.apache.org Subject: Re: multi-module maven 2 project a "command line project" is a Shell project. If you want to build all sub-modules when you build the parent, you have several solution. 1- You want all projects are independant in Continuum, so you add a Maven project. The default goal of a maven parent project isclean install with -N parameter that means that mvn doesn't run recursivly in all modules. You can remove -N parameter in build definition but all your submodules will be built twice (with parent pom and with independant project) 2- You don't need independant projects for submodules in Continuum. Add a Shell project instead of Maven project and set up the command line to run. Emmanuel Johnson, Jonathan a écrit : I submitted the parent pom to continuum. Its very nicely found all the sub-modules and set those up as well. I did not have to set up a command line project (not sure what that is either). One thing that could be enhanced for continuum is a tree structure instead of a flat list. The tree structure would indicate while module is the parent module. Currently there is not indicator which is you parent module. Of course that begs the question of a hierarchical, multi-project tree in maven and continuum. The other thing I noticed is forcing a build on the parent module in continuum does not execute the build on the all children. For me it quickly executes with a success yet the sub-module builds are not invoked. This is the build report on the parent module named "Java Modules". [INFO] Scanning for projects... [INFO] -- -- [INFO] Building Java Modules [INFO]task-segment: [clean, install] [INFO] -- -- [INFO] [clean:clean] [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [INFO] [install:install] [INFO] Installing /home/builder/454/AppJava/modules/66/pom.xml to /home/builder/.m2/repository/com/fourfivefour/AppJavaModules/1.0/AppJa vaModules-1.0.pom [INFO] -- -- [INFO] BUILD SUCCESSFUL [INFO] -- -- [INFO] Total time: 2 seconds [INFO] Finished at: Mon Jan 30 14:02:38 EST 2006 [INFO] Final Memory: 2M/5M [INFO] -- -- -Original Message- From: Stevenson, Chris [mailto:[EMAIL PROTECTED] Sent: Monday, January 30, 2006 1:04 PM To: 'continuum-users@maven.apache.org' Subject: RE: multi-module maven 2 project Gents, Can I just check, did you setup your mvn multi module project by submitting the parent pom and continuum working it out? Or did you have to create a command line project? I remember a while back that continuum couldn't build multi module projects, except as a command line project. Or am I going nuts.. Chris -Original Message- From: Johnson, Jonathan [mailto:[EMAIL PROTECTED] Sent: 27 January 2006 15:26 To: continuum-users@maven.apache.org Subject: RE: multi-module m
Re: Continuum build failure
Can you check your pom in d:\builds\cont-work-dir\28\? Is it the parent? If not, file an issue with more explanations of the problem and the full trace of project build Emmanuel Brian E. Fox a écrit : I just incremented all my versions on a branch in continuum and expected that it would build automatically. It appears something is really wierd because when attempting to build the parent, it is trying to find itself in the repository. What's up with that? If I build manually, it's fine. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:120) 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:534) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExceptio n: Cannot build maven project from d:\builds\cont-work-dir\28\pom.xml. at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:268) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. mapMetadataToProject(DefaultMavenBuilderHelper.java:89) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.upda teProjectFromCheckOut(MavenTwoBuildExecutor.java:116) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'com.stchome.modules.applications.dsms:parent' not found in repository: Unable to download the artifact from any repository com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:423) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(Defa ultMavenProjectBuilder.java:955) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:586) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile( DefaultMavenProjectBuilder.java:298) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:283) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:260) ... 7 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:380) ... 12 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Defaul tWagonManager.java:260) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:124) ... 14 more
Re: looking at the maven site via continuum
I do not really agree with you talking about the site:deploy stuff. A build
system is for building indeed, but the reports a part of building, the same
way unit tests are part of building. I will try the site:deploy stuff. How
can you integrate this with the different projects. Is there a way to tell
the number of the project in the work directory? Can we pass the version
number from continuum to maven or the other way around?
I do like the tool for it's simplicity, though some features would be very
nice. I will browse the wiki and jira stuff to see what is already there.
On 2/1/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
>
>
>
> Johnson, Jonathan a écrit :
> > I agree. When I first though about using Continuum over CruiseControl I
> > read the statement that Continuums integrates well with the maven
> > architecture. A strong feature of Maven is the site generation, yet in
> > Continuum there is no way to see the site. Moreover the default
> > Continuum build ('clean install') does not build the site.
> >
> > Even if you add 'site' as a build goal and then navigate to the Working
> > Copy then to the target/site directory you cannot open the HTML files in
> > continuum. Continuum lists the html as text.
>
> you can see the generated site if you deploy it in a server with
> site:deploy
> Site generation isn't added by default because the basic of a continuous
> integration tool is to
> build a project.
>
> >
> > Two things Continuum needs
> >
> > 1. Schedule builds based on scm commit activity (rather than fixed
> > scedules). CruiseControl has ability to launch builds soon after files
> > are commited to a repository and also has nice reporting facilities to
> > see the scm activity. (This feature is on future features list for
> > Continuum, I just want to put my vote in).
>
> How CruiseControl do it?
> For scm activity, we already have a report like changelog report
>
> >
> > 2. Provide support for Continuum to build and view the module site.
>
> You can already do it with a site deploy.
>
> Emmanuel
> >
> >
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> > Behalf Of Jettro Coenradie
> > Sent: Wednesday, February 01, 2006 6:31 AM
> > To: continuum-users@maven.apache.org
> > Subject: looking at the maven site via continuum
> >
> > Hi all,
> > I have another question. Is it possible to present the site generated by
> > maven next to the build? It would be nice to be able to check the site
> > from
> > the continuum website.
> >
> > greetz Jettro
> >
> > 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.
> >
> >
> >
> >
> >
>
>
clearcase, scm, Could not find Maven project descriptor
Hi All, I'm having this weired problem, Pleas let me know if anyone has solution for this i have project structure has Root + - - Module A + - - pom.xml + - - pom.xml in Root>pom.xml i have scm has scm|clearcase|MydevView_vu|/Raghu/config_spec.txt then i created maven 2 project in continuum and pointed to Root>pom.xml when i added this its checkedout files as i mentioned in my config_spec at "working directory" Then when clicked "Build Now" it did updated my new snapshot view at my "working directory" but after updating its failed to continue with the following error org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Could not find Maven project descriptor. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:111) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:62) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:169) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:534) But when checked at my working directory it has the pom and directory structure as shown above (i.e) C:\continuum-1.0.2\apps\continuum\working-directory\46\ + Root +- - Module A +- - pom.xml + pom.xml Can any one please tell me what am missing here?? Thanks, Raghurajan G
RE: Continuum build failure
Yes it's the parent. Here's the text of that pom: 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";> 4.0.0 com.stchome.modules.applications.dsms parent 2.1.0.2-SNAPSHOT DSMS Legacy Parent Pom com.stchome.modules.applications.dsms.legacy legacy pom com.stchome.non-maven MPI 1.6.0.2 compile hl7 nbs security case-assignment warehouse cdr-legacy user-management-struts cdr-ui I'm not sure where to find the log though, it's not in the cont-out-dir\28\ -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 01, 2006 12:28 PM To: continuum-users@maven.apache.org Subject: Re: Continuum build failure Can you check your pom in d:\builds\cont-work-dir\28\? Is it the parent? If not, file an issue with more explanations of the problem and the full trace of project build Emmanuel Brian E. Fox a écrit : > I just incremented all my versions on a branch in continuum and > expected that it would build automatically. It appears something is > really wierd because when attempting to build the parent, it is trying > to find itself in the repository. What's up with that? If I build > manually, it's fine. > org.apache.maven.continuum.execution.ContinuumBuildExecutorException: > Error while mapping metadata. > at > org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.up > da > teProjectFromCheckOut(MavenTwoBuildExecutor.java:120) > at > org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirecto > ry > ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumActi > on > .java:62) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.buil > d( > DefaultBuildController.java:169) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.ex > ec > uteTask(BuildProjectTaskExecutor.java:53) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Exec > ut > orRunnable.run(ThreadedTaskQueueExecutor.java:103) > at java.lang.Thread.run(Thread.java:534) > Caused by: > org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExcept > io > n: Cannot build maven project from d:\builds\cont-work-dir\28\pom.xml. > at > org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. > getMavenProject(DefaultMavenBuilderHelper.java:268) > at > org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. > mapMetadataToProject(DefaultMavenBuilderHelper.java:89) > at > org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.up > da > teProjectFromCheckOut(MavenTwoBuildExecutor.java:116) > ... 5 more > Caused by: org.apache.maven.project.ProjectBuildingException: POM > 'com.stchome.modules.applications.dsms:parent' not found in repository: > Unable to download the artifact from any repository > com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepos > it > ory(DefaultMavenProjectBuilder.java:423) > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(De > fa > ultMavenProjectBuilder.java:955) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMaven > Pr > ojectBuilder.java:586) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFil > e( > DefaultMavenProjectBuilder.java:298) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMaven > Pr > ojectBuilder.java:283) > at > org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. > getMavenProject(DefaultMavenBuilderHelper.java:260) > ... 7 more > Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: > Unable to download the artifact from any repository > com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Def > au > ltArtifactResolver.java:136) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Def > au > ltArtifactResolver.java:63) > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepos > it > ory(DefaultMavenProjectBuilder.java:380) > ... 12 more > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: > Unable to download the artifact from any repository > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Defa > ul > tWagonManager.java:260) > at >
Re: Continuum build failure
This parent pom have a parent : > > com.stchome.modules.applications.dsms > parent > 2.1.0.2-SNAPSHOT > it's this parent that is missing in your repo. Add it in your remote repo (or local) or add it in continuum Emmanuel Brian E. Fox a écrit : Yes it's the parent. Here's the text of that pom: 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";> 4.0.0 com.stchome.modules.applications.dsms parent 2.1.0.2-SNAPSHOT DSMS Legacy Parent Pom com.stchome.modules.applications.dsms.legacy legacy pom com.stchome.non-maven MPI 1.6.0.2 compile hl7 nbs security case-assignment warehouse cdr-legacy user-management-struts cdr-ui I'm not sure where to find the log though, it's not in the cont-out-dir\28\ -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 01, 2006 12:28 PM To: continuum-users@maven.apache.org Subject: Re: Continuum build failure Can you check your pom in d:\builds\cont-work-dir\28\? Is it the parent? If not, file an issue with more explanations of the problem and the full trace of project build Emmanuel Brian E. Fox a écrit : I just incremented all my versions on a branch in continuum and expected that it would build automatically. It appears something is really wierd because when attempting to build the parent, it is trying to find itself in the repository. What's up with that? If I build manually, it's fine. org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.up da teProjectFromCheckOut(MavenTwoBuildExecutor.java:120) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirecto ry ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumActi on .java:62) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.buil d( DefaultBuildController.java:169) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.ex ec uteTask(BuildProjectTaskExecutor.java:53) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Exec ut orRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:534) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExcept io n: Cannot build maven project from d:\builds\cont-work-dir\28\pom.xml. at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:268) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. mapMetadataToProject(DefaultMavenBuilderHelper.java:89) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.up da teProjectFromCheckOut(MavenTwoBuildExecutor.java:116) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'com.stchome.modules.applications.dsms:parent' not found in repository: Unable to download the artifact from any repository com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepos it ory(DefaultMavenProjectBuilder.java:423) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(De fa ultMavenProjectBuilder.java:955) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMaven Pr ojectBuilder.java:586) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFil e( DefaultMavenProjectBuilder.java:298) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMaven Pr ojectBuilder.java:283) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. getMavenProject(DefaultMavenBuilderHelper.java:260) ... 7 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Def au ltArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Def au ltArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepos it ory(DefaultMavenProjectBuilder.java:380) ... 12 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at
RE: Continuum build failure
Doht. Too many parents! -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 01, 2006 3:32 PM To: continuum-users@maven.apache.org Subject: Re: Continuum build failure This parent pom have a parent : > > com.stchome.modules.applications.dsms > parent > 2.1.0.2-SNAPSHOT > it's this parent that is missing in your repo. Add it in your remote repo (or local) or add it in continuum Emmanuel Brian E. Fox a écrit : > Yes it's the parent. Here's the text of that pom: > > 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";> > 4.0.0 > > > com.stchome.modules.applications.dsms > parent > 2.1.0.2-SNAPSHOT > > > DSMS Legacy Parent Pom > com.stchome.modules.applications.dsms.legacy > legacy > > pom > > > > >com.stchome.non-maven >MPI >1.6.0.2 > compile > > > > >hl7 >nbs >security >case-assignment >warehouse >cdr-legacy >user-management-struts >cdr-ui > > > > > > I'm not sure where to find the log though, it's not in the > cont-out-dir\28\ > > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 01, 2006 12:28 PM > To: continuum-users@maven.apache.org > Subject: Re: Continuum build failure > > Can you check your pom in d:\builds\cont-work-dir\28\? Is it the parent? > > If not, file an issue with more explanations of the problem and the > full trace of project build > > Emmanuel > > Brian E. Fox a écrit : > >>I just incremented all my versions on a branch in continuum and >>expected that it would build automatically. It appears something is >>really wierd because when attempting to build the parent, it is trying >>to find itself in the repository. What's up with that? If I build >>manually, it's fine. >>org.apache.maven.continuum.execution.ContinuumBuildExecutorException: >>Error while mapping metadata. >> at >>org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.up >>da >>teProjectFromCheckOut(MavenTwoBuildExecutor.java:120) >> at >>org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirecto >>ry >>ContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumActi >>on >>.java:62) >> at >>org.apache.maven.continuum.buildcontroller.DefaultBuildController.buil >>d( >>DefaultBuildController.java:169) >> at >>org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.ex >>ec >>uteTask(BuildProjectTaskExecutor.java:53) >> at >>org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Exec >>ut >>orRunnable.run(ThreadedTaskQueueExecutor.java:103) >> at java.lang.Thread.run(Thread.java:534) >>Caused by: >>org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperExcept >>io >>n: Cannot build maven project from d:\builds\cont-work-dir\28\pom.xml. >> at >>org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. >>getMavenProject(DefaultMavenBuilderHelper.java:268) >> at >>org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. >>mapMetadataToProject(DefaultMavenBuilderHelper.java:89) >> at >>org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.up >>da >>teProjectFromCheckOut(MavenTwoBuildExecutor.java:116) >> ... 5 more >>Caused by: org.apache.maven.project.ProjectBuildingException: POM >>'com.stchome.modules.applications.dsms:parent' not found in repository: >>Unable to download the artifact from any repository >> com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom >> >>from the specified remote repositories: >> central (http://repo1.maven.org/maven2) >> >> at >>org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepos >>it >>ory(DefaultMavenProjectBuilder.java:423) >> at >>org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(De >>fa >>ultMavenProjectBuilder.java:955) >> at >>org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMaven >>Pr >>ojectBuilder.java:586) >> at >>org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFil >>e( >>DefaultMavenProjectBuilder.java:298) >> at >>org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMaven >>Pr >>ojectBuilder.java:283) >> at >>org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper. >>getMavenProject(DefaultMavenBuilderHelper.java:260) >> ... 7 more >>Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: >>Unable to download the artifact from any repository >> com.stchome.modules.applications.dsms:parent:2.1.0.2-SNAPSHOT:pom >> >>from the specified remote repositories: >> central (http://repo1.maven.org/maven2) >> >> at >>org.apache.m
