[JBoss JIRA] (JBDS-2787) prepare for JBDS 7.0.1 patch release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2787?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2787 at 10/10/13 9:18 AM:
------------------------------------------------------------
Documented JDK 7u40 bug as follows:
!note-jdk7u40.png!
{quote}
*NOTE:* If you are using Oracle or Open JDK 7u40 (1.7.0_40), and encounter an issue using [JBoss Central|https://issues.jboss.org/browse/JBIDE-15494], Eclipse Marketplace or Mylyn, it may be due to a [temp file creation bug|https://bugs.openjdk.java.net/browse/JDK-8025128]. Please use an older JDK version, such as [7u25 (1.7.0_25)|http://www.oracle.com/technetwork/java/javase/downloads/java-ar...] to work around this issue until a new version is available.{quote}
https://www.jboss.org/tools/download/stable/4_1#noteJDK7u40
https://www.jboss.org/tools/download/dev/4_1_x#noteJDK7u40
https://www.jboss.org/tools/download/dev/4_1_IS#noteJDK7u40
https://www.jboss.org/tools/download/installation/update_4_1.html#noteJDK...
was (Author: nickboldt):
Documented JDK 7u40 bug as follows:
!note-jdk7u40.png!
{quote}
*NOTE:* If you are using Oracle JDK 7u40 (1.7.0_40), and encounter an issue using [JBoss Central|https://issues.jboss.org/browse/JBIDE-15494], Eclipse Marketplace or Mylyn, it may be due to a [temp file creation bug|https://bugs.openjdk.java.net/browse/JDK-8025128]. Please use an older JDK version, such as [7u25 (1.7.0_25)|http://www.oracle.com/technetwork/java/javase/downloads/java-ar...] to work around this issue until a new version is available.{quote}
https://www.jboss.org/tools/download/stable/4_1#noteJDK7u40
https://www.jboss.org/tools/download/dev/4_1_x#noteJDK7u40
https://www.jboss.org/tools/download/installation/update_4_1.html#noteJDK...
> prepare for JBDS 7.0.1 patch release
> ------------------------------------
>
> Key: JBDS-2787
> URL: https://issues.jboss.org/browse/JBDS-2787
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.1.GA
>
> Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png, jbds701ga-updates-avail.png, note-jdk7u40.png
>
>
> Placeholder JIRA to contain work needed to do to release JBDS 7.0.1.GA:
> 1. branch jbosstools-central from 4.1.x to 4.1.0.x
> 2. adjust jbosstools-central/site/category.xml so it only contains the affected features (and feature.sources)
> 3. build Central using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_410/ which gets its sources from the correct fork/branch
> 4. create new composite staging site containing the last stable release + the new staging site for jbosstools-central, eg.,
> http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1....
> 5. branch jbdevstudio-product from 4.1.x to 4.1.0.x
> 6. ensure that JBDS sources are correctly versioned (eg., 7.0.1 not 7.1.0)
> 7. build JBDS using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_70/ which sets -DBUILD_ALIAS=GA, pulls from the correct branch origin/jbosstools-4.1.0.x, and sets these overrides in the maven configuration:
> {code}
> jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
> jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c...
> {code}
--
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, 6 months
[JBoss JIRA] (JBIDE-12929) Delete dialog invoked by Del key is not located correctly
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12929?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-12929.
---------------------------------
I cannot reproduce this so hopefully it is fixed. I tried to mimic Jaroslav's scenario as much as I could.
Verified in JBDS 7.1.0.Alpha2 B431
> Delete dialog invoked by Del key is not located correctly
> ---------------------------------------------------------
>
> Key: JBIDE-12929
> URL: https://issues.jboss.org/browse/JBIDE-12929
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.0.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Snjezana Peco
> Fix For: 4.1.1.Alpha2
>
> Attachments: JBIDE-12929_context_menu.jpg, JBIDE-12929_del_key.jpg, org.eclipse.wst.server.ui_1.4.1.v20120821_1330.jar
>
>
> I hope this is not bug only in my environment. When I delete archive from server with context menu, delete dialog is opened in the middle of the eclipse screen. However, when invoking with Del key, it is located outside the eclipse (if eclipse not maximized of course).
--
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, 6 months
[JBoss JIRA] (JBIDE-15503) test failure in org.jboss.tools.as.test.core due to missing depency on jboss-eap-6.1.0.ER4.zip: please update your tests to use 6.1.0.GA or 6.1.1.GA (or both)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15503?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-15503.
---------------------------------
This issue has been resolved - jobs no longer red. But still yellow...
> test failure in org.jboss.tools.as.test.core due to missing depency on jboss-eap-6.1.0.ER4.zip: please update your tests to use 6.1.0.GA or 6.1.1.GA (or both)
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15503
> URL: https://issues.jboss.org/browse/JBIDE-15503
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.1.Alpha1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.1.1.Alpha2
>
>
> This has been failing for a few days:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-server_master/378/console}
> [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.0.ER4.zip (No such file or directory) -> [Help 1]
> {code}
> Please update your tests to use 6.1.0.GA or 6.1.1.GA (or both) instead.
> Even better, your tests should be able to download the missing zip and bootstrap itself if it can't find the zip in /home/hudson/static_build_env/jbds/download-cache/
--
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, 6 months
[JBoss JIRA] (JBTIS-186) ModeShape sometimes doesn't publish all models of Teiid VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/JBTIS-186?page=com.atlassian.jira.plugin.... ]
Barry LaFond edited comment on JBTIS-186 at 10/10/13 8:40 AM:
--------------------------------------------------------------
Lucie, can you attach an example VDB that you've reproduced this issue with?
And can you check for any error logging during the publish operation?
was (Author: blafond):
Lucie, can you attach an example VDB that you've reproduced this issue with?
> ModeShape sometimes doesn't publish all models of Teiid VDB
> -----------------------------------------------------------
>
> Key: JBTIS-186
> URL: https://issues.jboss.org/browse/JBTIS-186
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: modeshape
> Affects Versions: 4.1.3
> Environment: Ubuntu 12.04, JBTIS 4.1.3.Beta4, DV 6.0.0.ER2, sun jdk 1.6
> Reporter: Lucie Fabrikova
>
> If I publish a teiid VDB with relational models .xmi in given environment, sometimes some (or all) of the models are not published.
--
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, 6 months
[JBoss JIRA] (JBDS-2795) make sure current JBDS works with mult-domain OpenShift instance
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2795?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-2795:
-----------------------------------
Attachment: properties-shows-the-domain.png
> make sure current JBDS works with mult-domain OpenShift instance
> ----------------------------------------------------------------
>
> Key: JBDS-2795
> URL: https://issues.jboss.org/browse/JBDS-2795
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: openshift
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7,
> multidomain DEVENV (2013-10-9)
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 7.1.0.Alpha2
>
> Attachments: cannot-create-application.png, explorer-1.png, explorer-2.png, explorer-3.png, explorer-4.png, explorer-5.png, explorer-5.png, explorer-6.png, explorer-6.png, explorer-7.png, explorer-7.png, explorer-8.png, explorer-9.png, multi-domain-setup-adietish.png, multi-domain-setup-test.png, properties-shows-the-domain.png
>
>
> With the upcoming support for multiple domains, we have to make sure that the existing JBDS/JBT work smoothly even with this newer OpenShift.
--
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, 6 months
[JBoss JIRA] (JBDS-2795) make sure current JBDS works with mult-domain OpenShift instance
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2795?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim edited comment on JBDS-2795 at 10/10/13 8:37 AM:
------------------------------------------------------------------
Using the latest DEVENV with multi-domain enabled, a user that has the silver plan (and can therefore create multiple domains) and JBDS7 I did the tests shown further down:
JBDS works just fine. A users always sees its own domains. If he has none then it'll see the foreign domain it has access to in the order that it got access granted to. The only possible improvement is that writable access should take precendence of read-only access (see step 13)
1) I setup a DEVENV with 2 users:
* adietish(a)redhat.com (silver-plan)
* adietisheim(a)redhat.com
2) First I created 2 domains for adietish(a)redhat.com in the Web-ui:
* gringo
* ruskie
!multi-domain-setup-adietish.png!
3) the first domain (gringo) then showed up in the OpenShift Explorer:
!!explorer-1.png!
4) I granted adietish+test access to these domains. The first domain then showed up in the OpenShift Explorer:
!explorer-2.png!
5) I tried to create an application for adietish+test(a)redhat.com in the read-only domain he has from adietish(a)redhat.com: failure expected, only read-access to domain:
!cannot-create-application.png!
6) Then created adietish+test(a)redhat.com his very own domain:
!multi-domain-setup-test.png!
7) and refreshed the OpenShift Explorer: shows the empty list since new domain has no apps
!explorer-3.png!
8) and created an application in JBDS which shows up for the user:
!explorer-4.png!
9) Then deleted the domain for adietish(a)redhat.com. Once refreshed the explorer shows the 2nd domain:
!explorer-5.png!
10) which you can also see in the properties:
!properties-shows-the-domain.png!
11) And created another application for adietish(a)redhat.com:
!explorer-6.png!
12) killed the domain for adietish+test(a)redhat.com and the domain it has read-access to shows up:
!explorer-7.png!
13) re-created "viking" for adietish+test(a)redhat.com (no application within it) and created another domain "writable" in adietish(a)redhat.com where I granted *write* access for adietish+test(a)redhat.com: "viking" (empty apps-list) shows up for adietish+test(a)redha.com
!explorer-8.png!
14) and killed "viking" in JBDS: "ruskie" shows up for adietish+test(a)redhat.com and not "writable", since read-access was granted in a prior step - there's no precedence of writeable domains vs readable domains.
!explorer-9.png!
was (Author: adietish):
Using the latest DEVENV with multi-domain enabled, a user that has the silver plan (and can therefore create multiple domains) and JBDS7 I did the tests shown further down:
JBDS works just fine. A users always sees its own domains. If he has none then it'll see the foreign domain it has access to in the order that it got access granted to. The only possible improvement is that writable access should take precendence of read-only access (see step 13)
1) I setup a DEVENV with 2 users:
* adietish(a)redhat.com (silver-plan)
* adietisheim(a)redhat.com
2) First I created 2 domains for adietish(a)redhat.com in the Web-ui:
* gringo
* ruskie
!multi-domain-setup-adietish.png!
3) the first domain (gringo) then showed up in the OpenShift Explorer:
!!explorer-1.png!
4) I granted adietish+test access to these domains. The first domain then showed up in the OpenShift Explorer:
!explorer-2.png!
5) I tried to create an application for adietish+test(a)redhat.com in the read-only domain he has from adietish(a)redhat.com: failure expected, only read-access to domain:
!cannot-create-application.png!
6) Then created adietish+test(a)redhat.com his very own domain:
!multi-domain-setup-test.png!
7) and refreshed the OpenShift Explorer: shows the empty list since new domain has no apps
!explorer-3.png!
8) and created an application in JBDS which shows up for the user:
!explorer-4.png!
9) Then deleted the domain for adietish(a)redhat.com. Once refreshed the explorer shows the 2nd domain:
!explorer-5.png!
10) And created another application for adietish(a)redhat.com:
!explorer-6.png!
11) killed the domain for adietish+test(a)redhat.com and the domain it has read-access to shows up:
!explorer-7.png!
12) re-created "viking" for adietish+test(a)redhat.com (no application within it) and created another domain "writable" in adietish(a)redhat.com where I granted *write* access for adietish+test(a)redhat.com: "viking" (empty apps-list) shows up for adietish+test(a)redha.com
!explorer-8.png!
13) and killed "viking" in JBDS: "ruskie" shows up for adietish+test(a)redhat.com and not "writable", since read-access was granted in a prior step - there's no precedence of writeable domains vs readable domains.
!explorer-9.png!
> make sure current JBDS works with mult-domain OpenShift instance
> ----------------------------------------------------------------
>
> Key: JBDS-2795
> URL: https://issues.jboss.org/browse/JBDS-2795
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: openshift
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7,
> multidomain DEVENV (2013-10-9)
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 7.1.0.Alpha2
>
> Attachments: cannot-create-application.png, explorer-1.png, explorer-2.png, explorer-3.png, explorer-4.png, explorer-5.png, explorer-5.png, explorer-6.png, explorer-6.png, explorer-7.png, explorer-7.png, explorer-8.png, explorer-9.png, multi-domain-setup-adietish.png, multi-domain-setup-test.png, properties-shows-the-domain.png
>
>
> With the upcoming support for multiple domains, we have to make sure that the existing JBDS/JBT work smoothly even with this newer OpenShift.
--
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, 6 months