[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22673 at 7/8/16 10:39 AM:
-------------------------------------------------------------
Curiously, when I apply the above PR for discovery and try to use verifyTarget.sh [1] to verify the target platform, I get this:
[1] https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u...
{code}
[ERROR] Internal error: java.lang.ClassCastException: org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to org.eclipse.tycho.ReactorProject -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.ClassCastException: org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to org.eclipse.tycho.ReactorProject
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.ClassCastException: org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to org.eclipse.tycho.ReactorProject
at org.eclipse.tycho.core.osgitools.DefaultReactorProject.adapt(DefaultReactorProject.java:44)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:90)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
... 11 more
{code}
was (Author: nickboldt):
Curiously, when I apply the above PR for discovery and try to use verifyTarget.sh to verify the target platform, I get this:
{code}
[ERROR] Internal error: java.lang.ClassCastException: org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to org.eclipse.tycho.ReactorProject -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.ClassCastException: org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to org.eclipse.tycho.ReactorProject
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.ClassCastException: org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to org.eclipse.tycho.ReactorProject
at org.eclipse.tycho.core.osgitools.DefaultReactorProject.adapt(DefaultReactorProject.java:44)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:90)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
... 11 more
{code}
> Need better duplicate IU detection when validating target platforms
> -------------------------------------------------------------------
>
> Key: JBIDE-22673
> URL: https://issues.jboss.org/browse/JBIDE-22673
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, target-platform, upstream
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.4.1.AM2
>
>
> As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not.
> {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...?
> Or add a whitelist?{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22673:
------------------------------------
Meanwhile for both jbt and devstudio TPs, validation is successful and I still get the same list of dupe IUs:
{code}[WARNING] Found 8 duplicate jbosstools plugins:
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_13.0.0.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/javax.wsdl_1.5.1.v201012040544.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/javax.wsdl_1.6.2.v201012040545.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201005080400.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201209140446.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/javax.xml.soap_1.3.0.v201105210645.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/javax.xml.soap_1.2.0.v201005080501.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.axis_1.4.0.v201411182030.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.axis_1.4.0.v201005080400.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.0.4.v201101211617.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201005080502.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.1.0.v20160418-1457.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.100.v20160418-1457.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_4.0.0.v201302062210.jar
{code}
For jbtcentral TP, I get this:
{code}[WARNING] Found 2 duplicate jbtcentral plugins:
[WARNING] [1] jbtcentral-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201005080400.jar
[WARNING] [1] jbtcentral-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201209140446.jar
[WARNING] [2] jbtcentral-multiple.target.repo/plugins/org.apache.commons.codec_1.6.0.v201305230611.jar
[WARNING] [2] jbtcentral-multiple.target.repo/plugins/org.apache.commons.codec_1.3.0.v201101211617.jar
{code}
> Need better duplicate IU detection when validating target platforms
> -------------------------------------------------------------------
>
> Key: JBIDE-22673
> URL: https://issues.jboss.org/browse/JBIDE-22673
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, target-platform, upstream
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.4.1.AM2
>
>
> As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not.
> {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...?
> Or add a whitelist?{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22673:
------------------------------------
Curiously, when I apply the above PR for discovery and try to use verifyTarget.sh to verify the target platform, I get this:
{code}
[ERROR] Internal error: java.lang.ClassCastException: org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to org.eclipse.tycho.ReactorProject -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.ClassCastException: org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to org.eclipse.tycho.ReactorProject
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.ClassCastException: org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to org.eclipse.tycho.ReactorProject
at org.eclipse.tycho.core.osgitools.DefaultReactorProject.adapt(DefaultReactorProject.java:44)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:90)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
... 11 more
{code}
> Need better duplicate IU detection when validating target platforms
> -------------------------------------------------------------------
>
> Key: JBIDE-22673
> URL: https://issues.jboss.org/browse/JBIDE-22673
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, target-platform, upstream
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.4.1.AM2
>
>
> As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not.
> {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...?
> Or add a whitelist?{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBTIS-801) JBTIS Target Platform - Neon - sync with 4.60.1.xxx
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-801?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-801.
----------------------------
Resolution: Done
TP update complete:
Hey -
An updated 4.4.0.Alpha1-SNAPSHOT JBTIS TP is available for Neon -
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Al...
This TP picks up JBT core 4.4.0.Final, the updated JBT core TP 4.60.1.AM1-SNAPSHOT and latest released neon bits. SwitchYard and Fuse Tooling
target platforms both build.
See Jira for details:
https://issues.jboss.org/browse/JBTIS-801
> JBTIS Target Platform - Neon - sync with 4.60.1.xxx
> ---------------------------------------------------
>
> Key: JBTIS-801
> URL: https://issues.jboss.org/browse/JBTIS-801
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.0.Alpha1-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.4.0.Alpha1-TP
>
>
> *Reason:* sync with 4.60.1.AM1-SNAPSHOT
> *Project page/sources:*
> *Version:* 4.4.0.Alpha1-SNAPSHOT
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* .DevstudioIS components
> *Include in JBDS:* Yes (DevstudioIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> < org.jboss.tools.community.project.examples [3.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.community.central [2.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.community.central.feature.feature.group [2.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.common.test [3.8.0.Final-v20160603-0250-B985]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.as.test.core [3.2.0.Final-v20160603-0300-B1005]
> < org.jboss.tools.common.base.test [3.8.0.Final-v20160603-0250-B985]
> < org.jboss.tools.project.examples [3.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.project.examples.cheatsheet [3.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.jmx.core.test [1.8.0.Final-v20160603-0300-B1005]
> < org.jboss.tools.project.examples.feature.feature.group [3.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.tests [3.7.0.Final-v20160603-0250-B985]
> < org.jboss.tools.community.central.feature.feature.jar [2.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.project.examples.feature.feature.jar [3.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.common [3.8.0.Final-v20160603-0250-B985]
> > org.jboss.tools.common.test [3.8.0.Final-v20160610-1533-B7]
> > org.jboss.tools.community.central.feature.feature.jar [2.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.community.central.feature.feature.group [2.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.project.examples.cheatsheet [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.project.examples.feature.feature.jar [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.common.base.test [3.8.0.Final-v20160610-1533-B7]
> > org.jboss.tools.community.central [2.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.jmx.core.test [1.8.0.Final-v20160614-2020-B9]
> > org.jboss.tools.community.project.examples [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.as.test.core [3.2.0.Final-v20160614-2020-B9]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.project.examples [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.tests [3.7.0.Final-v20160610-1533-B7]
> > org.jboss.tools.common [3.8.0.Final-v20160610-1533-B7]
> > org.jboss.tools.project.examples.feature.feature.group [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.1.0.Final-v20160613-2000-B8]
> === Summary ===
> file:///home/pleacu/git-clone/PR/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 16 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 16 unique IUs
> < org.eclipse.rse.dstore.feature.group [3.7.0.201505221634]
> < org.eclipse.rse.doc.user [3.4.100.201403101646]
> < org.jboss.tools.community.central.feature.feature.jar [2.1.0.Final-v20160603-0539-B896]
> < org.eclipse.rse.connectorservice.local [2.1.400.201403100950]
> < org.jboss.tools.as.test.core [3.2.0.Final-v20160603-0300-B1005]
> < org.eclipse.rse.services [3.3.0.201403100950]
> < org.jboss.tools.common [3.8.0.Final-v20160603-0250-B985]
> < org.eclipse.rse.subsystems.processes.dstore [2.1.400.201403100950]
> < org.eclipse.rse.useractions.feature.group [3.7.0.201505221634]
> < org.jboss.tools.project.examples.cheatsheet [3.1.0.Final-v20160603-0539-B896]
> < org.eclipse.dstore.core [3.4.0.201501311530]
> < org.eclipse.rse.dstore.feature.jar [3.7.0.201505221634]
> < org.eclipse.rse.core.feature.group [3.7.0.201505221634]
> < org.eclipse.rse.subsystems.terminals.ssh [1.0.200.201411271155]
> < org.eclipse.rse.importexport [1.2.300.201403100950]
> < org.eclipse.rse.processes.ui [3.0.400.201403100950]
> < org.eclipse.rse.subsystems.files.dstore [2.1.300.201403100950]
> < org.jboss.tools.tests [3.7.0.Final-v20160603-0250-B985]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.1.0.Final-v20160603-0539-B896]
> < org.eclipse.rse.connectorservice.ssh [2.1.300.201505220524]
> < org.eclipse.rse.core.feature.jar [3.7.0.201505221634]
> < org.eclipse.rse.telnet.feature.jar [3.7.0.201505221634]
> < org.jboss.tools.community.central.feature.feature.group [2.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.jmx.core.test [1.8.0.Final-v20160603-0300-B1005]
> < org.eclipse.rse.useractions.feature.jar [3.7.0.201505221634]
> < org.jboss.tools.project.examples.feature.feature.jar [3.1.0.Final-v20160603-0539-B896]
> < org.eclipse.rse.connectorservice.dstore [3.1.301.201403100950]
> < org.eclipse.dstore.extra [2.1.400.201403100950]
> < org.eclipse.rse.core [3.3.100.201407181907]
> < org.eclipse.rse.services.local [2.2.0.201502030655]
> < org.jboss.tools.project.examples [3.1.0.Final-v20160603-0539-B896]
> < org.eclipse.rse.subsystems.processes.core [3.1.300.201403100950]
> < org.eclipse.rse.ftp.feature.group [3.7.0.201505221634]
> < org.eclipse.rse.ftp.feature.jar [3.7.0.201505221634]
> < org.jboss.tools.project.examples.feature.feature.group [3.1.0.Final-v20160603-0539-B896]
> < org.eclipse.rse.feature.group [3.7.0.201505221634]
> < org.eclipse.rse [3.5.0.201403100950]
> < org.eclipse.rse.ui [3.3.100.201503112018]
> < org.eclipse.rse.subsystems.files.core [3.3.1.201403100950]
> < org.eclipse.rse.files.ui [3.2.200.201502052140]
> < org.eclipse.rse.subsystems.shells.local [2.1.400.201403100950]
> < org.eclipse.rse.subsystems.shells.dstore [2.1.400.201403100950]
> < org.jboss.tools.community.project.examples [3.1.0.Final-v20160603-0539-B896]
> < org.eclipse.rse.subsystems.shells.telnet [1.2.300.201403100950]
> < org.eclipse.rse.telnet.feature.group [3.7.0.201505221634]
> < org.eclipse.rse.subsystems.processes.shell.linux [1.1.400.201403100950]
> < org.eclipse.rse.subsystems.files.local [2.1.300.201403251512]
> < org.eclipse.rse.terminals.feature.jar [3.8.0.201505221634]
> < org.eclipse.rse.subsystems.shells.ssh [2.1.400.201403100950]
> < org.eclipse.rse.dstore.security [3.0.400.201403100950]
> < org.eclipse.rse.subsystems.files.ftp [2.2.0.201403100950]
> < org.eclipse.rse.local.feature.group [3.7.0.201505221634]
> < org.eclipse.rse.ssh.feature.group [3.7.0.201505221634]
> < org.eclipse.rse.subsystems.files.ssh [2.1.300.201403100950]
> < org.eclipse.rse.terminals.ui [1.3.0.201504210807]
> < org.eclipse.rse.services.files.ftp [3.0.500.201403100950]
> < org.eclipse.rse.subsystems.processes.local [2.1.400.201403100950]
> < org.eclipse.rse.subsystems.terminals.core [1.0.300.201411271155]
> < org.eclipse.rse.feature.jar [3.7.0.201505221634]
> < org.eclipse.rse.local.feature.jar [3.7.0.201505221634]
> < org.eclipse.rse.shells.ui [3.0.500.201403271554]
> < org.jboss.tools.common.test [3.8.0.Final-v20160603-0250-B985]
> < org.eclipse.rse.useractions [1.1.500.201403100950]
> < org.jboss.tools.community.central [2.1.0.Final-v20160603-0539-B896]
> < org.eclipse.rse.services.ssh [3.2.100.201403281521]
> < org.eclipse.rse.terminals.feature.group [3.8.0.201505221634]
> < org.eclipse.rse.connectorservice.telnet [1.2.300.201505220524]
> < org.apache.commons.net [3.2.0.v201305141515]
> < org.eclipse.rse.services.telnet [2.0.400.201403100950]
> < org.eclipse.rse.ssh.feature.jar [3.7.0.201505221634]
> < org.eclipse.rse.efs.ui [2.1.400.201403100950]
> < org.eclipse.rse.efs [2.1.401.201503171741]
> < org.eclipse.rse.services.dstore [3.3.0.201406041609]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.1.0.Final-v20160603-0539-B896]
> < org.jboss.tools.common.base.test [3.8.0.Final-v20160603-0250-B985]
> < org.eclipse.rse.subsystems.shells.core [3.1.300.201403271554]
> > org.jboss.tools.tests [3.7.0.Final-v20160610-1533-B7]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.common.test [3.8.0.Final-v20160610-1533-B7]
> > org.jboss.tools.community.project.examples [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.project.examples [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.common [3.8.0.Final-v20160610-1533-B7]
> > org.jboss.tools.project.examples.cheatsheet [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.project.examples.feature.feature.jar [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.common.base.test [3.8.0.Final-v20160610-1533-B7]
> > org.jboss.tools.jmx.core.test [1.8.0.Final-v20160614-2020-B9]
> > org.jboss.tools.as.test.core [3.2.0.Final-v20160614-2020-B9]
> > org.jboss.tools.community.central.feature.feature.group [2.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.project.examples.feature.feature.group [3.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.community.central [2.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.community.central.feature.feature.jar [2.1.0.Final-v20160613-2000-B8]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.1.0.Final-v20160613-2000-B8]
> === Summary ===
> file:///home/pleacu/git-clone/PR/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 76 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 16 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22696) jbosstools and devstudio sites / installer use old timestamps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22696:
------------------------------------
{quote}[10:00 AM] Marián Labuda: it is a bit missleading if whole product has older bit ID (timestamp) than included plugins
[10:01 AM] Nick Boldt: right, which is why we reverted from jgit timestamp to "current date" timestamp for the product's update site and installer
[10:01 AM] Nick Boldt: question is now: should we also use current date for the branding plugin of the product, too?
[10:01 AM] Nick Boldt: sounds like you're arguing for "yes, we should"
[10:02 AM] Nick Boldt: I'm inclined to agree but wanted input from [~akazakov]{quote}
> jbosstools and devstudio sites / installer use old timestamps
> -------------------------------------------------------------
>
> Key: JBIDE-22696
> URL: https://issues.jboss.org/browse/JBIDE-22696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.1.AM2
>
> Attachments: devstudio10.01.png, jbt441.png
>
>
> Build id of devstudio installers contains old timestamp. E.g. latest build 2016-07-05_17-10-13-B5634 contains timestamp 20160613-2041 although the build which is producing bits is 20160705-5634.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22696) jbosstools and devstudio sites / installer use old timestamps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22696:
------------------------------------
>From a recent devstudio build log:
{code}
[INFO] --- maven-antrun-plugin:1.3:run (process-about-mapping) @ com.jboss.devstudio.core ---
[INFO] Executing tasks
[copy] Copying 1 file to /mnt/hudson_workspace/workspace/devstudio.product_master/sources/product/plugins/com.jboss.devstudio.core
[echo] product.releaseNumber = 10.0.1.AM1
[echo] buildQualifier = v20160613-2041
[echo] product.buildTimeStamp = ${product.buildTimeStamp}
{code}
Code for this is in https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co...
Build id is most likely coming from this plugin, com.jboss.devstudio.core, which has not been updated since 20160613-2041, so this is arguably correct.
Build date appears to be missing (regex match is failing to derive it from the plugin version) -- so we need that fixed.
But should that be the current date (eg., 20160708), or the last mod date of the repo, 20160613-2041 ?
[~akazakov] what do you think? Should the branding plugin use jgit timestamp, or the current timestamp, to align with the version of the installer jar?
> jbosstools and devstudio sites / installer use old timestamps
> -------------------------------------------------------------
>
> Key: JBIDE-22696
> URL: https://issues.jboss.org/browse/JBIDE-22696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.1.AM2
>
> Attachments: devstudio10.01.png, jbt441.png
>
>
> Build id of devstudio installers contains old timestamp. E.g. latest build 2016-07-05_17-10-13-B5634 contains timestamp 20160613-2041 although the build which is producing bits is 20160705-5634.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months