Don't include protos (and some other dependencies) in jars

[smparkes]

The cel target in publish does not exclude the googleapis protobufs and so the generated classes get included in the jar. Some other stuff like com.google.rpc.Status also get pulled in. This causes problems when trying to use the maven central artifact in builds that include the googleapis artifacts from maven central.

With this change, only dev.cel.* and cel.* classes are included in the artifact.

[l46kok]

Looks good, just a few nits:

[smparkes]

Thanks for the quick review.

[l46kok]

Merged a370d05. Thanks for the PR

[smparkes]

Thanks, @l46kok.
Any thoughts on a deployment to maven central?
I can create a branch off of the 0.3.0 commit and cherry pick the change if we want a 0.3.1 instead of a 0.4.0?
(We do have a workaround if there's a need to delay releasing ...)

[l46kok]

Cadence wise, we're targeting for a quarterly release at a minimum. I'm planning on cutting a 0.4.0 release once all of the Subexpression optimization related changes are in (likely around end of March).

If you need a release sooner than that, feel free to cherry pick and create a 0.3.1 branch. I'd be happy to publish to maven central off that.

[sfc-gh-sparkes]

Excellent! Thanks.

[sfc-gh-sparkes]

@l46kok : https://github.com/Snowflake-Labs/cel-java/tree/smparkes/0.3.1
I can't create a branch in upstream so I can't create a PR to get this in but shouldn't be hard ...

[l46kok]

#259 -- you could likely expect this in maven central within O(days).

By any chance, would you mind sharing your use-case with us? We're interested in documenting best practices for CEL and would love any feedback. Be happy to follow up over email.

[sfc-gh-sparkes]

@l46kok: Thanks! More offline ...