# portals-jetspeed-user mailing list archives

##### Site index · List index
Message view
Top
From "Mohan Kannapareddy" <kmoh....@gmail.com>
Subject RE: Maven error in tutorial
Date Tue, 15 Apr 2008 15:18:33 GMT
```Wanted to chime in on the eclipse plugins for Maven:
- m2eclipse (tried it a while ago, didn't do very well, maybe better now)
- Q4E (eclipse blessed maven integration plugin, a lot of activity,
much better now, still some rough edges)
- maven-eclipse-plugin (let maven generate the project files, I prefer
this
but requires messing poms, but you get the full WTP support).

All in all, the state of Maven integration to Eclipse, is *way* (IMHO)
behind
Netbeans 6. In NB6 it is native and the eclipse plugins have a long way to
go to match nb6 (q4e is getting there). Some of things I like in nb6:
- dependencies split by scope and viewable as a tree.
- right click and exclude dependencies (life saver for a new m2 project).

Mohan

-----Original Message-----
From: Andrew Strickland [mailto:strickla@gmail.com]
Sent: Tuesday, April 15, 2008 9:58 AM
To: Jetspeed Users List
Subject: Re: Maven error in tutorial

I use the m2eclipse plugin for Eclipse from Codehaus
http://m2eclipse.codehaus.org/.  It automatically puts the Maven
dependencies onto the Eclipse project build path (you may have to enable the
option "Enable Dependency Management") from the Maven context menu of your
project but I don't remember for sure.

On Tue, Apr 15, 2008 at 9:46 AM, Ron Wheeler
<rwheeler@artifact-software.com>
wrote:

> Get the Eclipse plug-in for Maven.
> It is a very nice way to run a project in Eclipse.
> It can not do anything that Ant can not do but it does a lot of what Ant
> can do without you having to write anything.
>
> It is a different way to approach things but is very nice once you get it
> set up.
> The Maven documentation is abysmal. It is sparse, written from a totally
> useless point of view and you have to read between the lines to make any
> sense of it. If they had decent docs, it would be universally used for any
> project with more than 2 developers.
> On the bright side, once you have a POM file set up or given to you, you
> usually do not have much contact with Maven until you start to add new
> dependencies to your project and they go in pretty well.
>
> The worst thing about Maven and Eclipse is that Eclipse has to be told
> about your dependencies manually in order to do syntax highlighting. You
> If not, your code will be lit up like a Xmas tree and still compile.
> Not a big deal but the Plug-in should deal with this. (Maybe it does and I
> have not found the right place to poke it - Eclipse is a great IDE but
takes
> a long time to get good at it.)
>
> Ron
>
>
> benethridge@charter.net wrote:
>
> > Thanks. So as to not waste any more of your time, sounds like I should
> > drop this tutorial and shift to the maven tutorial, as per David Taylor.
> >
> > Hopefully I can use the maven tutorial code as Eclipse projects with
> > some tweaking?
> >
> > Ben
> > ---- Andrew Strickland <strickla@gmail.com> wrote:
> >
> > > or rather, I guess that "null" corresponds to the groupId in the POM
> > > of the
> > > express-demo project.  Check to see if that has a value.
> > >
> > > On Mon, Apr 14, 2008 at 8:26 PM, Andrew Strickland <strickla@gmail.com
> > > >
> > > wrote:
> > >
> > >
> > >
> > > > without looking at the code, the problem to me seems to be the:
> > > > *
> > > > Caused by: org.apache.maven.project*
> > > > *.ProjectBuildingException: Cannot find parent
> > > > : org.apache.portals.tutorials**:portal-applications for project:
> > > > null:express-dem
> > > > o:war:null for project null:express-demo:war:null
> > > >
> > > > *
> > > > Whatever the value of the express-demo pom artifactId is, it's not
> > > > supposed to be "null".  Just a guess though,
> > > >
> > > > Andy
> > > >
> > > >
> > > >
> > > > On Mon, Apr 14, 2008 at 6:58 PM, <benethridge@charter.net> wrote:
> > > >
> > > >
> > > >
> > > > > Hi. I'm trying to figure out why I'm getting this maven error, at
> > > > > this
> > > > > point in the tutorial:
> > > > >
> > > > >
> > > > >
http://portals.apache.org/tutorials/jetspeed-2-ant/03/build-it.html
> > > > >
> > > > > Below are details of the error:
> > > > >
> > > > > ----------------------------------------------------------------
> > > > >  Directory of
> > > > > ions\express-demo
> > > > >
> > > > > 04/14/2008  06:11 PM    <DIR>          .
> > > > > 04/14/2008  06:11 PM    <DIR>          ..
> > > > > 04/14/2008  06:11 PM             7,816 pom.xml
> > > > > 04/14/2008  06:11 PM    <DIR>          src
> > > > >              1 File(s)          7,816 bytes
> > > > >              3 Dir(s)  169,487,032,320 bytes free
> > > > >
> > > > >
> > > > >
> > > > >
ss-d
> > > > > emo>mvn
> > > > > [INFO] Scanning for projects...
> > > > >
> > > > >
http://repo1.maven.org/maven2/org/apache/portals/tutorials/portal-a
> > > > > pplications/1.0/portal-applications-1.0.pom<
> > > > >
http://repo1.maven.org/maven2/org/apache/portals/tutorials/portal-applicatio
ns/1.0/portal-applications-1.0.pom
> > > > > >
> > > > > [INFO]
> > > > >
> > > > >
------------------------------------------------------------------------
> > > > > [ERROR] FATAL ERROR
> > > > > [INFO]
> > > > >
> > > > >
------------------------------------------------------------------------
> > > > > [INFO] Failed to resolve artifact.
> > > > >
> > > > > GroupId: org.apache.portals.tutorials
> > > > > ArtifactId: portal-applications
> > > > > Version: 1.0
> > > > >
> > > > > Reason: Unable to download the artifact from any repository
> > > > >
> > > > >  org.apache.portals.tutorials:portal-applications:pom:1.0
> > > > >
> > > > > from the specified remote repositories:
> > > > >  central (http://repo1.maven.org/maven2)
> > > > >
> > > > >
> > > > > [INFO]
> > > > >
> > > > >
------------------------------------------------------------------------
> > > > > [INFO] Trace
> > > > > org.apache.maven.reactor.MavenExecutionException: Cannot find
> > > > > parent:
> > > > > org.apache
> > > > > .portals.tutorials:portal-applications for project:
> > > > > null:express-demo:war:null f
> > > > > or project null:express-demo:war:null
> > > > >       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.apache.portals.tutorials:portal-applications for project:
> > > > > null:express-dem
> > > > > o:war:null for project null:express-demo:war:null
> > > > >       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.apache.po
> > > > > Unable to
> > > > >  the artifact from any repository
> > > > >
> > > > >  org.apache.portals.tutorials:portal-applications:pom:1.0
> > > > >
> > > > > from the specified remote repositories:
> > > > >  central (http://repo1.maven.org/maven2)
> > > > >  for project org.apache.portals.tutorials:portal-applications
> > > > >       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.apache.portals.tutorials:portal-applications:pom:1.0
> > > > >
> > > > > 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: Mon Apr 14 18:17:33 EDT 2008
> > > > > [INFO] Final Memory: 1M/2M
> > > > > [INFO]
> > > > >
> > > > >
------------------------------------------------------------------------
> > > > >
> > > > >
> > > > >
> > > > >
ss-d
> > > > > emo>
> > > > >
> > > > >
> > > > >
---------------------------------------------------------------------------
> > > > >
> > > > > As a side-issue, I've managed to work around many of the obvious
> > > > > errors
> > > > > in the tutorial and gotten pretty far with the changes and "delta"
> > > > > deploys,
> > > > > but it contains so many bugs and incorrect file locations and
> > > > > such, that
> > > > > it's almost useless as a "tutorial" for newcomers...hard to see
> > > > > the forest
> > > > > for all the trees.  Of course, those who already have good
> > > > > experience with
> > > > > jetspeed and/or portlets AND tomcat AND maven AND eclipse AND ant,
> > > > > will
> > > > > probably be able to figure it out....but that's more background
> > > > > knowledge
> > > > > than most newcomers will probably have...or are willing to learn
> > > > > for no
> > > > > other reason than to learn portlets.
> > > > >
> > > > > The tutorial looks like it was quite good at one time, so it gives
> > > > > me
> > > > > the feeling that this jetspeed (and maybe portlets in general)
> > > > > isn't being
> > > > > actively advanced anymore. Is that so?
> > > > >
> > > > > Ben
> > > > >
> > > > >
> > > > >
> > > > >
---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > > > > jetspeed-user-unsubscribe@portals.apache.org
> > > > > For additional commands, e-mail:
> > > > > jetspeed-user-help@portals.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org