[JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-15398:
-------------------------------------
I will try to import in Eclipse Java version (no WTP, no JBT), Eclipse JavaEE (no JBT) and Eclipse JavaEE + CDI tools to compare build times
> CDI Builder is sloooow
> ----------------------
>
> Key: JBIDE-15398
> URL: https://issues.jboss.org/browse/JBIDE-15398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.0.Final
> Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
> Reporter: Fred Bricon
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-15398:
-----------------------------------
Summary: CDI Builder is sloooow
Key: JBIDE-15398
URL: https://issues.jboss.org/browse/JBIDE-15398
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Affects Versions: 4.1.0.Final
Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
Reporter: Fred Bricon
After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBDS-2740) Support multiple namespaces in OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2740?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-2740:
----------------------------------------
[~burrsutter] yes "namespace" and "domain name" are equivalent. You can also see this in the Web-UI:
!namespace.png!
> Support multiple namespaces in OpenShift
> ----------------------------------------
>
> Key: JBDS-2740
> URL: https://issues.jboss.org/browse/JBDS-2740
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Andy Goldstein
> Assignee: Andre Dietisheim
> Labels: openshift
> Attachments: namespace.png
>
>
> OpenShift will soon add support for a user to have access to multiple namespaces. This includes:
> - a user creates and owns multiple namespaces
> - a user has permission to work with a domain owned by another user (with differing permission levels)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBDS-2740) Support multiple namespaces in OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2740?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-2740:
-----------------------------------
Attachment: namespace.png
> Support multiple namespaces in OpenShift
> ----------------------------------------
>
> Key: JBDS-2740
> URL: https://issues.jboss.org/browse/JBDS-2740
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Andy Goldstein
> Assignee: Andre Dietisheim
> Labels: openshift
> Attachments: namespace.png
>
>
> OpenShift will soon add support for a user to have access to multiple namespaces. This includes:
> - a user creates and owns multiple namespaces
> - a user has permission to work with a domain owned by another user (with differing permission levels)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15368) jbosstools-server has API Compatibility problem
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15368?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15368:
-------------------------------------
IJBossToolingConstants is not truly intended to be implemented by clients, however, it contains a very very large number of constants, and some clients do implement it for convenience. To fix this specific issue, we will need to add @noimplement to IJBossToolingConstants and allow the warnings to propagate. Problem is this will make dev environment fail to compile.
> jbosstools-server has API Compatibility problem
> -----------------------------------------------
>
> Key: JBIDE-15368
> URL: https://issues.jboss.org/browse/JBIDE-15368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.1.Alpha1
> Reporter: Denis Golovin
> Priority: Blocker
> Labels: api-compatibility
> Fix For: 4.1.1.Alpha1
>
>
> Latest version from jbosstools-server/jbosstools-4.1.x branch has API Compatibility problem:
> "The field org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants.WILDFLY8_MANAGEMENT_PORT_DEFAULT_PORT in an interface that is intended to be implemented or extended has been added".
> According to http://wiki.eclipse.org/Evolving_Java-based_APIs_2
> || Interface change || Conditions || Compatibility ||
> |Add API field|If interface not implementable by Clients | Binary compatible|
> |Add API field|If interface implementable by Clients| Breaks compatibility (2)|
> (2) Adding an API field to an API interface that is implemented by Clients (e.g., a callback, listener, or visitor interface) breaks binary compatibility in a different way. A field added to a superinterface of C may hide an instance field inherited from a superclass of C, causing linking errors to be detected. Because of this fact, it is important to distinguish between API interfaces that Clients should implement from those that Clients should merely use. API interfaces that Clients should implement should not include fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-14530) Support 'Arquillian Cruiser' in standard 'Outline' view
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14530?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14530:
---------------------------------------------
This would be nice, but because outlines can't be extended, I think better option is to have arquillian cruiser react to selections in java editor or possibly extend the outline in the project explorer where common navigator is present which might allow for this kind of extension ?
> Support 'Arquillian Cruiser' in standard 'Outline' view
> -------------------------------------------------------
>
> Key: JBIDE-14530
> URL: https://issues.jboss.org/browse/JBIDE-14530
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.x
>
>
> Would it be possible to extend the normal 'Outline' view to specially handle 'Deployment methods' and add the option to continue drilling down into the content of the defined archive?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months