[JBoss JIRA] (JBDS-2758) No repository found error message after installation Spring and Mylyn bugzilla connector
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2758?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen reassigned JBDS-2758:
-----------------------------------------
Assignee: Jiri Peterka (was: Nick Boldt)
[~jpeterka] please verify if this is still an issue for you or not. if not, then please reject this as cannot reproduce and if it is an issue provide details/answers [~nickboldt] is asking for. thanks.
> No repository found error message after installation Spring and Mylyn bugzilla connector
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-2758
> URL: https://issues.jboss.org/browse/JBDS-2758
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification
> Affects Versions: 7.1.0.Alpha1
> Environment: JBDS 7.1.0.Alpha1, L64
> Reporter: Jiri Peterka
> Assignee: Jiri Peterka
> Attachments: no-repository-found.png
>
>
> No repository found at file:/home/jpeterka/ide/test/jbds71a1/studio/configuration/org.eclipse.osgi/bundles/308/data/listener_1925729951/
--
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-16351) FixClasspathConfigurator isn't obliged in a newer m2e
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16351:
---------------------------------------
I have checked wfk seam examples. They work correctly without this configurator.
I think we can apply this PR to 4.1.x too.
> FixClasspathConfigurator isn't obliged in a newer m2e
> -----------------------------------------------------
>
> Key: JBIDE-16351
> URL: https://issues.jboss.org/browse/JBIDE-16351
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Fix For: 4.2.0.Alpha2
>
>
> The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433.
> The issue happens with a mavenized seam 2 project that has a flat layout structure.
> This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project.
> It is the configurator for maven-compiler-plugin so it is called for every Java project.
> Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies)
> The solution:
> - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).
--
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] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ]
Andre Dietisheim commented on TOOLSDOC-447:
-------------------------------------------
[~mmurray] +1
> Explain how to configure SSL options for connecting to Enterprise Servers.
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-447
> URL: https://issues.jboss.org/browse/TOOLSDOC-447
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide - OpenShift Tools
> Affects Versions: 4.1.1
> Environment: Build Name: 22443, User Guide-7.1
> Build Date: 11-12-2013 15:10:49
> Topic ID: 25166-566980 [Latest]
> Reporter: Eric Rich
> Assignee: Michelle Murray
> Priority: Minor
> Fix For: 4.1.1, 4.2.0
>
>
> Title: Customizing Overview
> Describe the issue:
> It would be good to explain configuration options for connecting to multiple or different Enterprise Servers.
> Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful.
> Suggestions for improvement:
> Additional information:
--
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-16401) OpenShift Explorer: Same connection as two different connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16401?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-16401.
--------------------------------------
Resolution: Rejected
@Marian: This is expected. If you have a connection to the default server, then the default server is not stored with it. We only store the username (and possibly the password). The server used for this connection is the one that your express.conf is pointing to. So once you change the server in express.conf the connection to the default server is pointing to the new (default) server in your express.conf. The connection that was using the same server but not using the default server is still pointing to the very same server (that was the default server before changing it in express.conf).
> OpenShift Explorer: Same connection as two different connections
> ----------------------------------------------------------------
>
> Key: JBIDE-16401
> URL: https://issues.jboss.org/browse/JBIDE-16401
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
>
> It allows to have 2 "different" connections for one connection - 2 items in OpenShift Explorer view for same thing.
> Steps to reproduce:
> 1. EXEC: Open OpenShift explorer view
> 2. EXEC: Create connection to default OpenShift server with some credentials (checkbox for default server MUST BE checked)
> 3. ASSERT: Have connection in view with label "user server (default)"
> 4. EXEC: Open new connection shell (to create new connection)
> 5. EXEC: Uncheck checkbox for default server, but leave the same name and provide same credentials as in step 2.
> 6. EXEC: Confirm connection creation
> 7. ASSERT: There are now 2 "different" connections for same connection in OpenShift explorer view (e.g. "mlabuda(a)redhat.com openshift.redhat.com (default)" and "mlabuda(a)redhat.com openshift.redhat.com").
> Probably connections are distinguished by labels, I guess.
--
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