Hi all,
After some investigations around JBIDE-11726
<https://issues.jboss.org/browse/JBIDE-11726> (Create target platforms
for developer), we have arrived to an interesting result by having
378987 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=378987>
and**JBIDE-12003 <https://issues.jboss.org/browse/JBIDE-12003> fixed, so
that target platform should be much more stable (CI job only publish
them after validating they can successfully be resolved) and having make
progress about JBIDE-11689
<https://issues.jboss.org/browse/JBIDE-11689>, by using "includeSource"
flag on target-platforms.
So if you want to be less surprised by dependencies-related issue, here
is a way to make your IDE use an equivalent target as the one used by
build, without loosing ability to view source:
1. Checkout the build/target-platform folder in your workspace
2. Open *multiple.target* using the target editor
3. Ckick on "*Set as Target"* on the upper-right corner
Then, PDE will rely on this target definition to resolve dependencies
(from Eclipse, Atlassian, SpringSource and other 3rd-party deps we have).
In order to resolve other JBoss Tools stuff, you may want to complete it
with entries from our development update-sites to resolve other modules
if you need, but please don't commit anything to this TP before opening
a ticket to the target-platform component.
Your feedback is welcome on JBIDE-11726.
--
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>
Ladies and Gentlemen,
as discussed with Max and Fred on IRC, there are projects using Java 6
API but still having
Bundle-RequiredExecutionEnvironment: J2SE-1.5
in their MANIFEST.MF's. The projects in question are the following:
* org.jboss.ide.eclipse.as.ui using java.util.Deque
* org.jboss.tools.seam.ui using java.lang.String.isEmpty()
* org.jboss.tools.maven.ui using java.lang.String.isEmpty()
org.jboss.tools.seam.ui and org.jboss.tools.maven.ui can be fixed either
though
(a) replacing isEmpty() with lenght() == 0 or through
(b) changing the execution environment to JavaSE-1.6
org.jboss.ide.eclipse.as.ui can be quickly be fixed only using (b).
Best,
Peter
Hi all,
FYI, I'm going on vacation in a couple hours (getting married on
saturday) and will come back as a new man on thursday 15th of august.
So if you have any maven related questions while I'm gone, please
contact Max (max.andersen(a)redhat.com), I'm sure he'll be happy to help :-)
Wish me luck!
Fred
Dear
Nice days !
1: We are professional silicone bags supplier ;
2: welcome you OEM / ODM all kind silicone rubber products
3: we are supplier of Wal-Mart and factory direct .
Sample will send to you if you need and let me know .
With my kindly regards and thank you
Seven
web: www.china-youngs.com.cn
skype id : hellobond007
Hello World,
the m2e-wtp team is *very* pleased to announce the very first milestone
release of m2e-wtp 0.16.0, incubating from the Eclipse Foundation. This
release focuses on bug fixes and the new Eclipse to Maven project
conversion feature introduced in m2e 1.1. You can read the complete
changelog[1] and New and Noteworthy notes[2] for further informations.
This m2e-wtp milestone release can be installed from [3].
Please note this release requires m2e 1.1 and you will need to uninstall
m2eclipse-wtp first.
If you find any issues, please open bugs or enhancement requests at [4].
We're planning on releasing a m2e-wtp 0.16.0 RC1 in mid-august and
hopefully go final along the Juno SR1 release, on 28/09/2012
Finally, I'd like to give special kudos to the guys at IBM who helped me
set up the project @ eclipse.org, you've been very helpful, thanks!
Happy hacking.
Fred Bricon
[1] http://wiki.eclipse.org/M2E-WTP/New_and_Noteworthy/0.16
[2]
https://bugs.eclipse.org/bugs/buglist.cgi?list_id=2391517;query_format=ad...
[3] http://download.eclipse.org/m2e-wtp/milestones/0.16.0
[4] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP
--
"Have you tried turning it off and on again" - The IT Crowd