Spread the word and binaries about angularjs-eclipse HOT 24 CLOSED

Hi Paul,

As suggested in Nodeclipse/nodeclipse#119 please create entry on Marketplace.

OK, I will see entry on Marketplace.

Can I include angularjs-eclipse into Enide Studio ?

Yes sure, with pleasure! License of AngularJS Eclipse + Tern IDE is EPL. Note that JBoss Tools is studying too to integrate AngularJS Eclipse + Tern IDE in JBoss Tools as JBoss modules.

So I hope you agree and actively support.

I will try to do that. But I develop Tern IDE + AngularJS Eclipse in my spare time, so I cannot promise you that I will fix problems quickly. But a good news id that JBoss Tools seems interested with AngularJS Eclipse. Victor https://github.com/vrubezhny an excadel guy has done some contribution.

Can we aline a bit our release times or at least be aware of them.

Yes it should be very cool. But it's hard for me to promise that, but I will try it.

Regards Angelo

from angularjs-eclipse.

Nodeclipse 0.12 release is to be around March 28th-29th week-end.
Just as you I need find personal time.

Tern IDE in JBoss Tools as JBoss modules.
Do you mean that, you do not pursue keep your own mark?

If and when JBoss would like to make some changes,
would you agree that they make them in their copy of angularjs-eclipse (in effect creating fork)?

Or will you keep this repository as angularjs center?

AngularJS is quite mature technology with a lot of users. So it should be very desired feature of any IDE.
For Marketplace just go to https://marketplace.eclipse.org/add_content
I can create initial entry, then pass it to if you like.

from angularjs-eclipse.

I have just added your 2 updates site to Enide repository.
https://raw.github.com/Enide/eclipse-p2-composite-repository/master/
It is similar easy to add to Nodeclipse updates http://www.nodeclipse.org/updates/
but I just usually do after using/testing myself to be able to answer questions.

If you agree to follow issues on nodeclipse-1 (though I think I can just redirect to this repo issues) and look from time to time to Stackoverflow
e.g. http://stackoverflow.com/questions/tagged/nodeclipse , for this repo it is http://stackoverflow.com/questions/tagged/angularjs+eclipse (by the way, there are some unaswered question)... So then I can announce on http://www.nodeclipse.org/ (actually you can too)

from angularjs-eclipse.

Thank's Paul for your work. I will try to follow issues from stackoverflow.

So then I can announce on http://www.nodeclipse.org/ (actually you can too)
Cool, many thank's for your help!

from angularjs-eclipse.

If and when JBoss would like to make some changes,
would you agree that they make them in their copy of angularjs-eclipse (in effect creating fork)?

Our goal is to provide well and continuous support for the users according to our release train. So, yes we want to have the forks for Angelo's repositories due to make it possible to include these projects into our build process and to make sure that all works with our Target Platform (and our Target Platform suites Tern.java and AngularJS-eclipse projects requirements as well). Doing so doesn't mean that all the bugfixing/upcomming development will be done in JBoss' repositories only. Any valuable change should come to 'upstream' (read as "Angelo's") repository first, or at least always be contributed back to Angelo's repository (there always are the situations possible that something could break our build, so we have to fix it quickly by patching and than contribute it back to upstream).

Or will you keep this repository as angularjs center?

it's only up to Angelo on how to develop and support his projects and repositories. We'll use his repositories as an upstream for our forks and will contribute our fixes/development back to Angelo's repositories.

from angularjs-eclipse.

Thank's Victor for your clarification.

from angularjs-eclipse.

Yes, it is clear to understand.

we can say

'upstream' (read as "Angelo's")

from angularjs-eclipse.

one thing we need to find out if we fork is how we version/name/package these to avoid too much conflicts/confusion.

its not good if our plugins are named the exact same but you stay on 1.0.0-snapshot... and we start doing 1.0.1, 1.0.2 etc. to make p2 work properly.

from angularjs-eclipse.

well, then when version here is released it would overlap,
unless there will be some convention like
1.1, 1.3, 1.5 for JBoss fork
and 1.2, 1.4, 1.6 for upstream

Any other ideas?

from angularjs-eclipse.

That approach could work - another one is that we create a separate feature that includes the plugins and just mark them as incompatible with the angelozerr feature so they won't overlap....that isn't awesome either though.

The best would be IMO that tern.java starts doing releases ;)

I suggest starting with 0.1.0 to indicate it is not 1.0 and we can do 0.1.100, 0.1.101 etc. releases based on that.

from angularjs-eclipse.

Max, I have discussed about creating release with @pascalleclercq

I think we will create it soon (when pascal will have time to do that). I though using 1.0.0 for tern.java + angularjs eclipse. Is it OK with that?

from angularjs-eclipse.

The best would be IMO that tern.java starts doing releases ;)

👍 absolutely.

Instead of issues like #30, that can be put afterwards, just think what
essentially should be released.

I suggest starting with 0.1.0

Numbers doesn't matters much, though I personally prefer start from 0.1.0
and follow semver.org

FYI Nodeclipse 0.12 is to be released in a week, see
www.nodeclipse.org/history

from angularjs-eclipse.

@paulvi

Will you include angularjs eclipse in nodeclipse 0.12 ? Apparently not from its history...

I've installed it alone in my nodeclipse 0.11 (a CDT Kepler with nodeclipse + aptana for their pydev tools - see below) but I can't do much of it as it doesn't provide any angularjs eclipse perspective or an angularjs project type - not even a plain angularjs file type...

Something must be missing in this installation but I just don't know what...

from angularjs-eclipse.

@nodeleaf AngularJS Eclipse doesn't provide eclipse perspective or an angularjs project type and not even a plain angularjs file type

I suggest you to read https://github.com/angelozerr/angularjs-eclipse/wiki/Getting-Started

from angularjs-eclipse.

@angelozerr Is this intentional or a temporary stage?

from angularjs-eclipse.

It's intentional. For the moment I don't know why we need features like you have listed :

• angular perspective : today there is an Angular Explorer view. is it really intersting to add a perspective just for adding this view?
• angular project type : you can use angular with PHP, JSP, simple dynamic web content, etc. So the idea is to add angular project to existing project and not provide a wizard for creating an angular project.
• angularjs file type : you can create an HTML or JSP file, and that's all. By adding angular nature, angular features (completion, hover, etc) are available after in yoru HTML/JSP editor.

If you wish to have an angular perspective, etc, please create an other issue, because it's out off the scope of this original issue. Thank's

from angularjs-eclipse.

@nodeleaf Patrick You should have opened new issue, but any way great to see you in.

Nodeclipse to be released in a week. Hopefully angularjs-eclipse too.
Then I will look more closely. And new users too :)

from angularjs-eclipse.

@paulvi I'll wait next week then ;+)

At this stage I have a feeling these 2 projects might merge somehow to provide a clean MEAN stack IDE but I'm not sure yet this is really making sense. I'll have to Test & Think about it - ASAP...

from angularjs-eclipse.

@angelozerr would you start with 0.1.0 so we don't call this 1.0 before API's are somewhat stable ?

from angularjs-eclipse.

Ok let's go for 0.1.0. @pascalleclercq are you OK with that?

from angularjs-eclipse.

Yes !!!

Will do It probably this thursday....

2014-03-25 18:21 GMT+01:00 Angelo [email protected]:

Ok let's go for 0.1.0. @pascalleclercq https://github.com/pascalleclercqare you OK with that?

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

Pascal Leclercq

from angularjs-eclipse.

oh, one bad thing about 0.1.0 is that existing users will need to uninstall before installing.
And existing update site should be cleared up.
(Personally me in such situation would not step version down it :) )

reminder about:
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=0.1.0-SNAPSHOT

that will change pom.xmls
then only to check/update category.xml

from angularjs-eclipse.

I agree downstepping is bad but until now this plugin "just" been experimental and @angelozerr said he didn't want to settle on an API yet. I think its worth making this explicit in the api versioning and releases going forward.

from angularjs-eclipse.

Both things are OK, and we have 0.1 release now :-)

from angularjs-eclipse.