-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jörg Schaible wrote:
> Hi Jörg,
Hi Jörg,
nice to "meet" again ;)
>
> [snip]
>
> So did you have multiple modules for each Solaris package or a single module
> with a Mojo that creates two artifacts (like the EJB and its client)?
I created one module per package. This is in principle the idea of maven to have
one artifact per module. The only part that breaks out is the configuration
package that is different for each machine where it will be deployed to (test,
staging, live1, live2).
For EXT and CUST I can put the dependencies in the parent POM.
> In your case I might have taken the second approach,
> since it is logical module, but your deployment requires two separate Solaris
packages.
> In the Mojos configuration you would just need to declare
> the groupIds of the custom packages e.g. like:
>
> <customGroupIds>
> <customGroupId>my.foo.id</customGroupId>
> </customGroupIds>
You are right - this way ensures that it will work in further releases and is
not missusing the POM. But it is quite greedy:
<build>
<plugins>
<plugin>
<groupId>my.foo</groupId>
<artifactId>mojo-hack</artifactId>
<executions>
<execution>
<goal>hack-dependencies</goal>
<configuration>
<customGroupIds>
<customGroupId>my.foo.id</customGroupId>
</customGroupIds>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
What I like more about my approach is that it is more natural and easier to
maintain if I express this as an exclusion in the dependencies. It is actually
not a plugin specific thing but really a configuration to express the modules
dependencies.
What I wanted to point out is that I have a need to express dependencies in a
way that is NOT yet supported with maven. I use maven for open-source as well as
for business. And in business it is a very common need to build packages in a
way as I described. Now the maven community could think about supporting such
exclusions in the core dependency management or come to the point that this is a
too specific situation and should be solved as you pointed out. But then the
next question is, if this specific solution shouldn't be available in the
maven-dependency-plugin.
>
> and take that list as exclusion for the the EXT package and as inclusion for
> your CUST package.
>
>
>>BTW: the plexus/components.xml was really hard to figure out.
>>Is there any
>>documentation that I missed? Should I write a mini xdoc about
>>what I figured out
>>about how to create your own packaging?
>>Are you interested in a maven-solaris-package-plugin ?
>>If there is a real solution for my "HACK" I would love to
>>donate the plugin to
>>maven.
>
>
> I doubt that anybody is against additional docs :)
I'll write an xdoc in the next weeks and put it into jira.
But I think I will not include my "Hack" and suggest to use the
maven-dependency-plugin. But then I have to make the ant stuff to be the plugin
itself. I haven't checked out yet, if it is possible to have an ant script as
maven2 plugin.
>
> - Jörg
Regards
Jörg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEtqMrmPuec2Dcv/8RArH1AJ455eUvwFb+buwLZouaKduXKcZFugCfbFiJ
iaD08di7zanQ8CRTA/s5TUY=
=ZZ3R
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
