Update Target Platform 4.40.0.Alpha2-SNAPSHOT to Luna M5
by Mickael Istria
Hi all,
Here is a proposal for a new 4.40.0.Alpha2-SNAPSHOT target platform: https://github.com/jbosstools/jbosstools-target-platforms/pull/35
It consists in the following changes:
* Update to Luna M5
** Some projects are still using same version that we had for Kepler release (Birt, jetty, m2e...)
** Most projects have contributed a new M5 build (Platform, EMF, DTP, Mylyn...)
** Use newer SWTBot 2.2.0 which contain some minor fixes.
Please review this PR and yell if there is anything shocking. You can use the following steps to try to build build the TP locally and try out against your component:
Build target-platform:
$ cd jbosstools-target-platforms
$ git fetch mistria luna-M5
$ git checkout FETCH_HEAD
$ cd jbosstools/multiple
$ mvn clean install -P \!multiple2repo
Try with just built target-platform:
$ cd /path/to/your/component
$ mvn clean verify (-Dtpc.version=4.40.0.Alpha2-SNAPSHOT) -Pmultiple.target
Cheers,
--
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>
10 years, 9 months
[Reminder] Feel free to request TP changes!
by Mickael Istria
Hi all,
Here is a reminder, as previous discussion seem to show that it's
something we've not made very clear.
You're free to *request changes in target-platform*. Those can be
addition of bundles, updates of some bundles to build against latest
changes, deletion of some deprecated bundles... or anything that can
help you to save time or write better code. Requesting a change is easy
and is generally considered as a high-priority task so you don't have to
wait:
https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
So if some of you are waiting for some changes in Target Platform to
happen, then stop waiting and request them as soon as you need them.
Additionally to changes that happen on your request, we also
systematically perform updates when important milestones or releases are
available.
Cheers,
--
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>
10 years, 10 months
m2eclipse-mavenarchiver writes pom.xml/pom.properties too aggressively
by Snjezana Peco
Hi,
The AbstractMavenArchiverConfigurator.writePom method is called whenever
the Maven builder is called. The method writes pom.xml/pom.properties
archive files no matter if pom.xml has been changed or not.
M2e-wtp includes the Maven Archiver configurator into different projects
(war, ear, ejb, rar...)
Since the Maven builder can often be called when there are a lot of
maven projects in the workspace (the wildfly distribution, for
instance), this issue will decrease performance.
It will also unnecessarily call other builders (CDI, KB, Arquillian
...). If those builders are created correctly, they won't do anything,
but performance will be decreased because the following useless actions
have been run:
- Maven Archiver writes pom.xml/pom.properties
- Eclipse runs other builders
- builders search a resource delta
The https://github.com/tesla/m2eclipse-mavenarchiver/pull/2 PR fixes the
issue by calling the writePom method only if pom.xml is changed or if
there isn't pom.xml in the output folder.
I have created the PR against the
https://github.com/tesla/m2eclipse-mavenarchiver repository. Not sure if
it is a valid repository for the m2eclipse-mavenarchiver plugin.
Snjeza
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
10 years, 10 months
ACTION REQUIRED: any jira that haven't seen updates for 720 days (~2years)
by Max Rydahl Andersen
Hi,
This query:
https://issues.jboss.org/issues/?jql=%28project%20%3D%20JBIDE%20OR%20proj...
returns currently 296 issues which have not been updated the last 730
days (~2 years).
I would like to close anything that is just not relevant anymore as
"outdated" and with a comment that
if issue still relevant then please reopen or re-report it.
But before I do that I would like to avoid closing stuff you believe
still is relevant.
Thus if you see an issue on here that should get looked at - please
leave a comment on it with why/info and it will automatically drop out
of this list.
Anything still on this list on Thursday morning (europe) time I will
batch close.
Thanks,
/max
10 years, 10 months
