RE: order of the unpacking from \unpack-dependencys\
Hi I have the following unpack goal:
execution
idunpack-modules/id
phaseverify/phase
goals
goalunpack-dependencies/goal
/goals
configuration
outputDirectory${basedir}/target/dist_tmp/classes/outputDirectory
includeGroupIds${project.groupId}/includeGroupIds
includeClassifiersclasses/includeClassifiers
includeTypesjar/includeTypes
includeScoperuntime/includeScope
excludeTransitivetrue/excludeTransitive
includes**/*.class/includes
excludesMETA-INF/**,com/atomikos/**/excludes
/configuration
/execution
The identification works with the group id. The solution with a separate
unpack per module would be possible.
But I would prefer that the unpack-dependencies uses the order in which i
define the dependency's. This would prevent further problems as mentioned by
Michael.
But what puzzles me is that the unpack order seams arbitrary but fixed.
Maybe i should as in the developer mailing list for an deeper insight of the
matter.
Regards David
order of the unpacking from unpack-dependencys
Hello,, i have the following strange problem with the unpack-dependencys in my pom. What i want is to unpack the scripts i need in the deploy directory. The problem is that i have multiple modules with the same scripts. Therefor to have a correct result they must be overwritten in the right order. Sadly unpack-dependencys does not care about the order in which i declare the dependency's. But strangely the order remains always the same so there must be a determining order. Could me help somebody to understand and hopefully manipulate the unpack order so that my project will be deployed correctly. Regards David
Re: order of the unpacking from unpack-dependencys
Hi, You could perhaps try the unpack goal... You do have to add all the dependencies again, but that one should take the order in which the artifacts are listed. Roland On 12-05-11 15:52, David Bräutigam wrote: Hello,, i have the following strange problem with the unpack-dependencys in my pom. What i want is to unpack the scripts i need in the deploy directory. The problem is that i have multiple modules with the same scripts. Therefor to have a correct result they must be overwritten in the right order. Sadly unpack-dependencys does not care about the order in which i declare the dependency's. But strangely the order remains always the same so there must be a determining order. Could me help somebody to understand and hopefully manipulate the unpack order so that my project will be deployed correctly. Regards David -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - business. people. technology. -
Re: order of the unpacking from unpack-dependencys
Or use maybe use both. Put an excludes in for the unpack-dependencies mojo to exclude all scripts and then use an includes in the unpack mojo for just the scripts you actually want from the proper artifact. Over-writing in the right order seems like the sort of thing that will eventually come back to cause headaches down the road. Better to just get the right file and none of the wrong ones. Mike On Thu, May 12, 2011 at 10:02 AM, Asmann, Roland roland.asm...@adesso.at wrote: Hi, You could perhaps try the unpack goal... You do have to add all the dependencies again, but that one should take the order in which the artifacts are listed. Roland On 12-05-11 15:52, David Bräutigam wrote: Hello,, i have the following strange problem with the unpack-dependencys in my pom. What i want is to unpack the scripts i need in the deploy directory. The problem is that i have multiple modules with the same scripts. Therefor to have a correct result they must be overwritten in the right order. Sadly unpack-dependencys does not care about the order in which i declare the dependency's. But strangely the order remains always the same so there must be a determining order. Could me help somebody to understand and hopefully manipulate the unpack order so that my project will be deployed correctly. Regards David -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - business. people. technology. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: order of the unpacking from unpack-dependencys
If you have multiple unpack steps, what are their ID's? Or are you saying you have one unpack step with multiple artifacts given? -Original Message- From: David Bräutigam [mailto:david.braeuti...@googlemail.com] Sent: Thursday, May 12, 2011 9:53 AM To: users@maven.apache.org Subject: order of the unpacking from unpack-dependencys Hello,, i have the following strange problem with the unpack-dependencys in my pom. What i want is to unpack the scripts i need in the deploy directory. The problem is that i have multiple modules with the same scripts. Therefor to have a correct result they must be overwritten in the right order. Sadly unpack-dependencys does not care about the order in which i declare the dependency's. But strangely the order remains always the same so there must be a determining order. Could me help somebody to understand and hopefully manipulate the unpack order so that my project will be deployed correctly. Regards David CONFIDENTIALITY NOTICE: This e-mail and the information transmitted within including any attachments is only for the recipient(s) to which it is intended and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of; or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please send the e-mail back by replying to the sender and permanently delete the entire message and its attachments from all computers and network systems involved in its receipt.
