ACTION REQUIRED: Beta2 code freeze is this Thursday July 16
by Nick Boldt
Just a reminder that it's code freeze time again. I'll send out the
usual branch-and-update-root-pom task JIRAs tomorrow.
Here's the schedule for the next couple weeks:
Wed July 15: target platform 4.50.0.Beta2 will be released (unless we
have some reason not to do so)
Thu July 16: code & *FEATURE* freeze for JBT 4.3 / JBDS 9.0 Beta2
Mon July 20: QE testing beings
Mon July 27: Beta2 released to public
Since Beta2 is our *feature freeze* as well as being a regular *code
freeze*, beyond Thursday you should *only be doing bugfixes*, not
creating new features. (Exceptions can be made; please contact Max.)
If you have any questions or concerns, please don't hesitate to ask.
Cheers,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years, 6 months
Proposed change to JBT TP 4.50.0.Beta2-SNAPSHOT : add Mylyn Wikitext Asciidoc editor
by Nick Boldt
Max has requested that we add the Mylyn Wikitext Asciidoc editor the the
JBT/JBDS TP.
Here's the JIRA, on which you can see the PR and p2diff.
Ideally this would be pushed in this week so that it will be in place
for Beta2's target platform freeze next week on July 15.
As a reminder, the Beta2 code freeze is next Thursday, July 16.
Cheers,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years, 6 months
License feature migration : Q&A
by Nick Boldt
I just sent out a bunch of Task JIRAs to remind everyone to update their
features to use the new license feature, some time before we release CR1.
Ref: https://issues.jboss.org/browse/JBIDE-20194
However, I've noticed a couple of questions being asked about this, so
here's a quick Q&A.
--
Q1. Do I need to upversion my features again?
A1. NO. If you already upversioned once during the JBT 4.3.0 cycle (eg.,
from 1.7 in JBT 4.2 to 1.8 in JBT 4.3), that's good enough. No need to
bump again! I just put that boilerplate reminder in there in case you
haven't already done a version bump for this cycle.
--
Q2. The fixversion target is CR1. Can I do this for Beta2?
A2. Yes, I only set CR1 so that this change would not prevent you from
getting more urgent work done in time for Beta2's feature freeze, which
is in 9 days on July 16 - next Thursday!
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years, 6 months
How to build fuseide locally? All I get is fails.
by Rob Stryker
Hi Lars:
I've made sure my fork of /home/rob/code/fuseide/fuseide/ is up to date,
and I've successfully built the TP. I was attempting to build the
actual plugins (since many of them are missing jars which are fetched on
build), and all I get is fails.
Specifically, one of the failures I'm getting is:
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could
not find artifact org.apache.camel:camel-core:jar:2.15.1.redhat-620129
in redhat-techpreview-all-repository
(http://maven.repository.redhat.com/techpreview/all/)
We've (Nick and I) taken a quick glance in the techpreview and
early-access nexus repos and have been unable to locate the version the
build is looking for. So it makes sense the build would fail... My
question is, how does the fuse team build this, and why does it work for
them and not for me?
It's very difficult for me to offer help with various topics (terminal
migration, other) to the fuse side if their code can't be built and
plugins cannot be imported.
I'm not sure if this comes off as rude, but I suggest you make a habit
of ensuring that your code can be actually built and imported by others.
If it doesn't work for me, it most likely also doesn't work for other
possible external contributors. One way to test this is to wipe your .m2
folder and try to build your stuff and make sure it works.
One other thing: I also suggest you clean up the repo a bit and remove
folders such as "old" that are not to be included in the build. Maybe
I'm alone on this one, but, the purpose of having a good SCM tool is
that you only need to have what's actually used in master. When I do an
import on your repo, it's importing plugins that will never be used, and
this is definitely confusing.
Either way, I can't make any progress offering to rewrite your terminal
if I can't import your code. Build is fsck'd. Plz to fix at earliest
convenience.
=/
9 years, 6 months