[JBoss JIRA] (JBIDE-15285) Increment minor version of jbosstools-base/foundation submodule
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15285?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-15285 at 9/11/13 2:48 AM:
----------------------------------------------------------------
Adding new class means changing internal implementation and that leads to version update anyway not for minor but for service part of version.
I did pushed it because I was not using API Tooling yet at that point and it is not clear without *.internal.* in package name, that package is actually private.
Updating 1.0.0 to 1.1.0 means you are now free to add any new public API packages in 4.2.x stream :)
was (Author: dgolovin):
Adding new class means changing internal implementation and that leads to version update anyway not for minor but for service part of version. So I am going to close PR request and update description
> Increment minor version of jbosstools-base/foundation submodule
> ---------------------------------------------------------------
>
> Key: JBIDE-15285
> URL: https://issues.jboss.org/browse/JBIDE-15285
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.2.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: versioning
> Fix For: 4.2.0.Alpha1
>
>
> New class [Trace|https://github.com/jbosstools/jbosstools-base/commit/0e97d80209db88...] was introduced in Public API of foundation submodule, thus minor version should be incremented.
> 1.0.0-SNAPSHOT -> 1.1.0-SNAPSHOT
--
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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15398:
----------------------------------
Fix Version/s: 4.1.1.Alpha2
> 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
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
> Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png
>
>
> 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 bulk 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-15392) Add api in server needed for source lookup
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15392:
---------------------------------------------
"A source lookup container knows only a home directory" - you keep repeating this but why don't we make it so it can use either a home directory (and then just scans for all jars) or a specific server which would then be able to provide much more specific knowledge like this API jboss servers could expose ?
Similar could be made for tomcats etc. if this was setup as an extension point where runtime type was mapped to a class that could handle it.
> Add api in server needed for source lookup
> ------------------------------------------
>
> Key: JBIDE-15392
> URL: https://issues.jboss.org/browse/JBIDE-15392
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven, server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha1
>
>
> As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes.
> We need to define a stable api that can be used here.
> lets outline what api is actually needed and then subjiras for the specifics.
> For me it looks like server lookup needs a few things:
> 0. know exact version of server
> 1. know the file structure of a certain server
> 2. get dir or directories that contain jar that is the "runtime"
> My guess is that #2 might just be sufficient for source code lookup.
> Any comments ?
--
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