Use for a while. Net return after the java on and found that the maintenance package jar can really be described as a nightmare. N a class can have a jar package to realize the function of almost, but there may be some minor deviations. The jar contains the class may meet the current needs of a small jar package, it may not only contains the class and its associated class, there are a pile of other features of the class heap big jar in the bag. There may be a good present, after the addition of new features have a problem, because the misuse of classloader large jar of the same name package class. In addition, if not very familiar with the classpath, when there may be a good build, run-time there is a problem.
java too much openness, any person or organization as long as pleased to be able to engage in a bunch of jar out of the same jar can be similar or different content, different content can be the same jar and so on and so on and so on and so on. Basically, a commonly used class of n are more achievable. In fact, reversal of the namespace name with the classname is a very good program, but there is no mandatory requirement to play jar package. Both a full name of the class in a jar in the basic, there can be no other basic jar of the same name inside the class, to the performance or some other situation, we could have some combination of jar, mix jar is a basic jar of aggregation is not allowed to include only an essential part of the jar, a jar is a set of combination of the basic jar of aggregation, and can not be changed in the area.
java the jar issues cited. Recent maven, sometimes in quite a bad mood. repo of maven to resolve claims that the management of the jar. But I think that is not enough. java the jar At best, it is very flexible, basically want to use what class can be set, it can not do custom classloader. Said to the poor, is its own trouble to themselves, a system jre, jdk are now several sets of sets, which do not duplicate the jar? Estimated because there is no room for lack of a few people are willing to share their own and other programs rely on the jar package. Therefore, a version of maven's jar in the end there is only one good copy is open to question.
It. Net model I think quite good, build is dependent on the dll full copy of the dll to the local directory, in addition to outside the GAC, so that although some waste of space, but very clean, one will know, what procedures in the jar, and set the classpath to avoid a lot of mistakes, and errors in the order of jar.
java too much openness, any person or organization as long as pleased to be able to engage in a bunch of jar out of the same jar can be similar or different content, different content can be the same jar and so on and so on and so on and so on. Basically, a commonly used class of n are more achievable. In fact, reversal of the namespace name with the classname is a very good program, but there is no mandatory requirement to play jar package. Both a full name of the class in a jar in the basic, there can be no other basic jar of the same name inside the class, to the performance or some other situation, we could have some combination of jar, mix jar is a basic jar of aggregation is not allowed to include only an essential part of the jar, a jar is a set of combination of the basic jar of aggregation, and can not be changed in the area.
java the jar issues cited. Recent maven, sometimes in quite a bad mood. repo of maven to resolve claims that the management of the jar. But I think that is not enough. java the jar At best, it is very flexible, basically want to use what class can be set, it can not do custom classloader. Said to the poor, is its own trouble to themselves, a system jre, jdk are now several sets of sets, which do not duplicate the jar? Estimated because there is no room for lack of a few people are willing to share their own and other programs rely on the jar package. Therefore, a version of maven's jar in the end there is only one good copy is open to question.
It. Net model I think quite good, build is dependent on the dll full copy of the dll to the local directory, in addition to outside the GAC, so that although some waste of space, but very clean, one will know, what procedures in the jar, and set the classpath to avoid a lot of mistakes, and errors in the order of jar.