You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Nick Efford (JIRA)" <de...@db.apache.org> on 2006/10/05 21:22:23 UTC
[jira] Created: (DERBY-1931) Derby JAR files should be grouped as a
single library in Package Explorer
Derby JAR files should be grouped as a single library in Package Explorer
-------------------------------------------------------------------------
Key: DERBY-1931
URL: http://issues.apache.org/jira/browse/DERBY-1931
Project: Derby
Issue Type: Improvement
Components: Eclipse Plug-in
Affects Versions: 10.1.3.1
Reporter: Nick Efford
Priority: Minor
After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1931) Derby JAR files should be grouped as
a single library in Package Explorer
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532487 ]
Dyre Tjeldvoll commented on DERBY-1931:
---------------------------------------
I have committed this as r581971. I took the liberty of adding ASF headers to the new files, as well as changing their indentation to only use spaces. Please check it out and let me know if I have managed to mess something up (I don't have eclipse available, so I cannot test it myself).
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4
> Reporter: Nick Efford
> Assignee: Aaron Tarter
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a
single library in Package Explorer
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-1931:
--------------------------------------
Fix Version/s: (was: 10.3.1.5)
10.4.0.0
Changing fix-version to 10.4 since the fix went into trunk.
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4
> Reporter: Nick Efford
> Assignee: Aaron Tarter
> Priority: Minor
> Fix For: 10.4.0.0
>
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a
single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Tarter updated DERBY-1931:
--------------------------------
Attachment: screenshot-1.jpg
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0
> Reporter: Nick Efford
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-1931) Derby JAR files should be grouped as
a single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Tarter reassigned DERBY-1931:
-----------------------------------
Assignee: Aaron Tarter
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0
> Reporter: Nick Efford
> Assignee: Aaron Tarter
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a
single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Tarter updated DERBY-1931:
--------------------------------
Derby Info: [Patch Available]
Affects Version/s: 10.3.1.4
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4
> Reporter: Nick Efford
> Assignee: Aaron Tarter
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a
single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Tarter updated DERBY-1931:
--------------------------------
Attachment: (was: DerbyUtils.diff)
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0
> Reporter: Nick Efford
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1931) Derby JAR files should be grouped as
a single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475491 ]
Aaron Tarter commented on DERBY-1931:
-------------------------------------
I agree that the current behavior of adding four derby lib entries with absolute path references to the .classpath is problematic. It prevents easy sharing through an SCM repository like SVN or CVS, since the references are not relative (i.e. portable). The solution suggested above would be to use an eclipse IClasspathContainer (like the JRE System Library). Define a container in the plugin that loads the derby jars and then just add that container to the .classpath when the user clicks "Add Derby Nature". Another simpler, but perhaps less pretty, approach is to modify the "Add Derby Nature" popup action to add var entries relative to the ECLIPSE_HOME variable. So, in this case they would still appear as non-collapsable individual entries, but at least they would be portable. The entries in the .classpath would then be:
<classpathentry kind="var" path="ECLIPSE_HOME/plugins/org.apache.derby.core_10.2.2/derby.jar"/>
<classpathentry kind="var" path="ECLIPSE_HOME/plugins/org.apache.derby.core_10.2.2/derbyclient.jar"/>
<classpathentry kind="var" path="ECLIPSE_HOME/plugins/org.apache.derby.core_10.2.2/derbynet.jar"/>
<classpathentry kind="var" path="ECLIPSE_HOME/plugins/org.apache.derby.core_10.2.2/derbytools.jar"/>
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1
> Reporter: Nick Efford
> Priority: Minor
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1931) Derby JAR files should be grouped as
a single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533121 ]
Aaron Tarter commented on DERBY-1931:
-------------------------------------
I checked out the trunk and verified that the patch was applied correctly. I was able to compile, run, add Derby nature, remove Derby nature, start, and stop a database server.
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4
> Reporter: Nick Efford
> Assignee: Aaron Tarter
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a
single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Tarter updated DERBY-1931:
--------------------------------
Attachment: DerbyUtils.diff
This patch modifies the DerbyUtils class to add variable entries relative to ECLIPSE_HOME as described in the comments above, so that eclipse projects with Derby Nature can be committed to an SCM without causing build path errors. I did not think any of the functional tests were applicable to this ui action, so I manually tested the code by trying the following:
1) Adding Derby Nature to a java project
2) Starting and stopping a database with the derby nature
3) Removing the Derby Nature from a java project
The code modification is only required on the add and not on the remove since the current remove looks for any entry that ends with the correct JAR names.
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1
> Reporter: Nick Efford
> Priority: Minor
> Attachments: DerbyUtils.diff
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a
single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Tarter updated DERBY-1931:
--------------------------------
Attachment: DerbyClasspathContainerInitializer.java
DerbyClasspathContainer.java
1931.diff
This patch provides an IClasspathContainer implementation so that all of the derby jars are contained under a single classpath entry. This allows system portability and simplifies the classpath management. The method is better than the patch provided as part of 2376, since that method will fail for cases where users install their plug-ins in non-default Eclipse installation locations.
Besides the diff there are two new files to be added that are included as attachments:
trunk/plugins/eclipse/org.apache.derby.ui/src/org/apache/derby/ui/container/DerbyClasspathContainer.java
trunk/plugins/eclipse/org.apache.derby.ui/src/org/apache/derby/ui/container/DerbyClasspathContainerInitializer.java
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0
> Reporter: Nick Efford
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, DerbyUtils.diff
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a
single library in Package Explorer
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll updated DERBY-1931:
----------------------------------
Derby Info: (was: [Patch Available])
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4
> Reporter: Nick Efford
> Assignee: Aaron Tarter
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1931) Derby JAR files should be grouped as
a single library in Package Explorer
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532457 ]
Dyre Tjeldvoll commented on DERBY-1931:
---------------------------------------
Hi Aron,
I tried applying your patch, but I have some questions wrt. the new files. The path you mention for them:
plugins/eclipse/org.apache.derby.ui/src/org/apache/derby/ui/container/
doesn't exist in my sandbox which I updated today. Specifically the "container" directory appears to be missing. Is that in fact a new directory that needs to be added, or am I misunderstanding something?
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4
> Reporter: Nick Efford
> Assignee: Aaron Tarter
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1931) Derby JAR files should be grouped as a
single library in Package Explorer
Posted by "Nathan Revo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Revo updated DERBY-1931:
-------------------------------
Affects Version/s: 10.2.2.0
Identifying that this error still exists in the latest released version of the eclipse plug-in.
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0
> Reporter: Nick Efford
> Priority: Minor
> Attachments: DerbyUtils.diff
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-1931) Derby JAR files should be grouped as
a single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Tarter resolved DERBY-1931.
---------------------------------
Resolution: Fixed
Fix Version/s: 10.3.1.5
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4
> Reporter: Nick Efford
> Assignee: Aaron Tarter
> Priority: Minor
> Fix For: 10.3.1.5
>
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1931) Derby JAR files should be grouped as
a single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521319 ]
Aaron Tarter commented on DERBY-1931:
-------------------------------------
As shown in the attached screenshot, the libraries are grouped under a container shown as "Derby Libraries". The .classpath for the project shown in the screenshot looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con" path="DERBY_CONTAINER"/>
<classpathentry kind="output" path="bin"/>
</classpath>
Notice the single container entry for DERBY_CONTAINER and compare this to the current implementation that adds a single entry for each of the four jars.
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0
> Reporter: Nick Efford
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1931) Derby JAR files should be grouped as
a single library in Package Explorer
Posted by "Aaron Tarter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532460 ]
Aaron Tarter commented on DERBY-1931:
-------------------------------------
Re: "Specifically the "container" directory appears to be missing. Is that in fact a new directory that needs to be added, or am I misunderstanding something?"
Yes, you need to create the new container directory.
> Derby JAR files should be grouped as a single library in Package Explorer
> -------------------------------------------------------------------------
>
> Key: DERBY-1931
> URL: https://issues.apache.org/jira/browse/DERBY-1931
> Project: Derby
> Issue Type: Improvement
> Components: Eclipse Plug-in
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.1.4
> Reporter: Nick Efford
> Assignee: Aaron Tarter
> Priority: Minor
> Attachments: 1931.diff, DerbyClasspathContainer.java, DerbyClasspathContainerInitializer.java, screenshot-1.jpg
>
>
> After adding the Apache Derby Nature to an Eclipse project, the four Derby JAR files appear individually in the Package Explorer View. It would be neater if they were grouped as a single library called "Apache Derby Library", in the same way that the JARs distributed with a Java run-time environment appear as "JRE System Library".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.