Nightly builds jar versions going backwards in time
by Galder Zamarreno
What's happened to the trunk nightly updates?
I have JBossAS tools 2.0.0.GA-N200812201616 installed on my laptop from
nightly updates and last night build's have gone back to
2.0.0.CR2-N200812290609, which means that I cannot update my system
automatically.
Can you please make sure you keep library versions consistent throughout?
Cheers,
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
17 years, 1 month
QA Daily report 31 December 2008
by Aliaksey Nis
Hello Denis,
This is Daily QA report for 31 December 2008.
Tasks performed:
1. Testcases updates.
Happy New Year!
--
Best regards,
Aliaksey mailto:anis@exadel.com
17 years, 1 month
jbosstools-issues mailing list
by Snjezana Peco
I am not receiving any email notification for jira issues. Have tried to
subscribe again, but haven't succeeded.
Is anyone else experiencing this problem?
Thanks,
Snjeza
17 years, 1 month
JBoss Tools and JBDS Candidate releases
by Max Rydahl Andersen
Hi,
If I don't hear anything else JBDS 2 CR1 is ready and we got ready with
JBoss Tools just a few days short of what we expected (22/12 instead of
19/12)
so it turned out to be Christmas after all this year - Thanks Team! ;)
We learned a lot (again) this time around and big kudos to both Nick
Boldt and Denis Golovin for pushing the builds through - Thanks!
Special thanks for Nick Boldt on improving the release process with
several magnitudes by simply utilizing the wonders of rsync and direct
copies to
our updatesites and sf.net - I feel much less bad for those doing the
future releases now :) It's those little improvements that makes a huge
difference - Nick, thanks again!
In the short and long term it is important that we all watch out on the
forums and follow up on anything we can so users feel helped and hopefully
also get helped. It is crucial for any opensource project to keep the
community alive.
The next phase is about fixing bugs and making the ui look and feel
smooth! GA should not add any features unless they are
critical/blockers - if in doubt speak up on this or jbosstools list.
For now I would like everyone to try and use our software and report the
bugs/issues you find - and then start help fixing bug.
Also remember that the documentation is also part of our feature set -
so if you find issues in the docs, report them or even better
fix them.
And most important of all, remember to enjoy the upcoming holiday season
no matter where you are - all of the above is not relevant during
vacation :)
Merry Christmas and See you next year!
Max
p.s. This is my last day before my vacation - I won't be reliably online
until 4th January; I will though check emails once in a while so if
something is urgent I'll reply.
17 years, 1 month
QA Daily report 23 December 2008
by Aliaksey Nis
Hello Denis,
This is Daily QA report for 23 December 2008.
Tasks performed:
1. Testing of latest JBoss Dev Studio 2.0.0 CR1 build.
Seam, ESB etc tests.
2. Issues verification.
3. Testcases updates.
--
Best regards,
Aliaksey mailto:anis@exadel.com
17 years, 1 month
QA Daily report 22 December 2008
by Aliaksey Nis
Hello Denis,
This is Daily QA report for 22 December 2008.
Tasks performed:
1. Testing of JBoss Dev Studio 2.0.0 CR1 build.
2. Issues verification.
3. Testcases updates.
--
Best regards,
Aliaksey mailto:anis@exadel.com
17 years, 1 month
Re: [Bug 257470] ComponentCore in WTP 3.0.3 isn't compatible with earlier 3.0.x versions
by Denny Xu
WTP team suggested the way to create VirtualComponent, so should I get
the changes applied to CR1 branch?
It seems that they would not like to recover the behavior
"ComponentCore.createComponent(project)" method.
Denny
bugzilla-daemon(a)eclipse.org wrote:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=257470
> Product/Component: WTP Common Tools / wst.common
>
>
>
>
> --- Comment #12 from Carl Anderson <ccc(a)us.ibm.com> 2008-12-18 16:30:58 -0400 ---
> As per Max's comment #4, in the scenario where developers wish to call
> VirtualComponent.create(int, IProgressMonitor) to create the appropriate
> component file, the following code is acceptable:
>
> VirtualComponent c = ComponentCore.createComponent(project);
> if(c==null) {
> c = ComponentCore.createComponent(project, false);
> }
> c.create(0, null);
>
> This code should work properly if it is compiled against WTP 3.0.3 (or later),
> and should run properly against all WTP 3.0.x versions.
>
> Now, what would not be advisable would be for developers to replace every
> previous instance of:
>
> VirtualComponent c = ComponentCore.createComponent(project);
>
> with:
>
> VirtualComponent c = ComponentCore.createComponent(project);
> if(c==null) {
> c = ComponentCore.createComponent(project, false);
> }
>
> as that would once again open up the same hole for possible component
> corruption that was closed down by bug 250004. The problem that was occurring,
> as stated in comment #5, was that, in some scenarios, access to the
> VirtualComponent through ComponentCore.createComponent(project), (which come
> from many adopters as well as WTP code) where it was not checking for the
> existance of the component file was causing the creation of an empty component
> model , thus causing the appearance of an inconsistent files dialog and
> component corruption. Therefore, in all scenarios other than the initial
> component creation scenario (which is the only scenario broken by the change in
> bug 250004), WTP code and adopters should call either
> ComponentCore.createComponent(project) or
> ComponentCore.createComponent(project, true).
>
>
>
17 years, 1 month
