Re: [M2] Custom 'packaging' without a custom plugin?
http://mojo.codehaus.org/build-helper-maven-plugin/howto.html basically right after you use exec or antrun plugin to build your swf file, you can use build-helper-maven-plugin:attach-artifact goal to configure maven to install or deploy your swf to repo as needed On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: On 4/4/06, dan tran [EMAIL PROTECTED] wrote: packagingpom/packaging Yep, that did the trick. Thanks! if you want to deploy your .swf file, use build-helper-maven-plugin to attach that artifact to the project to be deploy/install Hmm, I've been using deploy:deploy-file up 'til now, but I'm far from au fait with respect to the way deployment works. Could you clarify, please? -- Martin Cooper -D On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: I have a project that generates a Flash SWF file as its artifact. At the moment, I have the 'packaging' value set to 'jar', for lack of a better value. The problem is that this causes an empty jar file to be created, alongside my SWF file. However, I don't see how I can avoid this, since the other built in packaging types (e.g. war, ear) are no better suited to my needs. My POM is very simple, comprising only the use of the dependency and exec plugins. Looking at the M2 docs, the only way I see to have a custom packaging is to define it within a custom plugin. However, I don't need any additional plugins, and that seems like a complicated way to solve a simple problem. Is there some other way I can either define a custom packaging (or just a lifecycle), or even just tell the jar packaging not to do most of what it does by default? -- Martin Cooper
Re: [M2] Custom 'packaging' without a custom plugin?
Dan, you rock! Ian It's better to be hated for who you are than loved for who you are not Ian D. Stewart Appl Dev Analyst-Advisory, DCS Automation JPMorganChase Global Technology Infrastructure Phone: (614) 244-2564 Pager: (888) 260-0078 dan tran [EMAIL PROTECTED]To: Maven Users List users@maven.apache.org m cc: Subject: Re: [M2] Custom 'packaging' without a custom plugin? 04/05/2006 01:05 AM Please respond to Maven Users List packagingpom/packaging if you want to deploy your .swf file, use build-helper-maven-plugin to attach that artifact to the project to be deploy/install -D On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: I have a project that generates a Flash SWF file as its artifact. At the moment, I have the 'packaging' value set to 'jar', for lack of a better value. The problem is that this causes an empty jar file to be created, alongside my SWF file. However, I don't see how I can avoid this, since the other built in packaging types (e.g. war, ear) are no better suited to my needs. My POM is very simple, comprising only the use of the dependency and exec plugins. Looking at the M2 docs, the only way I see to have a custom packaging is to define it within a custom plugin. However, I don't need any additional plugins, and that seems like a complicated way to solve a simple problem. Is there some other way I can either define a custom packaging (or just a lifecycle), or even just tell the jar packaging not to do most of what it does by default? -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Custom 'packaging' without a custom plugin?
On 4/4/06, dan tran [EMAIL PROTECTED] wrote: http://mojo.codehaus.org/build-helper-maven-plugin/howto.html Yes, I found that. By the way, the page title looks wrong. It's currently Maven Build Dependency Plugin - Maven Build Helper Plugin. basically right after you use exec or antrun plugin to build your swf file, you can use build-helper-maven-plugin:attach-artifact goal to configure maven to install or deploy your swf to repo as needed The part I'm missing - sorry if I'm being dense - is why I need that. What does it mean to attach ... build outputs to the project for install and deploy, and why is that different / better than simply using deploy:deploy-file? -- Martin Cooper On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: On 4/4/06, dan tran [EMAIL PROTECTED] wrote: packagingpom/packaging Yep, that did the trick. Thanks! if you want to deploy your .swf file, use build-helper-maven-plugin to attach that artifact to the project to be deploy/install Hmm, I've been using deploy:deploy-file up 'til now, but I'm far from au fait with respect to the way deployment works. Could you clarify, please? -- Martin Cooper -D On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: I have a project that generates a Flash SWF file as its artifact. At the moment, I have the 'packaging' value set to 'jar', for lack of a better value. The problem is that this causes an empty jar file to be created, alongside my SWF file. However, I don't see how I can avoid this, since the other built in packaging types (e.g. war, ear) are no better suited to my needs. My POM is very simple, comprising only the use of the dependency and exec plugins. Looking at the M2 docs, the only way I see to have a custom packaging is to define it within a custom plugin. However, I don't need any additional plugins, and that seems like a complicated way to solve a simple problem. Is there some other way I can either define a custom packaging (or just a lifecycle), or even just tell the jar packaging not to do most of what it does by default? -- Martin Cooper
Re: [M2] Custom 'packaging' without a custom plugin?
On 4/5/06, Martin Cooper [EMAIL PROTECTED] wrote: On 4/4/06, dan tran [EMAIL PROTECTED] wrote: http://mojo.codehaus.org/build-helper-maven-plugin/howto.html Yes, I found that. By the way, the page title looks wrong. It's currently Maven Build Dependency Plugin - Maven Build Helper Plugin. basically right after you use exec or antrun plugin to build your swf file, you can use build-helper-maven-plugin:attach-artifact goal to configure maven to install or deploy your swf to repo as needed The part I'm missing - sorry if I'm being dense - is why I need that. What does it mean to attach ... build outputs to the project for install and deploy, and why is that different / better than simply using deploy:deploy-file? Never mind - I figured it out, and it's working now. Cool. Thanks! (Reminder to self: Consume more coffee before delving into Maven first thing in the morning...) -- Martin Cooper -- Martin Cooper On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: On 4/4/06, dan tran [EMAIL PROTECTED] wrote: packagingpom/packaging Yep, that did the trick. Thanks! if you want to deploy your .swf file, use build-helper-maven-plugin to attach that artifact to the project to be deploy/install Hmm, I've been using deploy:deploy-file up 'til now, but I'm far from au fait with respect to the way deployment works. Could you clarify, please? -- Martin Cooper -D On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: I have a project that generates a Flash SWF file as its artifact. At the moment, I have the 'packaging' value set to 'jar', for lack of a better value. The problem is that this causes an empty jar file to be created, alongside my SWF file. However, I don't see how I can avoid this, since the other built in packaging types (e.g. war, ear) are no better suited to my needs. My POM is very simple, comprising only the use of the dependency and exec plugins. Looking at the M2 docs, the only way I see to have a custom packaging is to define it within a custom plugin. However, I don't need any additional plugins, and that seems like a complicated way to solve a simple problem. Is there some other way I can either define a custom packaging (or just a lifecycle), or even just tell the jar packaging not to do most of what it does by default? -- Martin Cooper
Re: [M2] Custom 'packaging' without a custom plugin?
On 4/5/06, Martin Cooper [EMAIL PROTECTED] wrote: On 4/4/06, dan tran [EMAIL PROTECTED] wrote: http://mojo.codehaus.org/build-helper-maven-plugin/howto.html Yes, I found that. By the way, the page title looks wrong. It's currently Maven Build Dependency Plugin - Maven Build Helper Plugin. basically right after you use exec or antrun plugin to build your swf file, you can use build-helper-maven-plugin:attach-artifact goal to configure maven to install or deploy your swf to repo as needed The part I'm missing - sorry if I'm being dense - is why I need that. What does it mean to attach ... build outputs to the project for install and deploy, and why is that different / better than simply using deploy:deploy-file? so that mvn install/deploy will do both of building your custom artifact and deploy/install it -D -- Martin Cooper On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: On 4/4/06, dan tran [EMAIL PROTECTED] wrote: packagingpom/packaging Yep, that did the trick. Thanks! if you want to deploy your .swf file, use build-helper-maven-plugin to attach that artifact to the project to be deploy/install Hmm, I've been using deploy:deploy-file up 'til now, but I'm far from au fait with respect to the way deployment works. Could you clarify, please? -- Martin Cooper -D On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: I have a project that generates a Flash SWF file as its artifact. At the moment, I have the 'packaging' value set to 'jar', for lack of a better value. The problem is that this causes an empty jar file to be created, alongside my SWF file. However, I don't see how I can avoid this, since the other built in packaging types (e.g. war, ear) are no better suited to my needs. My POM is very simple, comprising only the use of the dependency and exec plugins. Looking at the M2 docs, the only way I see to have a custom packaging is to define it within a custom plugin. However, I don't need any additional plugins, and that seems like a complicated way to solve a simple problem. Is there some other way I can either define a custom packaging (or just a lifecycle), or even just tell the jar packaging not to do most of what it does by default? -- Martin Cooper
Re: [M2] Custom 'packaging' without a custom plugin?
packagingpom/packaging if you want to deploy your .swf file, use build-helper-maven-plugin to attach that artifact to the project to be deploy/install -D On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: I have a project that generates a Flash SWF file as its artifact. At the moment, I have the 'packaging' value set to 'jar', for lack of a better value. The problem is that this causes an empty jar file to be created, alongside my SWF file. However, I don't see how I can avoid this, since the other built in packaging types (e.g. war, ear) are no better suited to my needs. My POM is very simple, comprising only the use of the dependency and exec plugins. Looking at the M2 docs, the only way I see to have a custom packaging is to define it within a custom plugin. However, I don't need any additional plugins, and that seems like a complicated way to solve a simple problem. Is there some other way I can either define a custom packaging (or just a lifecycle), or even just tell the jar packaging not to do most of what it does by default? -- Martin Cooper
Re: [M2] Custom 'packaging' without a custom plugin?
On 4/4/06, dan tran [EMAIL PROTECTED] wrote: packagingpom/packaging Yep, that did the trick. Thanks! if you want to deploy your .swf file, use build-helper-maven-plugin to attach that artifact to the project to be deploy/install Hmm, I've been using deploy:deploy-file up 'til now, but I'm far from au fait with respect to the way deployment works. Could you clarify, please? -- Martin Cooper -D On 4/4/06, Martin Cooper [EMAIL PROTECTED] wrote: I have a project that generates a Flash SWF file as its artifact. At the moment, I have the 'packaging' value set to 'jar', for lack of a better value. The problem is that this causes an empty jar file to be created, alongside my SWF file. However, I don't see how I can avoid this, since the other built in packaging types (e.g. war, ear) are no better suited to my needs. My POM is very simple, comprising only the use of the dependency and exec plugins. Looking at the M2 docs, the only way I see to have a custom packaging is to define it within a custom plugin. However, I don't need any additional plugins, and that seems like a complicated way to solve a simple problem. Is there some other way I can either define a custom packaging (or just a lifecycle), or even just tell the jar packaging not to do most of what it does by default? -- Martin Cooper
