Also be aware that 2.1/2.2 already do some pom transformations, so this
would have to extend instead of replicate what's already there.
On Sat, May 16, 2009 at 5:14 PM, Ralph Goers wrote:
>
> On May 16, 2009, at 1:48 PM, Joerg Hohwiller wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
You could probably also add it to a jar and add that as a dependency in the
plugin block of your pom. The archiver looks up the unarchiver impl and it
needs to be known to plexus.
On Sat, May 16, 2009 at 7:20 PM, Tim O'Brien wrote:
> Is there a more straightforward way to add support for a custo
On Sat, May 16, 2009 at 4:53 PM, Joerg Hohwiller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi there,
>
>
> >> E.g. with maven 2.0.x you could have a module included in your
> >> toplevel pom that you also add as dependency to some plugin such
> >> as checkstyle or findbugs. In m
Is there a more straightforward way to add support for a custom
packaging type to the dependency plugin aside from just customizing
the components.xml, forking the plugin, and publishing your own custom
build?I'm assuming the answer is no because I see that there is an
UnArchiver with a "swc" r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Shane,
>
>> Something that I think would be useful is a language/platform element. Then
>> it's purely additions to the POM. If you could identify the
>> language/platform and it's version would that be enough for you?
>
>
> For this element, I t
On May 16, 2009, at 1:48 PM, Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ralph,
Okay. So thats what I guessed when I said that the MavenProject/
Model is
just a stupid POJO and various plugins manipulate it with side
effects.
Sounds a little hacky to me but th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
>> E.g. with maven 2.0.x you could have a module included in your
>> toplevel pom that you also add as dependency to some plugin such
>> as checkstyle or findbugs. In maven 2.1 you have to remove the
>> module declaration or you will get a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ralph,
>>
>> Okay. So thats what I guessed when I said that the MavenProject/Model is
>> just a stupid POJO and various plugins manipulate it with side effects.
>> Sounds a little hacky to me but thats the way it is. So my serialization
>> idea is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
>>
>> Do you need simple IT-projects that I shall attach to MNG-4161 and related?
>>
>
> Sample ITs for sure, and some level of detail in a proposal like these:
> http://docs.codehaus.org/display/MAVENUSER/User+Proposals
>
here is my propo
+1
it's a simple trade off. Do we like to punish >=jdk1.5 users or <=jdk1.4 users.
For a production build or in a CI system, plugin versions should be set in the
pom anyway. Otherwise a build is not 100% reproduceable.
LieGrue,
strub
- Ursprüngliche Mail
> Von: Brett Porter
> An:
Looks like it's all in the project-info plugin where the project
builder is used.
On 15-May-09, at 5:12 PM, Vincent Siveton wrote:
Hi Jason,
Thanks for your log.
Yes I think your changes are corrects. Could you please merge them to
the branch too [1]?
Cheers,
Vincent
[1]
https://svn.apa
From what Lukas pointed out it's further down in the Doxia tools that
uses the project builder. I'll go digging but I'm certain you don't
need the signature you're using.
On 15-May-09, at 5:12 PM, Vincent Siveton wrote:
Hi Jason,
Thanks for your log.
Yes I think your changes are corrects.
12 matches
Mail list logo