Hi maybe read http://openejb.979440.n4.nabble.com/Hello-all-together-td4661567.html
about your issue here the full idea: the path is a param sent to the remote tomee so basically it should be accessible from it. IIRC you can give a path (absolute or relative to the remote tomee), a http url, a mvn:gId:aId:version:war.... *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/3/25 David Salter <[email protected]> > Hi, > > I'm interested in helping out with TomEE / OpenEJB and was hoping I could > be of help to the project. I've been developing in Java EE for about 10 > years, so hopefully I can help out. > > I've had a problem deploying a war file which got solved over in the User > Forum ( > http://openejb.979440.n4.nabble.com/Problem-deploying-war-file-td4661699.html), > but I'm wondering if this could be enhanced and whether I should create a > JIRA for it. > > The issue is that when you do a mvn tomee:deploy, you need to pass a full > path name for the artifact to deploy to TomEE - a relative path name does > not work. > > I've got a "fix" for this, so you can pass either a full or relative path > name for the artifact to deploy. Do you think this is an issue that needs > resolving and that I should create an issue for? > > If not, where would be the best place to start looking for "beginners" > bugs to fix. > > Thanks, > > Dave. > >
