felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "luke w patterson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-636) Bundle-SymbolicName is generated incorrectly
Date Fri, 01 Aug 2008 20:02:31 GMT

    [ https://issues.apache.org/jira/browse/FELIX-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619110#action_12619110
] 

luke w patterson commented on FELIX-636:
----------------------------------------

One preference is [1]
	Bundle-SymbolicName = ${project.groupId}.${project.artifactId}
and the other is [2]  
	Bundle-SymbolicName = ${project.artifactId}

If (Bundle-SymbolicName = ${project.artifactId}) is preferred, it seems that the conventional
configuration for a pom would be:

        <groupId>someGroupId</groupId>
        <artifactId>${project.groupId}.someArtifactId</artifactId>



It is unfortunate that their isn't agreement on a standard convention.

--------------------------------
Here is an example that has caused me problems:

	SWT has gone from 

	<groupId>org.eclipse.swt</groupId> 
	<artifactId>org.eclipse.swt</artifactId> 
	see [3]

to

	<groupId>org.eclipse</groupId> 
	<artifactId>swt</artifactId> 
	see [4]


Now it sounds like it might go to 
	<groupId>org.eclipse</groupId> 
	<artifactId>org.eclipse.swt</artifactId> 


It's hard to managed mixed transitive dependencies, especially when no relocation poms have
been deployed.
--------------------------------



Does anyone have any ideas for forming a more unified approach in the community?


[1] - http://jira.codehaus.org/browse/MECLIPSE-238
[2] - http://mail-archives.apache.org/mod_mbox/maven-dev/200805.mbox/%3C69ECB380-90D7-4718-BD2D-A0E22A85B555@maven.org%3E
[3] - versions 3.2.0 and 3.2.1 @ http://repo1.maven.org/eclipse/
[4] - versions 3.3.0-v3339b, 3.3.0-v3345b and 3.3.0-v3346 @http://repo1.maven.org/eclipse/,
versions 3.2.1-v3235e and 3.3.0-v3346 @http://repo1.maven.org/maven2/


> Bundle-SymbolicName is generated incorrectly
> --------------------------------------------
>
>                 Key: FELIX-636
>                 URL: https://issues.apache.org/jira/browse/FELIX-636
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-1.4.1
>         Environment: Ubuntu
>            Reporter: Ken Paulsen
>         Attachments: pom.xml
>
>
> I have the following in the pom.xml:
>   <groupId>org.glassfish.jsftemplating</groupId>
>   <artifactId>jsftemplating</artifactId>
> After I build, I get the following in the MANIFEST.MF:
>    Bundle-SymbolicName: org.glassfish.jsftemplating
> Notice it only has 1 "jsftemplating" in the symbolic name.  If I change the artifactId
to something else and make no other changes, I get the expected results.  For example, if
I put this in the pom.xml:
>   <groupId>org.glassfish.jsftemplating</groupId>
>   <artifactId>jsft</artifactId>
> I get this in the MANIFEST.MF:
>    Bundle-SymbolicName: org.glassfish.jsftemplating.jsft
> Notice now both the full groupId AND artifact id appear in the symbolic name.  This is
what I expected to see. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message