[JBoss JIRA] Created: (JBIDE-3751) Let user change Seam varsion on Seam settings page.
by Alexey Kazakov (JIRA)
Let user change Seam varsion on Seam settings page.
---------------------------------------------------
Key: JBIDE-3751
URL: https://jira.jboss.org/jira/browse/JBIDE-3751
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.1.0
Max Andersen:
"now that we have more than 2 versions of Seam and especially 2.0 and 2.1 being so close it might make sense to show all runtimes in our seam combo and simply error if the versions doesn't match ? Or even better show a warning and if users click apply anyway and they are in a faceted project they are given a Dialog asking if they really want to change version and we show the change version dialog ... that would avoid the need to browse two different ui's for this."
--
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
16 years, 7 months
[JBoss JIRA] Created: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
by Nick Boldt (JIRA)
Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA
--------------------------------------------------------------------------------------------------
Key: JBIDE-4200
URL: https://jira.jboss.org/jira/browse/JBIDE-4200
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.1.0.M1
Reporter: Nick Boldt
Priority: Minor
Jars and zips currently look like 3.1.0.Alpha1-yyyymmddHHMM-H###
To support a more Eclipse-like naming convention involving milestones, we need to switch to:
3.1.0.vyyyymmddHHMM-PP-H###-T
Where PP = phase, eg., M1, H### = Hudson build number, and T = type, eg., N, I, S, or R. (Only N and R are currently supported.)
This will guarantee that regardless of where a build is produced (ie., in whatever phase) it can always be installed onto an older version because the qualifier will always increase w/ time, regardless of additional suffixes.
--
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
16 years, 7 months
[JBoss JIRA] Created: (JBIDE-3915) jBPM Eclipse plugin can't save graphical view if gpd.xml is marked as read only
by Hedley Proctor (JIRA)
jBPM Eclipse plugin can't save graphical view if gpd.xml is marked as read only
-------------------------------------------------------------------------------
Key: JBIDE-3915
URL: https://jira.jboss.org/jira/browse/JBIDE-3915
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0
Environment: Windows xp
Eclipse 3.3.2
jPDL Eclipse plugin v3.1.3 SP2
Reporter: Hedley Proctor
Usually when you get files out of a source control system, they will be marked as read only. So if you are editing a Java file in Eclipse, you will get a dialog box coming up asking you to make the file writable. Now consider what happens with jBPM:
Most likely you will check in the gpd.xml file. Otherwise, other people trying to view your processdefinition.xml file will not get a very viewable image. (Everything will appear in the top left.)
When you start editing your processdefinition.xml file, the picture you see will be updated. Everything will appear to be fine. However, none of the changes are saved to the gpd.xml file. When you shutdown Eclipse and restart, the gpd.xml will be out of step with the processdefinition.xml.
I think this could be fixed fairly easily with a couple of lines of code that check the writable status of the gpd.xml file and change it if necessary. Obviously the workaround is just to manually change the write flag, but it is a bit of a "gotcha" and can lead to work being lost if you don't know to do that.
--
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
16 years, 8 months