[JBoss JIRA] (JBIDE-10986) Installing "Abridged" impossible to make an RSE connection to remote linux machine
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-10986:
-----------------------------------
Summary: Installing "Abridged" impossible to make an RSE connection to remote linux machine
Key: JBIDE-10986
URL: https://issues.jboss.org/browse/JBIDE-10986
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
When installing an 'abridged' installation, attempting to create a new remote system connection shows very few options, not including ability to select several subsystems.
Steps:
1) Open remote system explorer
2) right click -> new -> connection
3) select 'linux', next
4) type in proper host name, next
5) verify next page is option to select file subsystem (fail)
6) verify next page is option to select process subsystem (fail)
7) verify next page is option to select shell subsystem
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBIDE-9693) There is no way to delete remote hosts in System Deployment UI.
by Jaroslav Jankovič (JIRA)
There is no way to delete remote hosts in System Deployment UI.
---------------------------------------------------------------
Key: JBIDE-9693
URL: https://issues.jboss.org/browse/JBIDE-9693
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Reporter: Jaroslav Jankovič
Assignee: Rob Stryker
Fix For: 3.3.0.M4
1. double click on server in Servers view
2. in Server Behaviour, choose "Remote System Deployment" in combobox
Adding new host can be done by click "New Host..." but removing added hosts cannot be done through this UI. In my opinion we should provide an easy way for removing hosts for remote deployment too.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
by Fred Bricon (JIRA)
[regression] - Exported files don't honor the module assembly settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Environment: Vista, eclipse 3.5.1, JBT 3.1.CR1
Reporter: Fred Bricon
Assignee: Rob Stryker
I'm investigating ways to implement SAR support in m2eclipse (for selfish motivations I agree). See https://issues.sonatype.org/browse/MNGECLIPSE-1984.
A SAR project would need to export dependencies in a lib folder, inside the archive.
During my investigation, I tried to use the JBT 3.1.CR1 module assembly page, which would, from my understanding, allow me to reach the desired effect.
So I've created sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/" handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project (which totally sucks). I've manually tweaked org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed. Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/" source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar" deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
Now, when exporting earproject.ear, there's no junit.jar to be found in sarproject.sar (not expected) nor in the ear (expected).
When using export module on sarproject, the resulting file doesn't contain junit.jar either.
This looks like a bug I've opened at eclipse's bugzilla for Connector projects : https://bugs.eclipse.org/bugs/show_bug.cgi?id=298735
The module assembly page looks very promising in theory, as it would allow support for any kind of archives (sar, har ...)
but from what I understand it's only usable for ear and war projects.
This bug should probably be opened at eclipse.org or is totally a duplicate of #298735 (you tell me),
but I think the module assembly page should not be visible on unsupported projects.
regards,
Fred Bricon
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (JBIDE-9863) ProjectExamplesFix assumes the Eclipse project name is identical to the Example name
by Fred Bricon (Created) (JIRA)
ProjectExamplesFix assumes the Eclipse project name is identical to the Example name
--------------------------------------------------------------------------------------
Key: JBIDE-9863
URL: https://issues.jboss.org/browse/JBIDE-9863
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.3.0.M3
Reporter: Fred Bricon
Assignee: Snjezana Peco
Fix For: 3.3.0.M4
When creating a project example from a maven archetype, the created Eclipse project ends up having a different name (user defined) than the original project example.
Implementations of ProjectExamplesFix rely on ProjectExamplesActivator.getEclipseProject(project, fix); to infer the generated eclipse project.
Since eclipse projects and archetype have a different name (more so in the case of archetype creating multiple projects), no fixes can be applied.
My opinion is we should modify the Import Job API so that it returns the list of created IProjects, then pass that list all along to the ProjectExamplesFix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (JBIDE-10009) project examples should provide way to set the output direcotry
by Max Rydahl Andersen (Created) (JIRA)
project examples should provide way to set the output direcotry
---------------------------------------------------------------
Key: JBIDE-10009
URL: https://issues.jboss.org/browse/JBIDE-10009
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
noticed today that project examples goes into a hidden workspace folder instead of where users normally store their projects.
i.e. /Users/max/Documents/workspaces/jbosstools-trunk/.JBossToolsMavenProjects/numberguess/jboss-as-numberguess
it should at least be /Users/max/Documents/workspaces/jbosstools-trunk/numberguess/jboss-as-numberguess
and optimally users should be able to say which root directory they want projects downloaded by an example goes to.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (JBIDE-11133) Different Git repository layout then OpenShift expects
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-11133:
---------------------------------------
Summary: Different Git repository layout then OpenShift expects
Key: JBIDE-11133
URL: https://issues.jboss.org/browse/JBIDE-11133
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Environment: JBT Beta1b
Reporter: Lucia Jelinkova
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
When trying to enable an OpenShift application for a project that is in different Git repository this scenario did not worked for me:
# WorkspaceA: Create Dynamic Web Project
# WorkspaceA: Team -> Share Project -> Create a new repository
# WorkspaceA: Create a new repository in a local folder
# WorkspaceA: Push all changes
# WorkspaceB: File -> Import -> Projects from Git -> Uri -> Local file
# WorkspaceB: Select local repository created in step 3 and import the project into the workspace
# WorkspaceB: Create a new OpenShift application and enable it with the imported project
# Publish the server of push changes to openshift
Console output:
Stopping application...
Done
Emptying tmp dir: /var/lib/libra/fd01187ca404461081e35495ea2ead41/new/jbossas-7.0/standalone/tmp/vfs
Emptying tmp dir: /var/lib/libra/fd01187ca404461081e35495ea2ead41/new/jbossas-7.0/standalone/tmp/work
Starting application...
Done
I suppose that the maven pom file has not been executed and it's because the repository layout is not as expected:
Expected: repository/pom.xml
Reality: repository/project/pom.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months