[JBoss JIRA] (JBDS-4349) Installer ignores Hyper-v
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4349?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-4349:
-----------------------------------
Yes, I've done the obligatory double reboot after enabling Hyper-v.
And this is what systeminfo returns: [^info]
> Installer ignores Hyper-v
> -------------------------
>
> Key: JBDS-4349
> URL: https://issues.jboss.org/browse/JBDS-4349
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.4.0.AM2
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Attachments: info
>
>
> I have enabled Hyper-v. On confirmation page, Hyper-v is not present, instead it still offers to install Virtualbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24219) Installation of JBoss Fuse Tools results in conflicting dependency while installing from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24219?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24219:
------------------------------------
I was able to reproduce this problem a different way:
{quote}
1. Install eclipse-jee-neon-3-linux-gtk-x86_64.tar.gz
2. Install all plugins from JBT through "Install New Software" from http://download.jboss.org/jbosstools/neon/staging/updates/
3. Open RH Central -> Software/Update and install everything (but most importantly, JBoss Fuse Development)
4. Preferences -> Maven -> Discovery -> Open Catalog and install Tycho Configurator{quote}
So... this means Fuse Tools prevents users from using Tycho based builds at the same time (?) . Not good.
> Installation of JBoss Fuse Tools results in conflicting dependency while installing from Central
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24219
> URL: https://issues.jboss.org/browse/JBIDE-24219
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central-update, maven
> Affects Versions: 4.4.4.AM2
> Environment: Eclipse JEE-NEON based on neon.3
> JBT 4.4.4.AM2
> Reporter: Ondrej Dockal
> Priority: Critical
> Attachments: docker_reddeer.zip
>
>
> We have got a conflicting dependency during installation of Fuse Tooling:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Fuse Tooling Apache Camel Editor 9.1.0.Final-v20170214-0902-B104 (org.fusesource.ide.camel.editor.feature.feature.group 9.1.0.Final-v20170214-0902-B104)
> Software currently installed: Tycho Project Configurators 0.8.0.201409231215 (org.sonatype.tycho.m2e.feature.feature.group 0.8.0.201409231215)
> Only one of the following can be installed at once:
> Tycho Project Configurators 0.8.0.201409231215 (org.sonatype.tycho.m2e 0.8.0.201409231215)
> Tycho Project Configurators 0.9.0.201609061714 (org.sonatype.tycho.m2e 0.9.0.201609061714)
> Cannot satisfy dependency:
> From: JBoss Fuse Tooling Apache Camel Editor 9.1.0.Final-v20170214-0902-B104 (org.fusesource.ide.camel.editor.feature.feature.group 9.1.0.Final-v20170214-0902-B104)
> To: org.fusesource.ide.project [9.1.0.Final-v20170214-0902-B104]
> Cannot satisfy dependency:
> From: Fuse Project Plugin 9.1.0.Final-v20170214-0902-B104 (org.fusesource.ide.project 9.1.0.Final-v20170214-0902-B104)
> To: bundle org.sonatype.tycho.m2e 0.9.0
> Cannot satisfy dependency:
> From: Tycho Project Configurators 0.8.0.201409231215 (org.sonatype.tycho.m2e.feature.feature.group 0.8.0.201409231215)
> To: org.sonatype.tycho.m2e [0.8.0.201409231215]
> {code}
> We have found out that m2e discovery catalog ([url|http://download.eclipse.org/technology/m2e/discovery/directory-1.7.xml], that is usually used when we import integration tests plugins into IDE, is installing org.sonatype.tycho.m2e.feature.feature.group 0.8.0.201409231215 feature. This version is in conflict with the one that Fuse Tooling uses as its target platform ([here|http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4...] - org.sonatype.tycho.m2e_0.9.0.201609061714.jar).
> [~apodhrad] You might want to take a look here, I am not sure if we need to update (report to upstream) discovery catalog url to use newer version of tycho configurator ([here|http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-tycho/] - 0.9.0).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24022) test failures in base: org.jboss.tools.common.test.CommonAllTests
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24022?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24022:
------------------------------------
Checking in again a month later... build #1 completed and was green.
Kicked again... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> test failures in base: org.jboss.tools.common.test.CommonAllTests
> -----------------------------------------------------------------
>
> Key: JBIDE-24022
> URL: https://issues.jboss.org/browse/JBIDE-24022
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common, foundation
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM1
>
>
> Some failing tests:
> {code}
> 02:31:17 testGetEnvironment(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0.111 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.eclipse.swt.internal.Library.loadLibrary(Library.java:327)
> 02:31:17 at org.eclipse.swt.internal.Library.loadLibrary(Library.java:236)
> 02:31:17 at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:34)
> 02:31:17 at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:118)
> 02:31:17 at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:80)
> 02:31:17 at org.eclipse.swt.widgets.Display.<clinit>(Display.java:140)
> 02:31:17 at org.jboss.tools.common.CommonPlugin.start(CommonPlugin.java:45)
> 02:31:17 at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
> 02:31:17 at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> 02:31:17 at java.security.AccessController.doPrivileged(Native Method)
> 02:31:17 at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
> 02:31:17 at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
> 02:31:17 at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:933)
> 02:31:17 at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
> 02:31:17 at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> 02:31:17 at org.eclipse.osgi.container.Module.start(Module.java:449)
> 02:31:17 at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468)
> 02:31:17 at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:103)
> 02:31:17 at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
> 02:31:17 at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:359)
> 02:31:17 at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:433)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:386)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:378)
> 02:31:17 at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> 02:31:17 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testGetEnvironment(CommonPluginTest.java:34)
> 02:31:17
> 02:31:17 testLogInfoString(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testLogInfoString(CommonPluginTest.java:104)
> 02:31:17
> 02:31:17 testLogErrorString(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testLogErrorString(CommonPluginTest.java:62)
> 02:31:17
> 02:31:17 testLogInfoStringThrowable(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0.001 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testLogInfoStringThrowable(CommonPluginTest.java:97)
> 02:31:17
> 02:31:17 testGetPluginLog(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testGetPluginLog(CommonPluginTest.java:48)
> 02:31:17
> 02:31:17 testLogErrorStringThrowable(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0.001 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testLogErrorStringThrowable(CommonPluginTest.java:55)
> 02:31:17
> 02:31:17 testLogWarningStringThrowable(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testLogWarningStringThrowable(CommonPluginTest.java:76)
> 02:31:17
> 02:31:17 testLogWarningString(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testLogWarningString(CommonPluginTest.java:83)
> 02:31:17
> 02:31:17 testLogWarningThrowable(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testLogWarningThrowable(CommonPluginTest.java:90)
> 02:31:17
> 02:31:17 testGetDefault(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testGetDefault(CommonPluginTest.java:41)
> 02:31:17
> 02:31:17 testGetInstance(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testGetInstance(CommonPluginTest.java:27)
> 02:31:17
> 02:31:17 testLogErrorThrowable(org.jboss.tools.common.test.CommonPluginTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/CommonPlugin
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testLogErrorThrowable(CommonPluginTest.java:69)
> 02:31:17 {code}
> More:
> {code}
> 02:31:17 testMessagesInitialization(org.jboss.tools.common.test.MessagesTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/Messages
> 02:31:17 at org.jboss.tools.common.test.MessagesTest.testMessagesInitialization(MessagesTest.java:19)
> 02:31:17 Caused by: java.lang.ClassNotFoundException: An error occurred while automatically activating bundle org.jboss.tools.common (202).
> 02:31:17 at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:112)
> 02:31:17 at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
> 02:31:17 at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:359)
> 02:31:17 at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:433)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:386)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:378)
> 02:31:17 at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> 02:31:17 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testGetEnvironment(CommonPluginTest.java:34){code}
> More:
> {code}
> 02:31:17 testMethodNotImplementedExceptionString(org.jboss.tools.common.test.MethodNotImplementedExceptionTest) Time elapsed: 0 sec <<< ERROR!
> 02:31:17 java.lang.NoClassDefFoundError: org/jboss/tools/common/MethodNotImplementedException
> 02:31:17 at org.jboss.tools.common.test.MethodNotImplementedExceptionTest.testMethodNotImplementedExceptionString(MethodNotImplementedExceptionTest.java:37)
> 02:31:17 Caused by: java.lang.ClassNotFoundException: An error occurred while automatically activating bundle org.jboss.tools.common (202).
> 02:31:17 at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:112)
> 02:31:17 at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
> 02:31:17 at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:359)
> 02:31:17 at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:433)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:386)
> 02:31:17 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:378)
> 02:31:17 at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> 02:31:17 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> 02:31:17 at org.jboss.tools.common.test.CommonPluginTest.testGetEnvironment(CommonPluginTest.java:34){code}
> Seems the problem is caused by this:
> {code}
> 02:31:17 Caused by: org.osgi.framework.BundleException:
> Exception in org.jboss.tools.common.CommonPlugin.start()
> of bundle org.jboss.tools.common.
> {code}
> and this:
> {code}
> 02:31:17 Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
> 02:31:17 /mnt/hudson_workspace/workspace/jbosstools-base_master/sources/common/tests/org.jboss.tools.common.test/target/work/configuration/org.eclipse.osgi/215/0/.cp/libswt-pi-gtk-4735.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /mnt/hudson_workspace/workspace/jbosstools-base_master/sources/common/tests/org.jboss.tools.common.test/target/work/configuration/org.eclipse.osgi/215/0/.cp/libswt-pi-gtk-4735.so)
> 02:31:17 no swt-pi-gtk in java.library.path
> 02:31:17 /qa/services/hudson/.swt/lib/linux/x86_64/libswt-pi-gtk-4735.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /qa/services/hudson/.swt/lib/linux/x86_64/libswt-pi-gtk-4735.so)
> 02:31:17 Can't load library: /home/hudson/.swt/lib/linux/x86_64/libswt-pi-gtk.so{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24225) publish p2diff app to Nexus for easier use in jenkins jobs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24225?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24225:
-------------------------------
Description:
Rather than bootstrapping by hand and having to reference p2diff like this:
{code}
p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
{code}
It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) ...
!maven-releng-fetch.png|thumbnail!
... and automatically unpack it to the workspace.
was:
Rather than bootstrapping by hand and having to reference p2diff like this:
{code}
p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
{code}
It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) and automatically unpack it to the workspace.
> publish p2diff app to Nexus for easier use in jenkins jobs
> ----------------------------------------------------------
>
> Key: JBIDE-24225
> URL: https://issues.jboss.org/browse/JBIDE-24225
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM3
>
> Attachments: maven-releng-fetch.png
>
>
> Rather than bootstrapping by hand and having to reference p2diff like this:
> {code}
> p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
> {code}
> It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) ...
> !maven-releng-fetch.png|thumbnail!
> ... and automatically unpack it to the workspace.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24225) publish p2diff app to Nexus for easier use in jenkins jobs
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-24225:
----------------------------------
Summary: publish p2diff app to Nexus for easier use in jenkins jobs
Key: JBIDE-24225
URL: https://issues.jboss.org/browse/JBIDE-24225
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.4.AM2
Reporter: Nick Boldt
Attachments: maven-releng-fetch.png
Rather than bootstrapping by hand and having to reference p2diff like this:
{code}
p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
{code}
It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) and automatically unpack it to the workspace.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24225) publish p2diff app to Nexus for easier use in jenkins jobs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24225?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24225:
-------------------------------
Attachment: maven-releng-fetch.png
> publish p2diff app to Nexus for easier use in jenkins jobs
> ----------------------------------------------------------
>
> Key: JBIDE-24225
> URL: https://issues.jboss.org/browse/JBIDE-24225
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM3
>
> Attachments: maven-releng-fetch.png
>
>
> Rather than bootstrapping by hand and having to reference p2diff like this:
> {code}
> p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
> {code}
> It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) and automatically unpack it to the workspace.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24225) publish p2diff app to Nexus for easier use in jenkins jobs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24225?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-24225:
----------------------------------
Assignee: Nick Boldt
> publish p2diff app to Nexus for easier use in jenkins jobs
> ----------------------------------------------------------
>
> Key: JBIDE-24225
> URL: https://issues.jboss.org/browse/JBIDE-24225
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM3
>
> Attachments: maven-releng-fetch.png
>
>
> Rather than bootstrapping by hand and having to reference p2diff like this:
> {code}
> p2diff=/home/hudson/static_build_env/jbds/p2diff/x86$(if [[ $(uname -a | grep x86_64) ]]; then echo _64; fi)/p2diff
> {code}
> It would be way better if we could just fetch it via a maven step (as we do for other releng scripts) and automatically unpack it to the workspace.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years