You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by cpilsworth <gi...@git.apache.org> on 2014/04/23 15:50:26 UTC

[GitHub] sling pull request: SLING-3510 Check for null classUrls and warn w...

GitHub user cpilsworth opened a pull request:

    https://github.com/apache/sling/pull/15

    SLING-3510 Check for null classUrls and warn when no @Model classes found

    When a non-existent package is added to Sling-Model-Packages, then an NPE is thrown as there are no matching classes found. I guess the same would happen for existing packages that contain no @Model classes. Check for classUrls and warn, then continue if null.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cpilsworth/sling SLING-3510

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #15
    
----
commit 88e2a197c7fda2922244b42b77499f54ab6a503a
Author: Chris Pilsworth <cp...@gmail.com>
Date:   2014-04-23T13:49:20Z

    SLING-3510 Check for null classUrls and warn when no @Model classes found by Sling Models

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] sling pull request: SLING-3510 Check for null classUrls and warn w...

Posted by cpilsworth <gi...@git.apache.org>.
Github user cpilsworth closed the pull request at:

    https://github.com/apache/sling/pull/15


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---