hi,
i am thinking about contributing to project, first providing some
"easier" patches and maybe after having digged into sources i would like
to have a look at Tycho project (maven-osgi integration in eclipse).
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). 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?
some more questions, which i couldn't find to be answered in wiki and
maybe could be added to it:
-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?
-why are there single feature projects (maybe a plugin-development
convention)?
-i cannot run a simple command-line 'mvn verify' on projects. this gives
me a 'Cannot find lifecycle mapping for packaging: 'eclipse-plugin'.
what kind of lifecylce is this and what is so 'eclipse-special' about it?
-a short explanation of maven-build-strategy/pom-structures of m2eclipse
projects would be helpful
-test-cases from eclipse.tests project crash, because OSGi access is
restricted to imported types (runtime ClassNotFoundException), maybe
there is a bundle restriction misconfiguration?
-if one wants to work on a m2eclipse sub-project (like wtp, tycho) some
guidelines would be nice, what resources to read first and understand
(like books, links) before able to touch some code.
another non-m2eclipse issue: i checked out sources with subclipse plugin
(1.4.1), but now my svn-command-line client (1.4.6) tells me that it is
to old for working copy. it seems that svn client 1.4.6 is not
down-compatible with checked out-sources of subclipse plugin. does
somebody know a workaround apart from installing older svn-client?
of course i could add your provided answers to wiki-pages myself.
many thanks!
--
manuel aldana
[EMAIL PROTECTED]
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
