Scheduled Maintenance: over the next few days, we will update Jira to a newer version.

If you don't know Jira 4.x yet, you might be a little surprised by the UI changes ... :)

Issue Details (XML | Word | Printable)

Key: MAGNOLIA-2686
Type: New Feature New Feature
Status: In Progress In Progress
Priority: Major Major
Assignee: Grégory Joseph
Reporter: Grégory Joseph
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Magnolia

Standalone bundle

Created: 07/Apr/09 12:39 PM   Updated: 12/Mar/10 09:38 PM
Component/s: build
Affects Version/s: None
Fix Version/s: Green

Time Tracking:
Not Specified

Issue Links:
dependency
 

Labels:
Date of First Response: 07/Apr/09 12:45 PM



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Hudson CI server added a comment - 07/Apr/09 12:45 PM
Integrated in magnolia_main-trunk #764
first shot at a standalone bundle using the winstone-maven-plugin

Grégory Joseph added a comment - 07/Apr/09 12:45 PM
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)