Re: [VOTE] Release Maven Ant Tasks 2.0.6
+1 --jason On May 15, 2007, at 6:15 PM, Jason van Zyl wrote: Hi, Repost of the vote after fixing the issues with the uber JAR that was produced. Hervé and I have tried them and they appear to work fine. The staging repository is here: http://people.apache.org/~jvanzyl/staging-repository/maven-ant- tasks-2.0.6/ The uber jar that people will want to try is here: http://people.apache.org/~jvanzyl/staging-repository/maven-ant- tasks-2.0.6/org/apache/maven/maven-ant-tasks/2.0.6/ Road map: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=true&&pid=11533&fixfor=13351&sorter/field=issuekey&sorter/ order=DESC Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nag: MNG-2854
On 5/16/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: It's not simply a matter of applying the patch. If you are willing to apply, run the integration tests against 2.0.x and 2.1.x and they work then I will integrate it. If you're willing to do this I will write up instructions (extract them from an email) and you can go to town. Carlos has already been so kind to apply the patch. However, being the one who triggered it, I'll do what you want me to do, if you send me said email. (I'd assume, it is mainly related to ensuring that the Maven build uses the right plugins? Which I am indeed unsure how to do it.) Thanks, Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release Maven Ant Tasks 2.0.6
Hi, Repost of the vote after fixing the issues with the uber JAR that was produced. Hervé and I have tried them and they appear to work fine. The staging repository is here: http://people.apache.org/~jvanzyl/staging-repository/maven-ant- tasks-2.0.6/ The uber jar that people will want to try is here: http://people.apache.org/~jvanzyl/staging-repository/maven-ant- tasks-2.0.6/org/apache/maven/maven-ant-tasks/2.0.6/ Road map: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=true&&pid=11533&fixfor=13351&sorter/field=issuekey&sorter/ order=DESC Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nag: MNG-2854
On 15 May 07, at 12:54 PM 15 May 07, Jochen Wiedmann wrote: Well, it's May, and nothing happened, so I'd like to ask one more time for someone to apply MNG-2854. This is the issue, that should fix that jar files are recreated always, which can make Maven real slow in larger projects. It's not simply a matter of applying the patch. If you are willing to apply, run the integration tests against 2.0.x and 2.1.x and they work then I will integrate it. If you're willing to do this I will write up instructions (extract them from an email) and you can go to town. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Specifying IntelliJ module name with maven-idea-plugin
Hi Arik,
Yes, I have been using the prefix for alittle while but found that it is a
silly way to get around the problem given that maven coordinate system is
groupId:artifactId:version (http://maven.apache.org/pom.html)
artifactId does not need to be unique and it is contextual to groupId. It
is silly to keep appending what is essentailly a groupId to the
artifactId.
Also what if there are more nested modules, prefixing artifactId would
means that the prefix grows as you go deeper. I definitely find that it is
harder to maitain the convention and harder still to enforce that
convention in a larger team environment.
BTW: I really think that the default finalName for the artifact should
have been a combination of groupId and artifactId. I think that is the
main motivation for users to prefix thir artifactId with project name.
Regards,
rOnn c.
"Arik Kfir" <[EMAIL PROTECTED]>
05/15/2007 05:49 PM
Please respond to
"Maven Developers List"
To
"Maven Developers List"
cc
Subject
Re: Specifying IntelliJ module name with maven-idea-plugin
I always prefix my artifactId(s) with a common prefix - for that reason;
e.g.
"myproject-core", "myproject-commons", "myproject-webapp",
"myproject-webapp-jsf", "myproject-webapp-struts", and so on. It lengthens
the names, but makes everything clear (and I don't need to use the
'finalName' property too...)
On 5/15/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] wrote:
> > Hi there,
> >
> > I've notice that when using maven-idea-plugin, the module name that is
> > generated is based solely on artifact id.
> >
> > Is there a particular reason for this? Why wouldn't it use project
name
> > instead?
> >
> > The reason I'm asking this is that we have three maven projects with
> > following structure,
> >
> > project/
> >+- common/webapp/
> >+- customer/webapp/
> >
> > Where artifact names are simply the name of the directory (e.g.,
> webapp),
> > and I use final-name as ${groupId}.${artifactId}-${version} to control
> the
> > uniqueness of the actual artifacts file name that get generated.
> >
> > Unfortunatly, with current maven-idea-plugin this results in a module
> > naming conflicting within IntelliJ. I think at the very least there
> should
> > be a way to specify generated IntelliJ module's name, using pom's
> project
> > name seems like a good idea to me.
> >
> > Does anyone have any thought on this?
>
> The artifact id is normally unique enough, but your idea is still useful
> so please file an issue in JIRA[1].
>
> [1]: http://jira.codehaus.org/browse/MIDEA
>
> --
> Trygve
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
##
DISCLAIMER:
This email and any attachment may contain confidential information.
If you are not the intended recipient you are not authorized to copy
or disclose all or any part of it without the prior written consent
of Toyota.
Opinions expressed in this email and any attachments are those of the
sender and not necessarily the opinions of Toyota.
Please scan this email and any attachment(s) for viruses.
Toyota does not accept any responsibility for problems caused by
viruses, whether it is Toyota's fault or not.
##
Re: [VOTE] Release Maven Ant Tasks 2.0.6
Le jeudi 26 avril 2007, Jason van Zyl a écrit : > Nice, thanks. > > I'm doing some Ant (well, a conversion) so I'll take a look as soon > as I can. > > Thanks, > > Jason. Any news on Maven Ant Tasks? What can I do to help release 2.0.6? Hervé - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Involvement for a new request
neither of those are specifically on the roadmap for development, but having said that if you were you take a look and implement them we would be more then happy to factor them into continuum :) the thing to do to start would be to probably log them as issues in jira, maybe kick out some thoughts on implementation on this mailing list and get some patches into jira. also feel free to hop on irc and ask any questions you might run up against. continuum makes use of a number of components that exist in plexus, namely the taskqueue stuff which would probably require some work to implement that sort of behavior.. would be great to hear more on what your thinking! jesse On 5/15/07, Bashar Abdul Jawad <[EMAIL PROTECTED]> wrote: Hi, We are using Continnum at my company and we had moved to it from Anthill pro. We are quite happy with continnum but there are a couple of features that were in AntHill that are missing from Continnum. The 2 features we are interested in the most are: 1- Ability to change the order of queued builds. 2- Grouping of projects according to their build status. A project that is currently building will be moved to the top, projects that are queued to build are grouped together and projects that are not queued to build are grouped together. My question is if these 2 features are planned for future releases of continnum, and if not then we are interested in implementing the features ourselves and submit the changes as a patch if other people are interested. Thanks, Bashar -- jesse mcconnell [EMAIL PROTECTED]
Nag: MNG-2854
Well, it's May, and nothing happened, so I'd like to ask one more time for someone to apply MNG-2854. This is the issue, that should fix that jar files are recreated always, which can make Maven real slow in larger projects. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Specify a dynamic profile
That is a good suggestion Eric, I may give that a try. Thanks much, Evan On 5/15/07, Eric Redmond <[EMAIL PROTECTED]> wrote: You can have an external profile.xml file which contains all the profiles you need. Rather than dynamically generate the POM, you can generate the profiles.xml file easily enough. Eric On 5/14/07, Evan Worley <[EMAIL PROTECTED]> wrote: > > Thanks for the reply Deng, > > The thing is, we don't know what combinations we will want to run. We > have > over 20 modules and a developer might want to build any combination of > them. We use a "precheckin" script which essentially is called such as > "precheckin module1 module2 moduleN..." and we want to build all the > specified modules. We could do this in separate maven calls, but we would > like them to be built in dependency order, which comes for free if we have > them in a profile. > > Evan > > On 5/14/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote: > > > > I'll go with #2, but instead of having each module in its own profile.. > > why don't you try grouping the modules you want to build per profile > > (e.g. have modules A and C in one profile), then build the project with > > -P? > > > > -Deng > > > > Evan Worley wrote: > > > Hello, > > > > > > Does anyone know of a way to specify via the command line a set of > > > modules > > > to build? > > > > > > For example, I have a pom with modules A,B,C. Is there a way I can > > > specify > > > that I would like to build modules A and C only? > > > > > > C:\> mvn -f mypom.xml A,C // something of the sort? > > > > > > Two approaches I've thought of, neither seems ideal > > > 1. Generate a pom dynamically and invoke it > > > 2. Put each module into it's own profile and then specify all the > > > profiles > > > to build > > > > > > Thanks for any help, > > > Evan > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Eric Redmond http://www.sonatype.com
Re: Specify a dynamic profile
You can have an external profile.xml file which contains all the profiles you need. Rather than dynamically generate the POM, you can generate the profiles.xml file easily enough. Eric On 5/14/07, Evan Worley <[EMAIL PROTECTED]> wrote: Thanks for the reply Deng, The thing is, we don't know what combinations we will want to run. We have over 20 modules and a developer might want to build any combination of them. We use a "precheckin" script which essentially is called such as "precheckin module1 module2 moduleN..." and we want to build all the specified modules. We could do this in separate maven calls, but we would like them to be built in dependency order, which comes for free if we have them in a profile. Evan On 5/14/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote: > > I'll go with #2, but instead of having each module in its own profile.. > why don't you try grouping the modules you want to build per profile > (e.g. have modules A and C in one profile), then build the project with > -P? > > -Deng > > Evan Worley wrote: > > Hello, > > > > Does anyone know of a way to specify via the command line a set of > > modules > > to build? > > > > For example, I have a pom with modules A,B,C. Is there a way I can > > specify > > that I would like to build modules A and C only? > > > > C:\> mvn -f mypom.xml A,C // something of the sort? > > > > Two approaches I've thought of, neither seems ideal > > 1. Generate a pom dynamically and invoke it > > 2. Put each module into it's own profile and then specify all the > > profiles > > to build > > > > Thanks for any help, > > Evan > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Eric Redmond http://www.sonatype.com
Re: [M2] Dashboard Plugin Plans
Hi, i have developed the Maven Dashboard plugin ( hosted by Codehaus). And i have many discussions with Garvin LeClaire about the Dashboard Quality application as http://jira.codehaus.org/browse/MOJO-732 http://jira.codehaus.org/browse/MOJO-732 and here http://docs.codehaus.org/display/MAVEN/Maven+Dashboard Maven Dashboard . where are we be able to find this new API ? thanks for all. brettporter wrote: > > Sorry for the late reply. > > The default is to be a singleton, but I think it only lives as long as > it's ref count is > 0. So you probably want to set it to the true > singleton. I remember seeing someone note this recently for something > else, but I don't know if it exists in the current version of Maven. > > In the interim, create a static field that is initialised to the > component on first use. That's obviously a bit gross but it will keep > the ref count up until we can determine if the proper way is available. > > - Brett > > Mauro Botelho wrote: >> I created a new library like you suggested, and modified both the >> checkstyle >> an pmd plugins to use it by adding the new library as a dependency. When >> I >> run them individually everything works fine and I see their metrics being >> reported, but when I try to run both in the same build, I only see the >> metrics of the last plugin run (in my case checkstyle). >> >> I think this has to do with classloading and the way plexus loads its >> components. The metrics library has a components.xml file in its jar, so >> I >> think that the registry singleton is being created by the plugin >> classloader. >> >> What would be the best way to ensure that the registry is a singleton for >> the build? >> >> Here's my components.xml: >> >> >> >> >> org.apache.maven.metrics.MetricRegistry >> org.apache.maven.metrics.DefaultMetricRegistry >> >> >> >> >> >> >> Mauro >> >> On 2/19/06, Brett Porter <[EMAIL PROTECTED]> wrote: >>> It would just need to be a common dependency. reporting-api definitely >>> is, but you could easily create a new library for it (and that probably >>> makes more sense). >>> >>> The component definition goes in the same JAR as the class. >>> >>> - Brett >>> >>> Mauro Botelho wrote: Brett, in order for any plug-in to use the MetricRegistry, would it have >>> to be declared in the reporting-api? Where would I add the component >>> definition for it? Mauro >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-M2--Dashboard-Plugin-Plans-tf343999s177.html#a10619992 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Archiva 0.9-alpha-2
+1 Emmanuel Wendy Smoak a écrit : Archiva 0.9-alpha-2 was tagged and built this afternoon. For extra credit, the entire build was done with an Archiva 0.9 snapshot running locally, configured as mirrorOf=* and proxying all necessary remote repositories. I also tested this configuration with the Struts 1 and Struts 2 builds. The proposed distribution, including signatures, can be found here: http://people.apache.org/builds/maven/archiva/0.9-alpha-2/ This will be Archiva's first release, and is intended to wrap up development of the original codebase to make way for 1.0. Known issues include problems running the webapp on Tomcat, and limitations on the number of artifacts this version can handle. Once you have had a chance to examine the distribution, please cast your vote. We welcome votes and feedback from all community members. [ ] +1 Release it! [ ] +/- 0 [ ] -1 Don't release it, because... 72 hours ends Wednesday night (GMT -7) but I probably won't do anything further with it until Friday afternoon. If you need more time, just ask. Thanks,
Re: dependency version ignored
Ecker Severin wrote: Hi, Unfortunately removing the exclusion clause didn't help ;/ is there anything wrong with my pom file? I can't find a problem there but maybe I'm missing something. Can't see anything obviously wrong. You might try running mvn with -X which will give you lots of debug, including a bit about how it's resolving dependencies. I don't think it's causing your problem, but one thing to note is that if you are only using junit for testing, you should specify it with test to avoid it ending up on your runtime classpath. -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:[EMAIL PROTECTED] Gesendet: Montag, 14. Mai 2007 17:32 An: Maven Developers List Betreff: Re: dependency version ignored Remove the junit under axis2-kernel and try again. Wayne On 5/14/07, Ecker Severin <[EMAIL PROTECTED]> wrote: Hi, I've tried both, version 2.0.5 and 2.0.6, equal results. Best regards, severin -Ursprüngliche Nachricht- Von: Ralph Goers [mailto:[EMAIL PROTECTED] Gesendet: Montag, 14. Mai 2007 16:00 An: Maven Developers List Betreff: Re: dependency version ignored What version of maven are you using? Ecker Severin wrote: Hi, There seems to be no one who can help me in the users list so I hope that someone around here does haven an idea: My problem is as follows: I'm not sure whether I'm not using dependencies correctly or this is a bug, but the situation is as follows: I have a junit 4.1 dependency in my project (and also xmlbeans). Now xmlbeans happens to have a dependency on junit 3.8. The problem is that my project uses junit 4 annotations BUT maven simply ignores my dependency and is totally content with junit3.8 on the classpath. Needless to say that the compilation fails. //this fails mvn clean test //all of these work, the first line always fails because of the "missing" junit4 of course mvn clean compile mvn compile test mvn clean compile mvn compiler:testCompile mvn clean compile mvn test A simple example looks like this: I've stripped some dependencies and all the repositories to keep the pom as simple and short as possible: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 mygroup myart jar 1.0 org.codehaus.mojo xmlbeans-maven-plugin xmlbeans generate-sources org.apache.axis2 axis2-wsdl2code-maven-plugin PATCHED wsdl2code org.apache.maven.plugins maven-compiler-plugin 2.0 1.5 1.5 junit junit 4.1 org.apache.axis2 axis2-kernel SNAPSHOT compile junit junit junit junit 4.1 Thanks in advance and best regards, Severin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Richard van der Hoff <[EMAIL PROTECTED]> Telephony Gateways Project Manager Tel: +44 (0) 845 666 7778 http://www.mxtelecom.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Archiva 0.9-alpha-2
+1 -Deng Wendy Smoak wrote: Archiva 0.9-alpha-2 was tagged and built this afternoon. For extra credit, the entire build was done with an Archiva 0.9 snapshot running locally, configured as mirrorOf=* and proxying all necessary remote repositories. I also tested this configuration with the Struts 1 and Struts 2 builds. The proposed distribution, including signatures, can be found here: http://people.apache.org/builds/maven/archiva/0.9-alpha-2/ This will be Archiva's first release, and is intended to wrap up development of the original codebase to make way for 1.0. Known issues include problems running the webapp on Tomcat, and limitations on the number of artifacts this version can handle. Once you have had a chance to examine the distribution, please cast your vote. We welcome votes and feedback from all community members. [ ] +1 Release it! [ ] +/- 0 [ ] -1 Don't release it, because... 72 hours ends Wednesday night (GMT -7) but I probably won't do anything further with it until Friday afternoon. If you need more time, just ask. Thanks,
Re: Specifying IntelliJ module name with maven-idea-plugin
I always prefix my artifactId(s) with a common prefix - for that reason; e.g.
"myproject-core", "myproject-commons", "myproject-webapp",
"myproject-webapp-jsf", "myproject-webapp-struts", and so on. It lengthens
the names, but makes everything clear (and I don't need to use the
'finalName' property too...)
On 5/15/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> Hi there,
>
> I've notice that when using maven-idea-plugin, the module name that is
> generated is based solely on artifact id.
>
> Is there a particular reason for this? Why wouldn't it use project name
> instead?
>
> The reason I'm asking this is that we have three maven projects with
> following structure,
>
> project/
>+- common/webapp/
>+- customer/webapp/
>
> Where artifact names are simply the name of the directory (e.g.,
webapp),
> and I use final-name as ${groupId}.${artifactId}-${version} to control
the
> uniqueness of the actual artifacts file name that get generated.
>
> Unfortunatly, with current maven-idea-plugin this results in a module
> naming conflicting within IntelliJ. I think at the very least there
should
> be a way to specify generated IntelliJ module's name, using pom's
project
> name seems like a good idea to me.
>
> Does anyone have any thought on this?
The artifact id is normally unique enough, but your idea is still useful
so please file an issue in JIRA[1].
[1]: http://jira.codehaus.org/browse/MIDEA
--
Trygve
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Specifying IntelliJ module name with maven-idea-plugin
[EMAIL PROTECTED] wrote:
Hi there,
I've notice that when using maven-idea-plugin, the module name that is
generated is based solely on artifact id.
Is there a particular reason for this? Why wouldn't it use project name
instead?
The reason I'm asking this is that we have three maven projects with
following structure,
project/
+- common/webapp/
+- customer/webapp/
Where artifact names are simply the name of the directory (e.g., webapp),
and I use final-name as ${groupId}.${artifactId}-${version} to control the
uniqueness of the actual artifacts file name that get generated.
Unfortunatly, with current maven-idea-plugin this results in a module
naming conflicting within IntelliJ. I think at the very least there should
be a way to specify generated IntelliJ module's name, using pom's project
name seems like a good idea to me.
Does anyone have any thought on this?
The artifact id is normally unique enough, but your idea is still useful
so please file an issue in JIRA[1].
[1]: http://jira.codehaus.org/browse/MIDEA
--
Trygve
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: dependency version ignored
Hi, Unfortunately removing the exclusion clause didn't help ;/ is there anything wrong with my pom file? I can't find a problem there but maybe I'm missing something. Best regards, Severin -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:[EMAIL PROTECTED] Gesendet: Montag, 14. Mai 2007 17:32 An: Maven Developers List Betreff: Re: dependency version ignored Remove the junit under axis2-kernel and try again. Wayne On 5/14/07, Ecker Severin <[EMAIL PROTECTED]> wrote: > Hi, > > I've tried both, version 2.0.5 and 2.0.6, equal results. > > Best regards, > severin > > -Ursprüngliche Nachricht- > Von: Ralph Goers [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 14. Mai 2007 16:00 > An: Maven Developers List > Betreff: Re: dependency version ignored > > What version of maven are you using? > > Ecker Severin wrote: > > Hi, > > > > There seems to be no one who can help me in the users list so I hope > > that someone around here does haven an idea: > > My problem is as follows: > > > > I'm not sure whether I'm not using dependencies correctly or this is a > > bug, but the situation is as follows: > > > > I have a junit 4.1 dependency in my project (and also xmlbeans). > > Now xmlbeans happens to have a dependency on junit 3.8. > > > > The problem is that my project uses junit 4 annotations BUT maven simply > > ignores my dependency and is totally content with junit3.8 on the > > classpath. Needless to say that the compilation fails. > > > > //this fails > > mvn clean test > > > > > > //all of these work, the first line always fails because of the > > "missing" junit4 of course > > > > mvn clean compile > > mvn compile test > > > > mvn clean compile > > mvn compiler:testCompile > > > > mvn clean compile > > mvn test > > > > > > > > > > A simple example looks like this: > > I've stripped some dependencies and all the repositories to keep the pom > > as simple and short as possible: > > > > > > http://maven.apache.org/POM/4.0.0"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > > http://maven.apache.org/maven-v4_0_0.xsd";> > > 4.0.0 > > mygroup > > myart > > jar > > 1.0 > > > > > > > > > > org.codehaus.mojo > > xmlbeans-maven-plugin > > > > > > > >xmlbeans > > > > generate-sources > > > > > > > > > > org.apache.axis2 > > axis2-wsdl2code-maven-plugin > > PATCHED > > > > > > > >wsdl2code > > > > > > > > > > > > org.apache.maven.plugins > > maven-compiler-plugin > > 2.0 > > > > 1.5 > > 1.5 > > > > > > > > > > > > > > > > > > junit > > junit > > 4.1 > > > > > > > > > > > > > > > >org.apache.axis2 > >axis2-kernel > >SNAPSHOT > >compile > > > > > > junit > > junit > > > > > > > > > > > >junit > >junit > >4.1 > > > > > > > > > > > > Thanks in advance and best regards, > > Severin > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
