Re: [ebr-dev] Greetings

[Justin Rosenberg <Justin.Rosenberg@xxxxxxxxxxx>]

I finally started diving into the code to work on the first item (automatically specify the bundle import bundle in the bnd file).  The problem with this idea is that the Maven file will have the version numbers, but not the package names (only group IDs).  Can you think of a way to determine what the package names would be for the dependencies?  Short of doing exactly what bnd tools does when it converts "*" to a manifest file, I can't think of a way to do this.

If the dependencies are already bundles, I could read their manifests and determine what they export, but that doesn't necessarily mean the project needs all of those packages.

Maybe defaulting to "*" and letting people modify manually for special situations is the best we can reasonably do.

What do you all think we should do?

~Justin

-----Original Message-----
From: ebr-dev-bounces@xxxxxxxxxxx [mailto:ebr-dev-bounces@xxxxxxxxxxx] On Behalf Of Gunnar Wagenknecht
Sent: Monday, March 23, 2015 3:31 PM
To: Discussion channel for EBR developers, not for discussion of individual bundles manifests
Subject: Re: [ebr-dev] Greetings

Justin,

Thanks for attending EclipseCon and my talk. :)

I like all three items. From my point of view, they are all within the scope of the EBR project. My suggestion would be to tackle them in the order you gave below. This should get you familiar with the existing Maven plug-in.

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/





> Am 23.03.2015 um 21:03 schrieb Justin Rosenberg <Justin.Rosenberg@xxxxxxxxxxx>:
> 
> Greetings all,
>  
>   I recently listened to a talk from Gunnar about the EBR tool.  I have some suggestions and would like to contribute when I can.
>  
> 	• It would be nice if the tool automatically set the dependency versions based on the pom.xml of the library that it’s creating the bundle for
> 	• Optionally it would be nice if the tool could create a Blueprint file based on any spring context files found in the library (both to expose beans and to inject them from other bundles)
> 	• Create a plugin for Nexus where if a group ending in “.ebr” is requested and the artifact does not exist, auto-generate the library using the EBR tool.  Additionally the generated project should be checked into a configured source repository.
>  
>   Converting an existing Spring project to OSGi with lots of dependencies is a real hassle.  These three items would be drastically reduce the cost of this kind of migration.  It would not be perfect and some of the projects would need to be touched after they have been auto-generated, but I think it’s a worthwhile goal.
>  
>   What do you guys think?  Too ambitious?  Outside the scope of what EBR is supposed to do?  What can I help with first (even if it’s not one of the items above)?
>  
> Thank you,
> Justin Rosenberg | Software Architect | Corporate Development Team | CRL Global Services 
> rosenbergj@xxxxxxxxxxx | www.crlcorp.com
>  
> 
> CONFIDENTIALITY NOTICE: The information in this message, and any attachment, is intended for the sole use of the individual and entity to whom it is addressed. This information may be privileged, confidential, and protected from disclosure. If you are not the intended recipient you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it, or its contents, is strictly prohibited. If you think that you have received this message in error please notify the sender and destroy all copies of this communication and any attachments. Thank you.   ­­   _______________________________________________
> ebr-dev mailing list
> ebr-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ebr-dev

_______________________________________________
ebr-dev mailing list
ebr-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ebr-dev

CONFIDENTIALITY NOTICE:
The information in this message, and any attachment, is intended for the 
sole use of the individual and entity to whom it is addressed. This 
information may be privileged, confidential, and protected from 
disclosure. If you are not the intended recipient you are hereby notified 
that you have received this communication in error and that any review, 
disclosure, dissemination, distribution or copying of it, or its contents, 
is strictly prohibited. If you think that you have received this message 
in error please notify the sender and destroy all copies of this 
communication and any attachments. Thank you.