manuel aldana wrote:
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?
You need to have m2e installed in your dev eclipse in order for
cliresolver, editor.tests and xml.tests to compile clean. I'll double
check wiki is explicit about this requirement.
I am not sure what's causing compile errors in eclipse.mylyn. Can you
please make sure your target platform has mylyn 2.3.2 (as specified in
prerequisites) and open JIRA bugreport with specific error message if
you do have required mylyn version.
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?
This is because most of m2e projects are OSGi bundles and OSGi does not
support classpath scopes.
-why are there single feature projects (maybe a plugin-development
convention)?
Can you please give an example? I am not sure what "single feature
project" is.
-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?
You need tycho (which is essentially maven 2.1 SNAPSHOT with some extra
configuration) to build m2e. You can download latest tycho distribution
from [1] or [2].
-a short explanation of maven-build-strategy/pom-structures of m2eclipse
projects would be helpful
Currently, we keep all m2e projects in one directory. m2e parent pom is
in org.maven.ide.eclipse.parent and this is where you need to run the
build. As I explained above, m2e cli build needs tycho maven 2.1
distribution. I can provide more details if you have specific questions.
-test-cases from eclipse.tests project crash, because OSGi access is
restricted to imported types (runtime ClassNotFoundException), maybe
there is a bundle restriction misconfiguration?
Are you running unit tests from Eclipse or CLI? Can I see exact error
messages you get?
-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.
I guess the best way to start this is to ask specific questions.
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?
You need to install subversion 1.5.
of course i could add your provided answers to wiki-pages myself.
many thanks!
[1] http://ci.sonatype.org/job/Tycho/ws/trunk/tycho-distribution/target/
[2]
http://repository.sonatype.org:8081/nexus/service/local/repositories/eclipse-snapshots/content/org/codehaus/tycho/tycho-distribution/0.3.0-SNAPSHOT/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
