Trouble attaching artifacts for release:perform.

2009-02-18 Thread David C. Hicks

Hi folks,

I'm attempting to attach an assembly to a sub-module's artifacts, but it 
fails to work when I do a release:perform.  I have the Assembly plugin 
bound to the package phase, but it lives in a pom type submodule.  
The assembly plugin is activated through a profile that exists in the 
submodule's pom, as well.  The idea being to not execute the assembly 
unless told to do so, thereby keeping build times at a minimum for 
development purposes.  The command used when releasing is mvn 
-Prelease_assembly release:perform.  Doing a mvn -Prelease_assembly 
clean package works just fine.  Well, the zip file is created for the 
assembly.  In the case of release:perform, the assembly plugin is never 
called.


I'm guessing that, for whatever reason, the package phase isn't 
executed, but I can't figure why that would be.  Here's my assembly 
profile/plugin configuration, in case it's helpful:


   profiles
   profile
   idrelease_assembly/id
   build
   plugins
   plugin
   
artifactIdmaven-assembly-plugin/artifactId   
   configuration

   descriptorassembly.xml/descriptor
   /configuration
   executions
   execution
   idmake-assembly/id
   phasepackage/phase
   goals
   goalattached/goal
   /goals
   /execution
   /executions
   /plugin
   /plugins
   /build
   /profile
   /profiles

Thanks,
Dave


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Attaching artifacts

2008-12-04 Thread Sommers, Elizabeth
Is there anyway to attach an artifact without writing a mojo to do it?
I would like to just do it with the pom if possible.

Liz Sommers
[EMAIL PROTECTED]
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Attaching artifacts

2008-12-04 Thread Martin Gainty

If your Maven POJO is a representation of a goal then a qualified 'yes'
example located here
http://maven.apache.org/maven-1.x/plugins/artifact/examples.html
The bigger question is Why execute a build script with no associated goal
?
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 




 Subject: Attaching artifacts
 Date: Thu, 4 Dec 2008 11:25:31 -0500
 From: [EMAIL PROTECTED]
 To: users@maven.apache.org
 
 Is there anyway to attach an artifact without writing a mojo to do it?
 I would like to just do it with the pom if possible.
 
 Liz Sommers
 [EMAIL PROTECTED]
  
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

_
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008

RE: [SPAM] RE: Attaching artifacts

2008-12-04 Thread Sommers, Elizabeth
I am trying to deploy an .exe file to our repository.  I am willing to
build a simple jar to go with it and use jar packaging but I will still
need to attach the .exe file. 

-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 04, 2008 11:45 AM
To: users@maven.apache.org
Subject: [SPAM] RE: Attaching artifacts
Importance: Low


If your Maven POJO is a representation of a goal then a qualified 'yes'
example located here
http://maven.apache.org/maven-1.x/plugins/artifact/examples.html
The bigger question is Why execute a build script with no associated
goal ?
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 




 Subject: Attaching artifacts
 Date: Thu, 4 Dec 2008 11:25:31 -0500
 From: [EMAIL PROTECTED]
 To: users@maven.apache.org
 
 Is there anyway to attach an artifact without writing a mojo to do it?
 I would like to just do it with the pom if possible.
 
 Liz Sommers
 [EMAIL PROTECTED]
  
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

_
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_spe
ed_122008

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [SPAM] RE: Attaching artifacts

2008-12-04 Thread Stephen Connolly
Use pom packaging so that you don't deploy a jar.

Use the buildhelper-maven-plugin bound to the package phase to attach the
exe to your build.

Use the exec-maven-plugin bound to the compile phase to (I'm guessing)
invoke your native code build system to generate the .exe.

That's an all-in-the-pom way that is in the Maven spirit

-Stephen

2008/12/4 Sommers, Elizabeth [EMAIL PROTECTED]

 I am trying to deploy an .exe file to our repository.  I am willing to
 build a simple jar to go with it and use jar packaging but I will still
 need to attach the .exe file.

 -Original Message-
 From: Martin Gainty [mailto:[EMAIL PROTECTED]
 Sent: Thursday, December 04, 2008 11:45 AM
 To: users@maven.apache.org
 Subject: [SPAM] RE: Attaching artifacts
 Importance: Low


 If your Maven POJO is a representation of a goal then a qualified 'yes'
 example located here
 http://maven.apache.org/maven-1.x/plugins/artifact/examples.html
 The bigger question is Why execute a build script with no associated
 goal ?
 Martin
 __
 Disclaimer and confidentiality note
 Everything in this e-mail and any attachments relates to the official
 business of Sender. This transmission is of a confidential nature and
 Sender does not endorse distribution to any party other than intended
 recipient. Sender does not necessarily endorse content contained within
 this transmission.




  Subject: Attaching artifacts
  Date: Thu, 4 Dec 2008 11:25:31 -0500
  From: [EMAIL PROTECTED]
  To: users@maven.apache.org
 
  Is there anyway to attach an artifact without writing a mojo to do it?
  I would like to just do it with the pom if possible.
 
  Liz Sommers
  [EMAIL PROTECTED]
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 

 _
 Send e-mail faster without improving your typing skills.
 http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_spe
 ed_122008http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: Attaching artifacts

2008-12-04 Thread Brian Fox

Use the build-helper plugin

--Brian (mobile)


On Dec 4, 2008, at 8:25 AM, Sommers, Elizabeth [EMAIL PROTECTED] 
 wrote:



Is there anyway to attach an artifact without writing a mojo to do it?
I would like to just do it with the pom if possible.

Liz Sommers
[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Mojos Attaching Artifacts to Project for Install Deploy

2008-02-02 Thread simon

On Fri, 2008-02-01 at 17:15 -0700, Cam wrote:
 Hi,
 
 I'm looking for a way to attach an extra generated artifact to a project 
 so it's installed and deployed in the standard project lifecycle, how 
 can i do this?  Do i need to write a mojo or can i just add this as part 
 of the pom config?

See build-helper-plugin:

  http://mojo.codehaus.org/build-helper-maven-plugin/index.html

 
 Also, does anyone know if it's possible to create a mojo which defines a 
 new project packaging?

This is definitely possible, although I don't personally know how.

See the standard jar, war, ear plugins, or the apache felix plugin
(defines packaging of bundle), etc.

Regards, Simon



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Mojos Attaching Artifacts to Project for Install Deploy

2008-02-02 Thread Erez Nahir
We are using
http://www.jfrog.org/sites/jade-plugins/latest/jade-plugin-parent/jade-build-plugin-parent/jade-multijar-plugin/index.html

Erez.

On Feb 2, 2008 10:12 AM, simon [EMAIL PROTECTED] wrote:


 On Fri, 2008-02-01 at 17:15 -0700, Cam wrote:
  Hi,
 
  I'm looking for a way to attach an extra generated artifact to a project
  so it's installed and deployed in the standard project lifecycle, how
  can i do this?  Do i need to write a mojo or can i just add this as part
  of the pom config?

 See build-helper-plugin:

  http://mojo.codehaus.org/build-helper-maven-plugin/index.html

 
  Also, does anyone know if it's possible to create a mojo which defines a
  new project packaging?

 This is definitely possible, although I don't personally know how.

 See the standard jar, war, ear plugins, or the apache felix plugin
 (defines packaging of bundle), etc.

 Regards, Simon



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: Mojos Attaching Artifacts to Project for Install Deploy

2008-02-02 Thread Cam

great - thanks for the links

cam

simon wrote:

On Fri, 2008-02-01 at 17:15 -0700, Cam wrote:
  

Hi,

I'm looking for a way to attach an extra generated artifact to a project 
so it's installed and deployed in the standard project lifecycle, how 
can i do this?  Do i need to write a mojo or can i just add this as part 
of the pom config?



See build-helper-plugin:

  http://mojo.codehaus.org/build-helper-maven-plugin/index.html

  
Also, does anyone know if it's possible to create a mojo which defines a 
new project packaging?



This is definitely possible, although I don't personally know how.

See the standard jar, war, ear plugins, or the apache felix plugin
(defines packaging of bundle), etc.

Regards, Simon



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Mojos Attaching Artifacts to Project for Install Deploy

2008-02-01 Thread Cam

Hi,

I'm looking for a way to attach an extra generated artifact to a project 
so it's installed and deployed in the standard project lifecycle, how 
can i do this?  Do i need to write a mojo or can i just add this as part 
of the pom config?


Also, does anyone know if it's possible to create a mojo which defines a 
new project packaging?


Thanks,
Cam

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Attaching artifacts from a reporting plugin

2007-09-21 Thread Wouter Hermeling

Are you sure the artifact isn't attached? If the code would work the artifact
will only be attached after the site:site goals had been run. If you want to
deploy the attached artifact you would have to run:

mvn site deploy

So my question is: In what way are you going to use the attached artifact?
And what does not seem to work then?



Lizzy wrote:
 
 
 Is there any way to attach an artifact (or define an artifact) from a
 reporting plugin?  It is simple enough to do in a build plugin, but I
 cannot figure out how to do it from a report plugin.
 
 helper.attachArtifact(project,zip,siteReport,coeOutputFile);
 
 and
 
 project.getArtifact().setFile(coeOutputFile);
 
 both seem to be ignored when the plugin is run.
 
 Thanks
 Liz Sommers
 [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Attaching-artifacts-from-a-reporting-plugin-tf4480848s177.html#a12812203
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Attaching artifacts from a reporting plugin

2007-09-19 Thread Sommers, Elizabeth

Is there any way to attach an artifact (or define an artifact) from a reporting 
plugin?  It is simple enough to do in a build plugin, but I cannot figure out 
how to do it from a report plugin.

helper.attachArtifact(project,zip,siteReport,coeOutputFile);

and

project.getArtifact().setFile(coeOutputFile);

both seem to be ignored when the plugin is run.

Thanks
Liz Sommers
[EMAIL PROTECTED]