Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a .war file with release #19

Open
2 of 3 tasks
peller opened this issue Apr 29, 2011 · 10 comments
Open
2 of 3 tasks

Provide a .war file with release #19

peller opened this issue Apr 29, 2011 · 10 comments

Comments

@peller
Copy link
Member

peller commented Apr 29, 2011

Tasks:

  • Get a working WAR from M6 release (pre-Orion).
  • Manually create WAR from nightlies (post-Orion).
  • Fix build to output WAR file.
@ghost ghost assigned childsb Jul 17, 2012
@JonFerraiolo
Copy link
Member

@jhpedemonte @childsb

@peller: our build scripts produce a .war file today. Are you saying we should post a .war file next to the .zip file that we post at maqetta.org/downloads? If so, I would say don't bother. Anyone who wants a .war file probably is a Java geek, and they can build their own .war file.

@jhpedemonte
Copy link
Member

Also, moving to Orion build, which doesn't produce a WAR file at all.

@peller
Copy link
Member Author

peller commented Jul 18, 2012

People were asking for it, since it made sense at the time to be able run our servlet on other servers. It's not unreasonable for someone to expect us to post the results of the build script. If our Orion configuration makes a war meaningless, I'm happy to close this issue.

@ghost ghost assigned jhpedemonte Oct 25, 2012
@peller
Copy link
Member Author

peller commented Jan 17, 2013

see a13ae63

@jhpedemonte
Copy link
Member

Here's what I had to do to manually create a working M9 WAR:

  1. Built a WAR file from the M6-war branch.
  2. Built an M9 nightly from the orion-war branch (no WAR is built, just a regular standalone build).
  3. In the WAR, copy in the following files:
    • Replace all of /WEB-INF/plugins/ with those from the M9 nightly, but keep:
      • org.eclipse.equinox.http.servletbridge
      • org.eclipse.equinox.servletbridge.extensionbundle
    • Replace all of /WEB-INF/features/ with those from the M9 nightly, but keep:
      • org.eclipse.equinox.server.servletbridge
      • org.eclipse.equinox.server.core
    • Replace all of /WEB-INF/configuration/ with same directory from M9 nightly.
  4. In the WAR, Replace the web.xml file with this one.
  5. In the WAR, Edit /WEB-INF/plugins/org.eclipse.equinox.servletbridge.extensionbundle/META-INF/MANIFEST.MF to export v2.6 of javax.servlet.* namespaces, and to export more of those namespaces. See patch.
  6. In the WAR, Edit /WEB-INF/configuration/org.eclipse.equinox.simpleconfigurator/bundle.info:
    • Comment out the 2 javax.servlet entries.

    • Find http.registry and change the false at the end of the line to true.

    • Add the following lines to the end of the file:

      org.eclipse.equinox.http.servletbridge,1.0.200.201301171751,plugins/org.eclipse.equinox.http.servletbridge_1.0.200.201301171751.jar,2,true
      org.eclipse.equinox.servletbridge.extensionbundle,1.2.0.201301171751,plugins/org.eclipse.equinox.servletbridge.extensionbundle_1.2.0.201301171751.jar,4,false
      

To update an M9 WAR with the latest code from a nightly, just repeat steps 3 & 6.

@billreed63
Copy link
Member

#3702 change theme editor to use relative url

@jhpedemonte
Copy link
Member

Adding long strings of "../../../.." to handle URLs is inconvenient. A couple of options come to mind:

  1. Make the standalone, Jetty-based build also have a "/maqetta" context, such that all URLs start with that (including the Orion ones -- not sure how that would work out). This would also have the benefit of removing the "/maqetta/maqetta/..." duplication we have now.
  2. Make the context variable, such that the server could determine if URLs require the added context when running from a WAR. This means that the server would have to do substitutions on HTML files (would be cached). For JS files, we could set it in one file and have all the others query the context info from that main file.

peller pushed a commit that referenced this issue Jan 28, 2013
jhpedemonte added a commit that referenced this issue Jan 28, 2013
* master:
  Update all icons on the Scenes palette toolbar. Also update the Rename icon on the Files palette.
  #3704 use relative path to walcome for logout
  remove unused code
  use relative cmd/ url #19
  #3704 temp debugger to help debug in war deployment
  #3704 logout in war file context
  #3702 changed absolute path to dojo to relative path
  Minor update to test plan file
peller pushed a commit that referenced this issue Jan 28, 2013
peller pushed a commit that referenced this issue Jan 28, 2013
jhpedemonte added a commit that referenced this issue Jan 28, 2013
* origin/master:
  remove unused code
  remove unused code
  use relative url for welcome #19
  use relative cmd url #19
peller pushed a commit that referenced this issue Jan 28, 2013
jhpedemonte added a commit that referenced this issue Jan 29, 2013
* master:
  Revert "Don't try to read config file if in WAR."
  Use getDavinciProperty(), to work in WAR.
  Get "orion.auth.name" prop using getDavinciProperty.
  Don't try to read config file if in WAR.
  Use `getDavinciProperty()`, to work in WAR.
  #3705 missed a System.getProperty
  open editor during initialization process rather than in parallel to avoid timing problem. Fixes #3695
  clean up IOException handling
  Construct url based on incoming REST call.  Do not assume url prefix. Fixes #3694 Refs #19
  fix typo

Conflicts:
	maqetta.server.orion/src/maqetta/server/orion/command/GetInitializationInfo.java
jhpedemonte added a commit that referenced this issue Jan 31, 2013
Manual process, until we can fix build to spit out a
WAR file for Maqetta/Orion.
#19
@jhpedemonte
Copy link
Member

Also see commits 47bcb54, 9d2b7ea, 6907d51, 9d0e7b5.

@peller
Copy link
Member Author

peller commented Feb 1, 2013

The war is working, more or less, but must be built manually. @jhpedemonte will work on automating this in M10

-> M10

@peller
Copy link
Member Author

peller commented Jun 6, 2013

still not automated, but should be possible based on latest Orion

-> future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants