This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 33569 - Include full name in module JAR names
Summary: Include full name in module JAR names
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Module System (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@xml
URL:
Keywords: ARCH
Depends on:
Blocks: 32081 38057
  Show dependency tree
 
Reported: 2003-05-13 16:25 UTC by Jesse Glick
Modified: 2008-12-23 08:34 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2003-05-13 16:25:28 UTC
E.g. use

org-netbeans-modules-text-1-1.32.jar

for org.netbeans.modules.text/1 1.32.

Ant might be able to partially handle this without
special tasks:

<properties file="manifest.mf"/>
<!-- ... -->
<jar
jarfile="netbeans/modules/org-netbeans-modules-text-1-${OpenIDE-Module-Specification-Version}.jar"
.../>
Comment 1 Jaroslav Tulach 2003-07-08 10:05:19 UTC
According the installation proposal 
http://openide.netbeans.org/proposals/arch/installation.html
the version number will be included in the name of installation
directory and that is why the name of module jars can remain without
version identification. 

Closing as won't fix.
Comment 2 David Konecny 2003-07-08 13:48:30 UTC
The first half of this issue is still valid I guess - include full
name in module JAR name.
Comment 3 Jaroslav Tulach 2003-07-17 08:24:51 UTC
You are right David: So module JAR should use

org-netbeans-modules-text.jar

for org.netbeans.modules.text/2 1.47.
Comment 4 Jesse Glick 2003-07-17 14:49:06 UTC
I agree, naming the JAR acc. to the full module code name base would
be better. Probably should at the same time get rid of the eager/ and
autoload/ subfolders, using only the module properties files to
represent this info. (1) The module system might be able to make
certain optimizations if it knows the JAR name of a module in advance.
(2) Would reduce risk of confusion as to what e.g. "ant.jar" is. (3)
Would reduce risk of JAR name collision; e.g. I think S1S has two
xalan.jar modules.

Mainly a change in build infrastructure at the moment, but some module
system changes too.
Comment 5 Jesse Glick 2004-02-15 20:39:04 UTC
Michal, take note.
Comment 6 Jesse Glick 2004-03-30 13:38:05 UTC
Done for many modules already.
Comment 7 Jesse Glick 2004-04-14 22:46:13 UTC
Module system is prepared to work this way, and many modules are
converted. Projectized modules work this way by default. Leaving to
Michal to complete for all modules.
Comment 8 Jaroslav Tulach 2004-06-23 14:07:33 UTC
Michal, do you plan to work on this for promoD?
Comment 9 Michal Zlamal 2004-06-23 14:45:37 UTC
IMHO this is up to module owners to update their modules names, not up 
to RE. Anyway I don't think that this is build systems issue.
Comment 10 Jesse Glick 2004-06-23 19:01:16 UTC
BTW current list of offenders:

ide4/modules/css.jar
ide4/modules/cvs-profile.jar
ide4/modules/db.jar
ide4/modules/diff.jar
ide4/modules/httpserver.jar
ide4/modules/jsp.jar
ide4/modules/junit.jar
ide4/modules/monitor.jar
ide4/modules/properties.jar
ide4/modules/pvcs-profile.jar
ide4/modules/tasklist-docscan.jar
ide4/modules/tomcat5.jar
ide4/modules/vcsgen.jar
ide4/modules/vss-profile.jar
ide4/modules/xml-catalog.jar
ide4/modules/xml-schema.jar
ide4/modules/xml-text-edit.jar
ide4/modules/xml-tools.jar
ide4/modules/xsl.jar
Comment 11 Michal Zlamal 2004-06-23 19:16:45 UTC
Please fix this for your modules, after it you can assign this to me 
of to other module. In case you need any help feel free to ask for it.
Comment 12 Jesse Glick 2004-07-07 16:56:43 UTC
No, this was intentionally assigned to issues@xml, as the owner of the
largest group of offending modules.
Comment 13 Jesse Glick 2005-12-31 20:06:04 UTC
I already did this myself, I guess.