You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/01/22 16:41:21 UTC
[jira] Commented: (JCR-2476) Add profile to enable deployment of
jackrabbit-standalone
[ https://issues.apache.org/jira/browse/JCR-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803730#action_12803730 ]
Jukka Zitting commented on JCR-2476:
------------------------------------
What's the use case for this, i.e. why would one want to have a Maven dependency on jackrabbit-standalone?
I'm not opposed to this change, just trying to understand why we need it.
> Add profile to enable deployment of jackrabbit-standalone
> ---------------------------------------------------------
>
> Key: JCR-2476
> URL: https://issues.apache.org/jira/browse/JCR-2476
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-standalone, maven
> Reporter: Marcel Reutegger
> Priority: Minor
> Attachments: JCR-2476.patch
>
>
> Deployment of the jackrabbit-standalone artifact is skipped using a configuration setting in the pom file.
> I'd like to deploy the artifact anyway to a private repository, but cannot override this configuration.
> The attached patch adds a profile that allows you to enable deployment on request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.