[JBoss JIRA] Created: (JBIDE-9309) Easily adding full JBoss AS source
by arjan tijms (JIRA)
Easily adding full JBoss AS source
----------------------------------
Key: JBIDE-9309
URL: https://issues.jboss.org/browse/JBIDE-9309
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: arjan tijms
Assignee: Rob Stryker
The JBoss AS server runtime from JBoss tools adds a library container to the classpath of an Eclipse project. This container provides a large amount of jar files that make up JBoss AS itself and the Java EE services it offers.
Attaching the source code for this is notoriously difficult. Because it concerns a large amount of jar files, attaching source code for each jar is a rather tedious job.
For JBoss AS 5, the fact that the location of jars in the source archive was completely different from the structure exposed in Eclipse or the binary build of JBoss AS, made it very hard to actually locate the correct source jar. Sometimes even names were different, making it even harder.
For JBoss AS 6, the source archive does not even contain the source for the majority of the JBoss AS artifacts. Source for 'core functionality' (from the point of view of the Java EE developer), like Servlet and JSF is missing. The user has to hunt the Internet to find the correct source for the correct version that JBoss AS 6 uses. This makes an already tedious job even more tedious.
I would like to request functionality where the user can point to a single _jboss-src.xyz_ file that contains all sources. JBoss tools should then automatically attach the right source from the archive to the right jar from the library container. Alternatively the user could point to a maven repository (but this should not make the Eclipse project dependent on maven).
--
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-9688) Add JBoss public repository to list of default repositories in Eclipse
by Rob Cernich (JIRA)
Add JBoss public repository to list of default repositories in Eclipse
----------------------------------------------------------------------
Key: JBIDE-9688
URL: https://issues.jboss.org/browse/JBIDE-9688
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: maven
Reporter: Rob Cernich
Assignee: Fred Bricon
Priority: Minor
M2e exposes an extension point, which allows plugins to contribute repositories to be indexed. Automatically registering the JBoss repository seems like a sensible thing for JBoss Tools. This would allow the user to access the JBoss public repository from the tooling (e.g. add dependency) without requiring them to add the JBoss public repository to their settings.xml file. Of course, the user would still need to ensure that the repository was correctly configured within their pom so the project will build correctly.
The following is all that is required (in plugin.xml):
<extension
point="org.eclipse.m2e.core.indexes">
<index
indexId="JBOSS_NEXUS"
isShort="true"
repositoryUrl="http://repository.jboss.org/nexus/content/groups/public">
</index>
</extension>
--
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-10232) exploded deploy does not work on windows because of use of File#renameTo
by Jim Sellers (Created) (JIRA)
exploded deploy does not work on windows because of use of File#renameTo
------------------------------------------------------------------------
Key: JBIDE-10232
URL: https://issues.jboss.org/browse/JBIDE-10232
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Environment: JBossAS Tools: Version: 2.3.0.v20111104-1515-H45-M4
Java version: 1.5.0_22, vendor: Sun Microsystems Inc.
Java home: C:\devtools\java\jdk1.5.0_22\jre
Default locale: en_CA, platform encoding: Cp1252
OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
Reporter: Jim Sellers
Assignee: Rob Stryker
Setup: in a project on windows with an ear / war / jar in an exploded format and having started the server in debug mode. If you make any changes to a file in the jar, the jar will be rebuilt and try to be deployed. This seems to work but it pops up an error dialog box *every time*. The error message looks like the following:
{code}
Error renaming C:\devtools\jboss\jboss-4.2.3.GA\server\default\tmp\jbosstoolsTemp\tmp2587902707203199490.jar to C:\devtools\jboss\jboss-4.2.3.GA\server\default\deploy\MyExampleEAR.ear\MyExampleWAR.war\WEB-INF\lib\MyDependantJar-2.3-SNAPSHOT.jar.
This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination.
You may adjust these settings in the server editor.
{code}
For the method org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil#safeRename(File,File,int) it calls File#renameTo(File) for moving the file from the temp directory to WEB-INF/lib. From the javadocs for renameTo it says that this might not work if the file in the destination already exists.
Possible fixes:
# before calling the rename, try to delete on the destination file ( to.delete() )
# org.apache.commons.io.FileUtils#moveFile(File,File) tries to call the renameTo and if that fails it falls back to coping the file to the destination.
{code:JAVA|title=Sample Unit test}
/* This test needs to be run on windows. */
@Test
public void testCopyForWindows() throws IOException {
File from = File.createTempFile("source", ".txt");
File to = File.createTempFile("target", ".txt");
File[] files = {from, to};
for (File file : files) {
// set for cleanup
file.deleteOnExit();
assertTrue("file should exist" + file.getAbsolutePath(), file.exists());
assertTrue("file should be writable" + file.getAbsolutePath(), file.canWrite());
}
// if safeRename was not private!
assertTrue("should have been able to rename the file", safeRename(from, to, 10));
}
{code}
--
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-10218) Run button in toolbar needs to run the newly generated project
by Burr Sutter (Created) (JIRA)
Run button in toolbar needs to run the newly generated project
--------------------------------------------------------------
Key: JBIDE-10218
URL: https://issues.jboss.org/browse/JBIDE-10218
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Burr Sutter
The Run icon in the Eclipse toolbar is where a new developer (new to JBoss Tools) expects to go directly after he has generated a new project from either File-New or JBoss Central by using one of the archetypes or project examples/quickstarts.
This means the generated project needs to be highlighted in the Project Explorer and the Run button should "just work".
There is also an issue with Run vs Debug - if the server is in "debug mode" then Run should just assume that is OK and not prompt the user.
Run on Server should be the default so the user can use a single click on OK
--
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