due to productivity issues, adopting this release will not be an option
for us until a work-around is in place, which is a shame because there
are so many improvements over 2.5.x (some of which we contributed).
however, i understand that netbeans does not hold a significant market
share among uportal developers, so from a practicality stand-point i can
justify moving forward since this is an issue with netbeans. this would
be similar to rolling out a ga release that does not operate with jboss,
because it does work with tomcat.
if this issue applied to eclipse, rolling out would be completely
unacceptable due to the volume of users of that ide in correlation with
the uportal community. that would be similar to rolling out a ga
release that did not operate under tomcat.
i'd like to see us take an approach that ensures support for the top
three tools of a category (i.e. ide-s, servlet containers, databases, etc.)
Cris J Holdorph wrote:
Hmm... I have to disagree with this. I'd also feel the same way about
Eclipse. We're trying to get 2.6.0 GA out the door. It's just my
opinion, but I don't believe any issues that are specific to an IDE
(Eclipse, Netbeans, Intellij, ...) should cause a delay in the release
at this point in the release process.
---- Cris J H
Timothy Carroll wrote:
i agree to moving forward. however, i think a documented work-around
to this issue should accompany the ga release.
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
