#187 provide an osginized package of htmlunit

SVN version
closed
None
5
2013-10-11
2010-10-02
No

For osgi integration testing frameworks (such as pax-exam or spring-integration) it would help to have one all-in-one package of htmlunit wrapped to run in an osgi enviornment. Creating and providing a new project with a pom (similar) to the attached one will do it.

WDYT?

Discussion

  • Andreas Pieber

    Andreas Pieber - 2010-10-02

    pom file building a complete, osiginzed version of htmlunit, containing all references (but not exporting them)

     
  • Marc Guillemot

    Marc Guillemot - 2010-10-02

    what would be a test confirming that the package is correctly "OSGInized"?

     
  • Andreas Pieber

    Andreas Pieber - 2010-10-02

    basically you need a pax-exam project, starting up with nothing than the htmlunit-wrapped plugin and execute the gettingStarted example:

    http://htmlunit.sourceforge.net/gettingStarted.html

    If there's a chance that this makes it into the master I can provide the two new projects as a patch (htmlunit-osgi and htmlunit-osgi-it)

     
  • Andreas Pieber

    Andreas Pieber - 2010-10-02

    btw: you can also osginize htmlunit itself, but most of its references are not osginized making it a pain to provide all the references. In addition the htmlunit osginized package will mostly run in integration test environments (such as pax-exam). Therefore it will not hurt to pack everything together (imho)

     
  • Andreas Pieber

    Andreas Pieber - 2010-10-18

    any interest for this improvement?

     
  • Ahmed Ashour

    Ahmed Ashour - 2010-10-18

    Hi,

    I am ok with any change if it doesn't affect default maven structure and behavior.

    In other words, patches are welcome to add more configuration files for other packaging mechanisms, but maven is the main supported way.

    Could you provide a minimal OCGI project, so others can have a look?

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2012-07-26

    well, at least that it could startup and execute the getting started example

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2012-07-26

    oh, read the comments the wrong way round :-) just for the sake of the example you can give https://github.com/openengsb/openengsb-wrapped-net.sourceforge.htmlunit a shot. The bundle in html itself will look quite similar (and yes, still everything will be build by maven)

     
  • Ahmed Ashour

    Ahmed Ashour - 2012-07-26

    Hi Andreas,

    I couldn't find a quick way to have both, the normal jars and the osgi bundle.

    We can have both, to be exposed to build.canoo.com/htmlunit/artifacts

    But we can't replace the <packaging>jar</packaging> with <packaging>bundle</packaging>, since we will lose the standard packaging.

    Please re-open if you know a way to have both.

     
  • Andreas Pieber

    Andreas Pieber - 2013-01-02

    In fact this would be a complete separate pom.xml building a new artifact. Is this sufficient?

     
  • Ahmed Ashour

    Ahmed Ashour - 2013-01-02
    • status: pending --> accepted
    • milestone: --> Next_Release_(example)
     
  • Ahmed Ashour

    Ahmed Ashour - 2013-01-03
    • status: accepted --> closed
     
  • Ahmed Ashour

    Ahmed Ashour - 2013-01-03

    Actually, there is a way to use same pom.xml, and was committed.

    Please run "mvn org.apache.felix:maven-bundle-plugin:bundle"

    Enjoy!

     
  • Andreas Pieber

    Andreas Pieber - 2013-01-03

    how to you plan to integrate this into the release process?

     
  • Ahmed Ashour

    Ahmed Ashour - 2013-01-03

    I don't think it should be part of the normal release, since we already have "htmlunit-x.yz-bin.zip"

    We can have it as snapshot in build.canoo.com/htmlunit/artifacts

    What do you suggest?

     
  • Andreas Pieber

    Andreas Pieber - 2013-01-03

    What would be won by a never released snapshot? A nice option might be to keep the osgified artifact completely out of the core pom and simply release it as an "afterthought" and provide it as a separate download/maven artifact?

     
  • Ahmed Ashour

    Ahmed Ashour - 2013-01-03

    Done:

    • Added in 2.11 files
    • Was documented to be part of the release steps
     
  • Andreas Pieber

    Andreas Pieber - 2013-01-09

    you're welcome :-)

    The only thing I'm missing now is a deploy to m2 central? Am I missing something?

     
  • Ahmed Ashour

    Ahmed Ashour - 2013-01-10

    From what I read, there is no public central repository for OSGi bundles available.

    Also, I believe maven central repository is not meant to host bundles.

     
  • Andreas Pieber

    Andreas Pieber - 2013-01-10

    While m2 isn't an Object Bundle Repository (OBR) it's definitely used quite successfully to hold bundles. E.g. the entire OPS4J Pax suite, Apache Karaf, Apache Felix, Apache ACE, ... are all available via m2 central. Would it be possible to include htmlunit-2.11 into the maven release/push process? AFAIK the "regular" is available via m2 central [1]. Isn't it shipped during the release process?

    [1] https://search.maven.org/#search|ga|1|htmlunit

     
  • Andreas Pieber

    Andreas Pieber - 2013-01-11

    In addition you can also use them directly together with pax-exam (just to add another use case)

     

Log in to post a comment.