[JBoss JIRA] (JBIDE-11524) Rename jobs, sites, profiles, variables... to clearer names (remove reference to nightly)
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-11524:
--------------------------------------
Summary: Rename jobs, sites, profiles, variables... to clearer names (remove reference to nightly)
Key: JBIDE-11524
URL: https://issues.jboss.org/browse/JBIDE-11524
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Nick Boldt
Priority: Minor
nightly is a very confusing name, that does not reflect at all what really happens.
We should prefer using "staging" in variable, profiles, jobs, url... to make it clearer
For instance,
* jbosstools-nightly-staging-composite -> jbosstools-staging-composite
* jboostools-nightly -> jbosstools-staging-aggregate
--
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, 6 months
[JBoss JIRA] Created: (JBIDE-8863) Error deploying EAR with a module having a sub-module in its component descriptor.
by Philippe Guinot (JIRA)
Error deploying EAR with a module having a sub-module in its component descriptor.
----------------------------------------------------------------------------------
Key: JBIDE-8863
URL: https://issues.jboss.org/browse/JBIDE-8863
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: core
Affects Versions: 3.2.0.Final
Environment: Tested with Eclipse Indigo Release 20110319-2305 with latest nightly build trunk of JBoss Tools.
Deploying on a JBoss 4.2 server.
Reporter: Philippe Guinot
Assignee: Max Rydahl Andersen
h3.Context:
For some reasons I have to deploy an EAR webapp with (in its libs) a jar containing itself another jar.
h3.Environment:
For this I have a first Java project with the following component descriptor:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="project1">
<wb-resource deploy-path="/" source-path="/src/main/java"/>
</wb-module>
</project-modules>
{code}
Then, the second Java project has the component descriptor:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="project2">
<wb-resource deploy-path="/" source-path="/src/main/java"/>
<dependent-module archiveName="project1.jar" deploy-path="/lib" handle="module:/resource/project1/project1">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{code}
Then, in Eclipse when exporting the *project2* as a *Module Archive*, I obtain a .jar file featuring both classes from *project2* and a *lib* folder with the project1 compiled jar.
Now, in the ear project I have the following lines in the component descriptor:
{code:xml}
<dependent-module archiveName=" project1.jar" deploy-path="/lib" handle="module:/resource/ project1/ project1">
<dependency-type>uses</dependency-type>
</dependent-module>
<dependent-module archiveName=" project2.jar" deploy-path="/lib" handle="module:/resource/ project2/ project2">
<dependency-type>uses</dependency-type>
</dependent-module>
{code}
(The EAR needs the 2 jars as well)
h3.Problem:
Then, when deployed into my *JBoss 4.2 Runtime* server in Eclipse, I got the following error:
{code}Error renaming C:\DEV\jboss\server\default\tmp\jbosstoolsTemp\tmp7021855122707247750.jar to C:\DEV\jboss\server\default\deploy\EAR_Project.ear\lib\project2.jar\lib\project1.jar{code}
After some research, I think an exception is thrown at *org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil.LocalCopyCallback.moveTempFile(File, File)* during the safe rename.
However, when I look to the error message I got the feeling that the publishing process want to copy the tmp jar file into a folder called "*C:\DEV\jboss\server\default\deploy\EAR_Project.ear\lib\project2.jar\lib\*" which can not work because "*C:\DEV\jboss\server\default\deploy\EAR_Project.ear\lib\project2.jar*" is a file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-11912) Improve SSH key management
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-11912:
----------------------------------------
Summary: Improve SSH key management
Key: JBIDE-11912
URL: https://issues.jboss.org/browse/JBIDE-11912
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.x
Initially OpenShift was only able to handle a single unique SSH (rsa) key. A user also had to provide his key when creating the domain.
Things evolved a lot since then. The current OpenShift release supports
- multiple keys
- rsa and dsa keys
- keys are not required when creating a domain
Our tooling still offers what we implemented when OpenShift required one to provide his single key when creating the domain. We require the user to create/provide his key when he wants to create his domain.
!create-domain.png!
Furthermore we also force the key-name to libra_id_rsa. We did that to avoid conflicts with the config (<home>/.ssh/config) that the rhc CLI tools create.
--
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, 6 months
[JBoss JIRA] (JBIDE-12298) Missing Requirement installing JBoss Extension
by Pete Miller (JIRA)
Pete Miller created JBIDE-12298:
-----------------------------------
Summary: Missing Requirement installing JBoss Extension
Key: JBIDE-12298
URL: https://issues.jboss.org/browse/JBIDE-12298
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.2.0.Final
Environment: Juno Java with J2EE added, under 64-bit JDK 1.7.0
Reporter: Pete Miller
Assignee: Rob Stryker
Get the following after trying to install new JBossAS Tools Extenion under Servers:
http://download.eclipse.org/webtools/downloads/drops/R3.4.0/I-3.4.0-20120...
Cannot complete the install because one or more required items could not be found.
Software being installed: JBossAS Tools 2.3.0.v20120504-0300-H103-Beta3 (org.jboss.ide.eclipse.as.feature.feature.group 2.3.0.v20120504-0300-H103-Beta3)
Missing requirement: JBoss AS Core Plug-in 2.3.0.v20120504-0300-H103-Beta3 (org.jboss.ide.eclipse.as.core 2.3.0.v20120504-0300-H103-Beta3) requires 'bundle org.eclipse.pde.core 3.7.0' but it could not be found
Cannot satisfy dependency:
From: JBossAS Tools Server / Compression Integration 2.3.0.v20120504-0300-H103-Beta3 (org.jboss.ide.eclipse.as.archives.integration.feature.feature.group 2.3.0.v20120504-0300-H103-Beta3)
To: org.jboss.ide.eclipse.as.core 0.0.0
Cannot satisfy dependency:
From: JBossAS Tools 2.3.0.v20120504-0300-H103-Beta3 (org.jboss.ide.eclipse.as.feature.feature.group 2.3.0.v20120504-0300-H103-Beta3)
To: org.jboss.ide.eclipse.as.archives.integration.feature.feature.group [2.3.0.v20120504-0300-H103-Beta3]
--
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, 6 months