Publish releases through an update site

[maherg]

Grabbing the JAR each time a release is published may not be the most suitable way of retrieving releases as opposed to the standardized way in Eclipse to fetch from an update site.

It will be more accessible to many people to just grab the update site and fetch from it.

[Arnauld]

Thanks for your feedback

Do you have any pointers on how to do this?

[maherg]

You can register at http://marketplace.eclipse.org/, click add new content and from there it should be straightforward.

[Arnauld]

Not so straightforward :p
Actually marketplace seems to be only a discovery directory, i need to create a working update site first.

FAQ How do I create an update site (site.xml)?

I'll to do this next week

[maherg]

Thanks Arnauld.

On Wed, Mar 14, 2012 at 8:48 PM, Arnauld Loyer <
reply@reply.github.com

wrote:

Not so straightforward :p
Actually marketplace seems to be only a discovery directory, i need to
create a working update site first.

http://wiki.eclipse.org/FAQ_How_do_I_create_an_update_site_(site.xml)%3F

I'll to do this next week

---

Reply to this email directly or view it on GitHub:

#38 (comment)

Maher
http://www.mahergamal.com

[Arnauld]

Don't worry i didn't forget you, but things are changing
why it takes so long: i'm in contact with Mauro that leads the jbehave project. This plugin will probably moved to jbehave project itself, that will host the update site

[dschneller]

Interesting... I am currently modifying the build to leverage Maven Tycho.
If you like, maybe you should take a look at my fork and its tycho branch. Currently there is a problem with TestNG support in tycho which I am trying to work around, but apparently this requires a patch on the tycho project.
What I've done so far is to separate the tests and the plugin into two projects which can be build with Maven alone.
I am not done yet, i. e. there is no gerenation of an update site yet, but that was my next goal, should the test stuff be more time consuming. https://github.com/dschneller/jbehave-eclipse-plugin/tree/tycho

[Arnauld]

That's sounds really great! i'll take a look once i've merged the localized-keyword branch, did you take a look at it?

[dschneller]

Sorry, no, not really in any meaningful depth yet. I have been rather busy
actually using the editor, but in the current project one has decided to
not use localized keywords for now.
I have seen that you don't do anything small, do you? ;-) Judging from the
amount of changes, especially due to the keyword language being really a
project level setting, I suspect that this was quite a lot of work.
As soon as I can shave off a few hours, I will have a look at it.

On Mon, Apr 23, 2012 at 13:21, Arnauld Loyer <
reply@reply.github.com

wrote:

That's sounds really great! i'll take a look once i've merged the
localized-keyword branch, did you take a look at it?

---

Reply to this email directly or view it on GitHub:

#38 (comment)

Daniel Schneller
ds@danielschneller.com
Twitter: @dschneller
http://www.danielschneller.com - Java, MySQL, Windows, Linux and other
insanities.

[branflake2267]

I'm curious if you've had time to look into the update site setup? If not let me know. (I know how it goes with a million things going on.)

[dschneller]

Working on it. Will probably be ready for a first go by the end of the week.

[branflake2267]

Good job :)

[dschneller]

Ok, you can try this URL for starters:

https://raw.github.com/dschneller/jbehave-eclipse-plugin.updatesite/master/target/site

Be advised, that this might change and is only a first try.

[branflake2267]

Nice work. I'll take a look this evening. :)

[branflake2267]

I did a similar thing with a maven repo on github.

[Arnauld]

Wooooot @dschneller congrats!