[JBoss JIRA] Created: (JBDS-1799) Hide 3rd party features from JBDS 5 Extras site - only com.jboss.jbds.* features should be exposed
by Nick Boldt (JIRA)
Hide 3rd party features from JBDS 5 Extras site - only com.jboss.jbds.* features should be exposed
--------------------------------------------------------------------------------------------------
Key: JBDS-1799
URL: https://issues.jboss.org/browse/JBDS-1799
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: 3rdPartyDependencies, Build, updatesite
Affects Versions: 4.1.0.CR4, 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.1.0.GA, 5.0.0.M3
1. instead of including 3rd party features in com.jboss.jbds.* features, include contained plugins.
2. rewrite com.jboss.jbds.* features to list out contents so it's clear what versions of 3rd party stuff are included.
Benefits:
* anything installable from JBDS Extras site is a feature we build and maintain (and test and support).
* to install any non-com.jboss 3rd party feature, must go to 3rd party site (or jboss.org community mirror). Because this is "off the reservation", it's not supported, and users' mileage may vary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBIDE-6178) releng update site, feature naming conventions
by Darryl Miles (JIRA)
releng update site, feature naming conventions
----------------------------------------------
Key: JBIDE-6178
URL: https://jira.jboss.org/jira/browse/JBIDE-6178
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: updatesite
Affects Versions: 3.1.0.GA
Reporter: Darryl Miles
Priority: Minor
Please consider the impact of users using the "All Update Site" view when installing JBoss plugins.
Some rules to consider:
1) If JBoss creates a new top-level group (which consists entirely of JBoss features) then that top-level name should begin with the word "JBoss".
2) If JBoss reuses a top-level group which belongs to another vendor (for which JBT is built on top of, for example BIRT/Maven/DTP) then you can reuse the top-level group name of the outside vendor, but ensure your features underneath are prefixed with the word "JBoss"."
In enclose a screen grab from 3.1.0.GA which indicates the discrepancy; BIRT is following the above rules, but "Maven Support" is not (and also "Data Services" top level group is not).
The "All in one JBoss" top-level group doesn't really need to follow this convention, since the top level group clearly indicates it is from JBoss and entirely contains JBoss features and those features are a duplicated entrypoint for installation (i.e. each feature also exist somewhere else in the "features to install" tree view). The ambigiouty is over such names as "Maven Support" and "Data Services" in the context of the "all update site view" from the drop-down filter at the top of the page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBDS-1577) using JBDS as updatesite on eclipse works, but causes outofmemory because of name change
by Max Rydahl Andersen (JIRA)
using JBDS as updatesite on eclipse works, but causes outofmemory because of name change
----------------------------------------------------------------------------------------
Key: JBDS-1577
URL: https://issues.jboss.org/browse/JBDS-1577
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Affects Versions: 4.0.0.GA
Reporter: Max Rydahl Andersen
Not sure if this qualifies as a bug or a feature request but
I noticed that if I use JBDS 4 updatesite against plain Eclipse things seem to work great
until you restart (possible on the second restart) since then it suddenly has zero
extra memory allocated.
It only started working properly when using the jbdevstudio.app; thus my assumption is that
eclipse.ini is ignored and jbdevstudio.ini is looked for instead but this file is nowhere
to be found (except inside jbdevstudio.app)
Would be good if we could handle this situation more gracefully since the shortcuts users
uses still points to eclipse thus they will see it as JBDS running out of memory since when launching
it says JBDS.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBIDE-8534) BIRT viewer should respect the locale attribute in an xhtml embedded report
by Dimitris Keramidas (JIRA)
BIRT viewer should respect the locale attribute in an xhtml embedded report
---------------------------------------------------------------------------
Key: JBIDE-8534
URL: https://issues.jboss.org/browse/JBIDE-8534
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: birt, JBossAS, Seam
Affects Versions: 3.2.0.Final
Environment: Windows 7 64-bit (x86), Eclipse Helios, Oracle jvm 1.6.0 update 23/24 (32bit), JBossAS 5.1, Seam 2.2.0, JBoss Tools 3.2.0, Birt Reporting Runtime Component 2.6.2
Reporter: Dimitris Keramidas
Assignee: Snjezana Peco
I have a simple report, using *.properties files for localization. When using the <b:birt/> tag to integrate the report in a .xhtml file (designType="embed"), the locale attribute is ignored. The documentation states that when using the "embed" parameter, only the designName and masterpage attributes may be used. However, this way the report always defaults to the JVM locale, and there is no - apparent - way to change the locale to match the user's preference. This behaviour does not apply when designType is "run" or "frameset".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBIDE-7783) GWT throws exceptions during Java field rename
by Daniel Azarov (JIRA)
GWT throws exceptions during Java field rename
----------------------------------------------
Key: JBIDE-7783
URL: https://jira.jboss.org/browse/JBIDE-7783
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: GWT
Affects Versions: 3.2.0.Beta1
Environment: JBoss Tools + GWT plugins
Reporter: Daniel Azarov
Assignee: Max Andersen
Test case:
1. Start JBDS
2. Create 'test' Java project
3. Create 'test' Java package
4. Create 'Test' Java class in 'test' package
5. Create 'int user' field
6. Select field and right-click on it
7. Select menu Source->Generate Getters and Setters then press OK button
8. Select field and right-click on it
9. Select menu Refactor->Rename then type user2 and press Ctrl+Enter
10. See Error log
FAIL:
java.lang.ClassCastException: org.eclipse.jdt.internal.core.SourceField cannot be cast to org.eclipse.jdt.core.IMethod
at com.google.gwt.eclipse.core.refactoring.GWTRenameParticipant.initialize(GWTRenameParticipant.java:115)
at com.google.gwt.eclipse.core.refactoring.GWTRenameMemberParticipant.initialize(GWTRenameMemberParticipant.java:38)
at com.google.gwt.eclipse.core.refactoring.rpc.PairedMethodRenameParticipant.initialize(PairedMethodRenameParticipant.java:224)
at org.eclipse.ltk.core.refactoring.participants.RefactoringParticipant.initialize(RefactoringParticipant.java:105)
at org.eclipse.ltk.core.refactoring.participants.ParticipantExtensionPoint.getParticipants(ParticipantExtensionPoint.java:100)
at org.eclipse.ltk.core.refactoring.participants.ParticipantManager.loadRenameParticipants(ParticipantManager.java:74)
at org.eclipse.jdt.internal.corext.refactoring.rename.RenameModifications.loadParticipants(RenameModifications.java:190)
at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.loadParticipants(JavaRenameProcessor.java:40)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:233)
at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85)
at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
java.lang.ClassCastException: org.eclipse.jdt.internal.core.SourceField cannot be cast to org.eclipse.jdt.core.IMethod
at com.google.gwt.eclipse.core.refactoring.GWTRenameParticipant.initialize(GWTRenameParticipant.java:115)
at com.google.gwt.eclipse.core.refactoring.GWTRenameMemberParticipant.initialize(GWTRenameMemberParticipant.java:38)
at org.eclipse.ltk.core.refactoring.participants.RefactoringParticipant.initialize(RefactoringParticipant.java:105)
at org.eclipse.ltk.core.refactoring.participants.ParticipantExtensionPoint.getParticipants(ParticipantExtensionPoint.java:100)
at org.eclipse.ltk.core.refactoring.participants.ParticipantManager.loadRenameParticipants(ParticipantManager.java:74)
at org.eclipse.jdt.internal.corext.refactoring.rename.RenameModifications.loadParticipants(RenameModifications.java:190)
at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.loadParticipants(JavaRenameProcessor.java:40)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:233)
at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85)
at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months