[JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20833:
------------------------------------
So... maybe for JBDS 9.1 and 10 these plugins should be in Central, not in Playground, since that's where they're included in the org.jboss.tools.central.easymport.feature ? Or perhaps the feature should live in Playground?
> Version of playground plugins is CR2 instead of Final
> -----------------------------------------------------
>
> Key: JBIDE-20833
> URL: https://issues.jboss.org/browse/JBIDE-20833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, playground
> Affects Versions: 4.3.0.CR2
> Reporter: Lucia Jelinkova
> Assignee: Nick Boldt
> Priority: Critical
>
> All plugins in JBT CR2 build have Final version, except for Easymport:
> org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar
> org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19808:
----------------------------------------
Description:
cy*Reason:*
Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
The current working implementation of Teiid with this widget can be found here:
https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
*Project page/sources:*
* [directory.apache.org|https://directory.apache.org]
* [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
* [udpate site | http://directory.apache.org/studio/update/2.x/]
*Version:* 2.0.0
*License and owner:* Apache licence and Foundation
*Original p2 repo:* http://directory.apache.org/studio/update/2.x/
*JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/apache-director...
*Include Sources:* Not available from existing update site but may well be in the next release.
*Affected projects:* Teiid Designer
*Include in JBDS:* Yes
*Type of dependency:* distribution
*List of bundles added/removed:*
* org.apache.directory.api.ldap.model
* org.apache.directory.studio.common.core
* org.apache.directory.studio.common.ui
* org.apache.directory.studio.connection.core
* org.apache.directory.studio.connection.ui
* org.apache.directory.studio.ldapbrowser.common
* org.apache.directory.studio.ldapbrowser.core
* -org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency
{code}
<!-- Needed by Teiid Designer for support with ldap browsing UI -->
<location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
<repository location="http://directory.apache.org/studio/update/2.x/"/>
<unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
</location>
{code}
was:
*Reason:*
Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
The current working implementation of Teiid with this widget can be found here:
https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
*Project page/sources:*
* [directory.apache.org|https://directory.apache.org]
* [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
* [udpate site | http://directory.apache.org/studio/update/2.x/]
*Version:* 2.0.0
*License and owner:* Apache licence and Foundation
*Original p2 repo:* http://directory.apache.org/studio/update/2.x/
*JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/apache-director...
*Include Sources:* Not available from existing update site but may well be in the next release.
*Affected projects:* Teiid Designer
*Include in JBDS:* Yes
*Type of dependency:* distribution
*List of bundles added/removed:*
* org.apache.directory.api.ldap.model
* org.apache.directory.studio.common.core
* org.apache.directory.studio.common.ui
* org.apache.directory.studio.connection.core
* org.apache.directory.studio.connection.ui
* org.apache.directory.studio.ldapbrowser.common
* org.apache.directory.studio.ldapbrowser.core
* -org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency
{code}
<!-- Needed by Teiid Designer for support with ldap browsing UI -->
<location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
<repository location="http://directory.apache.org/studio/update/2.x/"/>
<unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
</location>
{code}
> Teiid Designer would like to depend on org.apache.directory.studio plugins
> --------------------------------------------------------------------------
>
> Key: JBIDE-19808
> URL: https://issues.jboss.org/browse/JBIDE-19808
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, teiid
> Affects Versions: 4.2.3.Final
> Reporter: Paul Richardson
> Assignee: Barry LaFond
> Fix For: 4.2.4.Final
>
> Attachments: build.xml, p2.diff
>
>
> cy*Reason:*
> Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
> The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
> The current working implementation of Teiid with this widget can be found here:
> https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
> The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
> *Project page/sources:*
> * [directory.apache.org|https://directory.apache.org]
> * [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
> * [udpate site | http://directory.apache.org/studio/update/2.x/]
> *Version:* 2.0.0
> *License and owner:* Apache licence and Foundation
> *Original p2 repo:* http://directory.apache.org/studio/update/2.x/
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/apache-director...
> *Include Sources:* Not available from existing update site but may well be in the next release.
> *Affected projects:* Teiid Designer
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> * org.apache.directory.api.ldap.model
> * org.apache.directory.studio.common.core
> * org.apache.directory.studio.common.ui
> * org.apache.directory.studio.connection.core
> * org.apache.directory.studio.connection.ui
> * org.apache.directory.studio.ldapbrowser.common
> * org.apache.directory.studio.ldapbrowser.core
> * -org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency
> {code}
> <!-- Needed by Teiid Designer for support with ldap browsing UI -->
> <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
> <repository location="http://directory.apache.org/studio/update/2.x/"/>
> <unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
> </location>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20833:
----------------------------------------
{code}How can we educate Devs that they need to kick their own jobs when last-minute, urgent changes happen very close to the build time? Mickael Istria WDYT? {code}
In that case, it's not a last-minute urgent change. It's a planned change.
I expected to buildflow to run once all "Bump to Final" Jiras were resolved, to pick the right change. So I don't remember I triggered it manually, and honestly, I don't believe we should expect devs to do that for such "requested by releng" changes.
However, I believe the reason of the issue can be in the buildflow: the bundles of jbosstools-playground are consumed by other components: maven, jst, aerogear... and included in the component features. So if those comsumers weren't rebuilt after the update, the new bundles didn't make it into the consuming features so they didn't make it into aggregate neither.
For JBDS 10, the plan is to move the bundles to their components as much as possible. However, the current high frequence of API changes in Easymport made it easier to keep them in a separated repo for JBDS 9.
> Version of playground plugins is CR2 instead of Final
> -----------------------------------------------------
>
> Key: JBIDE-20833
> URL: https://issues.jboss.org/browse/JBIDE-20833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, playground
> Affects Versions: 4.3.0.CR2
> Reporter: Lucia Jelinkova
> Assignee: Nick Boldt
> Priority: Critical
>
> All plugins in JBT CR2 build have Final version, except for Easymport:
> org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar
> org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20737) On Linux, non-root user us not able to use auto-detect to access running Docker instance
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-20737:
---------------------------------------
[~mhusnain], just a small detail: Perhaps we could start with the recommended workaround and not the one that is not recommended? I.e. switch the order of the workarounds.
Otherwise it looks good.
> On Linux, non-root user us not able to use auto-detect to access running Docker instance
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20737
> URL: https://issues.jboss.org/browse/JBIDE-20737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.3.0.CR1
> Environment: RHEL 7
> OpenJDK 1.8
> Version: 9.0.0.CR1
> Build id: CR1-v20150912-1100-B100
> Build date: 20150912-1100
> CR1 includes:
> com.spotify.docker.client_3.1.1.jar
> org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar
> org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar
> org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Fix For: 4.3.1.Final
>
> Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png
>
>
> On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock)
> A non-root user is not able to connect. No warning or error is written to the UI/dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20833:
------------------------------------
I think I missed this because there are no playground FEATURES so when I scanned these pages for the correct qualifiers, I didn't see the CR2-named bits.
http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.CR2/
https://devstudio.redhat.com/9.0/staging/updates/core/9.0.0.CR2/
Of course if you look in the /plugins/ folders they're there.
Not sure why build #24 wasn't picked up by the aggregate - it had the correct Final-named bits.
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-pla...
Could be because the change to move to Final parent pom wasn't done until 2:27am on Friday [0], but the build to pick up the change didn't run until 8:25am on Friday [1]. This could have been optimized by having the playground or buildflow job kicked immediately at 2:28am.
[0] https://github.com/jbosstools/jbosstools-playground/commit/9758d0bfd73a87...
[1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-playground...
How can we educate Devs that they need to kick their own jobs when last-minute, urgent changes happen very close to the build time? [~mickael_istria] WDYT?
But then, I had set BUILD_ALIAS=Final overrides on all the jobs because when I kicked the job Thursday night, NO ONE had updated to use the Final parent pom, so I needed a way to force the correct qualifier in there.
It appears that I removed that override 2 hrs after the playground job picked up Mickael's change, so unless someone updated the job earlier than my commit and didn't push that change to git, then the correct BUILD_ALIAS should have been set.
{code}
$ git blame config.xml
29e1c1d2 (nickboldt 2015-09-25 10:33:42 -0400 55) <defaultValue>-B -U -fae -e -Djbosstools_site_stream=4.3.mars -P hudson,pack200,unified.target</defaultValue>
{code}
TL;DR, not sure why build #23's bits were used, or why my BUILD_ALIAS=Final override didn't get used.
> Version of playground plugins is CR2 instead of Final
> -----------------------------------------------------
>
> Key: JBIDE-20833
> URL: https://issues.jboss.org/browse/JBIDE-20833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, playground
> Affects Versions: 4.3.0.CR2
> Reporter: Lucia Jelinkova
> Assignee: Nick Boldt
> Priority: Critical
>
> All plugins in JBT CR2 build have Final version, except for Easymport:
> org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar
> org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20835) "Comparison method violates its general contract!" in JMX memory monitor view - 4.4
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20835?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-20835:
---------------------------------------
This issue is cloned from JBIDE-20748 and will be verified in 4.4.0.Alpha1.
> "Comparison method violates its general contract!" in JMX memory monitor view - 4.4
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-20835
> URL: https://issues.jboss.org/browse/JBIDE-20835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> {code}Workaround for comparator violation:
> - set system property java.util.Arrays.useLegacyMergeSort=true
> - use a 1.6 JRE
> message: Comparison method violates its general contract!
> this: org.jboss.tools.jmx.jvmmonitor.internal.ui.properties.memory.HeapComparator
> comparator: null
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months