[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2623:
----------------------------------
Updates to Central TP for 4.1.1.CR1 (TP version 4.31.0.Final-SNAPSHOT):
* JBDS-2709 Subclipse/SVNKit 1.10_1.8
See also comments in https://issues.jboss.org/browse/JBDS-2710
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.GA
>
> Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2623 at 11/29/13 11:59 AM:
-------------------------------------------------------------
Updates to Central TP for 7.1.0.CR1 / 4.1.1.CR1 (Central TP version 4.31.0.Final-SNAPSHOT):
* JBDS-2709 Subclipse/SVNKit 1.10_1.8
See also comments in https://issues.jboss.org/browse/JBDS-2710
was (Author: nickboldt):
Updates to Central TP for 4.1.1.CR1 (TP version 4.31.0.Final-SNAPSHOT):
* JBDS-2709 Subclipse/SVNKit 1.10_1.8
See also comments in https://issues.jboss.org/browse/JBDS-2710
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.GA
>
> Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBIDE-16165) org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions does not work with Tycho 0.19.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16165?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16165:
-------------------------------
Description:
Trying to perform target platform validation (according to the [README|https://github.com/jbosstools/jbosstools-discovery/blob/master/jbt...]), but using Tycho 0.19.0 instead of 0.18.1, and I end up with this:
{code:title=https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtcentraltarget/pom.xml#L12}
- <tychoVersion>0.18.1</tychoVersion>
+ <tychoVersion>0.19.0</tychoVersion>
{code}
{code}
$ pushd jbtcentraltarget/multiple && mvn -U org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions -DtargetFile=jbtcentral-multiple.target
{code}
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions (default-cli) on project jbtcentral-multiple: Execution default-cli of goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions failed: An API incompatibility was encountered while executing org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions: java.lang.NoSuchMethodError: org.eclipse.tycho.p2.resolver.facade.P2ResolverFactory.createTargetPlatformBuilder(Lorg/eclipse/tycho/core/ee/shared/ExecutionEnvironmentConfiguration;)Lorg/eclipse/tycho/p2/target/facade/TargetPlatformBuilder;
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/nboldt/.m2/repository/org/jboss/tools/tycho-plugins/target-platform-utils/0.16.0-SNAPSHOT/target-platform-utils-0.16.0-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[2] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[3] = file:/home/nboldt/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[4] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[5] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
[ERROR] urls[6] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[7] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[8] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.4/plexus-component-annotations-1.5.4.jar
[ERROR] urls[9] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-archiver/2.2/plexus-archiver-2.2.jar
[ERROR] urls[10] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-io/2.0.4/plexus-io-2.0.4.jar
[ERROR] urls[11] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/tycho-p2-publisher-plugin/0.16.0/tycho-p2-publisher-plugin-0.16.0.jar
[ERROR] urls[12] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/tycho-packaging-plugin/0.16.0/tycho-packaging-plugin-0.16.0.jar
[ERROR] urls[13] = file:/home/nboldt/.m2/repository/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools.targetplatforms:jbtcentral-multiple:4.31.0.Final-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
{code}
was:
Trying to perform target platform validation with <tychoVersion>0.19.0</tychoVersion> instead of 0.18.1, and I end up with this:
{code:title=https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtcentraltarget/pom.xml#L12-L13}
- <tychoVersion>0.18.1</tychoVersion>
+ <tychoVersion>0.19.0</tychoVersion>
{code}
{code}
$ pushd jbtcentraltarget/multiple && mvn -U org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions -DtargetFile=jbtcentral-multiple.target
{code}
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions (default-cli) on project jbtcentral-multiple: Execution default-cli of goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions failed: An API incompatibility was encountered while executing org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions: java.lang.NoSuchMethodError: org.eclipse.tycho.p2.resolver.facade.P2ResolverFactory.createTargetPlatformBuilder(Lorg/eclipse/tycho/core/ee/shared/ExecutionEnvironmentConfiguration;)Lorg/eclipse/tycho/p2/target/facade/TargetPlatformBuilder;
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/nboldt/.m2/repository/org/jboss/tools/tycho-plugins/target-platform-utils/0.16.0-SNAPSHOT/target-platform-utils-0.16.0-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[2] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[3] = file:/home/nboldt/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[4] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[5] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
[ERROR] urls[6] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[7] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[8] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.4/plexus-component-annotations-1.5.4.jar
[ERROR] urls[9] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-archiver/2.2/plexus-archiver-2.2.jar
[ERROR] urls[10] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-io/2.0.4/plexus-io-2.0.4.jar
[ERROR] urls[11] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/tycho-p2-publisher-plugin/0.16.0/tycho-p2-publisher-plugin-0.16.0.jar
[ERROR] urls[12] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/tycho-packaging-plugin/0.16.0/tycho-packaging-plugin-0.16.0.jar
[ERROR] urls[13] = file:/home/nboldt/.m2/repository/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools.targetplatforms:jbtcentral-multiple:4.31.0.Final-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
{code}
> org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions does not work with Tycho 0.19.0
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16165
> URL: https://issues.jboss.org/browse/JBIDE-16165
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.1.CR1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> Trying to perform target platform validation (according to the [README|https://github.com/jbosstools/jbosstools-discovery/blob/master/jbt...]), but using Tycho 0.19.0 instead of 0.18.1, and I end up with this:
> {code:title=https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtcentraltarget/pom.xml#L12}
> - <tychoVersion>0.18.1</tychoVersion>
> + <tychoVersion>0.19.0</tychoVersion>
> {code}
> {code}
> $ pushd jbtcentraltarget/multiple && mvn -U org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions -DtargetFile=jbtcentral-multiple.target
> {code}
> {code}
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions (default-cli) on project jbtcentral-multiple: Execution default-cli of goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions failed: An API incompatibility was encountered while executing org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions: java.lang.NoSuchMethodError: org.eclipse.tycho.p2.resolver.facade.P2ResolverFactory.createTargetPlatformBuilder(Lorg/eclipse/tycho/core/ee/shared/ExecutionEnvironmentConfiguration;)Lorg/eclipse/tycho/p2/target/facade/TargetPlatformBuilder;
> [ERROR] -----------------------------------------------------
> [ERROR] realm = plugin>org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = file:/home/nboldt/.m2/repository/org/jboss/tools/tycho-plugins/target-platform-utils/0.16.0-SNAPSHOT/target-platform-utils-0.16.0-SNAPSHOT.jar
> [ERROR] urls[1] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> [ERROR] urls[2] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> [ERROR] urls[3] = file:/home/nboldt/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[4] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[5] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
> [ERROR] urls[6] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[7] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[8] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.4/plexus-component-annotations-1.5.4.jar
> [ERROR] urls[9] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-archiver/2.2/plexus-archiver-2.2.jar
> [ERROR] urls[10] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-io/2.0.4/plexus-io-2.0.4.jar
> [ERROR] urls[11] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/tycho-p2-publisher-plugin/0.16.0/tycho-p2-publisher-plugin-0.16.0.jar
> [ERROR] urls[12] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/tycho-packaging-plugin/0.16.0/tycho-packaging-plugin-0.16.0.jar
> [ERROR] urls[13] = file:/home/nboldt/.m2/repository/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools.targetplatforms:jbtcentral-multiple:4.31.0.Final-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-16161 at 11/29/13 11:33 AM:
-------------------------------------------------------------------
{quote}If you try it locally, you will see that a lot of services aren't started. The tests are started, but the most of them either freeze or fail.{quote}
Ok, so some pieces of code may depend on PlatformAdmin. Do you know if those are inside JBT or Eclipse? Anyway, using PlatformAdmin is somehow deprecated in favor of Wiring API, We should migrate our code, and the bundles we depend on, to this Wiring API if possible
{quote}The org.eclipse.tycho.surefire.osgibooter plugin won't start without the PlatformAdmin service, so a lot of the tests won't be run correctly.{quote}
That's not exactly true. The PlatformAdmin is only used for login purpose, if it's not there surefire.osgibooter will log "Could not acquire...", continue and run tests (cf quote previously "The tests are started"). I've seen some test suite working without PlatformAdmin, I'd like ours to behave the same way, and rely on more sustainable API (Wiring API).
{quote}I can't find any components that build{quote}
See for example https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
{quote}Adding the o.e.e4.rcp feature would be the easiest solution{quote}
I agree, but I feel it's better to look for the more sustainable solution (Wiring API) instead of the easiest one.
was (Author: mickael_istria):
{quote}If you try it locally, you will see that a lot of services aren't started. The tests are started, but the most of them either freeze or fail.{quote}
Ok, so some pieces of code may depend on PlatformAdmin. Do you know if those are inside JBT or Eclipse? Anyway, using PlatformAdmin is somehow deprecated in favor of Wiring API, We should migrate our code, and the bundles we depend on, to this Wiring API if possible
{quote}The org.eclipse.tycho.surefire.osgibooter plugin won't start without the PlatformAdmin service, so a lot of the tests won't be run correctly.{quote}
That's not exactly true. The PlatformAdmin is only used for login purpose, if it's not there surefire.osgibooter will continue and run tests (cf quote previously "The tests are started"). I've seen some test suite working without PlatformAdmin, I'd like ours to behave the same way, and rely on more sustainable API (Wiring API).
{quote}I can't find any components that build{quote}
See for example https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
{quote}Adding the o.e.e4.rcp feature would be the easiest solution{quote}
I agree, but I feel it's better to look for the more sustainable solution (Wiring API) instead of the easiest one.
> Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
> -------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBIDE-16165) org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions does not work with Tycho 0.19.0
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16165:
----------------------------------
Summary: org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions does not work with Tycho 0.19.0
Key: JBIDE-16165
URL: https://issues.jboss.org/browse/JBIDE-16165
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.1.1.CR1
Reporter: Nick Boldt
Assignee: Mickael Istria
Trying to perform target platform validation with <tychoVersion>0.19.0</tychoVersion> instead of 0.18.1, and I end up with this:
{code:title=https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtcentraltarget/pom.xml#L12-L13}
- <tychoVersion>0.18.1</tychoVersion>
+ <tychoVersion>0.19.0</tychoVersion>
{code}
{code}
$ pushd jbtcentraltarget/multiple && mvn -U org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions -DtargetFile=jbtcentral-multiple.target
{code}
{code}
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions (default-cli) on project jbtcentral-multiple: Execution default-cli of goal org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions failed: An API incompatibility was encountered while executing org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions: java.lang.NoSuchMethodError: org.eclipse.tycho.p2.resolver.facade.P2ResolverFactory.createTargetPlatformBuilder(Lorg/eclipse/tycho/core/ee/shared/ExecutionEnvironmentConfiguration;)Lorg/eclipse/tycho/p2/target/facade/TargetPlatformBuilder;
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/nboldt/.m2/repository/org/jboss/tools/tycho-plugins/target-platform-utils/0.16.0-SNAPSHOT/target-platform-utils-0.16.0-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[2] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[3] = file:/home/nboldt/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[4] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[5] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
[ERROR] urls[6] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[7] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[8] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.4/plexus-component-annotations-1.5.4.jar
[ERROR] urls[9] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-archiver/2.2/plexus-archiver-2.2.jar
[ERROR] urls[10] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-io/2.0.4/plexus-io-2.0.4.jar
[ERROR] urls[11] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/tycho-p2-publisher-plugin/0.16.0/tycho-p2-publisher-plugin-0.16.0.jar
[ERROR] urls[12] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/tycho-packaging-plugin/0.16.0/tycho-packaging-plugin-0.16.0.jar
[ERROR] urls[13] = file:/home/nboldt/.m2/repository/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools.targetplatforms:jbtcentral-multiple:4.31.0.Final-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16161:
----------------------------------------
{quote}If you try it locally, you will see that a lot of services aren't started. The tests are started, but the most of them either freeze or fail.{quote}
Ok, so some pieces of code may depend on PlatformAdmin. Do you know if those are inside JBT or Eclipse? Anyway, using PlatformAdmin is somehow deprecated in favor of Wiring API, We should migrate our code, and the bundles we depend on, to this Wiring API if possible
{quote}The org.eclipse.tycho.surefire.osgibooter plugin won't start without the PlatformAdmin service, so a lot of the tests won't be run correctly.{quote}
That's not exactly true. The PlatformAdmin is only used for login purpose, if it's not there surefire.osgibooter will continue and run tests (cf quote previously "The tests are started"). I've seen some test suite working without PlatformAdmin, I'd like ours to behave the same way, and rely on more sustainable API (Wiring API).
{quote}I can't find any components that build{quote}
See for example https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
{quote}Adding the o.e.e4.rcp feature would be the easiest solution{quote}
I agree, but I feel it's better to look for the more sustainable solution (Wiring API) instead of the easiest one.
> Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
> -------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16161:
---------------------------------------
{quote}
If the test actually depend on PlatformAdmin, I'd rather have them reworked to depend on the OSGi Wiring API which is a standard provided by Luna.
{quote}
The org.eclipse.tycho.surefire.osgibooter plugin depends on PlatformAdmin. It doesn't matter if some test depends on it.
> Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
> -------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16161:
---------------------------------------
{quote}
You report is more focused on a solution than on the issue: In the case of base component, how does it fail? How do you see the error? Are tests at least starting?
{quote}
If you take a look at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
you will see the build is aborted after two hour timeout.
If you try it locally, you will see that a lot of services aren't started. The tests are started, but the most of them either freeze or fail.
For instance, CompatibilityEditor isn't initialized and all the tests that open a JBoss editor fail with a NPE.
{quote}
It seems to me that Tycho tests can generally run without PlatformAdmin being available (it probably depends on some test specificities).
{quote}
See http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-surefire/...
The org.eclipse.tycho.surefire.osgibooter plugin won't start without the PlatformAdmin service, so a lot of the tests won't be run correctly.
The following message can be often seen in the log: "Could not acquire PlatformAdmin server".
{quote}
Most other components have successfully run their tests without change in parent pom. I'm not sure changing surefire configuration is the optimal solution.
{quote}
I can't find any components that build on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
The most of them require the base component that isn't built.
Adding the o.e.e4.rcp feature would be the easiest solution. It is also possible to create a separate feature containing the compatibility fragment and include it to the main build or to every test separately.
You may also want to take a look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=407097
> Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna
> -------------------------------------------------------------------------
>
> Key: JBIDE-16161
> URL: https://issues.jboss.org/browse/JBIDE-16161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Mickael Istria
>
> Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin.
> The easiest way is to add the org.eclipse.e4.rcp feature to the main build.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (JBIDE-16134) CordovaSim should start the livereload server
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16134?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-16134:
------------------------------------------------
I guess there is a lot of controversy around that issue:
1. [~gercan], your options requires dependency from browsersim to livereload. Assuming that BrowserSim/CordovaSim can be installed without livereload. I don't think creating dependencies is a good idea.
2. [~maxandersen], it make sense, but don't you think this dialog would be annoying? And what should be done after this dialog? Should we "uncheck" livereload option in browsersim after that?
> CordovaSim should start the livereload server
> ---------------------------------------------
>
> Key: JBIDE-16134
> URL: https://issues.jboss.org/browse/JBIDE-16134
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.1.CR1
> Reporter: Gorkem Ercan
> Assignee: Konstantin Marmalyukov
>
> CordovaSim should configure and start the livereload server when the livereload is enabled.
> If starting the server from CordovaSim menu is a big problem, alternately, the server can always be configured and started before a CordovaSim launch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years