It's not just the docs, though.  It's also the modeler projects and
cayenne-project.

On Tue, Sep 24, 2013 at 10:21 AM, Andrus Adamchik
<and...@objectstyle.org> wrote:
> I haven't tried importing anything under doc/ into Eclipse. But other 
> projects seem to work fine. (Or maybe I need a newer m2eclipse to see it)
>
> Andrus
>
> On Sep 24, 2013, at 5:16 PM, Mike Kienenberger <mkien...@gmail.com> wrote:
>
>> So I'm really getting frustrated with maven the more I have to deal
>> with projects that use it as maven never seems to work as anything
>> other than a command-line tool.
>>
>> Like the 3.0 branch, the 3.1 branch also will not build in eclipse
>> using maven using the default instructions.  Hundreds of errors,
>> probably most of which are caused by the pom.xml problems listed at
>> the end.
>>
>> Yes, I can close all of the tutorial, modeler, project, docs, and all
>> of the other "optional" projects, and at least the core part builds,
>> but that seems to defeat the point of working on the project in
>> eclipse.
>>
>> Am I doing something wrong?  This is how I'm setting things up:
>>
>> 1) check out project using svn comand-line tool in a non-workspace location.
>>
>> 2) "mvn clean install" to build the project first.  Apache Maven 3.0.3
>> -- maybe this isn't the right version to use?
>>
>> 3) Create new Juno Eclipse workspace and "Import" "Existing Maven
>> Project" using m2e maven plugin.
>>
>>
>> Description    Resource    Path    Location    Type
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-pdf
>> (execution: build-pdf, phase: generate-resources)    pom.xml
>> /getting-started    line 22    Maven Project Build Lifecycle Mapping
>> Problem
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html
>> (execution: build-html, phase: generate-resources)    pom.xml
>> /getting-started    line 22    Maven Project Build Lifecycle Mapping
>> Problem
>> Plugin execution not covered by lifecycle configuration:
>> org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:javadoc
>> (execution: javadoc, phase: generate-resources)    pom.xml
>> /cayenne-doc    line 192    Maven Project Build Lifecycle Mapping
>> Problem
>> Plugin execution not covered by lifecycle configuration:
>> org.codehaus.mojo:dependency-maven-plugin:1.0:unpack (execution:
>> unpack-sources, phase: generate-sources)    pom.xml    /cayenne-doc
>> line 161    Maven Project Build Lifecycle Mapping Problem
>> Plugin execution not covered by lifecycle configuration:
>> org.objectstyle.woproject.maven2:maven-japplication-plugin:2.0.17:japplication
>> (execution: default, phase: generate-resources)    pom.xml
>> /cayenne-modeler-mac    line 94    Maven Project Build Lifecycle
>> Mapping Problem
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html
>> (execution: build-html, phase: generate-resources)    pom.xml
>> /getting-started-rop    line 22    Maven Project Build Lifecycle
>> Mapping Problem
>> The project was not built since its build path is incomplete. Cannot
>> find the class file for org.apache.cayenne.map.DbEntity. Fix the build
>> path then try building this project    maven-cayenne-plugin
>> Unknown    Java Problem
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-pdf
>> (execution: build-pdf, phase: generate-resources)    pom.xml
>> /getting-started-rop    line 22    Maven Project Build Lifecycle
>> Mapping Problem
>> Plugin execution not covered by lifecycle configuration:
>> org.apache.maven.plugins:maven-remote-resources-plugin:1.0-alpha-1:bundle
>> (execution: default, phase: generate-resources)    pom.xml
>> /cayenne-legal-unpublished    line 64    Maven Project Build Lifecycle
>> Mapping Problem
>> Plugin execution not covered by lifecycle configuration:
>> org.objectstyle.woproject.maven2:maven-japplication-plugin:2.0.17:japplication
>> (execution: default, phase: generate-resources)    pom.xml
>> /cayenne-modeler-generic    line 88    Maven Project Build Lifecycle
>> Mapping Problem
>> Plugin execution not covered by lifecycle configuration:
>> org.objectstyle.woproject.maven2:maven-japplication-plugin:2.0.17:japplication
>> (execution: default, phase: generate-resources)    pom.xml
>> /cayenne-modeler-win    line 91    Maven Project Build Lifecycle
>> Mapping Problem
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html
>> (execution: build-html, phase: generate-resources)    pom.xml
>> /upgrade-guide    line 22    Maven Project Build Lifecycle Mapping
>> Problem
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-pdf
>> (execution: build-pdf, phase: generate-resources)    pom.xml
>> /upgrade-guide    line 22    Maven Project Build Lifecycle Mapping
>> Problem
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-pdf
>> (execution: build-pdf, phase: generate-resources)    pom.xml
>> /cayenne-guide    line 22    Maven Project Build Lifecycle Mapping
>> Problem
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html
>> (execution: build-html, phase: generate-resources)    pom.xml
>> /cayenne-guide    line 22    Maven Project Build Lifecycle Mapping
>> Problem
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html
>> (execution: build-html, phase: generate-resources)    pom.xml
>> /docbook-stylesheets    line 23    Maven Project Build Lifecycle
>> Mapping Problem
>> Plugin execution not covered by lifecycle configuration:
>> com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-pdf
>> (execution: build-pdf, phase: generate-resources)    pom.xml
>> /docbook-stylesheets    line 23    Maven Project Build Lifecycle
>> Mapping Problem
>>
>

Reply via email to