On Wed, Oct 20, 2010 at 11:43 AM, Phillip Hellewell wrote:
> Hi all,
>
> Before I go down the road of writing my own plugin, can anyone tell me
> if there already exists a plugin that provides this functionality?
>
> 1. Resolve all dependencies using functionality similar to dependency:tree.
>
On Wed, Oct 20, 2010 at 12:46 PM, Anders Hammar wrote:
>> 2. Avoid downloading binary packages (for remote employees it may be
>> faster to build the code than to download binaries).
>>
> I very much doubt that! Performing a build will take time to compile and
> test (don't forget the unit tests)
> 2. Avoid downloading binary packages (for remote employees it may be
> faster to build the code than to download binaries).
>
>
I very much doubt that! Performing a build will take time to compile and
test (don't forget the unit tests) as well as downloading test dependencies,
which aren't downlo
Hi all,
Before I go down the road of writing my own plugin, can anyone tell me
if there already exists a plugin that provides this functionality?
1. Resolve all dependencies using functionality similar to dependency:tree.
- (only fetch poms to local repo, not the jar/zip/etc package)
2. Perfo
i have had the sources in src/main/java previously but that didn't
help either :-)
but it works now ;-)
the last thing i'm struggling with now is that hudson is executing my
builds with jre, not jdk, therefore my apt processors do not work.
On Tue, Oct 5, 2010 at 2:52 PM, Wendy Smoak wrote:
> O
On Tue, Oct 5, 2010 at 7:10 AM, Leon Rosenberg wrote:
> basically add this to my pom
...
> ${project.basedir}/java
Did you add this at the same time? If so, that's what did it...
without that Maven would expect the classes to be in src/main/java, so
nothing would have been compiled.
--
Wend
Hello Jörg,
basically add this to my pom
${artifactId}-${version}
${project.basedir}/java
org.apache.maven.plugins
maven-compiler-plugin
2.3.2
Hi Leon,
Leon Rosenberg wrote:
> ok, resolved, my error, i forgot to explicitly include the compile
> plugin, therefor my plugin was packaged but contained no classes.
> thanx for the help. now i only need to force the using project to add
> generated classes to the source dirs ;-)
What do you m
heck the plugin.xml file which is being
>> generated. Also mvn help:describe (which uses the plugin.xml
>> descriptor IIRC).
>>
>> Also, my guess is that you don't actually want to include this line:
>> * @execute phase="generate-sources"
>>
>> B
rces"
>
> But I doubt that's the source of the error below.
>
> Justin
>
>
>
> On Mon, Oct 4, 2010 at 5:50 PM, Leon Rosenberg
> wrote:
>> Hello,
>>
>> I'm currently writing my first plugin and am struggling with very basics.
>> From the guid
source of the error below.
Justin
On Mon, Oct 4, 2010 at 5:50 PM, Leon Rosenberg wrote:
> Hello,
>
> I'm currently writing my first plugin and am struggling with very basics.
> From the guide
> (http://maven.apache.org/guides/plugin/guide-java-plugin-development.html)
>
Hello,
I'm currently writing my first plugin and am struggling with very basics.
>From the guide
>(http://maven.apache.org/guides/plugin/guide-java-plugin-development.html)
I understood that if I
specify a goal in a javadoc annotation I will able to call it later
directly, but I fail
On 1/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
I'm want to write my own plugin to build my company's project.
Now I'm following the "Your First Plugin" Totorial on
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
.
<[EMAIL PROTECTED]> writes:
> Hi,
>
>
could you please post the pom ?
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
Hi,
I'm want to write my own plugin to build my company's project.
Now I'm following the "Your First Plugin" Totorial on
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
.
I've installed the hello-maven-plugin in my local repository.
ng mojo as an example :)
>
> Regards,
>
> Raphaël
>
> 2006/3/17, Mark <[EMAIL PROTECTED]>:
> >
> > I had a go at creating my first plugin, so I followed:
> >
> > http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
> >
the @goal annotation is to be defined in the class javadoc, not in the
execute method javadoc...
Just checkout the code of an existing mojo as an example :)
Regards,
Raphaël
2006/3/17, Mark <[EMAIL PROTECTED]>:
>
> I had a go at creating my first plugin, so I follow
I had a go at creating my first plugin, so I followed:
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
I aslo looked at:
http://maven.apache.org/developers/mojo-api-specification.html
My problem is that the mojo sections isn't being created in META-INF/
I had a the exact same problem however it went away when I updated to m2b2
and blew away my local repo allowing m2 to recreate it. Since then, it has
all work fine.
Wb
On 10/5/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
>
> I am trying to build my first plugin and having a problem.
I am trying to build my first plugin and having a problem.
I wrote a plugin which I can run as
sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi and that works
perfectly.
I want to set things up so I can reference the goal as hello:sayhi but
can't seem to get it to work. I
> -Original Message-
> From: STRAYER, JON (SBCSI) [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 23, 2004 4:23 PM
> To: 'Maven Users List'
> Subject: First plugin
>
>
> I'm working on my first plugin. Should I need to delete it
> from the cache
I'm working on my first plugin. Should I need to delete it
from the cache each time in install it?
Maven doesn't seem to pick up the changes otherwise.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional c
22 matches
Mail list logo
