Hi cghersi,
Thanks!
Trying to make sense of the GitHub project structure and what is different from
Cayenne. From what I can tell we need this piece in the pom:
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.3.7</version>
<extensions>true</extensions>
<configuration>
<instructions>
<Export-Package>org.apache.cayenne,
org.apache.cayenne.*</Export-Package>
<Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName>
</instructions>
</configuration>
</plugin>
and also the META-INF dir (
https://github.com/cristianoghersi/CayenneOSGi/tree/master/cayenne-osgi/META-INF
) ?
Or is META-INF generated?
Also integrating this into our convoluted build structure will be a challenge.
One of the 3.2 undeclared goals is simplifying the build structure, so maybe
once we start looking into it, we might consider the OSGi aspect. And in any
event it is very helpful for us, even we can't simply patch Cayenne from what's
on the GitHub. It gives a clear idea of what we need to do to make ours jars
OSGi-friendly.
Cheers,
Andrus
On Jan 31, 2013, at 3:42 PM, Cristiano Ghersi <[email protected]>
wrote:
> Good morning,
>
> My company (Abodata, www.abodata.com) has ported Cayenne into OSGi
> environment, and we would like to contribute to Cayenne project with this
> enhancement as I posted under user mailing list on October 2012.
>
> Following your instructions, we have uploaded the full content under the
> github repo:
> https://github.com/cristianoghersi/CayenneOSGi
>
> Basically, we have packaged the source code of 3.1 version into an OSGi
> bundle called cayenne-osgi, adding some stuff to manage the particular
> classloading features of OSGi.
> Then we added also another bundle, called Cayenne-3.1-Dependencies, that
> packages all the required dependencies.
>
> I'm at complete disposal for every clarification you need.
>
> I'll wait for your feedback.
>
> Best
> cghersi
