[
https://issues.apache.org/jira/browse/SLING-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz reopened SLING-4151:
----------------------------------------
I have removed the module from the contrib build for now, as the following line
in pom.xml causes trouble on our Jenkins builds:
{code}
<src>../../../launchpad/builder/target/${builder.artifact}-${project.version}-standalone.jar</src>
{code}
It assumes the build runs alongside a full Sling build which is not the case on
Jenkins, the launchpad jar file should be downloaded from the Maven repository
instead.
Using the maven dependencies plugin you can copy that jar file under target
first, and get it from there. There's an example in
bundles/extensions/models/integration-tests/pom.xml using the copy-dependencies
goal.
> Create debian/.ubuntu package for sling launchpad standalone jar
> ----------------------------------------------------------------
>
> Key: SLING-4151
> URL: https://issues.apache.org/jira/browse/SLING-4151
> Project: Sling
> Issue Type: New Feature
> Components: Installer
> Reporter: Bruce Edge
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Labels: debian, install, package, ubuntu
> Attachments: sling-dpkg.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I’m setting up a development env for a team to work on a sling asset manager
> app. I wanted to make the env setup simple so I put together a debian/ubuntu
> package for the org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar.
> It uses the jdeb maven plugin so it’s cross-platform. Here’s the patch on the
> off-chance it’s compatible with the upstream policies. If it needs tuning,
> let me know what it’s missing.
> Comments from dev list:
> - Do you mind creating a JIRA
> - my preference would be to have this in contrib instead of the launchpad
> folder
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
