Hi all,
I'm currently trying to write a small internal Maven plugin and as we're
on Maven 3.1+ only, I have no need to be backwards compatible.
My struggle is currently in finding good resources how a current Maven
plugin should be written. I found documentation of the Java5
annotations, so far s
Hi Robert,
Am 30.10.2013 19:48, schrieb Robert Scholte:
> I haven't finished the complete release process yet.
> There seems to be some misconfiguration to publish/copy the staged docs
> to production.
> So I need to fix that first before I'll update the plugins page and send
> the announcement.
Hi all,
Am 23.10.2013 21:52, schrieb Robert Scholte:
> Staging site:
> http://maven.apache.org/maven-release-archives/maven-release-2.4.2/maven-release-plugin/
As the plugin is released, shouldn't the site also be promoted?
http://maven.apache.org/maven-release/maven-release-plugin/ still schows
Hi Jason,
that sounds great. Do you have information on
http://jira.codehaus.org/browse/MNG-2802
Recently this turned out to produce quite some build errors on our
Jenkins. In the above mentioned Issue you noted, that you wanted to
integrate that once Maven is upgraded to 0.9.0.M1 - which now is
Am 28.09.2012 10:41, schrieb Jörg Schaible:
> You're aware that modern Maven plugins use now real annotations themselves?
I've heard of it, but the last time I searched for it (a few months ago)
did not yet find any documentation or even core plugins using that
mechanism to see how it looks like or
Hi,
Am 27.09.2012 18:42, schrieb Jörg Schaible:
> In M3 the plugins are no longer shared within the reactor i.e. each plugin
> is using its own classloader and can therefore have any arbitrary
> dependency. So if your plugin depends on another plugin, there should be no
> difference to any othe
Hey Chris,
I'm sorry :( This was not my intention.
See the other mail, we found a workaround ;)
Greetings
-Sascha-
Am 28.09.2012 07:50, schrieb Chris Graham:
> Yes, thanks. You've send me back to the drawing board...
>
> On 28/09/2012, at 12:23 AM, Sascha Vogt wrote:
chrieb Jörg Schaible:
>>> Sascha Vogt wrote:
>> The idea was to have one Mojo extend another Mojo.
> In M2, it is simply not reliable and should therefore never be done.
Ok, for M2 the stuff we did is bad :) For now let's concentrate on M3
>> There is also a
>
Am 27.09.2012 15:07, schrieb Jörg Schaible:
> Sascha Vogt wrote:
>> I need to find out if the dependency is a Maven plugin. With Maven 2.x
>> one could check the type by comparing Artifact.getType() to
>> "maven-plugin". With Maven 3 this returns now "jar"
Hi all,
I currently have a small issue with upgrading to Maven 3 and a custom
mojo I wrote.
I need to find out if the dependency is a Maven plugin. With Maven 2.x
one could check the type by comparing Artifact.getType() to
"maven-plugin". With Maven 3 this returns now "jar" instead of
"maven-plug
> compiler-plugin to 1.9.2 to fix the problem.
>
> Kristian
>
>
> 2012/9/6 Kristian Rosenvold :
>> It's obviously a bug ;)
>>
>> Kristian
>>
>>
>> 2012/9/6 Sascha Vogt :
>>> Hi all,
>>>
>>> last week I creat
Hi all,
last week I created http://jira.codehaus.org/browse/MCOMPILER-179 after
a short discussion on maven-user.
I bring this up on the dev list, as I think this is quite an issue
because it makes compile errors really hard to spot (if one has a few
warnings one cannot get rid of).
So the quest
Hi Asaf,
Am 01.04.2012 22:50, schrieb Asaf Mesika:
> Hi,
>
> Works great! I have the MavenProject, but since I'm running
> project-less(@requiresProject false), the lazy initialized dependency
> artifacts are not present. What API should I use to obtain the entire
> dependency (direct and transit
13 matches
Mail list logo
