multi-module maven project as one eclipse project.

[mpk]

I can not find a feature that works fine in the old eclipse
integration module:

I want to checkout root of the multi-module project (modules are just
sub-directories of the root, nothing fancy). And make eclipse see it
as a single project.

The primary goal for this is refactoring: I want to be able to
refactor the thing as a whole.
Presently, my project has 14 modules. When I checkout only the core,
refactoring will "see" the core module only. Same happens if I
checkout all 14 modules: refactoring seem to affect only the current
eclipse project.

Please, comment.

-Mike

[Abel Muiño Vizcaino]

q4e approach is to map each maven (sub)project to an eclipse project. This allows to accurately set the classpath for each project.

However, that should not hinder your ability to refactor, since (when all the projects are on the workspace) they should be linked and the refactoring should affect every project.

There are improvements on the management of dependent projects in the trunk version. The next release of q4e is being prepared, so you might want to wait a few days until it is available and then test the feature again.

--

Abel Muiño Vizcaino - http://ramblingabout.wordpress.com

[mpk]

The speed of reply is impressive. This makes me strong believer in q4e
project. Thanks for great effort, and good luck with the new release!

-Mike

[mpk]

Tried new release (just announced). It does not work.

Let me re-iterate, that this is a very important feature that does
work with the old maven integration pluging.

Namely: I have 14 modules. 13 of these modules depend on the "core"
one. I need to refactor something in the "core" module and expect
eclipse to propagate the change automatically to all modules that are
maven-dependent on the core.

Following your suggestion I do the following:

1. I open every project in the eclipse. Everyl individual project seem
to be fine. I can Maven->Install, etc.
2. I refactor something in the "core" project. Change does NOT
propagate to the maven-dependant ones!
3. If I configure eclipse JavaBuild dependencies manually to declare
the dependency on the core project, then refactoring works correctly.
But for this I do not need maven plugin.

Resume: maven dependencies do NOT cause "eclipse linkage" of the
projects, unfortunately.

Generally, managing large Maven project with Q4E seems much less
convenient (and note that Maven projects tend to be large - one does
not need maven for HelloWorld projects).

Comapre this:

A. With the old maven integration plugin I do this:
1. import root project (with all sub-folders) from CVS into workspace
2. Right-click on the project -> Maven -> Enable
3. Right-click on the project -> Maven -> Update Source Folders
Bingo - I have all sub-projects opened as a single eclipse project.
Refactoring goes like a charm.

B. With the q4e philosophy I have to do this:
1. import root propject (with all sub-folders) from CVS into temps
space (can not do it to workspace, otherwise steps 2-15 will fail).
2. New->JavaProject->From Existing Tree->navigate to sub-project1,
enter name, done
3. same for sub-project2
...
15. same for sub-project14
16. Right-Click on sub-peoject1, Maven->Enable
17, same for sub-project2
...
29. same for sub-project14

and after all that I still have to manually configure inter-project
dependencies in eclipse to do the refactoring... :( :(

Please, consider how this use case can be improved. Let me know if I
am missing something.

Thank you,
-Mike

> > -Mike- Hide quoted text -
>
> - Show quoted text -

[mpk]

After some more searching and researching, I've found the solution:

When modules of a multi-module maven project are imported into the
eclipse workspace using File->Import, q4e will correctly update
eclipse dependencies to match the maven ones. This makes refactoring
in a multi-module project work!

-Mike

> > - Show quoted text -- Hide quoted text -

[Abel Muiño]

Great that you were able to figure it out.

I've created a new issue to request documentation for this: http://code.google.com/p/q4e/issues/detail?id=88

http://ramblingabout.wordpress.com/

[Huberfeld Merlot]

Hi there,

I have followed this discussion and I heard the words, but I have
questions/ comments:

1. I understand that Devzuz is supporting this project?!
2. In Devzuz's "Better Builds with Maven" multi project/ multi module
is handled exact the way Mike described it (the Proficio example).
3. I understand that Eclipse (by nature) does not support this project
structure.
4. Is Devzuz leaving the proposed path now?
5. Can anybody provide the right setup for the Profico example with
Q4?
6. Up to now everybody talked about importing a existing project not
building a new multi module project.
7. I tried both ways. The Devzuz proposed way worked with my real life
project until I got the JDK error mentioned in an other threat here.
With the exception that I can use MVN only on the root project level
and not on module level (which M2Eclipse does)
8. If I try it the Elicpse (as proposed in this thread) way i could
not figure out how the POM defined dependencies are resolved/ managed.
9. Any idea/ example?

Holger

[Huberfeld Merlot]

To all,

I am getting more and more puzzled with these multi module issue. And
just to repeat: I do not have the case where I want to import a
project with modules, I set it (them) up with the new project wizard.

The maven sequence is that I define first the main project with
<packaging>pom</packaging> and the <modules> and
<dependencyManagement> entries and than the modules as single Eclipse
projects as proposed here in this forum. So far so good.

Running an install from Q4e went fine yesterday and not today. I now
found out why: Because the compiled JAR's were still present in the
local repository from mvn cmdline and M2Eclipse runs.

After clearing all target entries in the Eclipse dev space an the
local repository nothing works as expected.

1. I can not install the master project in the local repository
because mvn can not find the submodules, because it searches for them
under the master project and I did not find any possibility to tell it
where to find them. My expectation is that Q4e is doing this for me!

2. Because the main project is not in the local repository I find the
following error in the Eclipse log

!ENTRY org.devzuz.q.maven.core 4 0 2007-10-05 09:42:37.282
!MESSAGE Unable to read project
!STACK 1
org.eclipse.core.runtime.CoreException: Errors during Maven execution
at
org.devzuz.q.maven.embedder.internal.EclipseMavenExecutionResult.<init>(EclipseMavenExecutionResult.java:
55)
at
org.devzuz.q.maven.embedder.internal.EclipseMaven.getMavenProject(EclipseMaven.java:
325)
at
org.devzuz.q.maven.embedder.internal.EclipseMaven.getMavenProject(EclipseMaven.java:
297)
at
org.devzuz.q.maven.embedder.internal.EclipseMavenProjectAdapterFactory.getAdapter(EclipseMavenProjectAdapterFactory.java:
30)
at
org.eclipse.core.internal.runtime.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:
61)
at
org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:
277)
at
org.eclipse.core.runtime.PlatformObject.getAdapter(PlatformObject.java:
66)
at
org.devzuz.q.maven.ui.actions.AbstractMavenAction.getMavenProject(AbstractMavenAction.java:
47)
at
org.devzuz.q.maven.ui.actions.MavenInstallAction.runInternal(MavenInstallAction.java:
21)
at
org.devzuz.q.maven.ui.actions.AbstractMavenAction.run(AbstractMavenAction.java:
79)
at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:
256)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:
546)
at org.eclipse.jface.action.ActionContributionItem.access
$2(ActionContributionItem.java:490)
at org.eclipse.jface.action.ActionContributionItem
$5.handleEvent(ActionContributionItem.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:
3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
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:
169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:
106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.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:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
org.eclipse.core.runtime.CoreException[0]:
org.apache.maven.project.ProjectBuildingException: Cannot find parent:
com.wuerth.phoenix.auratix.axo:axo:pom:1.0-SNAPSHOT of: C:\Data
\DEV_Q4\axo-utils\pom.xml for project Parent:
com.wuerth.phoenix.auratix.axo:axo::1.0-SNAPSHOT
at
org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentFromRepositories(DefaultModelLineageBuilder.java:
410)
at
org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentPom(DefaultModelLineageBuilder.java:
320)
at
org.apache.maven.project.build.model.DefaultModelLineageBuilder.resumeBuildingModelLineage(DefaultModelLineageBuilder.java:
143)
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:
1056)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:
721)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:
485)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:
210)
at
org.apache.maven.embedder.MavenEmbedder.readProject(MavenEmbedder.java:
412)
at
org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies(MavenEmbedder.java:
429)
at
org.devzuz.q.maven.embedder.internal.EclipseMaven.getMavenProject(EclipseMaven.java:
320)
at
org.devzuz.q.maven.embedder.internal.EclipseMaven.getMavenProject(EclipseMaven.java:
297)
at
org.devzuz.q.maven.embedder.internal.EclipseMavenProjectAdapterFactory.getAdapter(EclipseMavenProjectAdapterFactory.java:
30)
at
org.eclipse.core.internal.runtime.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:
61)
at
org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:
277)
at
org.eclipse.core.runtime.PlatformObject.getAdapter(PlatformObject.java:
66)
at
org.devzuz.q.maven.ui.actions.AbstractMavenAction.getMavenProject(AbstractMavenAction.java:
47)
at
org.devzuz.q.maven.ui.actions.MavenInstallAction.runInternal(MavenInstallAction.java:
21)
at
org.devzuz.q.maven.ui.actions.AbstractMavenAction.run(AbstractMavenAction.java:
79)
at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:
256)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:
546)
at org.eclipse.jface.action.ActionContributionItem.access
$2(ActionContributionItem.java:490)
at org.eclipse.jface.action.ActionContributionItem
$5.handleEvent(ActionContributionItem.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:
3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
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:
169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:
106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.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:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
Caused by:
org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable
to download the artifact from any repository

com.wuerth.phoenix.auratix.axo:axo:pom:1.0-SNAPSHOT

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

at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:
203)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:
73)
at
org.apache.maven.project.artifact.CacheAwareArtifactResolver.resolve(CacheAwareArtifactResolver.java:
53)
at
org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentFromRepositories(DefaultModelLineageBuilder.java:
401)
... 45 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException:
Unable to download the artifact from any repository
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:
342)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:
191)
... 48 more
!SUBENTRY 1 org.devzuz.q.maven.core 4 0 2007-10-05 09:42:37.282
!MESSAGE Errors during Maven execution
!STACK 0
org.apache.maven.project.ProjectBuildingException: Cannot find parent:
com.wuerth.phoenix.auratix.axo:axo:pom:1.0-SNAPSHOT of: C:\Data
\DEV_Q4\axo-utils\pom.xml for project Parent:
com.wuerth.phoenix.auratix.axo:axo::1.0-SNAPSHOT
at
org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentFromRepositories(DefaultModelLineageBuilder.java:
410)
at
org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentPom(DefaultModelLineageBuilder.java:
320)
at
org.apache.maven.project.build.model.DefaultModelLineageBuilder.resumeBuildingModelLineage(DefaultModelLineageBuilder.java:
143)
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:
1056)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:
721)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:
485)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:
210)
at
org.apache.maven.embedder.MavenEmbedder.readProject(MavenEmbedder.java:
412)
at
org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies(MavenEmbedder.java:
429)
at
org.devzuz.q.maven.embedder.internal.EclipseMaven.getMavenProject(EclipseMaven.java:
320)
at
org.devzuz.q.maven.embedder.internal.EclipseMaven.getMavenProject(EclipseMaven.java:
297)
at
org.devzuz.q.maven.embedder.internal.EclipseMavenProjectAdapterFactory.getAdapter(EclipseMavenProjectAdapterFactory.java:
30)
at
org.eclipse.core.internal.runtime.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:
61)
at
org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:
277)
at
org.eclipse.core.runtime.PlatformObject.getAdapter(PlatformObject.java:
66)
at
org.devzuz.q.maven.ui.actions.AbstractMavenAction.getMavenProject(AbstractMavenAction.java:
47)
at
org.devzuz.q.maven.ui.actions.MavenInstallAction.runInternal(MavenInstallAction.java:
21)
at
org.devzuz.q.maven.ui.actions.AbstractMavenAction.run(AbstractMavenAction.java:
79)
at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:
256)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:
546)
at org.eclipse.jface.action.ActionContributionItem.access
$2(ActionContributionItem.java:490)
at org.eclipse.jface.action.ActionContributionItem
$5.handleEvent(ActionContributionItem.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:
3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
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:
169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:
106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.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:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
Caused by:
org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable
to download the artifact from any repository

com.wuerth.phoenix.auratix.axo:axo:pom:1.0-SNAPSHOT

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

at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:
203)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:
73)
at
org.apache.maven.project.artifact.CacheAwareArtifactResolver.resolve(CacheAwareArtifactResolver.java:
53)
at
org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentFromRepositories(DefaultModelLineageBuilder.java:
401)
... 45 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException:
Unable to download the artifact from any repository
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:
342)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:
191)
... 48 more

and I do not get any response in the maven Event window.

Can you help?!

Holger

[Abel Muiño]

Hi,

Current scenarios under test are starting a maven project from an archetype and importing an existing maven project.

Creating a multiproject from withing q4e is, as far as I can tell, not a use case we are considering for the early stages of the project.

This said, of course it should be possible, and it will. We just haven't set a deadline for that. Presently the priority is set on making q4e work efficiently and reliably on existing maven projects.

I've created Issue 89 for tracking the support of multiprojects in q4e.

        at org.eclipse.swt.widgets.Display.readAndDispatch (Display.java:3293)

        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
2389)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)

        at org.eclipse.ui.internal.Workbench.access$4 (Workbench.java:2219)

        at org.eclipse.swt.widgets.Widget.sendEvent (Widget.java:938)

        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:
3682)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
        at org.eclipse.ui.internal.Workbench.runEventLoop (Workbench.java:
2389)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
        at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)

        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:
169)
        at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:
106)
        at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start (EclipseAppLauncher.java:

        at org.eclipse.ui.internal.Workbench.runUI (Workbench.java:2353)

        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:508)

342)
        at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:
191)
        ... 48 more



and I do not get any response in the maven Event window.

Can you help?!


Holger

--
Abel Muiño - http://ramblingabout.wordpress.com/

[Huberfeld Merlot]

Abel,

thanks for your response. I hear your words and understand your
priorities but I as a user Ihave a different understand about what you
name "make it work".

For me, you as the project team decided regarding the multi module
flat mapping version and against the (natural) Maven structure for
this case. So far OK, but what is the difference in architectural
terms to tell one master project and x modules that they belong
together while they are imported or freshly set up in Eclipse?

Sorry, at that level I do not see any difference. Yes, I agree that
for my version you have to write the additional GUI parts.

Maybe I can do this by my self, but therefore I need the architectural
construct how you achieve this?! Can you provide me this details, so
that I can try my part?

Holger

[Huberfeld Merlot]

Abel,

sorry for the second response. Independent of the multi module
discussion you should have a look on the error messages. I think this
can happen also in case of import when by what reason ever the master
POM, JAR are not present either in the local or central repository.
Please, do not forget that aspect!

On Oct 5, 10:22 am, "Abel Muiño" <amu...@gmail.com> wrote:

[Abel Muiño]

Could you prepare a simple test case project and attach it to a new issue at http://code.google.com/p/q4e/issues/list?

That would be much helpful and make sure that we have the issue on our radar.

Thanks!
  Abel.

On 10/5/07, Huberfeld Merlot <holger...@alice.it> wrote:

[Huberfeld Merlot]

Abel,

I will make it so. May take some days, because my main focus is to
move our framework build to Maven.

Holger

[Huberfeld Merlot]

Abel,

can I add it to issue no. 4, because it is related to?!

Holger

[Abel Muiño]

There are two different issues:
  1) regarding multiproject support. I've filed Issue 89 for that.
  2) regarding error messages. If you can make a test case, please attach it to a new issue.

If you think the issue is related to a different one (but not the same), you can state that in the description. If it is the same problem, then you can provide any extra information you might have.

In this case, I think you should open a new issue.

You can also "star" any issue that you find interesting. You will receive change notifications and we will see the number of persons interested in each issue (that can help us prioritize future development).

On 10/5/07, Huberfeld Merlot <holger...@alice.it> wrote:

[Abel Muiño Vizcaino]

There's an "impedance mismatch" between maven multiprojects and eclipse projects.

Eclipse does not support nested projects on the workspace (the natural maven structure). For eclipse, every project is at the same level in the filesystem.

We've opted for initially supporting the "natural eclipse structure", so to speak. This allows us to set the classpath for each project matching maven classpath. 

I, for one, would like to allow other alternative set-ups, but that will be addressed after the base functionality is solid.

If you want to get more into the architecture and contribute a patch, you'll be welcome!

--

Abel Muiño Vizcaino - http://ramblingabout.wordpress.com

[mpk]

Two more things from my experience with multi-module projects:

1. File->Import works as expected when positioned on the root of a
multi-module maven project.
But if I do CVS->CheckOut of the same directory, I get a non-java
project. It would be nice if one would be able to import
a multi-module project directly from CVS. Currently the workaround is
to checkout to filesystem (outside of eclipse workspace), then delete
the project without deleting the files, then do File->Import. How hard
would it be to allow a shortcut here?

2. I could be completely wrong here, but please hear me out.
When I do File->Import of a multi-module maven project, it brings
Eclipse to its knees. The feeling is that q4e launches many copies of
maven embedder (one for every module?). Result is Eclipse freeze and
PermGen Space errors. This does not happen if I open modules one-by-
one. Does this make sense? Coult this be improved?

Thank you,
-Mike

[Abel Muiño]

Regarding 1, please open an enhancement request on the issue tracker.

Regarding 2, there are several issues we're actively reviewing about performance during the import (see issues 49 and 78). However, if you updated your eclipse recently, the PermGen issue is probably caused by an eclipse bug introduced in 3.3.1: https://bugs.eclipse.org/bugs/show_bug.cgi?id=203325.