Fwd: [wtp-dev] Upcoming platform change for Kepler M6
by Victor Rubezhny
For those who aren't subscribed to wtp-dev mailing lists.
Just to inform on upcoming change in Eclipse's core/debug packages
re-export policy.
See the forwarded messages.
Best Regards,
Victor
-------- Original Message --------
Subject: [wtp-dev] Upcoming platform change for Kepler M6
Date: Tue, 12 Feb 2013 19:47:11 -0500
From: Carl Anderson <ccc(a)us.ibm.com>
Reply-To: General discussion of project-wide or architectural issues.
<wtp-dev(a)eclipse.org>
To: wtp-dev(a)eclipse.org
Folks,
The Platform team announced that org.eclipse.debug.core will no longer
export org.eclipse.core.resources - see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=156134 . This already
effected the Source Editing team - see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=400538 . This may cause a
lot of compilation problems when we move up to an M6 build. Please look
through your plugin's dependencies for instances of
org.eclipse.debug.core to ensure that this is handled properly. (I see
at least 33 imports of org.eclipse.debug.core in WTP right now.)
I will hold off on moving up to an M6 platform build this week, but we
will move up early next week. Please address any compilation problems
as quickly as possible.
FWIW,
- Carl Anderson
WTP Build guy
11 years, 11 months
whats the magic trick to get tycho to use latest available IU ?
by Max Rydahl Andersen
Hey,
We talked about this 'sideeffect' in tycho where you see things like:
[WARNING] The following locally built units have been used to resolve project dependencies:
[WARNING] org.jboss.tools.common.text.ext/3.4.0.Beta2-v20121028-1355
[WARNING] org.jboss.tools.usage/1.2.0.Beta2-v20121028-1355
[WARNING] org.jboss.tools.common.el.ui/3.4.0.Beta2-v20121028-1355
[WARNING] org.jboss.tools.common.el.core/3.4.0.Beta2-v20121028-1355
Even when I got a repository with even newer bits on it.
Was there a flag for tycho to make it choose the latest instead or somehow ignore my local built ones ?
(even better I would like to just remove all local built stuff without having to guess/list all the names)
/max
11 years, 11 months
JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?
by Max Rydahl Andersen
Hey,
If we branched for JBT 4.1 Alpha next week would you be ok ?
Koen and Denis did an awesome job of at least getting Hibernate JPA/Dali integration compiling this week.
And as Nick announced our simplest plan moving forward is to compile JBT 4.1 which will be basis for JBDS 7 against Kepler (theoretically we could have something working
on both but it would be a massive QE effort).
Eclipse Kepler M5 is coming out Friday so we might still have some issues but Nick/Mistria will be setting up a M5 based target platform as soon as possible.
It would be great if we could get out an early Alpha to get some traction and figure out what issues we got to fight when it all comes together.
Could you let me know ASAP if you have any issues/concerns with doing a branch next week for an Alpha build ? Would you be ready ?
Being ready for this means:
1) tested your component works on M5
2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise it)
3) issues marked with N&N so you can get them documented
4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0 (we still have to do this "too high jump" in our current setup -hopefully can fix before next big version)
5) Branched your component with jbosstools-4.1.Alpha1x
Please let me know if you are ready for that or have questions/concerns.
Thanks,
Max
11 years, 11 months
New Feature for Target Platform: materialize a local "SDK"
by Mickael Istria
Hi all,
as requested by Max and Rob on
https://issues.jboss.org/browse/JBIDE-13462 , I've added an option on
our Mojo that turns a target-platform file into a site.
The new feature is that if you specify
"-Dmirror-target-to-repo.includeSources=true" to Maven while building a
"multiple" target, it will generate aggregated/unified site that also
contains available sources for the target-platform.
If for any reason you have an issue with using the "multiple.target" as
the target-platform in your IDE (which is still the recommended
procedure), then as a workaround you can build the target-platfroms with
this flag, and it will result on a single site containing everything
that is in mulitple + available source. You can use this local site a a
Target-platfrom in your IDE, it will contain the same thing as it would
resolve with multiple.
You use this site as an "Installation" when setting up a target-platform
in multiple workspaces, then it won't re-download everything in each
workspace.
If you're using multiple.target, and are happy enough with it, keep on
using it.
Feedback is highly welcome.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
11 years, 11 months
New Kepler M5 target platform in progress
by Nick Boldt
I've started work on the new Kepler M5 target platform, which includes
newer versions of m2e (1.3), m2e-wtp (0.17), GPE (3.1.3), and GWT SDK
(2.5.0), as well as the usual Eclipse.org stuff like Kepler (M5),
Eclipse (4.3.0.M5), WTP (3.5.0.M5), and BIRT 4.2.2.
It may have to be rebuilt again in a day or two if the Kepler staging
site I used changes to pull in newer WTP bits, or if the final WTP build
for M5 is different from the I build I used.
Speaking of WTP... it appears that the *org.eclipse.persistence.jpa*
feature no longer exists. The *org.eclipse.persistence.jpa* PLUGIN is
still part of WTP (and therefore Kepler), but it's now only wrapped by
the org.eclipse.jpt.jpa.feature. If you currently depend on the old
org.eclipse.persistence.jpa feature, you should now depend on either
just the plugin(s) you actually need, or the new feature.
---
The new TP bits will be located here, but are subject to change as noted
above:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3...
(REPO/ folder or zip file)
(A significant change in content, rather than just a fix, will result in
creation of a .3 version instead of simply rebuilding the .2 version.)
---
When the TP is ready, I'll switch the parent pom to use it by default.
For now, you can test it using this:
mvn verify -DTARGET_PLATFORM_VERSION=4.30.2.Alpha1-SNAPSHOT
---
Aside: if you're wondering how we got from 4.30.0 to 4.30.2, there was
an TP built in between which removed uml2, graphiti, and zest. See
https://issues.jboss.org/browse/JBIDE-13435.
Comments or issues w/ the new TP in progress, report them on
https://issues.jboss.org/browse/JBIDE-13336.
Cheers,
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
11 years, 11 months
