Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Give me a starting point for a complete beginner
This means you don't have apache commons exec in your eclipse target (typically your workspace if you've not configured it otherwise). Without it PDE will complain, although Tycho will be able to resolve it if you have pomDependencies=consider


Once you have installed it into your workspace you will have the bundle and so the problem will go away. You can install it via the host OSGi console in Eclipse with "install http://repo.maven.org/..." or just install your plugin built by maven/Tycho which will drag it in. 

You should check out the Tycho sample projects at https://github.com/eclipse/tycho-demo which show examples. 

I also wrote a book which covered Tycho in chapter 9; the source code is available on GitHub (each chapter is it's own branch)


Alex

Sent from my iPhone 5

On 20 Jun 2014, at 06:55, Carsten Harnisch <carsten.harnisch@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Nick, 
thanks for your answer. Please excuse my stupid questions, but I am pretty new to this kind of system.
I also attached a screenshot.

So as far as I understood we have 2 different builds systems ? One is "Eclipse internal" one and the other is Maven (or Tycho over Maven).
When I do a Maven build (from the cmd line) I am getting a success, that would be same if I explicitly run Maven built in Eclipse (so right click on the project and "run as", "maven install"). But anyway the errors as in the screenshot stay as they are. You see this a dependency to "org.apache.commons.exec".

I just assume that is something completely different system, so here are the "errors" coming from the Eclipse internal build system and NOT the onces from the maven build ? Or does Tycho "replace" the Eclipse Build system ?
In my understanding I can use maven for the headless build (or on the command line) or in a CI environment. But for developing (and debugging) I would use the Eclipse build system. So at the end both ways should work ?

The next I do not understand where the repository actually is? So in maven I am ending with a folder on the local disk with all the (dependencies) artifacts stored into. For the P2 how this is working ? And more pragmatically: How I can get the needed jars (apache-commons) and where to put them? Or this there a way that I can just Tycho does this for me; aka reusing the maven repo for this?

I was just wondering that these things are so complicated and just seeing that I had passed the last couple days with this issue without writing a single line of code. So I assume there is maybe just something missing in the config and then the things are solving magically :)

Mit herzlichem Gruss / Kind Regards

Carsten Harnisch
Harnisch-Consulting

Yilmaz Türk Cad. 52
TR-34970 Istanbul / Adalar

Tel: +90 216 3823 678 (Asia)
Tel: +90 212 2450 648 (Europe)

<Bildschirmfoto 2014-06-20 um 08.19.27.png>

Am 19.06.2014 um 18:35 schrieb Nick Boldt <nickboldt@xxxxxxxxx>:

If you look in Window > Preferences > Maven > User Settings, do you see the same settings.xml and ~/.m2 folder that your commandline mvn build used?

If it's different, that might be why commandline resolves deps but in-Eclipse builds do not.

"p2" has been said to stand for a lot of things, from "Pascal's Provisioning" to "Provisioning Platform". It's also been said that it's called p2 because it sounds a little like someone spitting something out, ie., ptooey :D

http://eclipse.dzone.com/articles/understanding-eclipse-p2-provi
http://www.urbandictionary.com/define.php?term=ptooey


On 06/19/2014 09:15 AM, Carsten Harnisch wrote:
I am a beginner with Eclipse plugin development and trying a bit around how things are working.

The main issue is how to connect the maven repo to be used for the eclipse build.

Basically I would like to "build" first an already existing project. But I am lost with then "tycho" configuration.
I started with a "standard Eclipse Kepler" install and added "m2eclipse"
So what I did is "git clone" the project and then "import maven project" in Eclipse.

On the command line (e.g. a mvm install) runs well. Also a "run as" for maven install in eclipse does the right thing.

The problem is basically that the projects in Eclipse won't build, giving always the error, that dependencies are missing. These dependencies are mostly from org.apache.commons.XXX and are referenced in the manifest.mf.

So as far as I understand right now:

- Eclipse Build and Maven Build are using 2 different repositories for dependencies
- Eclipse Build is using a "P2 Repo" (for whatever stands P2 ?)

So my question is how to bring this together, thus how I can have "Eclipse" use the Maven repository, or is there another way to fix the problem ?
So do people just use tycho (so maven build) and ignore the Eclipse build system ? But then how I can debug from out of Eclipse ? So maybe there is just a missing plugin, or configuration ?

all help appreciated

Carsten
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user


--
Nick Boldt :: http://nick.divbyzero.com
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user

Back to the top