search

ajermakovics / eclipse-jmockit

JMockit plugin for Eclipse. Checks and auto-completes mock objects.
http://ajermakovics.github.io/eclipse-jmockit/
Eclipse Public License 1.0
40 stars 15 forks source link

Build plugin from command line #16

Closed ajermakovics closed 10 years ago

ajermakovics commented 10 years ago

Build using a build tool. Maven, Ant or Gradle http://www.vogella.com/tutorials/EclipseTycho/article.htm

romixch commented 10 years ago

I could already build the plugin with this maven approach. I am using the artefact now in my company. To build the feature and the update site, we would need more projects: One for the feature plugin One for the update site And one for the master maven pom which holds all together.

IMHO this are lots of projects for just one artefact. - Anyway, I could do that if you would create the projects in your repo.

Greetings Roman

ajermakovics commented 10 years ago

Oh ok, I've just pushed the feature project to: https://github.com/ajermakovics/eclipse-jmockit-feature The update site is in this repo: https://github.com/ajermakovics/jmockit-eclipse-updatesite , however it has two branches: master and gh-pages. gh-pages contains the generated project webpage.

Anyway, added you as a collaborator so it should be possible to push to these repos as well as the main one.

Later I'll update the Eclipse Marketplace so that this new version is available to everyone.

romixch commented 10 years ago

Thank you! That is great! I just got it working. I think I can now build an update site with maven. Although I still need this master project. If I got rid of it I could commit it to a separete branch so you can have a look at it. Or what would you prefer?

romixch commented 10 years ago

There is now a branch "maven" on every project. If you checkout this branch and installed the eclipse maven plugin, you can build the update site, feature and plugin by simply running the persisted run configuration "eclipse-jmockit-assist updatesite".

ajermakovics commented 10 years ago

Thanks, will have a look. My current plan is to make it build on Travis CI and then maybe publish binaries on Bintray. We'll see

ajermakovics commented 10 years ago

Seems to work great. Though I might have to move all three projects into one repo for easier building on TravisCI. But that's a different issue