Re: assembly:single failing

2007-10-19 Thread Tim Kettler
Hi,

is the pom where the assembly is build also used as the parent pom for
the modules? If yes, you've hit a design flaw in maven. Currently, the
parent relationship introduces a dependency from child to parent, hence
the parent is build first and the artifact of the child doesn't exist
yet. Look at your log output, you should see that the parent project is
build first.

See this thread [1] for an explanation from a developer. If you  need to
create the assembly attached to the build lifecycle instead of the
proposed solution to just build it manually you need to factor out
either the parent-pom features or the assembly building stuff to a
separate pom.

-Tim

[1]
http://www.nabble.com/Problem-attaching-assembly-to-multi-module-pom-project-tf4576505s177.html#a13063505n

[EMAIL PROTECTED] schrieb:
 Hi again,
 
 (thanks to Stéphane Veyret for my previous question, I moved out the 
 phase and goals tags in an execution tag and it is triggered now -- 
 but does not work as expected)
 
 I know the subject has been brought up multiple times, but reading the 
 whole summary thread 
 (http://www.mail-archive.com/users@maven.apache.org/msg53354.html, linking 
 to http://jira.codehaus.org/browse/MASSEMBLY-97), I still can not use 
 assembly:single in my multi-module project.
 
 My main pom looks like :
 
 ...
 build
 plugins
  
 plugin
 artifactIdmaven-assembly-plugin/artifactId
 version2.2-beta-1/version
 inheritedfalse/inherited
 configuration
 appendAssemblyIdfalse/appendAssemblyId
 descriptors
 descriptorsrc/main/assembly/assembly.xml/
 descriptor
 /descriptors
 /configuration
 
 executions
 execution
 phasepackage/phase
 goals
 goalsingle/goal
 /goals
 /execution
 /executions
 
 /plugin
 
 From what I've read, the phase must be bound for the single goal. If I use 
 'mvn package' from the command line, I get :
 
 [INFO] Failed to create assembly: Artifact: 
 foo:module:jar:3.0.7-SNAPSHOT (included by module) does not have an 
 artifact with a file. Please ensure the package phase is run before the 
 assembly is generated.
 
 If it run 'assembly:assembly' from the command line, I get (for the main 
 project) :
 
 [INFO] Error reading assemblies: No assembly descriptors found.
 
 
 any idea about why it seems to work for everybody else except me? :)
 
 best regards,
 
 --Stéphane
 
 
 This message and any attachments (the message) is
 intended solely for the addressees and is confidential. 
 If you receive this message in error, please delete it and 
 immediately notify the sender. Any use not in accord with 
 its purpose, any dissemination or disclosure, either whole 
 or partial, is prohibited except formal approval. The internet
 can not guarantee the integrity of this message. 
 BNP PARIBAS (and its subsidiaries) shall (will) not 
 therefore be liable for the message if modified. 
 
 -
 
 Ce message et toutes les pieces jointes (ci-apres le 
 message) sont etablis a l'intention exclusive de ses 
 destinataires et sont confidentiels. Si vous recevez ce 
 message par erreur, merci de le detruire et d'en avertir 
 immediatement l'expediteur. Toute utilisation de ce 
 message non conforme a sa destination, toute diffusion 
 ou toute publication, totale ou partielle, est interdite, sauf 
 autorisation expresse. L'internet ne permettant pas 
 d'assurer l'integrite de ce message, BNP PARIBAS (et ses
 filiales) decline(nt) toute responsabilite au titre de ce 
 message, dans l'hypothese ou il aurait ete modifie.
 
 


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



assembly:single failing

2007-10-19 Thread stephane . demurget
Hi again,

(thanks to Stéphane Veyret for my previous question, I moved out the 
phase and goals tags in an execution tag and it is triggered now -- 
but does not work as expected)

I know the subject has been brought up multiple times, but reading the 
whole summary thread 
(http://www.mail-archive.com/users@maven.apache.org/msg53354.html, linking 
to http://jira.codehaus.org/browse/MASSEMBLY-97), I still can not use 
assembly:single in my multi-module project.

My main pom looks like :

...
build
plugins
 
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-1/version
inheritedfalse/inherited
configuration
appendAssemblyIdfalse/appendAssemblyId
descriptors
descriptorsrc/main/assembly/assembly.xml/
descriptor
/descriptors
/configuration

executions
execution
phasepackage/phase
goals
goalsingle/goal
/goals
/execution
/executions

/plugin

From what I've read, the phase must be bound for the single goal. If I use 
'mvn package' from the command line, I get :

[INFO] Failed to create assembly: Artifact: 
foo:module:jar:3.0.7-SNAPSHOT (included by module) does not have an 
artifact with a file. Please ensure the package phase is run before the 
assembly is generated.

If it run 'assembly:assembly' from the command line, I get (for the main 
project) :

[INFO] Error reading assemblies: No assembly descriptors found.


any idea about why it seems to work for everybody else except me? :)

best regards,

--Stéphane


This message and any attachments (the message) is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

-

Ce message et toutes les pieces jointes (ci-apres le 
message) sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.