[JBoss JIRA] (JBDS-2879) org.eclipse.core.net bundle is not included in p2director
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2879?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-2879.
----------------------------
> org.eclipse.core.net bundle is not included in p2director
> ---------------------------------------------------------
>
> Key: JBDS-2879
> URL: https://issues.jboss.org/browse/JBDS-2879
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
>
> Missing bundle triggers ClassNotFoundExceptions during installation:
> {code}!ENTRY org.eclipse.ecf.provider.filetransfer 4 0 2014-01-16 16:34:37.018
> !MESSAGE org.eclipse.core.runtime.Status[plugin=org.eclipse.ecf.provider.filetransfer;code=4;message=Warning: Platform proxy API not available;severity2;exception=java.lang.NoClassDefFoundError: org/eclipse/core/net/proxy/IProxyService;children=[]]
> !STACK 0
> java.lang.NoClassDefFoundError: org/eclipse/core/net/proxy/IProxyService
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.setupProxies(AbstractRetrieveFileTransfer.java:946)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:878)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570)
> at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:355)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:668)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:590)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:723)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:287)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:267)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:208)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:162)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.core.net.proxy.IProxyService cannot be found by org.eclipse.ecf.provider.filetransfer_3.2.0.v20130604-1622
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 18 more{code}
--
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
12 years, 2 months
[JBoss JIRA] (JBDS-2293) deprecation warning in installer build - warning: sun.swing.DefaultLookup is Sun proprietary API and may be removed in a future release
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2293?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-2293.
----------------------------
> deprecation warning in installer build - warning: sun.swing.DefaultLookup is Sun proprietary API and may be removed in a future release
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2293
> URL: https://issues.jboss.org/browse/JBDS-2293
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 6.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
>
> {code}
> cd ~/trunk/product
> mvn clean install
> ...
> buildcustompanels:
> [echo] Building panels ...
> [echo] Build properties written to /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/../../jbds-echoproperties.txt
> [mkdir] Created dir: /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/classes
> [mkdir] Created dir: /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/izpack-panels
> [unjar] Expanding: /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/IzPack-4.3.4/lib/standalone-compiler.jar into /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/izpack-panels
> [javac] Compiling 29 source files to /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/target/classes
> /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/src/panels/com/jboss/jbds/installer/ErrorUtils.java:21: warning: sun.swing.DefaultLookup is Sun proprietary API and may be removed in a future release
> import sun.swing.DefaultLookup;
> ^
> /home/nboldt/eclipse/workspace-jboss/devstudio_trunk/product/installer/src/panels/com/jboss/jbds/installer/ErrorUtils.java:32: warning: sun.swing.DefaultLookup is Sun proprietary API and may be removed in a future release
> Icon icon = (Icon)DefaultLookup.get(label, label.getUI(), "OptionPane.errorIcon");
> ^
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 2 warnings
> {code}
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-16592 at 2/19/14 1:22 AM:
-----------------------------------------------------------------
{quote}How about three options for the labelling text: installed, not installed, installed and update available?{quote}
Yes, that's what should happen. The update mechanism is not yet ready, but when it is, I thought about making status orange with label "Update Available".
Also, keep in mind that with JBIDE-16375, new status will be introduced.
{quote}If 'show installed' check box is going, how about continuing to show 'installed' items as greyed out and only 'not installed' and 'installed and update available' items in technicolor? I think the use of greyed out text is very powerful - it immediately conveys to the user that they're already got this item (expect uninstall it).{quote}
I've given a try to this, and the issue with "Show installed" and grey items is that it makes users first believe that the grey item is somehow disabled and that they can't perform an action on it such as uninstall. Also, the "Show installed" is not enough for filtering: we might also want to Show/Hide available updates. Later, with JBIDE-16375, we might want to show/hide stuff that is early-access...
{quote}I like the use of Eclipse Marketplace's install/uninstall buttons over a drop down list but I see that that is difficult to implement here as we want users to be able to select multiple items to modify with one action.{quote}
Same here, anticipating JBIDE-16375, the possible set of actions for let's say a given installed connector could be Update, Install Early-Access or Uninstall. This multiplicity of action makes that buttons won't really scale. Also, depending on the status of the unit, different actions will be available, and even different number of actions. That's why I believe a selection widget (such as a combo) is more relevent here.
What if I make the default text on combo "Select action...". Would it be better?
I'm not against usage of buttons, but I don't see how they can play well with the variety of actions available. Maybe you could draft some (either on a paper, or Eclipse WindowBuilder or wireframe sketcher), so I'd understand better what you have in mind.
{quote}I wonder whether it would look any better if the 'Installed' text and drop down box went at the end of the row rather than the beginning? That way the item name is the focal point. But without distinguishing items that are already installed and have no updates by greying out the name, the user might not immediately see which items have not pending actions.{quote}
I'll give it a try.
{quote}One niggle that I can see is that if this is to be the only method to notify users of updates then it means users have to be checking JBoss Central updates tab regularly. I guess that's why pop-up windows are so effective. Could a small circle with a + sign be added to the JBoss Central Updates tab label to indicate an update is available for an already installed item? I guess this is quite a universal language like when the Apple App Store icon has a '1' adornment to indicate an update is available for an app you have installed.{quote}
As far as I know, there is nothing like this (notifications on available updates) currently available in JBT/JBDS. This is for sure a good idea, can you please create another Jira for that?
was (Author: mickael_istria):
{quote}How about three options for the labelling text: installed, not installed, installed and update available?{quote}
Yes, that's what should happen. The update mechanism is not yet ready, but when it is, I thought about making status orange with label "Update Available".
Also, keep in mind that with JBIDE-16375, new status will be introduced.
{quote}If 'show installed' check box is going, how about continuing to show 'installed' items as greyed out and only 'not installed' and 'installed and update available' items in technicolor? I think the use of greyed out text is very powerful - it immediately conveys to the user that they're already got this item (expect uninstall it).{quote}
I've given a try to this, and the issue with "Show installed" and grey items is that it makes users first believe that the grey item is somehow disabled and that they can't perform an action on it -such as uninstall-. Also, the "Show installed" is not enough for filtering: we might also want to Show/Hide available updates. Later, with JBIDE-16375, we might want to show/hide stuff that is early-access...
{quote}I like the use of Eclipse Marketplace's install/uninstall buttons over a drop down list but I see that that is difficult to implement here as we want users to be able to select multiple items to modify with one action.{quote}
Same here, anticipating JBIDE-16375, the possible set of actions for let's say a given installed connector could be Update, Install Early-Access or Uninstall. This multiplicity of action makes that buttons won't really scale. Also, depending on the status of the unit, different actions will be available, and even different number of actions. That's why I believe a selection widget (such as a combo) is more relevent here.
What if I make the default text on combo "Select action...". Would it be better?
I'm not against usage of buttons, but I don't see how they can play well with the variety of actions available. Maybe you could draft some (either on a paper, or Eclipse WindowBuilder or wireframe sketcher), so I'd understand better what you have in mind.
{quote}I wonder whether it would look any better if the 'Installed' text and drop down box went at the end of the row rather than the beginning? That way the item name is the focal point. But without distinguishing items that are already installed and have no updates by greying out the name, the user might not immediately see which items have not pending actions.{quote}
I'll give it a try
{quote}One niggle that I can see is that if this is to be the only method to notify users of updates then it means users have to be checking JBoss Central updates tab regularly. I guess that's why pop-up windows are so effective. Could a small circle with a + sign be added to the JBoss Central Updates tab label to indicate an update is available for an already installed item? I guess this is quite a universal language like when the Apple App Store icon has a '1' adornment to indicate an update is available for an app you have installed.{qupte}
As far as I know, there is nothing like this (notifications on available updates) currently available in JBT/JBDS. This is for sure a good idea, can you please create another Jira for that?
> Allow to update/remove software installed from Central
> ------------------------------------------------------
>
> Key: JBIDE-16592
> URL: https://issues.jboss.org/browse/JBIDE-16592
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta1
>
> Attachments: JBIDE-16592-wip.jpeg, JBIDE_16592_shot2.jpeg
>
>
> Central software page should allow user to update or uninstall some modules.
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-16592 at 2/19/14 1:21 AM:
-----------------------------------------------------------------
{quote}How about three options for the labelling text: installed, not installed, installed and update available?{quote}
Yes, that's what should happen. The update mechanism is not yet ready, but when it is, I thought about making status orange with label "Update Available".
Also, keep in mind that with JBIDE-16375, new status will be introduced.
{quote}If 'show installed' check box is going, how about continuing to show 'installed' items as greyed out and only 'not installed' and 'installed and update available' items in technicolor? I think the use of greyed out text is very powerful - it immediately conveys to the user that they're already got this item (expect uninstall it).{quote}
I've given a try to this, and the issue with "Show installed" and grey items is that it makes users first believe that the grey item is somehow disabled and that they can't perform an action on it -such as uninstall-. Also, the "Show installed" is not enough for filtering: we might also want to Show/Hide available updates. Later, with JBIDE-16375, we might want to show/hide stuff that is early-access...
{quote}I like the use of Eclipse Marketplace's install/uninstall buttons over a drop down list but I see that that is difficult to implement here as we want users to be able to select multiple items to modify with one action.{quote}
Same here, anticipating JBIDE-16375, the possible set of actions for let's say a given installed connector could be Update, Install Early-Access or Uninstall. This multiplicity of action makes that buttons won't really scale. Also, depending on the status of the unit, different actions will be available, and even different number of actions. That's why I believe a selection widget (such as a combo) is more relevent here.
What if I make the default text on combo "Select action...". Would it be better?
I'm not against usage of buttons, but I don't see how they can play well with the variety of actions available. Maybe you could draft some (either on a paper, or Eclipse WindowBuilder or wireframe sketcher), so I'd understand better what you have in mind.
{quote}I wonder whether it would look any better if the 'Installed' text and drop down box went at the end of the row rather than the beginning? That way the item name is the focal point. But without distinguishing items that are already installed and have no updates by greying out the name, the user might not immediately see which items have not pending actions.{quote}
I'll give it a try
{quote}One niggle that I can see is that if this is to be the only method to notify users of updates then it means users have to be checking JBoss Central updates tab regularly. I guess that's why pop-up windows are so effective. Could a small circle with a + sign be added to the JBoss Central Updates tab label to indicate an update is available for an already installed item? I guess this is quite a universal language like when the Apple App Store icon has a '1' adornment to indicate an update is available for an app you have installed.{qupte}
As far as I know, there is nothing like this (notifications on available updates) currently available in JBT/JBDS. This is for sure a good idea, can you please create another Jira for that?
was (Author: mickael_istria):
> How about three options for the labelling text: installed, not installed, installed and update available?
Yes, that's what should happen. The update mechanism is not yet ready, but when it is, I thought about making status orange with label "Update Available".
Also, keep in mind that with JBIDE-16375, new status will be introduced.
> If 'show installed' check box is going, how about continuing to show 'installed' items as greyed out and only 'not installed' and 'installed and update available' items in technicolor? I think the use of greyed out text is very powerful - it immediately conveys to the user that they're already got this item (expect uninstall it).
I've given a try to this, and the issue with "Show installed" and grey items is that it makes users first believe that the grey item is somehow disabled and that they can't perform an action on it -such as uninstall-. Also, the "Show installed" is not enough for filtering: we might also want to Show/Hide available updates. Later, with JBIDE-16375, we might want to show/hide stuff that is early-access...
> I like the use of Eclipse Marketplace's install/uninstall buttons over a drop down list but I see that that is difficult to implement here as we want users to be able to select multiple items to modify with one action.
Same here, anticipating JBIDE-16375, the possible set of actions for let's say a given installed connector could be Update, Install Early-Access or Uninstall. This multiplicity of action makes that buttons won't really scale. Also, depending on the status of the unit, different actions will be available, and even different number of actions. That's why I believe a selection widget (such as a combo) is more relevent here.
What if I make the default text on combo "Select action...". Would it be better?
I'm not against usage of buttons, but I don't see how they can play well with the variety of actions available. Maybe you could draft some (either on a paper, or Eclipse WindowBuilder or wireframe sketcher), so I'd understand better what you have in mind.
> I wonder whether it would look any better if the 'Installed' text and drop down box went at the end of the row rather than the beginning? That way the item name is the focal point. But without distinguishing items that are already installed and have no updates by greying out the name, the user might not immediately see which items have not pending actions.
I'll give it a try
> One niggle that I can see is that if this is to be the only method to notify users of updates then it means users have to be checking JBoss Central updates tab regularly. I guess that's why pop-up windows are so effective. Could a small circle with a + sign be added to the JBoss Central Updates tab label to indicate an update is available for an already installed item? I guess this is quite a universal language like when the Apple App Store icon has a '1' adornment to indicate an update is available for an app you have installed.
As far as I know, there is nothing like this (notifications on available updates) currently available in JBT/JBDS. This is for sure a good idea, can you please create another Jira for that?
> Allow to update/remove software installed from Central
> ------------------------------------------------------
>
> Key: JBIDE-16592
> URL: https://issues.jboss.org/browse/JBIDE-16592
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta1
>
> Attachments: JBIDE-16592-wip.jpeg, JBIDE_16592_shot2.jpeg
>
>
> Central software page should allow user to update or uninstall some modules.
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16592:
----------------------------------------
> How about three options for the labelling text: installed, not installed, installed and update available?
Yes, that's what should happen. The update mechanism is not yet ready, but when it is, I thought about making status orange with label "Update Available".
Also, keep in mind that with JBIDE-16375, new status will be introduced.
> If 'show installed' check box is going, how about continuing to show 'installed' items as greyed out and only 'not installed' and 'installed and update available' items in technicolor? I think the use of greyed out text is very powerful - it immediately conveys to the user that they're already got this item (expect uninstall it).
I've given a try to this, and the issue with "Show installed" and grey items is that it makes users first believe that the grey item is somehow disabled and that they can't perform an action on it -such as uninstall-. Also, the "Show installed" is not enough for filtering: we might also want to Show/Hide available updates. Later, with JBIDE-16375, we might want to show/hide stuff that is early-access...
> I like the use of Eclipse Marketplace's install/uninstall buttons over a drop down list but I see that that is difficult to implement here as we want users to be able to select multiple items to modify with one action.
Same here, anticipating JBIDE-16375, the possible set of actions for let's say a given installed connector could be Update, Install Early-Access or Uninstall. This multiplicity of action makes that buttons won't really scale. Also, depending on the status of the unit, different actions will be available, and even different number of actions. That's why I believe a selection widget (such as a combo) is more relevent here.
What if I make the default text on combo "Select action...". Would it be better?
I'm not against usage of buttons, but I don't see how they can play well with the variety of actions available. Maybe you could draft some (either on a paper, or Eclipse WindowBuilder or wireframe sketcher), so I'd understand better what you have in mind.
> I wonder whether it would look any better if the 'Installed' text and drop down box went at the end of the row rather than the beginning? That way the item name is the focal point. But without distinguishing items that are already installed and have no updates by greying out the name, the user might not immediately see which items have not pending actions.
I'll give it a try
> One niggle that I can see is that if this is to be the only method to notify users of updates then it means users have to be checking JBoss Central updates tab regularly. I guess that's why pop-up windows are so effective. Could a small circle with a + sign be added to the JBoss Central Updates tab label to indicate an update is available for an already installed item? I guess this is quite a universal language like when the Apple App Store icon has a '1' adornment to indicate an update is available for an app you have installed.
As far as I know, there is nothing like this (notifications on available updates) currently available in JBT/JBDS. This is for sure a good idea, can you please create another Jira for that?
> Allow to update/remove software installed from Central
> ------------------------------------------------------
>
> Key: JBIDE-16592
> URL: https://issues.jboss.org/browse/JBIDE-16592
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta1
>
> Attachments: JBIDE-16592-wip.jpeg, JBIDE_16592_shot2.jpeg
>
>
> Central software page should allow user to update or uninstall some modules.
--
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
12 years, 2 months