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 54735 - Bad jar file names when importing project with multiple configurations
Summary: Bad jar file names when importing project with multiple configurations
Status: CLOSED FIXED
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: Martin Ryzl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-09 11:26 UTC by rubesm
Modified: 2006-10-23 16:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rubesm 2005-02-09 11:26:09 UTC
I have a project "Foo" with multiple
configurations importing other project "Foolib"
with multiple configurations too. In the Foolib
project every configuration has a different name
of the output jar.
When I want to import Foolib into Foo project I'm
ask to choose project jar and there is a list of
the Foolib's configurations and theirs output
jars. And this is the problem. 
All output jar offered by the dialogue are the
same (they have the same name as the name of the
output jar of the Foolib's actual configuration.
But the should differ.

example:



there is

dist/nokia/foolib_nokia.jar
dist/siemens/foolib_nokia.jar
dist/motorola/foolb_nokia.jar

when the nokia is the active configuration of the
Foolib project and 

dist/nokia/foolib_motorola.jar
dist/siemens/foolib_motorola.jar
dist/motorola/foolb_motorola.jar

when the motorola is the active configuration of
the Foolib project and 

instead of
dist/nokia/foolib_nokia.jar
dist/siemens/foolib_siemens.jar
dist/motorola/foolb_motorola.jar
Comment 1 Adam Sotona 2005-02-09 12:10:51 UTC
Yes, this happend when we added ${config.active} as a part of jar and
jad name.
We were not able to solve this problem other way then by removing the
${config.active} suffix from jar and jad names and return to the model
introduced in 4.0.
You can do the same manually for your library project. Go to jar
category in project properties, remove the conditional suffixes and
refresh the dependencies between the projects by selecting correct jars.
Comment 2 Lukas Hasik 2005-05-04 13:19:40 UTC
verified - no suffixies in jar names