Kepler M6 target platform coming next week
by Nick Boldt
Kepler M6 project bits will be available between today and Mar 22 [1].
As such, within the next week you'll see a new Kepler-based target
platform, updated with the following changes:
* Upgrade to Kepler M6 / Eclipse 4.3M6 / WTP 3.5M6 / etc.
* Add mockito and festassert JBIDE-12971, JBIDE-1972
* Add Zest (for SpringIDE 3.2) JBDS-2395
* Upgrade Atlassian JBIDE-13682, JBIDE-13724
* Upgrade to GWT 3.2 JBDS-2486
* Upgrade to m2e-wtp 0.18.0 [2]
* Fix Jetty JBIDE-13736, JBIDE-13712
If you have other requests for the next target platform, please let me
know what you need added/removed/changed/updated/tweaked... ideally via
a JBIDE jira, assigned to me or Mickael.
[1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#Schedule
[2] http://download.eclipse.org/m2e-wtp/milestones/kepler/0.18.0/
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years, 1 month
AS Test Suite failure fix?
by Rob Stryker
https://github.com/jbosstools/jbosstools-server/commit/b3672b46e4df710741...
Denis:
I realize the error in the test suite was that the .project file is now
included, whereas it was not included in the past. Why do you think the
proper solution to this change in behavior was to simply change the
expected count? That seems like a very bad fix.
If something upstream has changed, we should discover what it is before
simply changing the expected count in the unit test. Clearly these tests
used to pass, and started failing after the update to m5. Shouldn't we
try to discover what exactly changed here?
- Rob
13 years, 1 month
Funkyness with .target using google adt site
by Max Rydahl Andersen
Hey,
I made an experiment today at https://github.com/maxandersen/jbosstools-target-platforms/blob/tp_process where the jbosstools .targt file got the following added to it:
<location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit">
<unit id="com.android.ide.eclipse.ddms.feature.group" version="21.1.0.v201302060044-569685"/>
<unit id="com.android.ide.eclipse.adt.feature.group" version="21.1.0.v201302060044-569685"/>
<repository location="https://dl-ssl.google.com/android/eclipse"/>
</location>
mvn install for the multiple completes, but the only IU's added are:
./multiple/target/jbosstools-multiple.target.repo/features/com.android.ide.eclipse.adt_21.1.0.v201302060044-569685.jar
./multiple/target/jbosstools-multiple.target.repo/plugins/com.android.ide.eclipse.adt.package_21.1.0.v201302060044-569685.jar
./multiple/target/jbosstools-multiple.target.repo/plugins/com.android.ide.eclipse.adt_21.1.0.v201302060044-569685.jar
./multiple/target/jbosstools-multiple.target.repo/plugins/overlay.com.android.ide.eclipse.adt.overlay_21.1.0.v201302060044-569685.jar
where it should include much more.
After that it then fails during validation of unified stating:
[INFO] Validating /Users/max/code/jbosstools/jbosstools-target-platforms/jbosstools/unified/target/jbosstools-unified.target...
[INFO] Failed, see Error log below
[ERROR] Validation found errors in 1 .target files:
Could not resolve content of jbosstools-unified.target
Could not find "com.android.ide.eclipse.ddms.feature.group/21.1.0.v201302060044-569685" in the repositories of the current location
No other errors/warnings reported afaics.
Anyone with an idea on what is going on here?
/max
13 years, 1 month
SWTBot 2.1 is available... should we upgrade?
by Nick Boldt
We're currently including SWTBot 2.0.5 in the JBT 4.1 (Kepler-based)
target platform to allow tests to build & run.
However, 2.1 is now available. Does anyone want this new version
included in the Kepler-based target platform for JBT 4.1?
http://wiki.eclipse.org/SWTBot
If so, please open a JIRA requesting it be evaluated & then added to our
target platform.
Thanks!
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years, 1 month
Please test building your project w/ Tycho 0.17.0-SNAPSHOT
by Nick Boldt
Tycho 0.17.0 is about to be released. For us, this affects the following
issues:
[JBIDE-11558] Repositories are missing source feature titles [Open,
Major, (Build/Releng, updatesite, UpStream), mickael_istria]
https://issues.jboss.org/browse/JBIDE-11558
[JBIDE-13420] descriptionURL attribute is missing in feature.properties
file for org.jboss.tools.openshift.egit.integration.test.feature,
org.jboss.tools.openshift.express.test.feature and
org.jboss.ide.eclipse.as.test.feature [Closed, Major, (JBossAS/Servers,
openshift), dgolovin] https://issues.jboss.org/browse/JBIDE-13420
[JBDS-2497] Building JBDS product w/ -Ppack200 results in NPE and build
failure [Open, Major, (Build), mickael_istria]
https://issues.jboss.org/browse/JBDS-2497
If you get a chance to test building your project w/ Tycho 0.17.0,
please do so & report any problems in JIRA or to Eclipse Bugzilla, as
appropriate. You can test using the instructions posted below, or simply
with:
$ mvn clean install -DtychoVersion=0.17.0-SNAPSHOT
Unless something blocks it, I expect that we'll be moving up to this new
version in the parent pom in master branch in the next week or so.
Cheers,
-------- Original Message --------
Subject: [tycho-user] please test staged tycho 0.17.0
Date: Mon, 18 Mar 2013 10:58:05 +0000
From: Sievers, Jan <jan.sievers(a)sap.com>
Reply-To: Tycho user list <tycho-user(a)eclipse.org>
To: Tycho user list <tycho-user(a)eclipse.org>
Tycho milestone release 0.17.0 has been staged.
For details of new features and bugfixes, see release notes [1].
Please help by testing the staged milestone build.
To use it, change your tycho version to 0.17.0 and add snippet [2] to
your pom.
We encourage you to also test with an empty local Maven repository,
so that p2's new Apache httpclient v4 is tested more extensively.
We plan to promote this release on Friday unless major regressions are
found (and EclipseCon is canceled ;).
Regards,
Tycho team
---
[1] http://wiki.eclipse.org/Tycho/Release_Notes/0.17
[2]
<pluginRepositories>
<pluginRepository>
<id>tycho-staged</id>
<url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-913/</url>
</pluginRepository>
</pluginRepositories>
_______________________________________________
tycho-user mailing list
tycho-user(a)eclipse.org
https://dev.eclipse.org/mailman/listinfo/tycho-user
13 years, 1 month
Re: [jbosstools-dev] Time for a new SOA test repo?
by Max Rydahl Andersen
>https://github.com/jbosstools/jbosstools-integration-tests/pull/188
>
>
>The problem is (was) that:
>* The ESB tests require the ESB UI which requires Zest - tests build fails on master for 7.0
>* Zest is not in the JBT test package, but it is in the JBTIS test package
we probably need Zest for other reasons anyway so that probably makes sense to add to core TP anyway.
>* Adding JBTIS TP repo to our root pom in integration-tests would affect all our tests:
>-> The tests would run slower
Hopefully not...did you see a big effect ?
>-> The JBTIS test package might affect our tests - we might miss issues of plugins not being in the JBT test package
not following what you mean here ? if JBTIS test package does affect your test we want to know about it ;)
That said you should be using JBTIS since that is where the esb plugins are. Can't just use jbosstools core as base for this.
>So - what are the solutions?
Split out the github repository and move the integration-platform tests to a separate repo.
>Second, long-term
>* We had talked about this in the past - creating a new SOA test repo
integration-test repo - its no longer just SOA.
>-> The SOA 6 tests will be affected (remember that the ESB examples are still not configured here with JBTIS)
jira ?
>-> This will mean that existing 4.0.x work would move to the new repo
you'll need to migrate the history very carefully yes.
>-> Everyone using the SOA tests will have to adapt
>-> What else can go wrong?
>Need to tell Drools tests - BRMS team - Lukas Petroviky
>- the BRMS team has no one to do the testing at the moment.
/max
13 years, 1 month
Security warning when installing plugins
by Andrej Podhradsky
Hi folks,
maybe this was discussed a while ago but is it ok that a security warning occurs during installing any jboss tool?
Best Regards
--
Andrej Podhradsky
Quality Assurance Associate
JBoss SOA Platform
IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno
13 years, 1 month
