[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2669 at 1/6/14 10:55 AM:
-----------------------------------------------------------
+1 to Mickael's idea. So we would therefore have one of these two:
*Option A*
{quote}
com.jboss.jbds.product => *com.jboss.devstudio.product.plugin*
com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package*
{quote}
*Option B*
{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package*
{quote}
Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package", like this?
*Option C*
{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package*
{quote}
was (Author: nickboldt):
+1 to Mickael's idea. So we would therefore have one of these two:
*Option A*
{quote}
com.jboss.jbds.product => *com.jboss.devstudio.product.plugin*
com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package*
{quote}
*Option B*
{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package*
{quote}
Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package" this?
*Option C*
{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package*
{quote}
> rename/refactor JBDS product .feature / plugin / .product to have less confusing names
> --------------------------------------------------------------------------------------
>
> Key: JBDS-2669
> URL: https://issues.jboss.org/browse/JBDS-2669
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, installer, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Priority: Critical
> Fix For: 8.0.0.Alpha2
>
>
> We should consider some better names for these artifacts so they collide less and are more obvious which is which.
> 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c...
> ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site
> 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co...
> ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true
> 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j...
> ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product"
--
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
11 years, 9 months
[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2669 at 1/6/14 10:56 AM:
-----------------------------------------------------------
+1 to Mickael's idea. Also like Denis' idea of switching to com.redhat.jbdevstudio instead of com.jboss.devstudio, but not sure if we're allowed to use a com.redhat namespace.
So we would therefore have something like this:
*Option A*
{quote}
com.jboss.jbds.product => *com.jboss.devstudio.product.plugin*
com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package*
{quote}
*Option B*
{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package*
{quote}
Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package", like this?
*Option C*
{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package*
{quote}
[~maxandersen] [~dgolovin] [~mickael_istria] WDYT?
was (Author: nickboldt):
+1 to Mickael's idea. So we would therefore have one of these two:
*Option A*
{quote}
com.jboss.jbds.product => *com.jboss.devstudio.product.plugin*
com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package*
{quote}
*Option B*
{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package*
{quote}
Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package", like this?
*Option C*
{quote}
com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin*
com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature*
com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package*
{quote}
> rename/refactor JBDS product .feature / plugin / .product to have less confusing names
> --------------------------------------------------------------------------------------
>
> Key: JBDS-2669
> URL: https://issues.jboss.org/browse/JBDS-2669
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, installer, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Priority: Critical
> Fix For: 8.0.0.Alpha2
>
>
> We should consider some better names for these artifacts so they collide less and are more obvious which is which.
> 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c...
> ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site
> 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co...
> ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true
> 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j...
> ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product"
--
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
11 years, 9 months
[JBoss JIRA] (JBDS-2866) CordovaSim Debugger
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2866:
-----------------------------------
Do you have a HD version of this video? It is hard to see the differences due to the low resolution. For instance, it would appear that you are not using the JS editors in Eclipse but some 3rd party window for JS editing.
> CordovaSim Debugger
> -------------------
>
> Key: JBDS-2866
> URL: https://issues.jboss.org/browse/JBDS-2866
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: browsersim, requirements
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Attachments: DevToolsMenu.png
>
>
> The current FireBug Lite in CordovaSim has the following limitations:
> 1) When using LiveReload, the window closes with every reload
> 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready
> http://screencast.com/t/RRGhV9PV
> Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message
--
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
11 years, 9 months
[JBoss JIRA] (JBIDE-6184) Error while adding re-deployments on EAP-5
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6184?page=com.atlassian.jira.plugin... ]
Rob Stryker resolved JBIDE-6184.
--------------------------------
Resolution: Done
> Error while adding re-deployments on EAP-5
> ------------------------------------------
>
> Key: JBIDE-6184
> URL: https://issues.jboss.org/browse/JBIDE-6184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.1.0.GA
> Reporter: Libor Zoubek
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 3.2.0.Final, 3.1.1
>
> Attachments: JBIDE-6184_jbt.patch, server.log
>
>
> Steps to reproduce:
> 1. create EAR (with application.xml)
> 2. create web project 1 and add it to EAR
> 3. deploy EAR on EAP-5.0.GA (4.3 is not affected by this issue)
> 4. Create web project 2 add add it to EAR
> You should get same exception as attached in server.log
> Adapter is then in bad state, clicking on Full Republish on EAR in server view does not even help to get project 2 deployed. The only way is to remove and add EAR to server
--
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
11 years, 9 months
[JBoss JIRA] (JBIDE-6184) Error while adding re-deployments on EAP-5
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6184?page=com.atlassian.jira.plugin... ]
Rob Stryker closed JBIDE-6184.
------------------------------
> Error while adding re-deployments on EAP-5
> ------------------------------------------
>
> Key: JBIDE-6184
> URL: https://issues.jboss.org/browse/JBIDE-6184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.1.0.GA
> Reporter: Libor Zoubek
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 3.1.1, 3.2.0.Final
>
> Attachments: JBIDE-6184_jbt.patch, server.log
>
>
> Steps to reproduce:
> 1. create EAR (with application.xml)
> 2. create web project 1 and add it to EAR
> 3. deploy EAR on EAP-5.0.GA (4.3 is not affected by this issue)
> 4. Create web project 2 add add it to EAR
> You should get same exception as attached in server.log
> Adapter is then in bad state, clicking on Full Republish on EAR in server view does not even help to get project 2 deployed. The only way is to remove and add EAR to server
--
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
11 years, 9 months
[JBoss JIRA] (JBIDE-6184) Error while adding re-deployments on EAP-5
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6184?page=com.atlassian.jira.plugin... ]
Rob Stryker updated JBIDE-6184:
-------------------------------
Fix Version/s: 3.2.0.Final
(was: 3.2.x)
> Error while adding re-deployments on EAP-5
> ------------------------------------------
>
> Key: JBIDE-6184
> URL: https://issues.jboss.org/browse/JBIDE-6184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.1.0.GA
> Reporter: Libor Zoubek
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 3.1.1, 3.2.0.Final
>
> Attachments: JBIDE-6184_jbt.patch, server.log
>
>
> Steps to reproduce:
> 1. create EAR (with application.xml)
> 2. create web project 1 and add it to EAR
> 3. deploy EAR on EAP-5.0.GA (4.3 is not affected by this issue)
> 4. Create web project 2 add add it to EAR
> You should get same exception as attached in server.log
> Adapter is then in bad state, clicking on Full Republish on EAR in server view does not even help to get project 2 deployed. The only way is to remove and add EAR to server
--
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
11 years, 9 months
[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-2864:
-----------------------------------
Description:
Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift.
We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy
There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks...
was:
Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift.
We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy
> Support faster turnarounds (with possibly hot deploy)
> -----------------------------------------------------
>
> Key: JBDS-2864
> URL: https://issues.jboss.org/browse/JBDS-2864
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
>
> Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift.
> We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy
> There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks...
--
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
11 years, 9 months
[JBoss JIRA] (JBDS-2866) CordovaSim Debugger
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk commented on JBDS-2866:
-----------------------------------
{quote}
One critical test case is...does it work with something like
$.getJSON("http://mobile-html5.rhcloud.com/rest/members", function(data)
.
.
And besides deviceready console.logs, I also need to see JS syntax errors that show up when the page loads/refreshes.
{quote}
[~burrsutter], Dev tools debugger will handle Cross Domain AJAX calls and js syntax errors. I've made a short demo video - https://www.youtube.com/watch?v=Xsv6NSozHJQ . Burr, I want to know your vision of one important point - where should dev tools debugger be opened? Now I have 2 options - it could be either Chrome browser or javaFx pop-up (javaFx WebView) !DevToolsMenu.png|thumbnail!
Each approach has pros and cons:
*Chrome Browser*
- oracle JDK 7 and 8 will be supported;
- debugger works more stable;
- more pressure on user - chrome installation is needed + need to set it as a default system browser.
*JavaFx Web View*
- debugger support out of the box
- debugger works less stable. It freezes very often while debugging - I'm working on that issue
- oracle JDK 8 only (No web websocket support in javaFx 7)
> CordovaSim Debugger
> -------------------
>
> Key: JBDS-2866
> URL: https://issues.jboss.org/browse/JBDS-2866
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: browsersim, requirements
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Attachments: DevToolsMenu.png
>
>
> The current FireBug Lite in CordovaSim has the following limitations:
> 1) When using LiveReload, the window closes with every reload
> 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready
> http://screencast.com/t/RRGhV9PV
> Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message
--
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
11 years, 9 months