[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18239:
-------------------------------
Description:
In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
These would be produced as new zips using the JBT aggregate builder:
https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?
was:
In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
These would be produced as new zips using the JBT aggregate builder:
https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18239
> URL: https://issues.jboss.org/browse/JBIDE-18239
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
> We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
> These would be produced as new zips using the JBT aggregate builder:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18239) Create new update site zip (rather than target platform zip) for JBT content needed for Central/EA site
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18239:
----------------------------------
Summary: Create new update site zip (rather than target platform zip) for JBT content needed for Central/EA site
Key: JBIDE-18239
URL: https://issues.jboss.org/browse/JBIDE-18239
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, central, discovery, updatesite
Affects Versions: 4.2.0.CR1
Reporter: Nick Boldt
In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
These would be produced as new zips using the JBT aggregate builder:
https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3026) Provide better default JRE path in universal installer on Mac OS X
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3026?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3026:
--------------------------------
Labels: respin-a (was: )
> Provide better default JRE path in universal installer on Mac OS X
> ------------------------------------------------------------------
>
> Key: JBDS-3026
> URL: https://issues.jboss.org/browse/JBDS-3026
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta1
> Reporter: Michelle Murray
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 8.0.0.CR1
>
>
> Max OS X, universal installer, step 4 - choose JVM
> When installer is launched from command line, the Default JVM path is correct - /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home
> ^ great :D
> When installer is launched by double-clicking .jar file, the Default JVM path is not right - /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
> ^ can we provide a better default value when installer is launched by this method?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3111) Improve error for default java on OS X
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3111?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3111:
--------------------------------
Labels: respin-a (was: )
> Improve error for default java on OS X
> --------------------------------------
>
> Key: JBDS-3111
> URL: https://issues.jboss.org/browse/JBDS-3111
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta3
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Minor
> Labels: respin-a
> Fix For: 8.0.0.CR1
>
> Attachments: default-java.png
>
>
> This is a follow up of JBDS-3014.
> When you double click the installer in Finder on OS X, the default java located in /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home will now be rejected with an error because apparently that is just the JRE, not JDK.
> !default-java.png!
> But the error is a bit vague.
> Max suggested this:
> {quote}
> Should say something like JDK does not work, need to be a full JDK Java 7 or higher or similar if user point to a broken jdk.
> and if the folder does not contain anything it should not make it sound that a JDK is actually there
> {quote}
> Even better, we could find the location of real JDK and offer that first.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-15678) "Mark as deployable" visible twice in menu
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15678?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-15678.
------------------------------------
Resolution: Partially Completed
Resolving as partially completed.
> "Mark as deployable" visible twice in menu
> ------------------------------------------
>
> Key: JBIDE-15678
> URL: https://issues.jboss.org/browse/JBIDE-15678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, server
> Affects Versions: 4.1.0.Final
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: ContextMenu.png, EditMenu.png
>
>
> Test case:
> 1. Open any .html or .xhtml file in Visual Page Editor
> 2. Check menu "Edit"
> FAIL:
> !EditMenu.png!
> 3. Check context menu
> FAIL:
> !ContextMenu.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months