Dependencies do not resolve.

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Install q4e
2. Import project (archiva trunk in this case)

What is the expected output? What do you see instead?

Projects are available, all dependencies resolved.

What version of the product are you using? On what operating system?

Latest from update site. Linux. Ubuntu Fiesty.

Please provide any additional information below.

Original issue reported on code.google.com by joakim.erdfelt on 18 Jul 2007 at 2:49

GoogleCodeExporter commented 9 years ago

Original comment by carlossg on 24 Jul 2007 at 5:34

Changed state: Started
Added labels: Priority-Critical
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

to be clear, this appears to be only inter-project dependencies - from what I 
can
see. That is, it doesn't resolve the dependencies on snapshots to the other 
modules
being imported from Archiva (this causes a big slowdown as it checks the remote
repository for snapshots, and an incorrect result at the end when it doesn't 
resolve
to anything)

Original comment by brett.po...@gmail.com on 30 Jul 2007 at 4:26

GoogleCodeExporter commented 9 years ago

Actually. I get NO dependencies resolved.
Not even simple ones like 'junit'.

I updated and tested again, using org.devzuz.q.feature_0.2.0.v200707261452 now.
Still does not resolve dependencies.

Original comment by joakim.erdfelt on 30 Jul 2007 at 5:10

GoogleCodeExporter commented 9 years ago

doing this on a smaller set of libraries, I saw a problem, then eventually it
resolved itself. But then after changes or restarting the workbench they are 
lost
again. Doing a refresh and then a "clean" from the build menu helps it to 
resolve itself.

Original comment by brett.po...@gmail.com on 10 Aug 2007 at 3:04

GoogleCodeExporter commented 9 years ago

The cause of this problem is in this thread 

http://groups.google.com/group/q4e-dev/browse_thread/thread/3ea808ec0f8e0cb

Original comment by eman...@gmail.com on 15 Aug 2007 at 5:35

GoogleCodeExporter commented 9 years ago

this shouldn't be a problem if projects are already installed in the repo, is 
it?

Original comment by carlossg on 15 Aug 2007 at 9:56

GoogleCodeExporter commented 9 years ago

I just upgraded to q4e 0.2.0.v200708302115 and tried again.

What I did.

1) Checked out a fresh copy of archiva/trunk into a new directory.
2) Did a mvn clean install from the command line (to ensure that all artifacts 
are in
the local repository)
3) Opened up Eclipse 3.3.0 - Build id: I20070625-1500
4) Imported the maven 2 project from the archiva/trunk root.

Waited ...

5) Of the 30 imported projects, 17 show up with errors due to missing 
dependencies.

Most common missing dependency is the plexus container itself.

Still can't get the dependencies to resolve.

Original comment by joakim.erdfelt on 31 Aug 2007 at 7:06

Attachments:

q4e_missing_dep_issue.jpg

GoogleCodeExporter commented 9 years ago

I get a new error dialog with the latest 0.2.1 from the update site.

An internal error occurred during: "Updating classpath container: 
archiva-consumer-api".
org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException.getMissing
Artifacts()Ljava/util/List;

This is the most common error.
The project can still compile perfectly on command line and even using the
competition (m2eclipse)

Original comment by joakim.erdfelt on 18 Sep 2007 at 12:45

GoogleCodeExporter commented 9 years ago

I get a dialog with several errors "loader constraints violated" for XMLReader 
(not
sure it this is really important for now) and a "Some builds failed" error

All the folders in the project dir look like added as source folders, and 
there's no
.classpath file generated

First thing to do is change it so if build fails while trying to get the 
generated
folders the "static" source folders from the pom should be used

Then look at why the build fails

Original comment by carlossg on 18 Sep 2007 at 1:23

GoogleCodeExporter commented 9 years ago

Original comment by carlossg on 18 Sep 2007 at 1:24

Added labels: Milestone-0.2.2

GoogleCodeExporter commented 9 years ago

I also see in the error log the following alongside the loader constraints:

java.lang.NullPointerException
        at
org.devzuz.q.maven.jdt.core.exception.MavenExceptionHandler.handle(MavenExceptio
nHandler.java:55)

Original comment by brett.po...@gmail.com on 18 Sep 2007 at 1:50

GoogleCodeExporter commented 9 years ago

Fixed the NullPointerException in comment #11

Original comment by carlossg on 18 Sep 2007 at 2:05

GoogleCodeExporter commented 9 years ago

Now it seems to be imported with some out of memory exceptions but generated 
source
folders are not added

Original comment by carlossg on 19 Sep 2007 at 12:30

GoogleCodeExporter commented 9 years ago

I noticed that when a dependency is specified in a parent pom that is not a 
project
then that dependency isn't being added into the cp of the project.

for example, in redback the redback-authorization pom specifies the 
redback-users-api
dependency and also modules for the providers and the authorization-api...it 
puts
that dependency there since all of the children of that parent will need that
dependency anyway, but in q4e they don't get it, I have to specifically put the
dependency in each pom for it to be factored into their CP.

Original comment by jesse.mc...@gmail.com on 25 Sep 2007 at 3:37

GoogleCodeExporter commented 9 years ago

I noticed that when a dependency is specified in a parent pom that is not a 
project
then that dependency isn't being added into the cp of the project.

for example, in redback the redback-authorization pom specifies the 
redback-users-api
dependency and also modules for the providers and the authorization-api...it 
puts
that dependency there since all of the children of that parent will need that
dependency anyway, but in q4e they don't get it, I have to specifically put the
dependency in each pom for it to be factored into their CP.

Original comment by jesse.mc...@gmail.com on 25 Sep 2007 at 3:41

GoogleCodeExporter commented 9 years ago

I just tried importing the entire archiva codebase(30 projects) into q4e(trunk) 
with
-Xmx256m , and all the dependencies were resolved, no errors. Can anyone verify 
this?

Original comment by eman...@gmail.com on 25 Sep 2007 at 4:06

GoogleCodeExporter commented 9 years ago

Can you provide the commands to fetch Archiva? If so, I can spend some minutes
testing it.

Original comment by amu...@gmail.com on 25 Sep 2007 at 11:39

GoogleCodeExporter commented 9 years ago

Archiva is hosted at the apache repo ...

svn checkout http://svn.apache.org/repos/asf/maven/archiva/trunk/ archiva-trunk

Original comment by eman...@gmail.com on 26 Sep 2007 at 7:18

Attachments:

GoogleCodeExporter commented 9 years ago

Checked out and imported the projects in a clean workspace using a run-time 
workbench.

On the first import (lots of dependencies missing from my local repo) I saw some
errors regarding the update of source folders. After cleaning the workspace and
importing projects again, I could see no errors on the eclipse log.

In both cases, there where lots of unresolved classes in the "Problems" view.
Rebuilding all projects did not fix those.

I'm running mac osx 10.4.10 on an Intel Core2Duo processor.
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)

Original comment by amu...@gmail.com on 26 Sep 2007 at 10:49

GoogleCodeExporter commented 9 years ago

Original comment by amu...@gmail.com on 3 Oct 2007 at 1:40

Added labels: Milestone-0.2.3
Removed labels: Milestone-0.2.2

GoogleCodeExporter commented 9 years ago

Update: Just tested the following combo.

* Eclipse 3.3.1 (Fall Update / JEE / Linux) -
http://ftp.ussg.iu.edu/eclipse/technology/epp/downloads/release/20070927/eclipse
-jee-europa-fall-linux-gtk.tar.gz
* Executed via command line [eclipse/]$ eclipse -data
$HOME/java/eclipse/workspaces/archiva-q4e -showlocation -vmargs -Xmx1536m
* q4e - 0.2.2.200710031825
* Java JDK - Java(TM) 2 Runtime Environment, Standard Edition (build 
1.5.0_11-b03)

Results.
1. Fresh checkout of archiva/trunk to new directory.
2. Load eclipse, and use File / Import ... / General / Maven 2 Project
3. Browse to top level directory of checkout ( 
/home/joakim/code/archiva/trunk-q4e )
4. All projects are listed in dialog box.  Select All.  Hit Finish.
5. Import begins, but results in a NullPointerException during the "Importing 
Maven
Projects" step.  only archiva-common and archiva-policies gets loaded, the rest 
are
not there.

Checking logs I find the following tidbits.

---

!ENTRY org.eclipse.update.core 4 0 2007-10-03 09:59:06.559
!MESSAGE Unable to retrieve remote reference "http://q4e.googlecode.com/svn/trun
k/updatesite/features/org.devzuz.q.feature_0.2.0.v200708302159.jar". [Server ret
urned HTTP response code: "404 Not Found" for URL: http://q4e.googlecode.com/svn
/trunk/updatesite/features/org.devzuz.q.feature_0.2.0.v200708302159.jar.]
!STACK 0
org.eclipse.update.internal.core.FatalIOException: Server returned HTTP response
 code: "404 Not Found" for URL: http://q4e.googlecode.com/svn/trunk/updatesite/f
eatures/org.devzuz.q.feature_0.2.0.v200708302159.jar.
        at org.eclipse.update.internal.core.UpdateManagerUtils.checkConnectionRe
sult(UpdateManagerUtils.java:562)
        at org.eclipse.update.core.ContentReference.getInputStream(ContentRefere
nce.java:147)

---

!ENTRY org.devzuz.q.maven.jdt.ui 4 0 2007-10-03 10:02:18.120
!MESSAGE Unable to import project from
/home/joakim/code/maven/archiva/trunk-q4e/archiva-base/archiva-policies
!STACK 1
org.eclipse.core.runtime.CoreException: Problems encountered while setting 
project
description.
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:983)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1009)
    at org.devzuz.q.maven.jdt.core.MavenNatureHelper.addNature(MavenNatureHelper.java:35)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectJob.createMavenProject(Impo
rtProjectJob.java:159)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectJob.run(ImportProjectJob.ja
va:87)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectWorkspaceJob.runInWorkspace
(ImportProjectWorkspaceJob.java:57)
    at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJo
b.java:38)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SUBENTRY 1 org.eclipse.core.resources 4 568 2007-10-03 10:02:18.120
!MESSAGE Problems encountered while setting project description.
!SUBENTRY 2 org.eclipse.core.resources 4 566 2007-10-03 10:02:18.120
!MESSAGE Error configuring nature 'org.devzuz.q.maven.jdt.core.mavenNature'.
!STACK 0
java.lang.LinkageError: loader constraints violated when linking
org/xml/sax/XMLReader class
    at org.jdom.input.SAXBuilder.createParser(SAXBuilder.java:573)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:424)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:810)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:789)
    at
org.codehaus.plexus.cdc.DefaultComponentDescriptorCreator.mergeDescriptors(Defau
ltComponentDescriptorCreator.java:246)
    at
org.codehaus.plexus.maven.plugin.AbstractMergeMojo.execute(AbstractMergeMojo.jav
a:150)
    at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:647)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:354)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:255)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.java:141)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
    at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:911)
    at
org.devzuz.q.maven.embedder.internal.EclipseMaven.executeRequest(EclipseMaven.ja
va:250)
    at
org.devzuz.q.maven.embedder.internal.EclipseMavenRequest.run(EclipseMavenRequest
.java:56)
    at org.devzuz.q.maven.embedder.internal.EclipseMaven.executeGoals(EclipseMaven.java:134)
    at org.devzuz.q.maven.embedder.internal.EclipseMaven.executeGoal(EclipseMaven.java:119)
    at org.devzuz.q.maven.embedder.internal.EclipseMaven.executeGoal(EclipseMaven.java:113)
    at org.devzuz.q.maven.jdt.core.nature.MavenNature.addClasspath(MavenNature.java:193)
    at org.devzuz.q.maven.jdt.core.nature.MavenNature.configure(MavenNature.java:104)

---

!ENTRY org.eclipse.core.jobs 4 2 2007-10-03 10:02:18.151
!MESSAGE An internal error occurred during: "Importing Maven Projects".
!STACK 0
java.lang.NullPointerException
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectJob.run(ImportProjectJob.ja
va:93)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectWorkspaceJob.runInWorkspace
(ImportProjectWorkspaceJob.java:57)
    at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJo
b.java:38)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.devzuz.q.maven.jdt.core 1 0 2007-10-03 10:02:20.749
!MESSAGE New classpath for project archiva-common

Original comment by joakim.erdfelt on 3 Oct 2007 at 5:10

GoogleCodeExporter commented 9 years ago

More updates / workaround.

1. I ran from command line [archiva/trunk-q4e/]$ mvn clean install
2. Then, within eclipse/q4e, selected all m2 projects to import.
3. The import failed with a NullPointerException.
4. Repeat from step #2 until all projects are imported without error. (about 4 
times
through)
5. The following projects do not have their build path setup correctly (likely 
due to
NPE during import)

* archiva-cli
* archiva-policies
* archiva-scheduled
* archiva-repository-layer

The other projects that show up in red, seem to have a correct build path, but 
they
depend on the previous 4 projects.

Original comment by joakim.erdfelt on 3 Oct 2007 at 5:21

GoogleCodeExporter commented 9 years ago

Unable to manually fix the problem projects.  Results in OOM when attempting to 
open
Project / Properties dialog.

Original comment by joakim.erdfelt on 3 Oct 2007 at 5:23

GoogleCodeExporter commented 9 years ago

Did an independent testing on windows xp.
Fresh install of Eclipse 3.3M7 used and fresh update of q4e from updatesite.
Fresh update of archiva.

Ran mvn clean install in command line then mvn eclipse:eclipse.
Import archiva as maven 2 project.
There were no NPEs. The import just went fine.
There were projects that did not have the maven classpath so I did went to 
Enable
Maven Dependency Management.
Checked on the projects individually and the following did not have the maven
classpath set:
* archiva-cli
* archiva-policies
* archiva-scheduled
* archiva-repository-layer

One noticeable error was in archiva-scheduled. It has "Error configuring nature
'org.devzuz.q.maven.jdt.core.mavenNature'. " and the stack trace :
java.lang.LinkageError: loader constraint violation: when resolving method
"org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Ljava/lang/String;)Lorg/xm
l/sax/XMLReader;"
the class loader (instance of
org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class,
org/jdom/input/SAXBuilder, and the class loader (instance of <bootloader>) for
resolved class, org/xml/sax/helpers/XMLReaderFactory, have different Class 
objects
for the type org/xml/sax/XMLReader used in the signature
    at org.jdom.input.SAXBuilder.createParser(SAXBuilder.java:573)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:424)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:810)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:789)
    at
org.codehaus.plexus.cdc.DefaultComponentDescriptorCreator.mergeDescriptors(Defau
ltComponentDescriptorCreator.java:246)
    at
org.codehaus.plexus.maven.plugin.AbstractMergeMojo.execute(AbstractMergeMojo.jav
a:150)
    at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:647)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:354)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:255)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.java:141)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
    at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:911)
    at
org.devzuz.q.maven.embedder.internal.EclipseMaven.executeRequest(EclipseMaven.ja
va:250)
    at
org.devzuz.q.maven.embedder.internal.EclipseMavenRequest.run(EclipseMavenRequest
.java:56)
    at org.devzuz.q.maven.embedder.internal.EclipseMaven.executeGoals(EclipseMaven.java:134)
    at org.devzuz.q.maven.embedder.internal.EclipseMaven.executeGoal(EclipseMaven.java:119)
    at org.devzuz.q.maven.embedder.internal.EclipseMaven.executeGoal(EclipseMaven.java:113)
    at org.devzuz.q.maven.jdt.core.nature.MavenNature.addClasspath(MavenNature.java:193)
    at org.devzuz.q.maven.jdt.core.nature.MavenNature.configure(MavenNature.java:104)
    at org.eclipse.core.internal.resources.NatureManager$1.run(NatureManager.java:143)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at
org.eclipse.core.internal.resources.NatureManager.configureNature(NatureManager.
java:158)
    at
org.eclipse.core.internal.resources.NatureManager.configureNatures(NatureManager
.java:203)
    at org.eclipse.core.internal.resources.Project.basicSetDescription(Project.java:65)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:981)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1009)
    at org.devzuz.q.maven.jdt.core.MavenNatureHelper.addNature(MavenNatureHelper.java:35)
    at
org.devzuz.q.maven.jdt.ui.actions.MavenManageDependenciesAction.runInternal(Mave
nManageDependenciesAction.java:30)
    at
org.devzuz.q.maven.jdt.ui.actions.AbstractMavenAction.run(AbstractMavenAction.ja
va:90)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
    at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionCont
ributionItem.java:545)
    at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.
java:490)
    at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContribution
Item.java:402)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3673)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2365)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2329)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2204)
    at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
    at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ecli
pseAppLauncher.java:106)
    at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLau
ncher.java:76)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:497)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:436)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1162)

Also I noticed that in the maven events log, it keeps on showing this : 
6:17:12 PM SGT  warn    Deprecated expression: ${version} - missing prefix. Use
${pom.version} (model:
org.apache.maven.archiva:archiva-database-consumers:jar:1.0-beta-3-SNAPSHOT) 
6:17:12 PM SGT  warn    Deprecated expression: ${version} - missing prefix. Use
${pom.version} (model:
org.apache.maven.archiva:archiva-report-manager:jar:1.0-beta-3-SNAPSHOT) 
6:17:12 PM SGT  warn    Deprecated expression: ${version} - missing prefix. Use
${pom.version} (model:
org.apache.maven.archiva:archiva-artifact-reports:jar:1.0-beta-3-SNAPSHOT) 
6:17:12 PM SGT  warn    Deprecated expression: ${version} - missing prefix. Use
${pom.version} (model: 
org.apache.maven.archiva:archiva-cli:jar:1.0-beta-3-SNAPSHOT) 
6:17:12 PM SGT  warn    Deprecated expression: ${version} - missing prefix. Use
${pom.version} (model:
org.apache.maven.archiva:archiva-database:jar:1.0-beta-3-SNAPSHOT) 

The messages were shown everytime I enable maven dependency management
or clean/build project/s.

I will verify these results soonest time possible.

Original comment by xgenesis...@gmail.com on 10 Oct 2007 at 11:57

GoogleCodeExporter commented 9 years ago

1) q4e should not need mvn eclipse:eclipse to be called before importing the 
projects. 
2) Regarding the LinkageError, it's been discussed on the dev list
(http://tinyurl.com/2q42r4). It was decided to remove the org.w3c packages and 
test
again (since they are provided by the JDK).

Original comment by amu...@gmail.com on 10 Oct 2007 at 12:33

GoogleCodeExporter commented 9 years ago

i have removed also org.w3c.dom from the embedder

Original comment by carlossg on 10 Oct 2007 at 1:01

GoogleCodeExporter commented 9 years ago

I've fixed the detection of unresolved artifacts in Issue 97... please review 
the current status.
So far, I've detected problems in some projects resolving the parent pom and 
other classpath issues with non-
explicit (i.e. not declared in the project's pom) dependencies, but haven't 
tracked those down.
I've tested using cocoon trunk.

Original comment by amu...@gmail.com on 17 Oct 2007 at 9:49

GoogleCodeExporter commented 9 years ago

I did a test for Archiva just today with the latest q4e release.
Used a fresh install of Eclipse Version: 3.3.0 Build id: I20070625-1500

Steps:

Updated to the latest trunk.
Did an mvn clean install - went good.
Imported the Archiva project and have the following errors:
1.)
Message : 
Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
Stack trace :
java.lang.LinkageError: loader constraint violation: when resolving method
"org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Ljava/lang/String;)Lorg/xm
l/sax/XMLReader;"
the class loader (instance of
org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class,
org/jdom/input/SAXBuilder, and the class loader (instance of <bootloader>) for
resolved class, org/xml/sax/helpers/XMLReaderFactory, have different Class 
objects
for the type org/xml/sax/XMLReader used in the signature
    at org.jdom.input.SAXBuilder.createParser(SAXBuilder.java:573)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:424)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:810)
    at org.jdom.input.SAXBuilder.build(SAXBuilder.java:789)
    at
org.codehaus.plexus.cdc.DefaultComponentDescriptorCreator.mergeDescriptors(Defau
ltComponentDescriptorCreator.java:246)
    at
org.codehaus.plexus.maven.plugin.AbstractMergeMojo.execute(AbstractMergeMojo.jav
a:150)
    at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:647)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:354)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:255)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.java:141)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
    at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:911)
    at
org.devzuz.q.maven.embedder.internal.EclipseMaven.executeRequest(EclipseMaven.ja
va:252)
    at
org.devzuz.q.maven.embedder.internal.EclipseMavenRequest.run(EclipseMavenRequest
.java:57)
    at org.devzuz.q.maven.embedder.internal.EclipseMaven.executeGoals(EclipseMaven.java:135)
    at org.devzuz.q.maven.embedder.internal.EclipseMaven.executeGoal(EclipseMaven.java:120)
    at org.devzuz.q.maven.embedder.internal.EclipseMaven.executeGoal(EclipseMaven.java:114)
    at org.devzuz.q.maven.jdt.core.nature.MavenNature.addClasspath(MavenNature.java:193)
    at org.devzuz.q.maven.jdt.core.nature.MavenNature.configure(MavenNature.java:104)
    at org.eclipse.core.internal.resources.NatureManager$1.run(NatureManager.java:143)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at
org.eclipse.core.internal.resources.NatureManager.configureNature(NatureManager.
java:158)
    at
org.eclipse.core.internal.resources.NatureManager.configureNatures(NatureManager
.java:203)
    at org.eclipse.core.internal.resources.Project.basicSetDescription(Project.java:65)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:981)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1009)
    at org.devzuz.q.maven.jdt.core.MavenNatureHelper.addNature(MavenNatureHelper.java:35)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectJob.createMavenProject(Impo
rtProjectJob.java:160)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectJob.runInWorkspace(ImportPr
ojectJob.java:88)
    at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJo
b.java:38)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectWorkspaceJob.runInWorkspace
(ImportProjectWorkspaceJob.java:57)
    at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJo
b.java:38)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

2.)
Message : 
Unable to import project from C:\archiva_trunk\archiva-base\archiva-policies
Stack Trace :
org.eclipse.core.runtime.CoreException: Problems encountered while setting 
project
description.
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:983)
    at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1009)
    at org.devzuz.q.maven.jdt.core.MavenNatureHelper.addNature(MavenNatureHelper.java:35)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectJob.createMavenProject(Impo
rtProjectJob.java:160)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectJob.runInWorkspace(ImportPr
ojectJob.java:88)
    at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJo
b.java:38)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectWorkspaceJob.runInWorkspace
(ImportProjectWorkspaceJob.java:57)
    at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJo
b.java:38)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

3.)
Message:
An internal error occurred during: "Importing Maven Projects".
Stack Trace:
java.lang.NullPointerException
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectJob.runInWorkspace(ImportPr
ojectJob.java:94)
    at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJo
b.java:38)
    at
org.devzuz.q.maven.jdt.ui.projectimport.ImportProjectWorkspaceJob.runInWorkspace
(ImportProjectWorkspaceJob.java:57)
    at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJo
b.java:38)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Original comment by xgenesis...@gmail.com on 24 Oct 2007 at 4:39

GoogleCodeExporter commented 9 years ago

I thought the java.lang.LinkageErrors had been resolved...

They are a different beast than dependency resolution, so it should be tracked
separately. See Issue 108.

Original comment by amu...@gmail.com on 24 Oct 2007 at 3:21

GoogleCodeExporter commented 9 years ago

I think that all the remaining problems resolving dependencies are being tracked
separately now:
 - artifacts that need to be manually installed: Issue 98.
 - some parent poms are not found: Issue 113.
 - LinkageErrors: Issue 108.

We'll be getting a new release in a few days which will allow verifying this by 
the
community.

Original comment by amu...@gmail.com on 29 Oct 2007 at 11:34

GoogleCodeExporter commented 9 years ago

Dependencies are being resolved, except for the cases stated in the previous 
comment.
As those cases are tracked in different issues, is anyone against marking this 
issue
as Fixed?

Original comment by amu...@gmail.com on 6 Nov 2007 at 8:29

GoogleCodeExporter commented 9 years ago

This ticket is still valid.
This ticket is dependent on Issue 98, and Issue 113, and Issue 108.
Normal process is to closed the dependent tickets, retest this one, and close 
if fixed.

Original comment by joakim.erdfelt on 6 Nov 2007 at 9:26

GoogleCodeExporter commented 9 years ago

Re-scheduling for 0.3.0.

Original comment by amu...@gmail.com on 6 Nov 2007 at 10:45

Added labels: Milestone-0.3.0
Removed labels: Milestone-0.2.3

GoogleCodeExporter commented 9 years ago

This ticket does not depend on Issue 98 (it is ok to fail when resolving 
dependencies
that must be manually installed), so I'm closing this issue (Issue 113 and 
Issue 108
have been resolved).

Original comment by amu...@gmail.com on 27 Nov 2007 at 11:21

Changed state: Fixed

google-code-export / q4e

Dependencies do not resolve. #9