Risky business... I know about the Red Hat / Fedora balance.... But I never thought the same relation It would be applied to JBoss.
In this way you have an "option" between Commercial Tools or Community Tools....... If I stay "outside" the subscription.... I'll be a second class developer without the best tools.... interesting, very interesting.
Well, the world is big enough ..... to have another subscription.
You understand... I'm very dissapointed... I tested and reported bugs related with JBDS.... just to discovered I'm not helping to build a community, just a software company.
i'm sorry if you feel this way, I always made it very clear in every statement i've done about it.
But seriously all the bug fixes you report are available and will always be available in opensource....what is wrong with JBoss Tools here ?
There is no second class developer here.
*All* the tooling is available for free and opensource; you just need to install Eclipse and JBoss AS etc. on your own.
The problem is with the additional software value added to JBDS, restricted to the general community.
If Eclipse+Tools+Seam are exactly the same than JBDS, just release JBDS as free as the other projects. It's going to be easier.... unless you are waiting for a forked bundled JDBS.
Just think about all the time we are wasting integrating Tools, Seam, Jbpm to Eclipse... everytime we want to use JBoss.
.... and now... the main Jboss development IDE ... is a paid suscription....
Always... Always.. the compiler and the IDE must be the easiest tools to be provided and supported to developers....if you put any restriction... more difficult to build the Red Hat Application Stack.
I just purchased but cannot fine the link to download - Red Hat issue 1790198. The links are all Red Hat software no JBoss?
I'll ping them - it should just be available directly after the buy.
BTW the price is too high MyEclipse offers much more for less.
I don't recall MyEclipse bundling JBoss EAP, RHEL and Red Hat network in their offerings ;)
Anyhow let us know what features you are missing in the tooling (preferably in a another thread). Thats the way you get more in there.
Well it is interesting,
These two articles are clearly stating, Exadel Pro - Red Hat Developer Studio would be open sourced, now you say, JBoss Tool is open source so it is the same thing.
To my knowledge, JBoss Tools doesn't include the Exadel Studio Pro feature, so where can we get Exadel Studio as open source????
You should release JBDS as public as the other software projects.
You always are going to have subscriptions to the supporting services from corporate users.
If you begin to mix things..... problems and confusion...
Fox example... Jboss has no Development Studio.... but Red Hat has a paid suscription that provides one... but they are the same... but you always have the Tools to build the same IDE...what ?......no.. no .,.. no.... very very complex.....not a clear path.
At the end, the subscription value should be at a certified, stable, upgradeable, deployable, supportable tool oriented to enterprises. With partners, training, etc, etc.
Now, I only see amodel based on an access restriction. You are downgrading JDBS to a Shareware price.