[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Arnie Morein (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Arnie Morein commented on JBIDE-25923:
--------------------------------------
I just downloaded WF 12.0.0.Final and noticed that the server starts re-deploying all standalone configurations over and over.
This is a clean unzip of the version, no customizations or reconfigurations.
{{19:01:37,797 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 12.0.0.Final (WildFly Core 4.0.0.Final) started in 5877ms - Started 292 of 513 services (308 services are lazy, passive or on-demand)
19:01:38,840 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory /Users/acm/dev/jboss/wildfly-12.0.0.Final/standalone
19:01:39,036 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /Users/acm/dev/jboss/wildfly-12.0.0.Final/standalone/data/content/80/6f9c9b1378d16142bcc678621f22a45d2f00fd/content
19:01:39,043 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /Users/acm/dev/jboss/wildfly-12.0.0.Final/standalone/data/content/c9/4293666ebba61afaa24b98957b4b8389366080/content
19:01:39,046 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /Users/acm/dev/jboss/wildfly-12.0.0.Final/standalone/data/content/18/e7e6652b227daf6e37a002d5d93c138bd60a76/content
19:01:39,049 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /Users/acm/dev/jboss/wildfly-12.0.0.Final/standalone/data/content/26/07eeffe43cdf4dbff6f271be7c1ec591372a17/content
19:01:39,062 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /Users/acm/dev/jboss/wildfly-12.0.0.Final/standalone/data/content/03/6457ff5066ffdd7f3586beb297fdc3d453c7e1/content
19:01:39,067 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /Users/acm/dev/jboss/wildfly-12.0.0.Final/standalone/data/content/ac/0a03f32d1af994e976b1b31bd8d6bf38f1ff07/content
19:01:39,072 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /Users/acm/dev/jboss/wildfly-12.0.0.Final/standalone/data/content/4b/a81d7901ad5910632f4359cdb224e7a3d1200b/content
19:01:39,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
19:01:39,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone-full-ha.xml" (runtime-name: "standalone-full-ha.xml")
19:01:39,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "standalone-ee8.xml" (runtime-name: "standalone-ee8.xml")
19:01:39,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.initial.xml" (runtime-name: "standalone.initial.xml")
19:01:39,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone.boot.xml" (runtime-name: "standalone.boot.xml")
19:01:39,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone-full.xml" (runtime-name: "standalone-full.xml")
19:01:39,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.v1.xml" (runtime-name: "standalone.v1.xml")
19:01:39,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone-ha.xml" (runtime-name: "standalone-ha.xml")
19:01:39,172 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
19:01:39,172 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone-load-balancer.xml" (runtime-name: "standalone-load-balancer.xml")
19:01:39,893 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Bastille' 9.1.6.Final
19:01:40,066 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 19) WFLYCLINF0002: Started client-mappings cache from ejb container
19:01:40,141 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
19:01:40,142 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-load-balancer.xml" (runtime-name : "standalone-load-balancer.xml")
19:01:40,142 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-ee8.xml" (runtime-name : "standalone-ee8.xml")
19:01:40,142 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-full.xml" (runtime-name : "standalone-full.xml")
19:01:40,142 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.boot.xml" (runtime-name : "standalone.boot.xml")
19:01:40,142 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
19:01:40,142 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
19:01:40,142 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.initial.xml" (runtime-name : "standalone.initial.xml")
19:01:40,142 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-ha.xml" (runtime-name : "standalone-ha.xml")
19:01:40,142 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-full-ha.xml" (runtime-name : "standalone-full-ha.xml")
19:01:45,242 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 32ms
19:01:45,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
}}
> Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-25923
> URL: https://issues.jboss.org/browse/JBIDE-25923
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.3.Final
> Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.6.0.AM1
>
> Attachments: ServerAdapterEAP.gif, ServerAdapterEAPRepaired.gif
>
>
> When there is specific maven project imported in Project explorer (jbosstools-openshift), Started EAP 7.1 server adapter is printing output where deployment scanner replaces deployment and redeploy over and over again, see part of log:
> {code}
> 15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
> 15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
> 15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml")
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms
> 15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25586:
-------------------------------------
[~jkopriva] I'm not able to replicate this.
Fedora 24, jdk-9.0.1, cdk-3.3.0-1-minishift-linux-amd64 using master jbosstools.
Can't replicate at all. Also I fail to see how this is a CDK-specific issue. Do connections to other openshift instances work in java9, but only connections to cdk-based ones don't? I'm confused as to why this would happen at all.
> OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
> ----------------------------------------------------------------
>
> Key: JBIDE-25586
> URL: https://issues.jboss.org/browse/JBIDE-25586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.2.Final
> Environment: FC27
> OpenJDK 9.0.1
> CDK v3.3.0-rc.1-1
> eclipse.buildId=11.2.0.GA-v20180115-0516-B1866
> java.version=9.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Priority: Critical
> Labels: cdk, connection
> Fix For: 4.6.0.AM2
>
>
> But, connecting to online openshift instance works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25971:
-------------------------------------
1) https://github.com/jbosstools/jbosstools-openshift/pull/1742 will provide a registration link.
2) I will not remvoe the domain composite. It's too difficult at this time and not worth the investment.
3) Renaming jboss.org credentials to red hat has already been done
3a) re signup url... we will see. Asking denis for the full URL and we'll see if he gets back to me.
> Add Red Hat Developers sign up link to CDK New Server wizard
> ------------------------------------------------------------
>
> Key: JBIDE-25971
> URL: https://issues.jboss.org/browse/JBIDE-25971
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: cdk_server_adapter_wizard
> Fix For: 4.6.x
>
> Attachments: new-server-cdk.png
>
>
> While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow.
> Imagine you don't have an account on developers.redhat.com yet.
> You go to New Server -> CDK 3.2+.
> On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome.
> So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials.
> That's issue 1.
> !new-server-cdk.png!
> There are also a few side issues:
> 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough.
> 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title?
> 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-24997) could org.jboss.tools.ws.jaxrs.core migrate to use lucene 7.1 instead of 3.5?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24997?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24997:
-------------------------------
Description:
According to p2, org.jboss.tools.ws.jaxrs.core depends on lucene 3.5. But the latest in Photon.0.My is 7.1. Could we move up to the latest?
was:
According to p2, org.jboss.tools.ws.jaxrs.core depends on lucene 3.5. But the latest in Oxygen is 6.1. Could we move up to the latest?
> could org.jboss.tools.ws.jaxrs.core migrate to use lucene 7.1 instead of 3.5?
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24997
> URL: https://issues.jboss.org/browse/JBIDE-24997
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.6.x
>
> Attachments: ws.jaxrs.core_lucene3.5.png
>
>
> According to p2, org.jboss.tools.ws.jaxrs.core depends on lucene 3.5. But the latest in Photon.0.My is 7.1. Could we move up to the latest?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-25597 at 5/17/18 2:40 PM:
-------------------------------------------------------------
With the latest changes to move to Photon.0.M7 today, here is the small list of duplicate IUs still in the TP for version 4.80.0.AM2-SNAPSHOT:
{code}[WARNING] Found 9 duplicate jbosstools plugins:
[1] com.google.guava_15.0.0.v201403281430.jar < required by org.eclipse.recommenders.injection
[1] com.google.guava_21.0.0.v20170206-1425.jar
[2] javax.wsdl_1.6.2.v201012040545.jar
[2] javax.wsdl_1.5.1.v201012040544.jar < ?
[3] org.apache.commons.codec_1.10.0.v20180409-1845.jar
[3] org.apache.commons.codec_1.9.0.v20170208-1614.jar
[4] org.apache.commons.logging_1.2.0.v20180409-1502.jar
[4] org.apache.commons.logging_1.1.1.v201101211721.jar < ?
[4] org.apache.commons.logging_1.0.4.v201101211617.jar < ?
[5] org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[5] org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar < org.eclipse.epp.logging.aeri.feature 2.0.7.v20170906-1327
[6] org.apache.lucene.core_3.5.0.v20120725-1805.jar < required by org.jboss.tools.ws.jaxrs.core
[6] org.apache.lucene.core_6.1.0.v20170814-1820.jar < org.eclipse.epp.logging.aeri.feature 2.0.7.v20170906-1327
[6] org.apache.lucene.core_7.1.0.v20171214-1510.jar
[7] org.hamcrest.core_1.3.0.v201303031735.jar < swtbot 2.5
[7] org.hamcrest.core_1.3.0.v20180420-1519.jar < ?
[8] org.objectweb.asm_6.1.1.v20180414-0329.jar
[8] org.objectweb.asm_5.0.1.v201404251740.jar < batch requires sapphire, which requires ASM 5
[9] org.slf4j.api_1.7.2.v20121108-1250.jar < ?
[9] org.slf4j.api_1.7.10.v20170428-1633.jar
{code}
Next up, moving to swtbot 2.6 and maybe removing some of the other dupe deps.
was (Author: nickboldt):
With the latest changes to move to Photon.0.M7 today [1], here is the small list of duplicate IUs still in the TP:
{code}[WARNING] Found 9 duplicate jbosstools plugins:
[1] com.google.guava_15.0.0.v201403281430.jar < required by org.eclipse.recommenders.injection
[1] com.google.guava_21.0.0.v20170206-1425.jar
[2] javax.wsdl_1.6.2.v201012040545.jar
[2] javax.wsdl_1.5.1.v201012040544.jar < ?
[3] org.apache.commons.codec_1.10.0.v20180409-1845.jar
[3] org.apache.commons.codec_1.9.0.v20170208-1614.jar
[4] org.apache.commons.logging_1.2.0.v20180409-1502.jar
[4] org.apache.commons.logging_1.1.1.v201101211721.jar < ?
[4] org.apache.commons.logging_1.0.4.v201101211617.jar < ?
[5] org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[5] org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar < org.eclipse.epp.logging.aeri.feature 2.0.7.v20170906-1327
[6] org.apache.lucene.core_3.5.0.v20120725-1805.jar < required by org.jboss.tools.ws.jaxrs.core
[6] org.apache.lucene.core_6.1.0.v20170814-1820.jar < org.eclipse.epp.logging.aeri.feature 2.0.7.v20170906-1327
[6] org.apache.lucene.core_7.1.0.v20171214-1510.jar
[7] org.hamcrest.core_1.3.0.v201303031735.jar < swtbot 2.5
[7] org.hamcrest.core_1.3.0.v20180420-1519.jar < ?
[8] org.objectweb.asm_6.1.1.v20180414-0329.jar
[8] org.objectweb.asm_5.0.1.v201404251740.jar < batch requires sapphire, which requires ASM 5
[9] org.slf4j.api_1.7.2.v20121108-1250.jar < ?
[9] org.slf4j.api_1.7.10.v20170428-1633.jar
{code}
> TP: create target platforms based on Eclipse Photon
> ---------------------------------------------------
>
> Key: JBIDE-25597
> URL: https://issues.jboss.org/browse/JBIDE-25597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: target-platform
> Fix For: 4.6.0.AM2, 4.6.0.AM3, 4.6.0.Final
>
> Attachments: base.log
>
>
> In order to start Photon based builds, we need a working Photon based target platform
> For sprint 148 / AM1: Photon.0.M6
> For sprint 149 / AM2: Photon.0.M7
> For sprint 150 / AM3: Photon.0.RC3
> For sprint 151 / GA: Photon.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-25597 at 5/17/18 2:30 PM:
-------------------------------------------------------------
With the latest changes to move to Photon.0.M7 today [1], here is the small list of duplicate IUs still in the TP:
{code}[WARNING] Found 9 duplicate jbosstools plugins:
[1] com.google.guava_15.0.0.v201403281430.jar < required by org.eclipse.recommenders.injection
[1] com.google.guava_21.0.0.v20170206-1425.jar
[2] javax.wsdl_1.6.2.v201012040545.jar
[2] javax.wsdl_1.5.1.v201012040544.jar < ?
[3] org.apache.commons.codec_1.10.0.v20180409-1845.jar
[3] org.apache.commons.codec_1.9.0.v20170208-1614.jar
[4] org.apache.commons.logging_1.2.0.v20180409-1502.jar
[4] org.apache.commons.logging_1.1.1.v201101211721.jar < ?
[4] org.apache.commons.logging_1.0.4.v201101211617.jar < ?
[5] org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[5] org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar < org.eclipse.epp.logging.aeri.feature 2.0.7.v20170906-1327
[6] org.apache.lucene.core_3.5.0.v20120725-1805.jar < required by org.jboss.tools.ws.jaxrs.core
[6] org.apache.lucene.core_6.1.0.v20170814-1820.jar < org.eclipse.epp.logging.aeri.feature 2.0.7.v20170906-1327
[6] org.apache.lucene.core_7.1.0.v20171214-1510.jar
[7] org.hamcrest.core_1.3.0.v201303031735.jar < swtbot 2.5
[7] org.hamcrest.core_1.3.0.v20180420-1519.jar < ?
[8] org.objectweb.asm_6.1.1.v20180414-0329.jar
[8] org.objectweb.asm_5.0.1.v201404251740.jar < batch requires sapphire, which requires ASM 5
[9] org.slf4j.api_1.7.2.v20121108-1250.jar < ?
[9] org.slf4j.api_1.7.10.v20170428-1633.jar
{code}
was (Author: nickboldt):
With the latest changes to move to Photon.0.M7 today [1], here is the small list of duplicate IUs still in the TP:
{code}[WARNING] Found 9 duplicate jbosstools plugins:
[1] com.google.guava_21.0.0.v20170206-1425.jar
[1] com.google.guava_15.0.0.v201403281430.jar
[2] javax.wsdl_1.6.2.v201012040545.jar
[2] javax.wsdl_1.5.1.v201012040544.jar
[3] org.apache.commons.codec_1.10.0.v20180409-1845.jar
[3] org.apache.commons.codec_1.9.0.v20170208-1614.jar
[4] org.apache.commons.logging_1.2.0.v20180409-1502.jar
[4] org.apache.commons.logging_1.1.1.v201101211721.jar
[4] org.apache.commons.logging_1.0.4.v201101211617.jar
[5] org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[5] org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar
[6] org.apache.lucene.core_6.1.0.v20170814-1820.jar
[6] org.apache.lucene.core_3.5.0.v20120725-1805.jar
[6] org.apache.lucene.core_7.1.0.v20171214-1510.jar
[7] org.hamcrest.core_1.3.0.v201303031735.jar
[7] org.hamcrest.core_1.3.0.v20180420-1519.jar
[8] org.objectweb.asm_6.1.1.v20180414-0329.jar
[8] org.objectweb.asm_5.0.1.v201404251740.jar
[9] org.slf4j.api_1.7.2.v20121108-1250.jar
[9] org.slf4j.api_1.7.10.v20170428-1633.jar
{code}
> TP: create target platforms based on Eclipse Photon
> ---------------------------------------------------
>
> Key: JBIDE-25597
> URL: https://issues.jboss.org/browse/JBIDE-25597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: target-platform
> Fix For: 4.6.0.AM2, 4.6.0.AM3, 4.6.0.Final
>
> Attachments: base.log
>
>
> In order to start Photon based builds, we need a working Photon based target platform
> For sprint 148 / AM1: Photon.0.M6
> For sprint 149 / AM2: Photon.0.M7
> For sprint 150 / AM3: Photon.0.RC3
> For sprint 151 / GA: Photon.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months