[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-19820:
------------------------------------------
with validation off
before fix
M6 - 431,451
M6+batch - 785,790
M6 + CDI - 649,683
after fix:
M7 - 451,463
M7+Batch - 610,602
M7+CDI - 605,573
> Batch feature makes wildfly import way slower
> ---------------------------------------------
>
> Key: JBIDE-19820
> URL: https://issues.jboss.org/browse/JBIDE-19820
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies.
> I did a 4 runs with following results:
> M6 was able to import WF 628,575,577,612 (in seconds) = average 598s
> M6 with batch feature: 843,832,924,877 (in seconds) = average 869s
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19900) Installing only V3 feature results is limited capability, need to know to install V2
by Steve Speicher (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19900?page=com.atlassian.jira.plugi... ]
Steve Speicher updated JBIDE-19900:
-----------------------------------
Attachment: Screen Shot 2015-05-29 at 5.11.03 PM.png
> Installing only V3 feature results is limited capability, need to know to install V2
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19900
> URL: https://issues.jboss.org/browse/JBIDE-19900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: eclipse.buildId=4.5.0.I20150522-2000
> org.jboss.tools.openshift.client (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active]
> org.jboss.tools.openshift.common.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active]
> org.jboss.tools.openshift.common.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift Common UI" [Active]
> org.jboss.tools.openshift.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active]
> org.jboss.tools.openshift.egit.core (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit Core" [Starting]
> org.jboss.tools.openshift.egit.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit UI" [Starting]
> org.jboss.tools.openshift.ui (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active]
> Reporter: Steve Speicher
> Attachments: Screen Shot 2015-05-29 at 5.11.03 PM.png
>
>
> If a user is interested in only V3, they are tempted to just install the V3 feature. The issue is that a number of things don't work, namely the "Create"/"New" paths.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-18772 at 6/2/15 9:06 AM:
----------------------------------------------------------------
Needs changes:
* devstudio.product : requires more specific steps, so pom has to be changed
* jbosstools-browsersim-standalone : doesn't match the generic deployment procedure, so its pom requires some customization
* jbosstools-discovery : requires more specific steps, as generic process isn't covering this case
* jbosstools-integration-stack-tests.aggregate : Needs adoption of a more recent parent pom +needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina] [~pleacu]
* jbosstools-integration-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. See suggested Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/990 .cc [~mmalina]
* RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before updating the job. cc [~mmalina]
Nothing to change:
* jbosstools-locus.site : Latest version only seems to be published and consumed only through Nexus (in all .target definition I've checked), so it's just a regular "mvn deploy", without any other publish step necessary (more like JBIDE-16128 ). Nothing to change on the job.
was (Author: mickael_istria):
Needs changes:
* devstudio.product : requires more specific steps, so pom has to be changed
* jbosstools-browsersim-standalone : doesn't match the generic deployment procedure, so its pom requires some customization
* jbosstools-discovery : requires more specific steps, as generic process isn't covering this case
* jbosstools-integration-stack-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina]
* jbosstools-integration-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. See suggested Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/990 .cc [~mmalina]
* RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before updating the job. cc [~mmalina]
Nothing to change:
* jbosstools-locus.site : Latest version only seems to be published and consumed only through Nexus (in all .target definition I've checked), so it's just a regular "mvn deploy", without any other publish step necessary (more like JBIDE-16128 ). Nothing to change on the job.
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBTIS-439) Add XMLBeans to TP
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-439?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-439:
----------------------------------
p2diff:
{code}
< org.eclipse.equinox.security [1.2.0.v20150223-1455]
< org.eclipse.equinox.simpleconfigurator.manipulator [2.0.0.v20150121-1551]
< org.eclipse.jdt.junit.core [3.7.300.v20141114-1947]
> org.apache.xmlbeans [2.3.0.v201405241900]
> org.eclipse.emf.ecore.feature.jar [2.11.0.v20150318-0449]
> org.eclipse.emf.codegen.ecore.ui [2.10.0.v20150323-0420]
> org.eclipse.emf.ecore [2.11.0.v20150318-0449]
> org.eclipse.emf.ecore.xmi [2.11.0.v20150318-0449]
> com.fasterxml.jackson.core.jackson-core [2.5.0.v201504151636]
> org.eclipse.emf.codegen.ecore.ui.feature.group [2.10.0.v20150323-0420]
> org.eclipse.emf.codegen.ecore.ui.feature.jar [2.10.0.v20150323-0420]
> org.eclipse.emf.ecore.feature.group [2.11.0.v20150318-0449]
> org.eclipse.emf.ecore.change [2.10.0.v20150318-0449]
> com.fasterxml.jackson.core.jackson-databind [2.5.0.v201504151636]
> com.fasterxml.jackson.core.jackson-annotations [2.5.0.v201504151636]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 3 unique IUs
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 12 unique IUs
< org.jboss.tools.as.test.core [3.1.0.Alpha2-v20150417-0145-B13]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 1 unique IUs
{code}
> Add XMLBeans to TP
> ------------------
>
> Key: JBTIS-439
> URL: https://issues.jboss.org/browse/JBTIS-439
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: Fuse IDE, target-platform
> Affects Versions: 4.3.0.Alpha1
> Reporter: Keith Babo
> Assignee: Paul Leacu
> Fix For: 4.3.0.Alpha2b-TP
>
>
> Fuse Data Transformation tooling relies on XMLBeans to generate an XML schema from an XML instance document in order to support the generation of model classes for XML source/target. We currently bundle xmlbeans inside the data transformation plugin within Fuse IDE.
> *Project page/sources:* http://xmlbeans.apache.org/
> *Version:* 2.6.0 (no hard requirement on this specific version that I know of)
> *License and owner:* ALv2
> *Original p2 repo:* unknown
> *JBoss mirror:* unknown
> *Include Sources:* Yes
> *Affected projects:* Fuse IDE
> *Include in JBDS:* unknown
> *Type of dependency:* unknown
> *non-p2 repository:* https://repo1.maven.org/maven2/org/apache/xmlbeans/xmlbeans/2.6.0/xmlbean...
> Looks like there is a prior version of xmlbeans in Orbit already:
> http://download.eclipse.org/tools/orbit/downloads/drops/R20150124073747/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19900) Installing only V3 feature results is limited capability, need to know to install V2
by Steve Speicher (JIRA)
Steve Speicher created JBIDE-19900:
--------------------------------------
Summary: Installing only V3 feature results is limited capability, need to know to install V2
Key: JBIDE-19900
URL: https://issues.jboss.org/browse/JBIDE-19900
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Alpha2
Environment: eclipse.buildId=4.5.0.I20150522-2000
org.jboss.tools.openshift.client (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active]
org.jboss.tools.openshift.common.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active]
org.jboss.tools.openshift.common.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift Common UI" [Active]
org.jboss.tools.openshift.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active]
org.jboss.tools.openshift.egit.core (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit Core" [Starting]
org.jboss.tools.openshift.egit.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit UI" [Starting]
org.jboss.tools.openshift.ui (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active]
Reporter: Steve Speicher
If a user is interested in only V3, they are tempted to just install the V3 feature. The issue is that a number of things don't work, namely the "Create"/"New" paths.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-18772 at 6/2/15 8:34 AM:
----------------------------------------------------------------
Needs changes:
* devstudio.product : requires more specific steps, so pom has to be changed
* jbosstools-browsersim-standalone : doesn't match the generic deployment procedure, so its pom requires some customization
* jbosstools-discovery : requires more specific steps, as generic process isn't covering this case
* jbosstools-integration-stack-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina]
* jbosstools-integration-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. See suggested Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/990 .cc [~mmalina]
* RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before updating the job. cc [~mmalina]
Nothing to change:
* jbosstools-locus.site : Latest version only seems to be published and consumed only through Nexus (in all .target definition I've checked), so it's just a regular "mvn deploy", without any other publish step necessary (more like JBIDE-16128 ). Nothing to change on the job.
was (Author: mickael_istria):
Needs changes:
* devstudio.product : requires more specific steps, so pom has to be changed
* jbosstools-browsersim-standalone : doesn't match the generic deployment procedure, so its pom requires some customization
* jbosstools-discovery : requires more specific steps, as generic process isn't covering this case
* jbosstools-integration-stack-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina]
* jbosstools-integration-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina]
* RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before updating the job. cc [~mmalina]
Nothing to change:
* jbosstools-locus.site : Latest version only seems to be published and consumed only through Nexus (in all .target definition I've checked), so it's just a regular "mvn deploy", without any other publish step necessary (more like JBIDE-16128 ). Nothing to change on the job.
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19897) Connection wizard: Remove "check server type" button and functionality
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19897:
-------------------------------------
Summary: Connection wizard: Remove "check server type" button and functionality (was: Remove check server type)
> Connection wizard: Remove "check server type" button and functionality
> ----------------------------------------------------------------------
>
> Key: JBIDE-19897
> URL: https://issues.jboss.org/browse/JBIDE-19897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: connection_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: check-server-type-disabled.png
>
>
> In JBIDE-19829 we disabled the "Check Server Type" button that was detecting the server type (v2 or v3) for a given server url. We should now remove the widget and the related code.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19884) cdi.ui test failure
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19884?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-19884:
------------------------------------------
Sorry, changed an assignee by mistake.
> cdi.ui test failure
> -------------------
>
> Key: JBIDE-19884
> URL: https://issues.jboss.org/browse/JBIDE-19884
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Beta1
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Beta1
>
>
> {code}
> testCDINamedBeanDialogSearch(org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest) Time elapsed: 6.177 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Unexpected editor is opened for CDI Named Bean 'blackWidow': SpiderProducer.java
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.find(OpenCDINamedBeanDialogTest.java:74)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.testCDINamedBeanDialogSearch(OpenCDINamedBeanDialogTest.java:32)
> testCDINamedBeanDialogSearchShortHand(org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest) Time elapsed: 5.786 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Unexpected editor is opened for CDI Named Bean 'blackWidow': SpiderProducer.java
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.find(OpenCDINamedBeanDialogTest.java:74)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.testCDINamedBeanDialogSearchShortHand(OpenCDINamedBeanDialogTest.java:38)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months