You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Douglas Ferguson <do...@epsiia.com> on 2006/08/04 17:31:47 UTC
Assembly
Is anybody aware of any working examples of assembly in practice?
The docs make sense but I'd like to see an example of using it in an actual
project.
Specifically,
1) What is the best way to kick it off? I was thinking perhaps this is
a pre-goal for package?
2) How can I make the output of the assembly plugin be the actual
artifact for the module?
As far as I understand, running assembly during a build would generate the
assembly but then the package phase would then create whatever package type
was defined. i.e. you'd end up with a jar that contains your assembly.
__________________________________________
Douglas W. Ferguson
EPSIIA - Another Fiserv Connection
Development
Office Phone: 512-329-0081 ext. 3309
Dial Toll Free: 800-415-5946
Mobile Phone: 512-293-7279
Fax: 512-329-0086
douglas.ferguson@epsiia.com
www.epsiia.com <http://www.epsiia.com/>
__________________________________________
RE: Assembly
Posted by Douglas Ferguson <do...@epsiia.com>.
Is there a way to release an assembly?
-----Original Message-----
From: Douglas Ferguson [mailto:douglas.ferguson@epsiia.com]
Sent: Friday, August 04, 2006 11:14 AM
To: 'Maven Users List'
Subject: RE: Assembly
Yeah,
I was thinking that part would be easy. I am about to test it local here in
a few moments. It's the assembly part. The client specific files that need
to reside outside the war that's got be stumped.
I want to be able to restrict certain files (release notes, sql files,
external configs) from going into the war. Then I want to put those files
and the war into a zip file and have that be my artifact.
D-
-----Original Message-----
From: Matt Brozowski [mailto:brozow@opennms.org]
Sent: Friday, August 04, 2006 11:05 AM
To: Maven Users List
Subject: Re: Assembly
On Aug 4, 2006, at 11:48 AM, Douglas Ferguson wrote:
> I have a strange project here. Basically they are building custom
> for each
> client. The build pulls custom jsp files & custom configuration
> into a war
> file with the context name based on the the client context name.
>
> What I want to do is move the custom stuff out of the main build
> and into
> separate project. Then the app itself will get built using normal
> maven. The
> client stuff can get merged in using assembly.
>
> I would actually like to figure out how to merge the client
> specific stuff
> into the the platform war to generate a composite war. Then I'd
> like to take
> that war and include some of the external config files and sql
> files into a
> zip file. I'd like this zip file to be the output for the client
> specific
> module. This is what would get released to the Web Hosting team.
I haven't played with this nearly as much as others here. But I'm
pretty sure that if you create a war packaged project with <type>war</
type> dependencies, it will 'merge' in someway the dependencies with
the code that is in the current project.
Hope that helps,
Matt
________________________________________________________________________
___
Matt Brozowski, OpenNMS Maintainer Main: +1 919 812
4984
The OpenNMS Group, Inc. Fax: +1
503 961 7746
Email: brozow@opennms.org URL:
http://www.opennms.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Assembly
Posted by Douglas Ferguson <do...@epsiia.com>.
Yeah,
I was thinking that part would be easy. I am about to test it local here in
a few moments. It's the assembly part. The client specific files that need
to reside outside the war that's got be stumped.
I want to be able to restrict certain files (release notes, sql files,
external configs) from going into the war. Then I want to put those files
and the war into a zip file and have that be my artifact.
D-
-----Original Message-----
From: Matt Brozowski [mailto:brozow@opennms.org]
Sent: Friday, August 04, 2006 11:05 AM
To: Maven Users List
Subject: Re: Assembly
On Aug 4, 2006, at 11:48 AM, Douglas Ferguson wrote:
> I have a strange project here. Basically they are building custom
> for each
> client. The build pulls custom jsp files & custom configuration
> into a war
> file with the context name based on the the client context name.
>
> What I want to do is move the custom stuff out of the main build
> and into
> separate project. Then the app itself will get built using normal
> maven. The
> client stuff can get merged in using assembly.
>
> I would actually like to figure out how to merge the client
> specific stuff
> into the the platform war to generate a composite war. Then I'd
> like to take
> that war and include some of the external config files and sql
> files into a
> zip file. I'd like this zip file to be the output for the client
> specific
> module. This is what would get released to the Web Hosting team.
I haven't played with this nearly as much as others here. But I'm
pretty sure that if you create a war packaged project with <type>war</
type> dependencies, it will 'merge' in someway the dependencies with
the code that is in the current project.
Hope that helps,
Matt
________________________________________________________________________
___
Matt Brozowski, OpenNMS Maintainer Main: +1 919 812
4984
The OpenNMS Group, Inc. Fax: +1
503 961 7746
Email: brozow@opennms.org URL:
http://www.opennms.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Assembly
Posted by Matt Brozowski <br...@opennms.org>.
On Aug 4, 2006, at 11:48 AM, Douglas Ferguson wrote:
> I have a strange project here. Basically they are building custom
> for each
> client. The build pulls custom jsp files & custom configuration
> into a war
> file with the context name based on the the client context name.
>
> What I want to do is move the custom stuff out of the main build
> and into
> separate project. Then the app itself will get built using normal
> maven. The
> client stuff can get merged in using assembly.
>
> I would actually like to figure out how to merge the client
> specific stuff
> into the the platform war to generate a composite war. Then I'd
> like to take
> that war and include some of the external config files and sql
> files into a
> zip file. I'd like this zip file to be the output for the client
> specific
> module. This is what would get released to the Web Hosting team.
I haven't played with this nearly as much as others here. But I'm
pretty sure that if you create a war packaged project with <type>war</
type> dependencies, it will 'merge' in someway the dependencies with
the code that is in the current project.
Hope that helps,
Matt
________________________________________________________________________
___
Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984
The OpenNMS Group, Inc. Fax: +1 503 961 7746
Email: brozow@opennms.org URL: http://www.opennms.com
RE: Assembly
Posted by Douglas Ferguson <do...@epsiia.com>.
I have a strange project here. Basically they are building custom for each
client. The build pulls custom jsp files & custom configuration into a war
file with the context name based on the the client context name.
What I want to do is move the custom stuff out of the main build and into
separate project. Then the app itself will get built using normal maven. The
client stuff can get merged in using assembly.
I would actually like to figure out how to merge the client specific stuff
into the the platform war to generate a composite war. Then I'd like to take
that war and include some of the external config files and sql files into a
zip file. I'd like this zip file to be the output for the client specific
module. This is what would get released to the Web Hosting team.
D-
> 1) What is the best way to kick it off? I was thinking perhaps this
is
> a pre-goal for package?
Separately, after you build the project. If you're trying to make the
assembly part of a single build of all the modules + the assembly,
read this first:
http://www.nabble.com/Re%3A-building-assemblies-from-the-top-level-project-d
irectory-p4735063.html
> 2) How can I make the output of the assembly plugin be the actual
> artifact for the module?
> As far as I understand, running assembly during a build would generate the
> assembly but then the package phase would then create whatever package
type
> was defined. i.e. you'd end up with a jar that contains your assembly.
What are you trying to accomplish? Getting a .zip file
installed/deployed to a repository?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Assembly
Posted by Wendy Smoak <ws...@gmail.com>.
On 8/4/06, Douglas Ferguson <do...@epsiia.com> wrote:
> Is anybody aware of any working examples of assembly in practice?
>
> The docs make sense but I'd like to see an example of using it in an actual
> project.
Both Struts and Shale have working assemblies, but we're not using the
latest released version. I haven't managed to get <modules> in the
assembly descriptor to do what I want.
http://svn.apache.org/repos/asf/shale/framework/trunk/shale-dist/
http://svn.apache.org/repos/asf/struts/struts2/trunk/assembly/
> 1) What is the best way to kick it off? I was thinking perhaps this is
> a pre-goal for package?
Separately, after you build the project. If you're trying to make the
assembly part of a single build of all the modules + the assembly,
read this first:
http://www.nabble.com/Re%3A-building-assemblies-from-the-top-level-project-directory-p4735063.html
> 2) How can I make the output of the assembly plugin be the actual
> artifact for the module?
> As far as I understand, running assembly during a build would generate the
> assembly but then the package phase would then create whatever package type
> was defined. i.e. you'd end up with a jar that contains your assembly.
What are you trying to accomplish? Getting a .zip file
installed/deployed to a repository?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org