Re: [orbit-dev] javax.activation vs. org.apache.poi

[David M Williams <david_williams@xxxxxxxxxx>]

Posting to orbit-dev for broader discussion/visibility
... 

There is a way to add a "prebuilt"
bundle to Orbit. Use the "prebuilt" attribute! :) 

See http://wiki.eclipse.org/Orbit/Adding_Bundles_to_Orbit#Adding_a_library_that_is_already_a_bundle

This can have a view tricky angles itself,
but if it solves this problem I'd be all for it .... 

BUT ... this still goes through the
"build", it is just not "assembled" like the others.
I'm not sure the prebuilt attribute/method will actually fix a _resolution_
problem during the build, but if you want to try it, you are welcome too.


On the plus side, remember the "failed
build" is trying to be helpful ... to warn that "if certain things
are installed together then they will not run correctly". 

The fact that the cycle now occurs between
different bundles (i.e. one problem area was fixed) makes me think there
is a way to solve this second problem? 

Thanks, 





From:      
 Edwin Park <esp@xxxxxxxxxx>
To:      
 David M Williams/Raleigh/IBM@IBMUS,

Date:      
 01/18/2013 08:05 PM
Subject:    
   Re: javax.activation
vs. org.apache.poi
Sent by:    
   Edwin Park <edwin.park@xxxxxxxxx>

---

I know at least one other project had indicated interest
in it on the orbit-dev list. Poi is basically for interacting with Microsoft
documents. We use it to export NatTable data to Excel.

I don't have a problem building and distributing Poi it
in our own project - we used to do just that when we were hosted at SourceForge.
We just repackaged the jar with an OSGi manifest generated by the maven
BND plugin, which worked fine.

If we are already repackaging the jar, it would be nice
for others to be able to use it too; and it would be nice for folks to
be able to go to a central location to find such repackaged dependencies,
which brings us back to Orbit. The problem is that Poi doesn't play nice
with the Orbit build system.

Is there any way we could use our working maven build
to package the jar and still distribute it in Orbit? Worse comes to worse
we'll do as you suggest and build and host it ourselves, but for the sake
of others who may want to consume it, it would be nice if we could distribute
it in Orbit. 

Thanks,
Edwin


On Jan 18, 2013, at 6:34 PM, David M Williams <david_williams@xxxxxxxxxx>
wrote:

>  What am I doing wrong? 

I suspect nothing. Some third party jars (not written for OSGi) are just
not very well behaved ... or well "componentized". 

I'll try to take a look, but doubt I'd see anything. 

Is this something you anticipate to be "widely shared"? I was
just thinking if its pretty specific to your own project, you might be
better off just having in your project's repo, and building it all on its
own yourself (as part of your normal build). There might still be "runtime"
problems, if wrong things "installed together" ... so, I'm just
mentioning it as a possibility (not a recommendation). (Sorry, I don't
know what poi is or how much it might be needed by others). 

Thanks for trying, 





From:        Edwin
Park <esp@xxxxxxxxxx>
To:        David
M Williams/Raleigh/IBM@IBMUS, 
Date:        01/18/2013
05:56 PM 
Subject:        Re:
javax.activation vs. org.apache.poi 
Sent by:        edwin.park@xxxxxxxxx

---

You're right, it didn't fix it. Now we're back to the logging cycle. Ok
I'm going to revert everything and pull poi out again. I'm getting to my
wit's end here. I don't have any idea how a simple org.apache.commons.logging
import can cause the build to break so badly. What am I doing wrong? 

:-( 


On Fri, Jan 18, 2013 at 5:51 PM, David M Williams <david_williams@xxxxxxxxxx>
wrote: 
The reasons for that change was this bug ... 

https://bugs.eclipse.org/bugs/show_bug.cgi?id=393280

I'd be amazed if that fixes the problem, but ... willing to "read
all about it" if it does. 

Thanks, 




From:        Edwin
Park <esp1@xxxxxxxxxxx>
To:        David
M Williams/Raleigh/IBM@IBMUS, 
Date:        01/18/2013
05:25 PM 
Subject:        javax.activation
vs. org.apache.poi 
Sent by:        edwin.park@xxxxxxxxx

---

Hi David, 

I'm fighting with the org.apache.poi build again today. Currently I'm up
against a cyclic dependency in javax.activation. I noticed that you added
optional import dependencies on javax.activation on javax.mail; but the
javax.mail.glassfish bundle has dependencies back on javax.activation.
I don't know how this was building before, but when poi is added into the
mix, it hits this cycle by way of the logging bundles, and the build fails.

I took the liberty of removing the optional javax.mail dependencies from
javax.activation and am re-running the build to see if this fixes things.
It looks like you has some rationale for adding these dependencies into
javax.activation tho, so I wanted to ask you about it. I can certainly
roll back my changes if I was out of line with this change. Please let
me know - 

Thanks, 
Edwin