[Task] make maintenance 0.3 release

[paulvi]

After @damschmideg blesses migration to Nodeclipse adamschmideg#13 , build and release without new features just as starting point.

There are also some infrastructure issues to be solved.
adamschmideg#12 Compilation is difficult

[adamschmideg]

blessings given

[pulse00]

Hi everyone!

I'd like to propose the following tasks for the maintenance release:

• Upgrade to Xtext 2.4
• Add maven / tycho support
• Refactor namespace to org.nodeclipse.coffeescript
• Setup CI

As for the CI, we could use travis-ci.org or i can also add a project to the PDT-Extensions Jenkins instance.

[paulvi]

Well, initial maintenance 0.3 release idea was just to build it (at new place to check everything is OK)

Then proposed steps could be in 0.4 .

I totally agree to 1,2,4 for roadmap.
We should use latest version of XText.
Maven/Tycho would be nice to use later with nodeclipse-1 . @tomotaro1065 please take notice

For 3, I like it. It would set standard for the organization. However Adam @adamschmideg should not be against that.
(He asked his company to be reference in some way. Hope we don't delete some copyright notices)

Robert, please don't hurry to delete "Looking for owner" in readme.
Let it be for a month. Hopefully someone more would join. We are definitely in early transition phase.

I configure write access for you to this repo. If you want to experiment, I propose create own fork instead of branches.

Please wait for enough communication to happen.

[pulse00]

@paulvi no worries, i won't commit anything in the repo, i've created my own fork for now. I'll have plenty of other things to do the next few weeks, so there's no hurry here.

The above points of course are just suggestions. I'm fine with the current namespace, i just thought it would be concise to have the same namespace over all projects of the organisation.

Regarding maven/tycho: It has prooved to ease maintenance a lot for my projects, so i'd highly recommend it.

[paulvi]

@pulse00 Totally agree.

@pushkar85 Please join us here.

[tomotaro1065]

@paulvi I know Maven, but not know Tycho. I will try it when I have time.

[paulvi]

@tomotaro1065 me too, I know maven, not Tycho

This link I added before in README http://wiki.eclipse.org/Tycho/Reference_Card

@pulse00 Robert, can you recommend some materials?

[pulse00]

can you recommend some materials?

I've mainly used what's available in the Wiki you've linked. It's actually pretty simple. Tycho basically provides:

• Eclipse packaging types
• Resolve OSGI dependencies (p2 repositories) during the build
• Create maven artifacts ready for p2 deployment

You can have a look at an example here:

• https://github.com/pulse00/Composer-Eclipse-Plugin/blob/master/pom.xml
• https://github.com/pulse00/Composer-Eclipse-Plugin/blob/master/com.dubture.composer.core/pom.xml

[pushkar-g]

@paulvi @tomotaro1065
I am familiar with Tycho/ Maven. I can take up that task.

[tomotaro1065]

@pushkar85

Thanks a lot. Great. We'll leave it to you.

2013/5/18 pushkar85 notifications@github.com

@paulvi https://github.com/PaulVI @tomotaro1065https://github.com/tomotaro1065
I am familiar with Tycho/ Maven. I can take up that task.

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

http://www.nodeclipse.org/

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

[paulvi]

Actually it was Robert who said he is going to do it for Coffee-Eclipse.

And then it is also good for Nodeclipse-1.

I hope Robert & pushkar85 can go ping pong on Coffee, just as me & Tomoyuki on Nodeclipse-1.

[pulse00]

@paulvi i'll do it for the coffeescript plugin, no problem.

[paulvi]

At this point I think Skype would be better. My Skype ID pverest.