precautions with a rebuild of jopr| JBoss.org Content Archive (Read Only)

15. Re: precautions with a rebuild of jopr

jbosstcs Feb 16, 2009 1:32 PM (in response to jbosstcs)

1.) yes i am on windows vista sp1 ( could the vista part be a problem ? )

2.) there is no settings.xml in the .m2 directory...

3.) the output of mvn -N install from trunk is as follows

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Cannot execute mojo: resources. It requires a project with an existing po
m.xml, but the build is not using one.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Mon Feb 16 23:55:45 IST 2009
[INFO] Final Memory: 3M/127M
[INFO] ------------------------------------------------------------------------

4.) the result of mvn -e install as suggested in the above result is

+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Cannot execute mojo: resources. It requires a project with an existing po
m.xml, but the build is not using one.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute mojo: res
ources. It requires a project with an existing pom.xml, but the build is not usi
ng one.
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:583)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:499)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:478)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:330)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:291)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.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(DelegatingMethodAcces
sorImpl.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: Cannot execute mojo:
resources. It requires a project with an existing pom.xml, but the build is not
using one.
 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:377)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:558)
 ... 16 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Tue Feb 17 00:01:22 IST 2009
[INFO] Final Memory: 3M/127M
[INFO] ------------------------------------------------------------------------

16. Re: precautions with a rebuild of jopr

mazz Feb 16, 2009 1:44 PM (in response to jbosstcs)

Ok, this sounds like your svn working copy is not correct. You are missing the pom.xml file.

Let's step back. When I say checkout the jopr project, and the "root jopr trunk module" I literally mean this directory:

https://anonsvn.jboss.org/repos/jopr/trunk/

So if you did this (assuming you have a C:\Temp directory):

cd C:\Temp
svn co https://anonsvn.jboss.org/repos/jopr/trunk/

You should have a "C:\Temp\trunk" directory. In there, you should have a pom.xml that matches this pom.xml:
https://anonsvn.jboss.org/repos/jopr/trunk/pom.xml

So if you run "mvn" from inside this C:\Temp\trunk directory you should be building the jopr-parent pom module - but your mvn output is saying the pom.xml for your project doesn't exist! I don't see how that can be.

Double check your jopr source working copy - see if your root directory matches the content in here:

https://anonsvn.jboss.org/repos/jopr/trunk/

17. Re: precautions with a rebuild of jopr

jbosstcs Feb 16, 2009 2:02 PM (in response to jbosstcs)

oh.. so sorry... i ran mvn from c:\ instead of c:\trunk in haste... having run mvn from trunk , the output is

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.rhq
ArtifactId: rhq-parent
Version: 1.2.0-SNAPSHOT

Reason: Unable to download the artifact from any repository

 org.rhq:rhq-parent:pom:1.2.0-SNAPSHOT

from the specified remote repositories:
 central (http://repo1.maven.org/maven2)


[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.rhq:rh
q-parent for project: org.jboss.on:jopr-parent:pom:2.2.0-SNAPSHOT for project or
g.jboss.on:jopr-parent:pom:2.2.0-SNAPSHOT
 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
 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(DelegatingMethodAcces
sorImpl.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.project.ProjectBuildingException: Cannot find parent
: org.rhq:rhq-parent for project: org.jboss.on:jopr-parent:pom:2.2.0-SNAPSHOT fo
r project org.jboss.on:jopr-parent:pom:2.2.0-SNAPSHOT
 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
efaultMavenProjectBuilder.java:1370)
 at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def
aultMavenProjectBuilder.java:821)
 at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
leInternal(DefaultMavenProjectBuilder.java:506)
 at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
nProjectBuilder.java:198)
 at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
 at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
 ... 11 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.rhq:rhq-p
arent' not found in repository: Unable to download the artifact from any reposit
ory

 org.rhq:rhq-parent:pom:1.2.0-SNAPSHOT

from the specified remote repositories:
 central (http://repo1.maven.org/maven2)
 for project org.rhq:rhq-parent
 at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
sitory(DefaultMavenProjectBuilder.java:603)
 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
efaultMavenProjectBuilder.java:1366)
 ... 17 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable
to download the artifact from any repository

 org.rhq:rhq-parent:pom:1.2.0-SNAPSHOT

from the specified remote repositories:
 central (http://repo1.maven.org/maven2)

 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:212)
 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:74)
 at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
sitory(DefaultMavenProjectBuilder.java:556)
 ... 18 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to downl
oad the artifact from any repository
 at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def
aultWagonManager.java:331)
 at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
faultArtifactResolver.java:200)
 ... 20 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Tue Feb 17 00:31:15 IST 2009
[INFO] Final Memory: 1M/127M
[INFO] ------------------------------------------------------------------------

and yes the trunk/ structure is the same as https://anonsvn.jboss.org/repos/jopr/trunk/

18. Re: precautions with a rebuild of jopr

mazz Feb 16, 2009 2:11 PM (in response to jbosstcs)

grrr... we didn't put RHQ snapshots up on the repo either:

http://repository.jboss.com/maven2/org/rhq/rhq-parent/

We are missing 1.2.0-SNAPSHOT here.

Ian - what are your thoughts on getting snapshot builds up on the repo?

19. Re: precautions with a rebuild of jopr

ips Feb 16, 2009 2:36 PM (in response to jbosstcs)

We do publish RHQ snapshots, but they are published to the JBoss snapshots repo (http://snapshots.jboss.org/maven2/org/rhq/). However, we only publish the core jars and a few of the plugin jars - enough for someone to build a Jopr plugin from trunk without having to checkout and build RHQ, but not enough to build the entire Jopr distribution.

To enable downloading of snapshots, you'll need to add the following to the repositories section of your ~/.m2/settings.xml.

 <repository>
 <id>jboss-snapshots</id>
 <name>JBoss Snapshot Repository</name>
 <url>http://snapshots.jboss.org/maven2/</url>
 <snapshots>
 <enabled>true</enabled>
 </snapshots>
 </repository>

20. Re: precautions with a rebuild of jopr

mazz Feb 16, 2009 3:19 PM (in response to jbosstcs)

ah, ok, so he can do what he wants, because all he wants to do it build the jopr plugins.

So, we should consider putting this information in /etc/settings.xml as an example, because otherwise, how would people know to do this?