[
https://issues.apache.org/jira/browse/SLING-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790051#action_12790051
]
Bertrand Delacretaz commented on SLING-1197:
--------------------------------------------
I had a look at your code and I like it, although SLING-1197-take3.patch is not
directly consumable with my usual "patch -o0 < patchfile" command at the top of
the svn tree, does it need special patch flags?
One thing that we're losing (I assume) by moving the bundle dependencies
outside of the POM is the check for SNAPSHOTs when we release a module. Do you
know how that could be added to the plugin? I assume there's a Maven phase
where it checks for snapshots, so maybe the maven-sling-plugin could do that as
well?
About your questions:
> 1) What's the right name for the project I'm calling "uber"?...
"builder" maybe? The role of that module is mostly to build other things
2) Is "standalone" a good classifier for the app jar?
I like it
3) Are there other provisioning schemas worth supporting?
I don't see any at the moment.
> new prepare-package Maven goal to simplify launchpad poms
> ---------------------------------------------------------
>
> Key: SLING-1197
> URL: https://issues.apache.org/jira/browse/SLING-1197
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins
> Reporter: Justin Edelson
> Assignee: Felix Meschberger
> Attachments: SLING-1197-take3.patch, SLING-1197-updated.patch,
> SLING-1197.patch
>
>
> See http://www.mail-archive.com/[email protected]/msg01908.html for
> discussion
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
