On Dec 30, 2007 12:04 AM, Haim Ashkenazi <[EMAIL PROTECTED]> wrote: > On Dec 28, 2007 5:14 PM, amidrunk <[EMAIL PROTECTED]> wrote: > > > > Hi, thanks for responding! > > > > > > > Waouh, it may have taken some time :) > > > > You have no idea :) > > > > > > > See http://jira.codehaus.org/browse/MEAR-51 > > > > Looked good until I saw "Would be really great if you implement that." at > > the end :) > > > > I get the impression that the purpose of exploding an ear into a deploy-dir > > didn't really get communicated in that discussion. In my case, I can't > > really point the server to the target-directories of individual projects. We > > have a bunch of ears deployed on a bunch of developer-computers who don't > > necessarily use the same paths. For this to work, I need to be able to > > explode the ears into a directory defined e.g. by an environment variable or > > a property in the profile. Everyone will hate me if this becomes a mess :) > > > > So, to clarify, I need to produce a completely exploded application, meaning > > the ear should be exploded and all modules within the ears should be > > exploded as well. The latter ensures that the ide can synchronoize with the > > deploy directory, so a redeploy won't be necessary for minor jsp-changes and > > similiar. > > > > Is this possible? > > I'm not sure If I understand correctly, but I'll tell you what I use > to Implement exploded ears on jboss. I have a profile in my pom: > > <profile> > <id>exploded</id> > <activation> > <property> > <name>exploded</name> > <value>true</value> > </property> > </activation> > <build> > <plugins> > <plugin> > <artifactId>maven-ear-plugin</artifactId> > <configuration> > <unpackTypes>ejb,war</unpackTypes> > </configuration> > </plugin> > </plugins> > </build> > </profile> > When you create an ear, maven creates a working directory with all > the files in it in the final state. If you use the profile above, all > you ejb's and wars (you can add other types as well) will be exploded > inside this directory. I then soft-link this directory to the jboss > deploy directory. > > If you really want an un-elegant solution you can add to the > configuration the following setting: > <workDirectory>${appserver.deploy.dir}</workDirectory>. you can now > point to whatever directory you want (I'm sure you can reference an > environment variable also).
Actually, don't use the soft-link. it just caused me some nasty bugs in jboss. If you really have to, use the ugly <workDirectory> hack. Bye -- Haim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
