[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 edited comment on JBIDE-22696 at 7/7/16 12:04 PM:
-------------------------------------------------------------
With this PR [1] applied, I get the following artifacts produced:
[1] https://github.com/jbdevstudio/jbdevstudio-product/pull/388/files?w=1
{code}
$➔ ll site/target/*.zip*
-rw-rw-r-- 1 nboldt nboldt 557M Jul 7 11:23 site/target/com.jboss.devstudio.core.site-10.0.1-SNAPSHOT.zip
-rw-rw-r-- 1 nboldt nboldt 223M Jul 7 11:24 site/target/devstudio-10.0.1.AM1-src.zip
-rw-rw-r-- 1 nboldt nboldt 64 Jul 7 11:24 site/target/com.jboss.devstudio.core.site-10.0.1-SNAPSHOT.zip.sha256
-rw-rw-r-- 1 nboldt nboldt 64 Jul 7 11:24 site/target/devstudio-10.0.1.AM1-src.zip.sha256
$➔ ll installer/target/*.jar*
-rw-rw-r-- 1 nboldt nboldt 535M Jul 7 11:28 installer/target/devstudio-10.0.1.AM1-v20160613-2041-installer-standalone.jar
-rw-rw-r-- 1 nboldt nboldt 64 Jul 7 11:29 installer/target/devstudio-10.0.1.AM1-v20160613-2041-installer-standalone.jar.sha256
{code}
Resulting update site looks like this:
!devstudio10.01.png|thumbnail!
So, the html is correctly named. While the installer jars still have *v20160613-2041* in their name, they at least have the AM1 prefix now. Is that better? Not sure why the timestamp isn't changing to 20160707.
was (Author: nickboldt):
With this PR [1] applied, I get the following artifacts produced:
[1] https://github.com/jbdevstudio/jbdevstudio-product/pull/388/files?w=1
{code}
$➔ ll site/target/*.zip*
-rw-rw-r-- 1 nboldt nboldt 557M Jul 7 11:23 site/target/com.jboss.devstudio.core.site-10.0.1-SNAPSHOT.zip
-rw-rw-r-- 1 nboldt nboldt 223M Jul 7 11:24 site/target/devstudio-10.0.1.AM1-src.zip
-rw-rw-r-- 1 nboldt nboldt 64 Jul 7 11:24 site/target/com.jboss.devstudio.core.site-10.0.1-SNAPSHOT.zip.sha256
-rw-rw-r-- 1 nboldt nboldt 64 Jul 7 11:24 site/target/devstudio-10.0.1.AM1-src.zip.sha256
$➔ ll installer/target/*.jar*
-rw-rw-r-- 1 nboldt nboldt 535M Jul 7 11:28 installer/target/devstudio-10.0.1.AM1-v20160613-2041-installer-standalone.jar
-rw-rw-r-- 1 nboldt nboldt 64 Jul 7 11:29 installer/target/devstudio-10.0.1.AM1-v20160613-2041-installer-standalone.jar.sha256
{code}
Resulting update site looks like this:
!devstudio10.01.png|thumbnail!
> 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-22673) Need better duplicate IU detection when validating target platforms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-22673:
----------------------------------------
[~nickboldt] Note that once the patch is Tycho is merged and we start consuming it and enable the checkProvisioning=true, the install tests that we usually do after TP build will become useless as the errors of conflicting or uninstallable IUs should all be checked while validating the multiple TP. We can keep the extra-checks that are currently in, but if we want to speed up the feedback loop for TP, we can also imagine dropping them.
> 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-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 updated JBIDE-22696:
-------------------------------
Attachment: devstudio10.01.png
With this PR [1] applied, I get the following artifacts produced:
[1] https://github.com/jbdevstudio/jbdevstudio-product/pull/388/files?w=1
{code}
$➔ ll site/target/*.zip*
-rw-rw-r-- 1 nboldt nboldt 557M Jul 7 11:23 site/target/com.jboss.devstudio.core.site-10.0.1-SNAPSHOT.zip
-rw-rw-r-- 1 nboldt nboldt 223M Jul 7 11:24 site/target/devstudio-10.0.1.AM1-src.zip
-rw-rw-r-- 1 nboldt nboldt 64 Jul 7 11:24 site/target/com.jboss.devstudio.core.site-10.0.1-SNAPSHOT.zip.sha256
-rw-rw-r-- 1 nboldt nboldt 64 Jul 7 11:24 site/target/devstudio-10.0.1.AM1-src.zip.sha256
$➔ ll installer/target/*.jar*
-rw-rw-r-- 1 nboldt nboldt 535M Jul 7 11:28 installer/target/devstudio-10.0.1.AM1-v20160613-2041-installer-standalone.jar
-rw-rw-r-- 1 nboldt nboldt 64 Jul 7 11:29 installer/target/devstudio-10.0.1.AM1-v20160613-2041-installer-standalone.jar.sha256
{code}
Resulting update site looks like this:
!devstudio10.01.png|thumbnail!
> 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
>
>
> 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-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:
------------------------------------
With recent fixes to TP ( https://github.com/jbosstools/jbosstools-target-platforms/pull/224 ), you shouldn't see the above mylyn conflict anymore.
Here's the updated list of duplicate IUs in the TP. Unclear if we actually require all these dupes. If we do, we need some sort of whitelist capability; if we don't, then we should remove the dupes and retain only the latest (?).
{code}
[WARNING] Found 8 duplicate jbdevstudio plugins:
[WARNING] [1] jbdevstudio-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [1] jbdevstudio-multiple.target.repo/plugins/com.google.guava_13.0.0.jar
[WARNING] [2] jbdevstudio-multiple.target.repo/plugins/javax.wsdl_1.5.1.v201012040544.jar
[WARNING] [2] jbdevstudio-multiple.target.repo/plugins/javax.wsdl_1.6.2.v201012040545.jar
[WARNING] [3] jbdevstudio-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201005080400.jar
[WARNING] [3] jbdevstudio-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201209140446.jar
[WARNING] [4] jbdevstudio-multiple.target.repo/plugins/javax.xml.soap_1.3.0.v201105210645.jar
[WARNING] [4] jbdevstudio-multiple.target.repo/plugins/javax.xml.soap_1.2.0.v201005080501.jar
[WARNING] [5] jbdevstudio-multiple.target.repo/plugins/org.apache.axis_1.4.0.v201411182030.jar
[WARNING] [5] jbdevstudio-multiple.target.repo/plugins/org.apache.axis_1.4.0.v201005080400.jar
[WARNING] [6] jbdevstudio-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
[WARNING] [6] jbdevstudio-multiple.target.repo/plugins/org.apache.commons.logging_1.0.4.v201101211617.jar
[WARNING] [6] jbdevstudio-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201005080502.jar
[WARNING] [7] jbdevstudio-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.1.0.v20160418-1457.jar
[WARNING] [7] jbdevstudio-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.100.v20160418-1457.jar
[WARNING] [8] jbdevstudio-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [8] jbdevstudio-multiple.target.repo/plugins/org.objectweb.asm_4.0.0.v201302062210.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-22633) jbosstools-multiple.target has multiple incompatible IUs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22633?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22633:
------------------------------------
PR merged and building.
Here's the updated list of dupe IUs in the TP. Unclear if we actually require all these dupes.
{code}
[WARNING] Found 8 duplicate jbdevstudio plugins:
[WARNING] [1] jbdevstudio-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [1] jbdevstudio-multiple.target.repo/plugins/com.google.guava_13.0.0.jar
[WARNING] [2] jbdevstudio-multiple.target.repo/plugins/javax.wsdl_1.5.1.v201012040544.jar
[WARNING] [2] jbdevstudio-multiple.target.repo/plugins/javax.wsdl_1.6.2.v201012040545.jar
[WARNING] [3] jbdevstudio-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201005080400.jar
[WARNING] [3] jbdevstudio-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201209140446.jar
[WARNING] [4] jbdevstudio-multiple.target.repo/plugins/javax.xml.soap_1.3.0.v201105210645.jar
[WARNING] [4] jbdevstudio-multiple.target.repo/plugins/javax.xml.soap_1.2.0.v201005080501.jar
[WARNING] [5] jbdevstudio-multiple.target.repo/plugins/org.apache.axis_1.4.0.v201411182030.jar
[WARNING] [5] jbdevstudio-multiple.target.repo/plugins/org.apache.axis_1.4.0.v201005080400.jar
[WARNING] [6] jbdevstudio-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
[WARNING] [6] jbdevstudio-multiple.target.repo/plugins/org.apache.commons.logging_1.0.4.v201101211617.jar
[WARNING] [6] jbdevstudio-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201005080502.jar
[WARNING] [7] jbdevstudio-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.1.0.v20160418-1457.jar
[WARNING] [7] jbdevstudio-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.100.v20160418-1457.jar
[WARNING] [8] jbdevstudio-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [8] jbdevstudio-multiple.target.repo/plugins/org.objectweb.asm_4.0.0.v201302062210.jar
{code}
> jbosstools-multiple.target has multiple incompatible IUs
> --------------------------------------------------------
>
> Key: JBIDE-22633
> URL: https://issues.jboss.org/browse/JBIDE-22633
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.1.AM1
>
>
> Please correct the jbosstools-multiple.target to avoid the duplication of the IU as this is causing build failures in both SwitchYard and Fuse Tooling (development).
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
> org.eclipse.egit.ui.smartimport is defined twice with two different versions:
> {code}
> [ERROR] Resolution failed:
> [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2
> [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r
> [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22697) Javaee build contains untracked files, which need to be added to .gitignore to use jgit timestamps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22697?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22697:
------------------------------------
Purging the workspace has given us a blue ball again, but the above PR could still be applied if you wanted.
> Javaee build contains untracked files, which need to be added to .gitignore to use jgit timestamps
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22697
> URL: https://issues.jboss.org/browse/JBIDE-22697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.4.1.AM1
> Reporter: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
>
> Problem when building JavaEE since migration to jgit timestamps (JBIDE-13671):
> {code}
> 15:36:03 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.25.0:build-qualifier (default-build-qualifier) on project org.jboss.tools.batch.core.itest: Working tree is dirty.
> 15:36:03 [ERROR] git status batch/itests/org.jboss.tools.batch.core.itest:
> 15:36:03 [ERROR]
> 15:36:03 [ERROR] Untracked files:
> 15:36:03 [ERROR] batch/itests/org.jboss.tools.batch.core.itest/projects/TestProject/lib/javax.inject-1.jar
> 15:36:03 [ERROR] batch/itests/org.jboss.tools.batch.core.itest/projects/TestProject/lib/javax.batch-api-1.0.jar
> 15:36:03 [ERROR]
> 15:36:03 [ERROR] You are trying to use tycho-buildtimestamp-jgit on a directory that has uncommitted changes (see details above).
> 15:36:03 [ERROR] Either commit all changes/add files to .gitignore, or enable fallback to default timestamp provider by configuring
> 15:36:03 [ERROR] jgit.dirtyWorkingTree=warning for tycho-packaging-plugin
> {code}
> Solution:
> *add files generated as part of the build to .gitignore*
> This has been failing for a week. Does no one see the Jenkins emails anymore? :(
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22697) Javaee build contains untracked files, which need to be added to .gitignore to use jgit timestamps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22697?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-22697:
----------------------------------
Assignee: Alexey Kazakov
> Javaee build contains untracked files, which need to be added to .gitignore to use jgit timestamps
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22697
> URL: https://issues.jboss.org/browse/JBIDE-22697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.4.1.AM1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
>
> Problem when building JavaEE since migration to jgit timestamps (JBIDE-13671):
> {code}
> 15:36:03 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.25.0:build-qualifier (default-build-qualifier) on project org.jboss.tools.batch.core.itest: Working tree is dirty.
> 15:36:03 [ERROR] git status batch/itests/org.jboss.tools.batch.core.itest:
> 15:36:03 [ERROR]
> 15:36:03 [ERROR] Untracked files:
> 15:36:03 [ERROR] batch/itests/org.jboss.tools.batch.core.itest/projects/TestProject/lib/javax.inject-1.jar
> 15:36:03 [ERROR] batch/itests/org.jboss.tools.batch.core.itest/projects/TestProject/lib/javax.batch-api-1.0.jar
> 15:36:03 [ERROR]
> 15:36:03 [ERROR] You are trying to use tycho-buildtimestamp-jgit on a directory that has uncommitted changes (see details above).
> 15:36:03 [ERROR] Either commit all changes/add files to .gitignore, or enable fallback to default timestamp provider by configuring
> 15:36:03 [ERROR] jgit.dirtyWorkingTree=warning for tycho-packaging-plugin
> {code}
> Solution:
> *add files generated as part of the build to .gitignore*
> This has been failing for a week. Does no one see the Jenkins emails anymore? :(
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months