Hmm, I would definitely not want an un-archived assembly directory to be
installed/deployed to a repository, this was really just intended as a
development-time tool. I am still very new to Maven, so I'm not quite sure
of the best approach here. I will take another look. Maybe my patch should
See MNG-735 for a patch that adds support for a 'directory' archive type
On 8/14/05, Daniel Krisher [EMAIL PROTECTED] wrote:
Thanks for the quick response... I've already looked at the assembly
plugin source, I'll put together a patch tonight or tomorrow morning and
submit it along with a
Hi Daniel,
FYI, I have assembly patches sitting in Jira, and awaiting publication
to svn:
1) MNG-723: Adds an 'unpack' goal that unpacks all project dependencies
(jars and zips) into the working directory.
2) MNG-483: Attaches all assemblies as project artifacts, so that they
get installed
I recently made the jump from Ant to Maven (2.0-beta snapshot), and I must
say that I am very impressed. Having never used Maven before, it only took a
couple of hours to set up a fairly complex multi-module build process. We
had spent a significant amount of time attempting to engineer a
Hi Daniel,
This sounds like a reasonable request. There are two things I can think of:
- create an assembly type that is just the directory
- pass a flag to the assembly plugin to not create the archive
The second would be preferable if at some point you intend to use the
archive to distribute.
Thanks for the quick response... I've already looked at the assembly plugin
source, I'll put together a patch tonight or tomorrow morning and submit it
along with a JIRA request.
Thanks
Dan Krisher
On 8/14/05, Brett Porter [EMAIL PROTECTED] wrote:
Hi Daniel,
This sounds like a
