[MAGNOLIA-2686] Standalone bundle Created: 07/Apr/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: build
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-2685 Setting headers multiple times does n... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

See http://confluence.magnolia-cms.com/display/DEV/Concept+Standalone+bundles



 Comments   
Comment by Magnolia International [ 07/Apr/09 ]

First shot using the maven-winstone-plugin.
While this works (pending MAGNOLIA-2685), this doesn't seem to be as flexible as could be, since users couldn't start two instances without command-line parameters.
If we want to avoid a gui like described in the concept, maybe we could generate two artifacts: 1) running on different ports 2) using a different value for a new property such as magnolia.authorInstance=true.

(we already have magnolia.bootstrap.authorInstance whose name would sound slightly inappropriate - might consider consolidating those)

Comment by Magnolia International [ 27/Nov/13 ]

A -standalone.jar file currently gets created with the magnolia-empty-webapp project, which doesn't make it extremely useful. It's also currently not deployed (the file is not "attached" so the build lifecycle by the plugin), and suffers from a couple of bugs (MAGNOLIA-2685 for example)
However, it still seems to be working (which is fun): java -jar target/magnolia-empty-webapp-5.2.1-SNAPSHOT-standalone.jar
(although AdminCentral doesn't load because it somehow needs the jsp api libraries, which don't seem to be bundled by default with this winstone version - I don't think it should matter for AdminCentral, but in general we probably want to enable jsp support in standalone bundles anyway, so...)

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:39:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.