You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by GitBox <gi...@apache.org> on 2018/04/05 18:37:51 UTC

[GitHub] rombert opened a new pull request #1: [discuss] SLING-5648 - Make Non-Eclipse Module regular Maven Packages

rombert opened a new pull request #1: [discuss] SLING-5648 - Make Non-Eclipse Module regular Maven Packages 
URL: https://github.com/apache/sling-ide-tooling/pull/1
 
 
   Preparatory work for making non-eclipse modules Maven packages, and therefore much easier to reuse.
   
   i've extracted several modules from the Eclipse build and made them regular Maven modules, which should be easily consumable by other IDEs/environments. Being a regular bnd project means that it's impossible to slip by a dependency on Eclipse - I've removed one for impl-vlt.
    
   The modules are not yet OSGi-free due to the `EventAdmin` dependencies, that will require more work and will probably be tracked with [SLING-5618](https://issues.apache.org/jira/browse/SLING-5618).
   
   I'm almost done with this, but I'd like to put this up for review since I won't be available until Wednesday.
   
   What does not yet work:
   
   - `BundleDeploymentIT` ; although bundle deployment works from the IDE
   - running tests from Eclipse; did not spend too much time with this, getting weird errors as is the workspace is already provisioned
   
   @schaefa - does this fit your expectation on what reusable modules would look like?
   @kwin  - your feedback would be welcome, given that you have contributed extensively to the IDE tooling in the past

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services