You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Kevan Miller <ke...@gmail.com> on 2011/05/16 00:44:57 UTC
add an m2_repo to geronimo svn
In order to fix some JCDI TCK issues, we need to move up to a 3.7.0 build of Eclipse Equinox. Equinox jars aren't normally available in a maven repo. I'm planning on adding an m2-repo to our svn and pointing our pom.xml to this. This technique is/has been used by other projects. I'm open to other suggestions on how to handle this, if anyone has alternate ideas or orbjections.
--kevan
Re: add an m2_repo to geronimo svn
Posted by Kevan Miller <ke...@gmail.com>.
On May 15, 2011, at 10:18 PM, Shawn Jiang wrote:
> Another possible way is to create a geornimo bundle/jar for it.
>
> 1, wget the equinox jar
> 2, add customized fix code. (need to contribute back to eclipse per EPL)
> 3, use bundle plugin or dependency plugin to build it to org.apache.geronimo.bundles.equinox jar without changing the original manifest.
>
> This way, our costomized equinox has its clear versioning. and we could add new fix to it easily.
Right. So, there are no customizations or fixes to be applied -- we'd be using the jar (http://www.eclipse.org/downloads/download.php?file=/equinox/drops/I20110514-0800/org.eclipse.osgi_3.7.0.v20110513.jar), unaltered. So, I see no reason to move the jar into an org.apache.geronimo-based groupId.
I'll also note that any patches would likely be EPL licensed. We won't host EPL source code at Apache. So, IMO, we'll never be hosting Equinox patches...
--kevan
Re: add an m2_repo to geronimo svn
Posted by Shawn Jiang <ge...@gmail.com>.
Another possible way is to create a geornimo bundle/jar for it.
1, wget the equinox jar
2, add customized fix code. (need to contribute back to eclipse per EPL)
3, use bundle plugin or dependency plugin to build it to
org.apache.geronimo.bundles.equinox jar without changing the original
manifest.
This way, our costomized equinox has its clear versioning. and we could
add new fix to it easily.
On Mon, May 16, 2011 at 6:44 AM, Kevan Miller <ke...@gmail.com>wrote:
> In order to fix some JCDI TCK issues, we need to move up to a 3.7.0 build
> of Eclipse Equinox. Equinox jars aren't normally available in a maven repo.
> I'm planning on adding an m2-repo to our svn and pointing our pom.xml to
> this. This technique is/has been used by other projects. I'm open to other
> suggestions on how to handle this, if anyone has alternate ideas or
> orbjections.
>
> --kevan
--
Shawn