Migrate to new p2 repository

[pulse00]

Currently the plugin is available in the p2 repo at http://coffeescript-editor.eclipselabs.org.codespot.com/hg/.

We should migrate 0.3 to be available at http://www.nodeclipse.org/updates.

@paulvi I'd need your help here as i don't know how you deploy your artifacts.

[paulvi]

I am not guru for p2 repo. @tomotaro1065 please join.

I propose to do the same staging folder, as @tomotaro1065 did, see https://github.com/Nodeclipse/nodeclipse-1#testing

Developers may try latest unreleased version at update URL: http://www.tomotaro1065.com/nodeclipse/staging/

http://www.nodeclipse.org/updates/staging/ should have latest builds.

Robert, I am adding write access for you to https://github.com/Nodeclipse/www.nodeclipse.org .
But you may find it more convenient for communications to send Pull Request as well. I am not sure how it should be in long run.

master is current unreleased version of site, gh-pages is online version.

[tomotaro1065]

Hi Paul,

What may I do? And what is p2 repo?

[paulvi]

Can you help with putting coffeescript-eclipse 0.3 into our updates.

http://www.nodeclipse.org/updates is p2 repository.

See also Wikipedia definition of repository

[pulse00]

@paulvi how do you generate the updatesite in the update folder? Do you import it as an eclipse project and then manually build it?

[paulvi]

I must confess I am not so good with that. I was just putting files, and changing site.xml
@tomotaro1065 has released latest versions.

@pulse00 Do you hive ideas? I think ,in the end, using Tycho for that would be better.

[tomotaro1065]

Hi Robert,

Yes. I built it manually. Do you know any more convenience way else?

2013/5/20 Robert Gründler [email protected]

@paulvi https://github.com/PaulVI how do you generated the updatesite
in the updatesites folder? Do you import it as an eclipse project and
then manually build it?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-18136630
.

http://www.nodeclipse.org/

blog: http://d.hatena.ne.jp/tomotaro1065/
twitter: @tomotaro1065

[pulse00]

@tomotaro1065 i prefer to use maven and tycho to build my artifacts, it's way more convenient once setup. If you want i can have a look into this.

I'd need some help though on the following features:

• markdown.editor.feature
• com.eclipsesource.jshint.feature
• org.chromium.debug
• org.chromium.sdk

Where do they come from?

[paulvi]

All sources forked into https://github.com/Nodeclipse (so you can find link to any component)

https://github.com/winterstein/Eclipse-Markdown-Editor-Plugin
https://github.com/eclipsesource/jshint-eclipse
org.chromium is actually in SVN on googlecode http://code.google.com/p/chromedevtools/
but there's also some source on GitHUb for a quick vew https://github.com/Nodeclipse/chromedevtools

[tomotaro1065]

Markdown and jshint features are here.

https://github.com/Nodeclipse/jshint-eclipse/tree/master/releng/com.eclipsesource.jshint.feature
https://github.com/Nodeclipse/Eclipse-Markdown-Editor-Plugin/tree/master/feature

chromedevtools features are here.

https://github.com/Nodeclipse/nodeclipse-1/tree/master/chromedevtools/features/org.chromium.debug
https://github.com/Nodeclipse/nodeclipse-1/tree/master/chromedevtools/features/org.chromium.sdk

[paulvi]

@tomotaro1065 It would be nice to migrate nodeclipse-1 to Tycho build also.
@gurock has also mention that it is hard to build.

See also Nodeclipse/nodeclipse#40

[paulvi]

New repository is http://www.nodeclipse.org/coffeescript/repository/

We can integrate into Nodeclipse 0.5 if needed.

There are some related not resolved issues, discussed in this thread, but I close for now to clean up.