Maven 1

"maven eclipse" can't find org.apache.commons.jelly.tags.xml.XMLTagLibrary

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.0-rc2
  • Fix Version/s: 1.0-rc3
  • Component/s: jelly/ant integration
  • Labels:
    None
  • Environment:
    Win2k
    JRE 1.4.2_04
    *clean/empty* Maven repo
  • Number of attachments :
    2

Description

See attached files for more console output. It seems to be a dependency problem with the cactus plugin.

This is, how I produce the error:

C:\>rmdir /S /Q "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven\repository"

C:\>mkdir App

C:\>cd App

C:\App>maven genapp

[...]

C:\App>maven eclipse

[...]

Could not find the class:
org.apache.commons.jelly.tags.xml.XMLTagLibrary

[...]

  1. maven_-X_eclipse.txt
    06/May/04 12:46 AM
    6 kB
    Christian Stein
  2. maven+eclipse.txt
    06/May/04 12:45 AM
    15 kB
    Christian Stein

Activity

Hide
Christian Stein added a comment -

Complete console output.

Show
Christian Stein added a comment - Complete console output.
Hide
Christian Stein added a comment -

Debugging console. (-X)

Show
Christian Stein added a comment - Debugging console. (-X)
Hide
Christian Stein added a comment -

Why cactus? See excerpt from maven_-X_eclipse.txt:

[...]

Using projectPropertiesFile: ...\.maven\plugins\cactus-maven-1.6dev-20040226\project.properties

Using projectBuildPropertiesFile: ...\.maven\plugins\cactus-maven-1.6dev-20040226\build.properties

running script ...\.maven\plugins\cactus-mav
en-1.6dev-20040226\plugin.jelly

Processing dependencies for project Maven Cactus plugin; classloader [ForeheadClassLoader: name="root.maven"]

Non classpath dependency: '...\.maven\repository\maven\plugins\maven-ear-plugin-1.3.jar' not added to classpath

Non classpath dependency: '...\.maven\repository\maven\plugins\maven-ejb-plugin-1.2.jar' not added to classpath

Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary

[...]

Show
Christian Stein added a comment - Why cactus? See excerpt from maven_-X_eclipse.txt: [...] Using projectPropertiesFile: ...\.maven\plugins\cactus-maven-1.6dev-20040226\project.properties Using projectBuildPropertiesFile: ...\.maven\plugins\cactus-maven-1.6dev-20040226\build.properties running script ...\.maven\plugins\cactus-mav en-1.6dev-20040226\plugin.jelly Processing dependencies for project Maven Cactus plugin; classloader [ForeheadClassLoader: name="root.maven"] Non classpath dependency: '...\.maven\repository\maven\plugins\maven-ear-plugin-1.3.jar' not added to classpath Non classpath dependency: '...\.maven\repository\maven\plugins\maven-ejb-plugin-1.2.jar' not added to classpath Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary [...]
Hide
Brett Porter added a comment -

eclipse uses cactus if it is installed
cactus plugin you are using has a bug, missing that dependency
update cactus plugin, or file bug there.

Show
Brett Porter added a comment - eclipse uses cactus if it is installed cactus plugin you are using has a bug, missing that dependency update cactus plugin, or file bug there.
Hide
Christian Stein added a comment -

Ok. I'll file a bug there.

Show
Christian Stein added a comment - Ok. I'll file a bug there.
Hide
dion gillard added a comment -

I don't think cactus is the issue.

From the src\plugin-test dir of maven-plugins\eclipse gives an error running: maven testPlugin, whereas running maven plugin:test from the eclipse directory works ok. The test project has an xml dependency.

Something is screwy here.

Show
dion gillard added a comment - I don't think cactus is the issue. From the src\plugin-test dir of maven-plugins\eclipse gives an error running: maven testPlugin, whereas running maven plugin:test from the eclipse directory works ok. The test project has an xml dependency. Something is screwy here.
Hide
Brett Porter added a comment -

alright I'll take a look

Show
Brett Porter added a comment - alright I'll take a look
Hide
Brett Porter added a comment -

That was misleading. The eclipse plugin test project.xml was invalid, so the dependency was not being used.

I return to my original verdict

Show
Brett Porter added a comment - That was misleading. The eclipse plugin test project.xml was invalid, so the dependency was not being used. I return to my original verdict

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: