Igor Fedorenko wrote:
as a first step i followed
http://docs.codehaus.org/display/M2ECLIPSE/Configuring+Development+Environment
and checked out things to winXP Ganymede (Build-ID I20080617-2000).
but i get compile errors in 4 projects (cliresolver, editor.tests,
xml.tests, eclipse.mylyn).
There is some additions to the target platform required for
editor.tests project. See
http://docs.codehaus.org/display/M2ECLIPSE/UI+testing+with+WindowTester
Also note that if you only interested to contribute to specific
components, you may not need to have all projects in your Workspace.
For instance, cliresolver project is not needed to build m2eclipse,
because jar built from that project is actually included into
org.maven.ide.eclipse project.
BTW, Igor, we may need to change that and also use
"update-dependencies" profile to bring that jar in.
classpath errors arise from non-resolved types, which are contained
in components-maven-embedder/jars. when adding project
components-maven-embedder to classpath compile errors vanish. it
seems that there is a missing project or bundle reference in
errornous projects?
It would be easier to tell what is missing if you could provide
details on the compilation errors, e.g. select them in the Problems view
(or "All Markers" in Eclipse 3.4), copy to clipboard and them paste or
attach that text to the email message.
-why aren't tests kept in src/test/java, they are always contained in
own projects. maybe because they aren't real unit-tests (need PDE
environment)? but then why aren't they put to src/test/integration or
something? why are other maven-conventions (especially folder stuff)
not followed, is it for historic reasons?
This is because most of m2e projects are OSGi bundles and OSGi does
not support classpath scopes.
Not only that, but there are also limitations in Eclipse PDE tools
that don't allow to exclude test code from osgi bundle. So, consider it
as a general Eclipse convention.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
