Tong Fin wrote: > Something is wrong with my keybord ... Resent the mail. > > When I rebuilt the UIMA runtime "fragment" used by the Deployment Descriptor > Editor, I got the target jar having the following name: > org.apache.uima.runtime.fragments.deployeditor_2.2.2.incubating.jar > which is consistent with the bundle-name in manifest.mf: > Bundle-SymbolicName: org.apache.uima.runtime.fragments.deployeditor > and with what we have in pom. > > But, the jar file for this "fragment" in the UIMA-AS distribution is: > org.apache.uima.runtime-deployeditor.2.2.2.incubating.jar > > Is there any reason to re-name the jar file to be different from the > fragment id ? > (Eclipse suggests to have "same" name). > > Either name is fine with me, but I prefer them to be the same. > Does the comment in http://issues.apache.org/jira/browse/UIMA-1123 explain this?
I found when building the Eclipse update site that the jar name has to match the "id". So, I changed the build and POM for this as part of creating the update site. Because we had already released 2.2.2-incubating, that jar name (the one in the binary distribution in the Eclipse Plugins directory) wasn't changed. For subsequent releases, as it stands now, because the POM was changed, the jar name in the binary distribution in the Eclipse Plugins directory will change to match what it is in the update site. -Marshall > -- Tong > >
