[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3191:
----------------------------------
Current flow:
Alphax: points at 8.0-development
Betax: points at 8.0-development
CRx: points at 8.0-development
*MANUAL CHANGE TO SWITCH properties files*
GA: points at 8.0, with p2.inf to remove any old refs to 8.0-development
Max's proposed flow:
Alphax: points at 8.0-development and empty 8.0
Betax: points at 8.0-development and empty 8.0
CRx: points at 8.0-development and empty 8.0
*MANUAL CHANGE TO SWITCH properties files*
GA: points at 8.0, with p2.inf to remove any old refs to 8.0-development
So in both cases there's a manual change required to switch pre-GA builds to include the correct GA URL. I don't see how including an empty 8.0 in the list improves the situation.
--
p2.inf works great *at install time only* to add/remove sites to the Available Software Sites list in Eclipse.
If there's a way to do that *at plugin runtime* that's even better, because it can happen to an existing JBDS install w/o having to first be updated. It could for example ping /8.0/ looking for actual content (non-empty content*.xml files, with actual children). But I don't know if you can have a plugin remove 8.0-development/ from the list programmatically while Eclipse/JBDS is running.
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associate.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ]
Len DiMaggio closed JBDS-2949.
------------------------------
> Require Java 7 for the IDE
> --------------------------
>
> Key: JBDS-2949
> URL: https://issues.jboss.org/browse/JBDS-2949
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: integration
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Fix For: 8.0.0.GA
>
> Attachments: Java_JBDS.png
>
>
> Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1
> Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle)
> Forge already requires Java 7.
> Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-2949:
-------------------------------
Attachment: Java_JBDS.png
Safe to close this - installer traps Java6 - installs with 7 and 8
> Require Java 7 for the IDE
> --------------------------
>
> Key: JBDS-2949
> URL: https://issues.jboss.org/browse/JBDS-2949
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: integration
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Fix For: 8.0.0.GA
>
> Attachments: Java_JBDS.png
>
>
> Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1
> Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle)
> Forge already requires Java 7.
> Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18650:
---------------------------------------------
koen, can you look at this one, I wont have time the next couple of weeks.
The change can't go to branch before after GA and I recall there was a reason with respect to focus handling these focus calls were added...wondering if a) that usecase is now broken ? b) why we ever need to mess with the focus anyway? is this maybe not only an issue of mutter/fedora20?
> Forge wizard window isn't focused after command selection (CTRL-4)
> ------------------------------------------------------------------
>
> Key: JBIDE-18650
> URL: https://issues.jboss.org/browse/JBIDE-18650
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR1
> Environment: jbds 8.0.0.CR1
> [selrahal@fedora20 jbdevstudio]$ uname -a
> Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> [selrahal@fedora20 jbdevstudio]$ java -version
> java version "1.7.0_65"
> OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17)
> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Reporter: Salem Elrahal
> Assignee: Koen Aers
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18650:
----------------------------------------
Assignee: Koen Aers (was: Max Rydahl Andersen)
> Forge wizard window isn't focused after command selection (CTRL-4)
> ------------------------------------------------------------------
>
> Key: JBIDE-18650
> URL: https://issues.jboss.org/browse/JBIDE-18650
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR1
> Environment: jbds 8.0.0.CR1
> [selrahal@fedora20 jbdevstudio]$ uname -a
> Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> [selrahal@fedora20 jbdevstudio]$ java -version
> java version "1.7.0_65"
> OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17)
> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Reporter: Salem Elrahal
> Assignee: Koen Aers
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3191:
-------------------------------------------
just to be clear - I believe the main updatesite should be there from day one. First initial alpha build. No need to wait for beta.
And when the beta is out the users will get updates because ide.properties will have told the tools to add the updatesite.
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associate.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3191:
-------------------------------------------
I'm not following your example Nick.
Why would it be bad if users continue to see the additonal updatesites in his install IFF he have been using developments build ?
The problem we have is that the -development/staging etc. sites is *always* added - but if we add the stable/released updatesite and only add the -development site when users are running development versions I think we should be fine.
Yes, I complain about too many updatessites in here when they are *wrong*. If the user been running development versions he is expected to be okey getting more development content so there it is not a problem, and if a new user installs the stable one he will not get the development site so the list will be correct in both cases.
Is there a case where the list will be wrong/incorrect in this suggested approach ?
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associate.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months