Hi, > The problem with this solution (separate the war project into a classes > and a webapp part) is that the IDEs and a Testserver will not be able to see > the project as a whole --> you'll just have a dependency on the jar as a > library and will not be able to reload the classes when working on a running > server.
Indeed. I have similar problems using Eclipse with such a project. My workaround is to just copy the .classpath file from my jar subproject one level above so that at least Eclipse is able to compile the code without having to create separate projects for the jar and war... > I was wondering whether it's possible to specify packaging as > <packaging>jar,war</packaging> but this doesn't work. Would it be possible to > change > the build-lifecycle, so that it produces two packages? How about filing an enhancement request in Jira? Regards Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
