[JBoss JIRA] (JBIDE-16357) ApplicationWizard: RemoteSystemsTempFiles is possible to choose in OpenShift select project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16357?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16357:
------------------------------------------
I looked up how RSE does things:
They're offering a resource filter for the explorer that filter out what they call Internal RSE projects:
{code:title=https://eclipse.googlesource.com/tm/org.eclipse.tm/+/b896bfa678aa814c531c2cce558aa3fb56d9db40/rse/plugins/org.eclipse.rse.ui/plugin.properties}
ProjectFilter.label=RSE Internal Projects
ProjectFilter.description=Hides RSE internal projects
{code}
What they do is to filter upon project name ("RemoteSystems*"):
{code:title=https://eclipse.googlesource.com/tm/org.eclipse.tm/+/b896bfa678aa814c531c2cce558aa3fb56d9db40/rse/plugins/org.eclipse.rse.ui/plugin.xml}
<commonFilter
id="org.eclipse.rse.project.filters.RemoteSystemsProjects"
name="%ProjectFilter.label"
description="%ProjectFilter.description"
activeByDefault="true">
<filterExpression>
<and>
<instanceof value="org.eclipse.core.resources.IProject"/>
<test property="org.eclipse.core.resources.name" value="RemoteSystems*"/>
</and>
</filterExpression>
</commonFilter>
{code}
I thus suggest that we do the same, even though it's not a nicelooking fix.
> ApplicationWizard: RemoteSystemsTempFiles is possible to choose in OpenShift select project
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-16357
> URL: https://issues.jboss.org/browse/JBIDE-16357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Burr Sutter
>
> The Select Existing Project dialog should not display
> RemoteSystemTempFiles as an option
> http://screencast.com/t/CKEnB16Rbad
--
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, 5 months
[JBoss JIRA] (JBIDE-16357) ApplicationWizard: RemoteSystemsTempFiles is possible to choose in OpenShift select project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16357?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16357:
------------------------------------------
Our current code that filters acceptable project looks like follows:
{code}
private boolean isValid(IProject project) {
if (!project.isAccessible()) {
return false;
}
if (EGitUtils.isShared(project)) {
if (!EGitUtils.isSharedWithGit(project)) {
return false;
}
}
return true;
}
{code}
In words we accept all accessible (all opened) projects excluding non-git shared ones. Thinking this through I also dont see how we should distinguish RemoteSystemsTempFiles from other valid projects. We cannot rely on the maven nature, since the user possibly deals with PHP (or other) projects. We cannot rely on the project being WTP since pure maven project are bdidged via m2e. Hard-coding to this particular name is imho not a good solution.
> ApplicationWizard: RemoteSystemsTempFiles is possible to choose in OpenShift select project
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-16357
> URL: https://issues.jboss.org/browse/JBIDE-16357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Burr Sutter
>
> The Select Existing Project dialog should not display
> RemoteSystemTempFiles as an option
> http://screencast.com/t/CKEnB16Rbad
--
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, 5 months
[JBoss JIRA] (JBIDE-16392) Application wizard: application type is not stored/restored from preferences
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16392?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16392:
------------------------------------------
The root cause is in jbosstools-base/WizardUtils which triggers the binding to update 1) model->widget and 2) widget->model. Updating the widgets after the job was run is required since the job is synced to the wizard runnable. Before running the wizard runnable the wizard framework stores the widget states, disables all widgets and shows the progress bar. Once the runnable is finished, the wizard framework restores the widget state/enablement. The binding is not blocked by the wizard runnable/job. It possibly updated models/widgets. When the wizard framework restores the widget states (after the wizard runnable finished) it would override updated widget states and thus lead to erroneous widget states. We fix this by telling the databinding context to re-propagate model values to the widgets. Triggering updates from widgets to model is 1) unneccessary and 2) would possibly propagate erroneous widget states back to the model. We therefore eliminate these unneeded updates (widget->model) and only keep the required updates model->widget.
> Application wizard: application type is not stored/restored from preferences
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16392
> URL: https://issues.jboss.org/browse/JBIDE-16392
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
> Attachments: application-type-empty.png
>
>
--
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, 5 months
[JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14744:
---------------------------------------------
Here are some first reaction comments:
Title of first page says "choose application type" - it should say something like "choose new openshift application type or use existing application"
I'm wondering if we should call this wizard "New OpenShift Project" since it does not always create an OpenShift application...or maybe "Configure OpenShift Application" ? thinking out aloud.
On Page 1 there are three domains listed under existing applications, but on page 2 a domain is already selected when have the user chosen this domain ? From the initial login or ?
The source code field is filled out on page 2 in first usecase, is that expected ? (I think it is but not sure since it is not using a repo that looks like an openshift app ;)
Should we out Existing Applications on the top in the three ?
Can we show Featured ?
Should we maybe prepend this wizard with a binary choice: Create new OpenShift application or Use Existing application which would then change the rest of the wizard. I think that might simplify things but avoid the user to have to make that choice upfront from outside the wizard.
One page 2 in second scenario the title just says "please configure your application" - Maybe make it "You chose 'myApplication' - review and press next to continue or press back to change the application.
I've asked [~crobson] to provide input too.
> Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14744
> URL: https://issues.jboss.org/browse/JBIDE-14744
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.0.Beta1
>
> Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, openshift-quickstart.png
>
>
> The web ui offers a large set of quickstarts/templates:
> !openshift-quickstart.png!
> in a mail from clayton on the 4th of june:
> {quote}
> For QuickStarts, brokers may choose to
> a) enable community quickstarts
> (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf)
> b) enable their own list of quickstarts
> (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json)
> c) disable the quickstarts link
> (delete /etc/openshift/quickstarts.json)
> To correctly fetch the quickstarts for a server, retrieve the API document
> /broker/rest/api
> and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts. If it is absent, you should assume there are no quickstarts.
> Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific:
> * API versioning is not supported
> * Only JSON is supported
> * The body of the response is slightly different than standard REST API feed results
> * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not)
> The format of the JSON response (in either a) or b) above) is:
> {quote}
> {code}
> {
> data: [
> quickstart: {
> id: "<string id>",
> href: "<absolute URL to a display URL for the quickstart>",
> name: "<name>",
> updated: "<last update date in seconds from the epoch>",
> summary: "<brief HTML body of the item>",
> body: "<full HTML body of the item>",
> cartridges: "<cartridge spec>",
> website: "<URL of metadata about the source of the quickstart or the technology>",
> tags: "<comma delimited list of tags>",
> language: "<display name of the type of quickstart>",
> initial_git_url: "<absolute URL or Git reference to source>",
> provider: "openshift|reviewed|partner|community", # default is community
> },
> ]
> }
> {code}
> {quote}
> You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately. You should also assume that the structure could be changed at any time.
> Cartridge spec:
> The cartridge spec is defined as either:
> a) a comma delimited list of cartridge name search conditions
> b) a string containing a JSON array
> If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field.
> Otherwise,
> 1) split the string by "," into "segments"
> 2) trim whitespace from each segment
> 3) split each segment by "|" into "matches" - these represent logical ORs
> 4) strip leading and trailing "*" characters
> 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select.
> See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> {quote}
--
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, 5 months
[JBoss JIRA] (JBDS-2879) org.eclipse.core.net bundle is not included in p2director
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2879?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2879:
--------------------------------------
Fix Version/s: 7.1.1.GA
8.0.0.Alpha2
> 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: 7.1.1.GA, 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, 5 months
[JBoss JIRA] (JBDS-2879) org.eclipse.core.net bundle is not included in p2director
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2879?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2879:
-------------------------------------------
This should be fixed in 7.1.x too, right?
> 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: 7.1.1.GA, 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, 5 months
[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2635:
-------------------------------------------
Okey, but we would need similar mechanisms that izpack provides. splashscreen, legal text, panels etc.
Just trying to understand what the value we get by reimplementing these ?
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {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, 5 months
[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-2032:
--------------------------------------------
Interesting - how would that jbds extension look like ? would we need one for every link or could we go so far to dynamically replace the url ?
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
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, 5 months