2008/4/28 Derek Baum <[EMAIL PROTECTED]>: > Peter, > > Can you clarify - are you uncomfortable with the existing behaviour where > an attached artefact classifier is automatically added to the > Bundle-Version, or to the JIRA I raised to disable this behaviour? >
also just want to clarify that the classifier in question is the one from Maven which is typically appended after the version (though this is just convention) Thanks, > > Derek > > Peter Kriens wrote: > > > This feels like a bad practice? I feel uncomfortable with the version > > qualifier being (ab)used for identity. If two bundles are compiled for > > different environments (I assume this is for generic info?) then they should > > have different bundle symbolic names. If you use Import-Package, the BSN is > > irrelevant for dependents. > > > > Kind regards, > > > > Peter Kriens > > > > > > > > On 25 apr 2008, at 09:59, Derek Baum (JIRA) wrote: > > > > add switch to prevent classifier being appended to Bundle-Version > > > ----------------------------------------------------------------- > > > > > > Key: FELIX-543 > > > URL: https://issues.apache.org/jira/browse/FELIX-543 > > > Project: Felix > > > Issue Type: New Feature > > > Components: Maven Bundle Plugin > > > Reporter: Derek Baum > > > Priority: Minor > > > > > > > > > I have a use-case for using classifier to create multiple bundles with > > > different symbolic names but the same Bundle-Version. > > > > > > This is not currently possible, as the maven-bundle-plugin > > > automatically appends the classifier to the Bundle-Version. > > > > > > Could some switch be added, to disable the appending of classifier to > > > Bundle-Version? > > > > > > Thanks, > > > > > > Derek > > > > > > stuart.mcculloch wrote: > > > > > > the use-case for adding this feature was for people who > > > wanted to produce JDK5 and JDK1.4 versions of the _same_ bundle, so > > > because the symbolic name would be the same, the classifier must then > > > be added to the version to distinguish them. > > > > > > it is the intended behaviour for the above use-case, but we could add > > > a switch > > > to turn it off - it's difficult to detect whether the classifier > > > should be added to the > > > version automatically, because each bundling process is run in > > > isolation > > > > > > there's also no way to distinguish where the bundle version came from > > > in Maven > > > (ie. general config or specific to the classifier) once it reaches the > > > bundleplugin, > > > so a new switch is the only safe way to detect the different > > > use-case... > > > > > > > > > > > > -- > > > This message is automatically generated by JIRA. > > > - > > > You can reply to this email to add a comment to the issue online. > > > > > > > > > > ________________________________________________________________________ > > This email has been scanned by both Message Labs and Paremus > > internalsystems for viruses and inappropriate attachments. > > > > __________________________________________________ > > This email has been virus scanned by Message Labs. > -- Cheers, Stuart
