Balsmiq Mockup license
by Max Rydahl Andersen
Hi,
I bumped into http://www.balsamiq.com/products/mockups/ today and liked
what I saw.
Their webapp allows export of images and import of mockup code so it is
usable without the license
but only if you are online.
I contacted them if JBoss Tools dev could get a license and they answered
almost instantly.
If you work on JBoss Tools and want to use the desktop tool for discussing
ideas/mockups send me an
email and I'll give you the license key.
--
/max
17 years, 11 months
ESB editor has been removed?
by Denny Xu
Hi all
I get yesterday's nightly build, and I can't find the esb editor and
its category, has it been removed from esb module?
Denny
17 years, 11 months
Hibernate tests
by Snjezana Peco
The problem with Hibernate tests happens because the tests are being
executed in a workspace mounted as NFS share.
This problem is described on
http://www.cs.indiana.edu/csg/FAQ/General/dotnfs.html.
Hibernate tests remove the ejb3-persistence.jar, but the NFS server
creates .nfsXXX file in the project directory because a Java
classloader keeps the ejb3-persistence.jar file open (JBIDE-1012). The
project can't be removed because the project root directory is not empty.
We can do the following:
- fix JBIDE-1012; we can remove System.currentTimeMilis() from the
project name
or
- skip deleting the project or ignore an exception thrown when deleting
the project. System.currentTimeMilis() can't be removed from the project
name.
Snjeza
17 years, 11 months
We have branched !
by Max Rydahl Andersen
Hi,
In case you don't follow svn-commits, Denis created the
jbosstools-3.0.0.Beta1 branch last night.
What does this mean ?
It means that if you do fixes that needs to go into Beta1 you need to do
it both in branches/jbosstools-3.0.0.Beta1
and in /trunk.
If you are doing stuff that should not go into Beta1 you only commit in
trunk.
Also remember this when you resolve issues - make sure the fix version is
correct! either 3.0.0.Beta1 (in beta1 and trunk) or 3.0.0.cr1 (only in
trunk)
I recommend you use svnmerge.py to keep track of which revisions you have
merged!
If you committed after the branch (Rob ?), please verify if your fixes
needs to go into the branch too.
This also means that Beta1 should now not receive any new features unless
it is something critical. Beta1 branch is intended to be stable and ready
for
QA so we can have the planned release on 31st October.
Thanks,
--
/max
17 years, 11 months
