[JBoss JIRA] (JBIDE-8866) Move all plugins up to baseline
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8866?page=com.atlassian.jira.plugin... ]
Rob Stryker resolved JBIDE-8866.
--------------------------------
Resolution: Partially Completed
I don't remember the impetus for this, but since 4.0 has shipped, I think this is kinda out of date.
> Move all plugins up to baseline
> -------------------------------
>
> Key: JBIDE-8866
> URL: https://issues.jboss.org/browse/JBIDE-8866
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: Build/Releng
> Affects Versions: 3.3.0.M2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: LATER
>
> Attachments: hibernate-tools.patch, manifests.zip
>
>
> Not really sure who to assign this to, short of making three dozen separate jira issues ;) I have 33 patches, one for each module, which modify all manifest.mf version numbers (in plugins, not in tests) to be brought up to our current baseline.
> So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a dependency on this.specific.runtime into this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads this.specific.plugin;bundle-version="3.5.0", it will move it up to this.specific.runtime;bundle-version="3.6.200".
> Etc.
--
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
13 years, 5 months
[JBoss JIRA] (JBDS-2437) Cannot deploy BPEL project
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-2437?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBDS-2437:
-----------------------------------------
Verified with JBDS 5.0.2.CR3 build H248
> Cannot deploy BPEL project
> --------------------------
>
> Key: JBDS-2437
> URL: https://issues.jboss.org/browse/JBDS-2437
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.2.GA
> Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 5.0.2.GA
>
> Attachments: deploy_error.png, jbosstools-diagnostics-20130109091445.zip
>
>
> Cannot deploy a bpel project.
--
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
13 years, 5 months
[JBoss JIRA] (TOOLSDOC-297) Document Release Notes for JBT 3.3.2 & JBDS 5.0.2
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-297:
----------------------------------------
Summary: Document Release Notes for JBT 3.3.2 & JBDS 5.0.2
Key: TOOLSDOC-297
URL: https://issues.jboss.org/browse/TOOLSDOC-297
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Release Notes
Affects Versions: 3.3.2
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 3.3.2
JIRA created for tracking git pull requests relating to release note creation.
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-13372) improve usability of jiralint emails
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13372:
----------------------------------
Summary: improve usability of jiralint emails
Key: JBIDE-13372
URL: https://issues.jboss.org/browse/JBIDE-13372
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 4.1.0.Alpha1
Could these be reformatted to list the names of the offenders at the top of the email, so we don't have to waste time scanning to see whose name is associated w/ the incorrectly versioned jiras?
Better, can they simply be sent to the people who've set bad fixVersions, rather than the whole list? The only person who needs to see the email below is Snjezana.
{code}
-------- Original Message --------
Subject: Weekly jira sanity check - jbosstools-jiralint - Build # 138 - Still Unstable!
Date: Sun, 13 Jan 2013 00:01:28 -0500 (EST)
From: ci-builds(a)redhat.com
To: external-exadel-list(a)redhat.com
This is the weekly check for jira problems.
Please fix the issues outlined below if there are any. Thank you!
jbosstools-jiralint - Build # 138 - Still Unstable:
Check console output at http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint/138/ to view the results.
1 tests 1 failure(s) / -2
1 tests failed.
FAILED: ToolsIllegalFixVersion.ToolsIllegalFixVersion.JBIDE-13332_snjeza
Error Message:
https://jira.jboss.org/browse/JBIDE-13332 (last update: 22 days, 10:21:51.551414) -> Issue have been resolved with an illegal fix version, i.e. an .x version, LATER or no fix version at all. This means it will not be shown in the right release notes so neither developers or users can see where things happend. Please adjust the issue so it correctly states the proper fix version! Thank you! See http://bit.ly/aTUeGq for how to track down right fix versions.
Stack Trace:
JBIDE-13332: Update list of quickstarts to be consistent with current goals(https://jira.jboss.org/browse/JBIDE-13332)
{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
13 years, 5 months
[JBoss JIRA] (JBIDE-13205) XML Editors not always update status bar
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13205?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13205:
-----------------------------------------------
WTP's XML Editor has the same problem.
> XML Editors not always update status bar
> ----------------------------------------
>
> Key: JBIDE-13205
> URL: https://issues.jboss.org/browse/JBIDE-13205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml source editing
> Affects Versions: 4.0.0.CR1
> Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.CR1-v20121129-0502-B147.jar
> Reporter: Daniel Azarov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.1.x
>
> Attachments: TLDEditor1.png, TLDEditor1.png, TLDEditor2.png, TLDEditor2.png
>
>
> When I open tld file in JBoss Tools Tag Library Editor first time it does not show any information in status bar:
> !TLDEditor1.png!
> If I switch to tab "Source" or did it before status bar looks fine:
> !TLDEditor2.png!
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-13371) test failure in org.jboss.ide.eclipse.as.test.server.XPathModelTest.testEap60Mock (from org.jboss.ide.eclipse.as.test.ASTestSuite) : The XPath File has not been created. Xpaths will be lost on workspace restart
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13371:
----------------------------------
Summary: test failure in org.jboss.ide.eclipse.as.test.server.XPathModelTest.testEap60Mock (from org.jboss.ide.eclipse.as.test.ASTestSuite) : The XPath File has not been created. Xpaths will be lost on workspace restart
Key: JBIDE-13371
URL: https://issues.jboss.org/browse/JBIDE-13371
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.2
Reporter: Nick Boldt
Assignee: Rob Stryker
Fix For: 3.3.2
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.component--as/lastCompletedBuild/testReport/org.jboss.ide.eclipse.as.test.server/XPathModelTest/testEap60Mock/}
Regression
org.jboss.ide.eclipse.as.test.server.XPathModelTest.testEap60Mock (from org.jboss.ide.eclipse.as.test.ASTestSuite)
Failing for the past 1 build (Since Unstable#152 )
Took 30 ms.
add description
Error Message
The XPath File has not been created. Xpaths will be lost on workspace restart
Stacktrace
junit.framework.AssertionFailedError: The XPath File has not been created. Xpaths will be lost on workspace restart
at junit.framework.Assert.fail(Assert.java:47)
at org.jboss.ide.eclipse.as.test.server.XPathModelTest.serverTestImpl(XPathModelTest.java:31)
at org.jboss.ide.eclipse.as.test.server.SimpleServerImplTest.testEap60Mock(SimpleServerImplTest.java:61){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
13 years, 5 months
[JBoss JIRA] (JBIDE-13351) Dialogs look and fill problems
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13351?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13351:
----------------------------------
Attachment: Result1_2.png
> Dialogs look and fill problems
> ------------------------------
>
> Key: JBIDE-13351
> URL: https://issues.jboss.org/browse/JBIDE-13351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, runtime-detection, Seam 2, Visual Page Editor Templates
> Affects Versions: 4.1.0.Alpha1
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Priority: Trivial
> Fix For: 4.1.x
>
> Attachments: AddCapability.png, AddELReeference.png, AddInterface.png, ADDJBossToolsRuntimeDialog.png, AddJSFProjectVersion.png, AddLibraryReference.png, AddLibrarySet.png, AddMavenRepository.png, BrowseFontDialog.png, ConfigureMavenRepositories.png, ConfigureMavenRepositories2.png, DownloadRuntimes.png, EditInterface.png, EditServletClassDialog.png, EditTLDFilesDialog.png, ImportUserSpecifiedTagTemplates.png, NewJBossESBRuntime.png, NewRepositoryDialog.png, NewTemplateDialog.png, Result1.png, Result1_2.png, Result2.png, Result2.png, Result3.png, Result4.png, UserSpecifiedTagTemplate.png
>
>
> Follow
> 1. New->Other->JBoss Tools->Configure MavenRepositories
> ConfigureMavenRepositoriesWizard.java
> Wizard banner has wrong high less than 66 pixels
> !ConfigureMavenRepositories.png!
> then press button "Add Repository..."
> !AddMavenRepository.png!
> 2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..."
> EditNexusRepositoryDialog.java
> Dialog should have a banner:
> !NewRepositoryDialog.png!
> 3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories"
> Dialog should have a not empty banner:
> !ConfigureMavenRepositories2.png!
> 4. Window->Preferences, JBoss Tools->JBoss ESB Runtimes, button "Add". BTW it should be "Add..."
> Dialog should have a not empty banner:
> !NewJBossESBRuntime.png!
> 5.Window->Preferences, JBoss Tools->JBoss Runtime Detection, button "Download..."
> Dialog should have a not empty banner:
> !DownloadRuntimes.png!
> 6. Window->Preferences, JBoss Tools->Web->Custom Capabilities, buttons "Add" (button should be "Add...")
> Dialogs should have a not default bunner:
> !AddCapability.png!
> !AddLibraryReference.png!
> 7. Window->Preferences, JBoss Tools->Web->Editors->Visual Page Editor, tab Visual Templates, buttons "Add..." and "Import..."
> Dialogs should have a not default bunner:
> !UserSpecifiedTagTemplate.png!
> !ImportUserSpecifiedTagTemplates.png!
> 8. Window->Preferences, JBoss Tools->Web->Expression Language->Variables, button "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddELReeference.png!
> 9. Window->Preferences, JBoss Tools->Web->JSF->JSF Environment, button "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddJSFProjectVersion.png!
> 10. Window->Preferences, JBoss Tools->Web->Library Sets, button "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddLibrarySet.png!
> 11. Window->Preferences, JBoss Tools->Web->Templates, buttons "Add" and "Edit"(buttons should be "Add..." and "Edit...")
> Dialogs should have a not default bunner:
> !AddInterface.png!
> !EditInterface.png!
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-13351) Dialogs look and fill problems
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13351?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-13351 at 1/11/13 8:33 PM:
----------------------------------------------------------------
What I've done:
1.
!Result1.png!
!Result1_2.png!
2.
!Result2.png!
3.
!Result3.png!
4.
!Result4.png!
was (Author: dazarov):
What I've done:
1.
!Result1.png!
2.
!Result2.png!
3.
!Result3.png!
4.
!Result4.png!
> Dialogs look and fill problems
> ------------------------------
>
> Key: JBIDE-13351
> URL: https://issues.jboss.org/browse/JBIDE-13351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, runtime-detection, Seam 2, Visual Page Editor Templates
> Affects Versions: 4.1.0.Alpha1
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Priority: Trivial
> Fix For: 4.1.x
>
> Attachments: AddCapability.png, AddELReeference.png, AddInterface.png, ADDJBossToolsRuntimeDialog.png, AddJSFProjectVersion.png, AddLibraryReference.png, AddLibrarySet.png, AddMavenRepository.png, BrowseFontDialog.png, ConfigureMavenRepositories.png, ConfigureMavenRepositories2.png, DownloadRuntimes.png, EditInterface.png, EditServletClassDialog.png, EditTLDFilesDialog.png, ImportUserSpecifiedTagTemplates.png, NewJBossESBRuntime.png, NewRepositoryDialog.png, NewTemplateDialog.png, Result1.png, Result1_2.png, Result2.png, Result2.png, Result3.png, Result4.png, UserSpecifiedTagTemplate.png
>
>
> Follow
> 1. New->Other->JBoss Tools->Configure MavenRepositories
> ConfigureMavenRepositoriesWizard.java
> Wizard banner has wrong high less than 66 pixels
> !ConfigureMavenRepositories.png!
> then press button "Add Repository..."
> !AddMavenRepository.png!
> 2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..."
> EditNexusRepositoryDialog.java
> Dialog should have a banner:
> !NewRepositoryDialog.png!
> 3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories"
> Dialog should have a not empty banner:
> !ConfigureMavenRepositories2.png!
> 4. Window->Preferences, JBoss Tools->JBoss ESB Runtimes, button "Add". BTW it should be "Add..."
> Dialog should have a not empty banner:
> !NewJBossESBRuntime.png!
> 5.Window->Preferences, JBoss Tools->JBoss Runtime Detection, button "Download..."
> Dialog should have a not empty banner:
> !DownloadRuntimes.png!
> 6. Window->Preferences, JBoss Tools->Web->Custom Capabilities, buttons "Add" (button should be "Add...")
> Dialogs should have a not default bunner:
> !AddCapability.png!
> !AddLibraryReference.png!
> 7. Window->Preferences, JBoss Tools->Web->Editors->Visual Page Editor, tab Visual Templates, buttons "Add..." and "Import..."
> Dialogs should have a not default bunner:
> !UserSpecifiedTagTemplate.png!
> !ImportUserSpecifiedTagTemplates.png!
> 8. Window->Preferences, JBoss Tools->Web->Expression Language->Variables, button "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddELReeference.png!
> 9. Window->Preferences, JBoss Tools->Web->JSF->JSF Environment, button "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddJSFProjectVersion.png!
> 10. Window->Preferences, JBoss Tools->Web->Library Sets, button "Add" (button should be "Add...")
> Dialog should have a not default bunner:
> !AddLibrarySet.png!
> 11. Window->Preferences, JBoss Tools->Web->Templates, buttons "Add" and "Edit"(buttons should be "Add..." and "Edit...")
> Dialogs should have a not default bunner:
> !AddInterface.png!
> !EditInterface.png!
--
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
13 years, 5 months