Best practicse for filtering within Java-Files

[Christian Hartmann]

Hi there,

I wonder, what is the best practicse to do a filtering within Java- 
Source-Files during a


'mvn clean install'

Any suggestions?

Regards,

Christian


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Junit Test reports - Excel format

[neptune_pluto]

Hi

How we can generate junit test reports in a more friendlier xls sheet format 

Regards


--
Click for exclusive coverage on the Maruti Ritz by ZigWheels.com experts
http://www.zigwheels.com/maruti-ritz?utm_source=mail&utm_medium=1&utm_content=ritz&utm_campaign=1

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-dependency-plugin odd behaviour

[Brian Fox]

This can happen if the phase run in a reactor is < package.

2009/5/22 Adam Purkiss 

>
> Well that did not work
>
> One thing to note is that CLI copies the jar NOT the classes folder where
> as m2eclipse wants to copy the classes folder and not the jar file as I
> expect so I am wondering if its a m2eclipse configuration or some
> classpath/command line type mess up.
>
> > From: ajpurk...@hotmail.com
> > To: users@maven.apache.org
> > Subject: RE: maven-dependency-plugin odd behaviour
> > Date: Thu, 21 May 2009 20:36:52 -0400
> >
> >
> > Thanks will give that a try. I tried a few things around that idea that
> did not seem to work but maybe that will address it. All else fails I will
> just CLI it anyway for doing builds.
> >
> > 
> > > From: kmoh@gmail.com
> > > To: users@maven.apache.org
> > > Subject: RE: maven-dependency-plugin odd behaviour
> > > Date: Thu, 21 May 2009 15:11:28 -0500
> > >
> > > Yup..seen that..be careful switching between CLI and m2eclipse..turn of
> > > Build Automatically when running CLI..
> > >
> > >
> > > Thanks,
> > > mohan kr
> > >
> > >
> > > -Original Message-
> > > From: Adam Purkiss [mailto:ajpurk...@hotmail.com]
> > > Sent: Thursday, May 21, 2009 2:18 PM
> > > To: users@maven.apache.org
> > > Subject: maven-dependency-plugin odd behaviour
> > >
> > >
> > >
> > > I have the following setup in a POM file during a transition phase
> between a
> > > massive ANT based project and trying to mavenise it. When run using the
> > > install target from the command line with maven 2.1 I get the expected
> > > behaviour:
> > >
> > > [INFO] [dependency:copy {execution: copy}]
> > > [INFO] Configured Artifact:
> com.intellimec.drive-sync:drive-sync-ias-common:
> > > 3.3.0-SNAPSHOT:jar
> > > [INFO] Copying drive-sync-ias-common-3.3.0-SNAPSHOT.jar to
> C:\iPaid\iPaid
> > > Application Server\lib\drive-sync-ias-common-3.3.0-SNAPSHOT.jar
> > >
> > >
> > > When I use the Eclipse Maven plugin however setup to use 2.1 I get:
> > >
> > > [INFO] [dependency:copy {execution: copy}]
> > > [INFO] Configured Artifact:
> com.intellimec.drive-sync:drive-sync-ias-common:
> > > 3.3.0-SNAPSHOT:jar
> > > [INFO] Copying classes to C:\iPaid\iPaid Application Server\lib\classes
> > > [INFO]
> > >
> 
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> 
> > > [INFO] Error copying artifact from C:\iPaid\iPaid Application
> > > Server\maven\modules\drive-sync-ias-common\target\classes to
> C:\iPaid\iPaid
> > > Application Server\lib\classes
> > >
> > > Embedded error: C:\iPaid\iPaid Application
> > > Server\maven\modules\drive-sync-ias-common\target\classes (Access is
> denied)
> > >
> > >
> > >
> > > Any idea what is going on? I must be missing something obvious. I just
> dont
> > > get why one way works and the other fails. I am running Maven 2.1 on a
> > > Windows XP box
> > >
> > >
> > >
> > > POM excert:
> > >
> > >
> > > org.apache.maven.plugins
> > > maven-dependency-plugin
> > > 2.1
> > >
> > >
> > > copy
> > > install
> > >
> > > copy
> > >
> > >
> > >
> > >
> > > com.intellimec.drive-sync
> > > drive-sync-ias-common
> > > ${project.version}
> > > jar
> > > true
> > >
> > >
> > > ../../../lib
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Debug output
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > [DEBUG] The following artifacts were filtered out for plugin:
> > > org.apache.maven.plugins:maven-dependency-plugin:2.1 because they're
> already
> > > in the core of Maven:
> > >
> > > org.apache.maven:maven-artifact:jar:2.0.9:runtime
> > > org.apache.maven:maven-plugin-api:jar:2.0.9:runtime
> > > org.apache.maven:maven-project:jar:2.0.9:runtime
> > > org.apache.maven:maven-model:jar:2.0.9:runtime
> > > org.apache.maven:maven-core:jar:2.0.9:runtime
> > >
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:runtim
> > > e
> > > org.apache.maven.reporting:maven-reporting-api:jar:2.0.6:runtime
> > >
> > > These will use the artifact files already in the core ClassRealm
> instead, to
> > > allow them to be included in PluginDescriptor.getArtifacts().
> > >
> > >
> > > [DEBUG] Configuring mojo
> > > 'org.apache.maven.plugins:maven-dependency-plugin:2.1:copy' -->
> > > [DEBUG] (s) groupId = com.intellimec.drive-sync
> > > [DEBUG] (s) artifactId = drive-sync-ias-common
> > > [DEBUG] (s) version = 3.3.0-SNAPSHOT
> > > [DEBUG] (s) type = jar
> > > [DEBUG] (s) overWrite = true
> > > [DEBUG] (s) artifactItems =
> > > [com.intellimec.drive-sync:drive-sync-ias-common:3.3.0-SNAPSHOT:jar]
> > > [DEBUG] (s) local = Repository[local|file://C:\Documents and
> > > Settings\apurkiss\.m2\repository]
> > > [DEBUG] (f) outputAbsoluteArtifactFilename = false
> > > [DEBUG] (s) outputDirectory = C:\iPaid\iPaid Application Server\lib
> > > [DEBUG] (s) overWriteIfNewer = true
> > > [DEBUG] (s) overWriteRelease

Does reactor spawn a subprocess for each submodule?

[Tracy Hartford]

I am working on a large multi-module project, and I need to know how the
reactor works when I invoke a maven goal on the parent POM. I know that
Maven adds all the submodule POMs into the Reactor, which analyzes the
dependencies between them, and determines the build order. I understand
that the Reactor then "effectively executes" the goal for each
submodule. What I need to know is, when the Reactor executes the goal
for a given submodule, does it spawn a child process to do so, or does
it execute in the current process? If it execute in the current process,
is there a way to force it to spawn a new process first?

 

 

Re: 回复： AW: About unittest run three times

[Dominic Mitchell]

On 22 May 2009, at 23:02, Forest wrote:


Thanks for your clarification. I really aplied those features.

I'd chang the object to only get test report. Are there any  
suggestions for setting the goals?


By the way, are there any good practices for this case?


The only thing I'd mention is that I've got two separate hudson jobs:  
one for the main build, and one for the site build.  That way, the  
tests only get run once in the main build.


Of course, that doesn't account for cobertura running them again, as  
that'd have to be part of the main build…


-Dom
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

回复： AW: About unittest run three times

[Forest]

Thanks for your clarification. I really aplied those features.

I'd chang the object to only get test report. Are there any suggestions for 
setting the goals?

By the way, are there any good practices for this case?
  
Thanks

原信息
主题： AW: About unittest run three times
发件人： Mark Struberg 
日期： 2009/05/20 18:39


Old story, and as far as I remember (please correct me if I'm wrong) the reason 
is:

The site lifecycle and the default build lifecycle are isolated things.
So if you run mvn install, the 'test' phase will be invoked -> 1st run

Your site has a test reporting section? -> 2nd run

I assume you have cobertura or another code coverage tool enabled?
Because this runs all the tests in an instrumended form -> 3nd run

I'm not saying this situation is optimal though ;) This especially sucks while 
running releases, because prepare and perform will do all those steps a few 
times...

LieGrue,
strub


--- forum geng  schrieb am Mi, 20.5.2009:

> Von: forum geng 
> Betreff: About unittest run three times
> An: users@maven.apache.org
> Datum: Mittwoch, 20. Mai 2009, 8:30
> Dear all,
> 
>While I set
> the nightly build command for continum by "clean
> install site-deploy", my unit tests all run for three
> times.
>And while I
> changed to "clean install", the unit tests run for
> one time, and changed to "clean site-deploy", my unit tests
> run for two
> times.
> 
>   Are there any to explain
> the behind mechanism?
>   And my requirement is
> that to let all the unit tests run for only
> time, and I can also find the info from the deployed site,
> such as with
> PMD/FindBug related report.
> 
> Thanks.
> 
> Forest.
> 


  

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Negation of boolean property

[Stephen Connolly]

profile activation defining skip false in the profile

Sent from my [rhymes with myPod] ;-)

On 22 May 2009, at 21:10, rajks  wrote:



Hi,

The team here want to by default skip the test/integration-test  
targets when

doing mvn install i.e skip test.

They would like to explicitly pass a system property when they want to
execute the tests also. Particularly when we want an automated build
happening periodically on a build machine.

We have different profiles and hence we want to control the tests.  
We do not
want to duplicate existing profiles and combine with this additional  
skip

test combination to produce more profiles.

The surefire plugin has a attribute
   boolean
that allows the test to be skipped. So by default to skip test we were
trying to do something like this

! ${executeUnitTest}  ( note negation of  
boolean )


and we have a property
   
  false
   

This way test is disabled by default.

To enable from command line we can then do

-DexecuteUnitTest=true

If I cannot use NEGATION then I have to do it other way which is not
intuitive

${skipUnitTest}

And by default
   
  true
   


And from command line we have to do

-DskipUnitTest=false

The is like a negative logic.

I was looking for a way to keep it intuitive or if there some other  
way to

achieve this.

Thanks
Raj




mkr wrote:


Not sure the intent. But you can always *override* by passing in  
the key

as
system property.
mvn -DexecuteUnitTest=true ...


Thanks,
mohan kr

-Original Message-
From: rajks [mailto:ra...@hotmail.com]
Sent: Thursday, May 21, 2009 2:06 AM
To: users@maven.apache.org
Subject: Negation of boolean property


Hi,

Is it possible to negate a boolean property value. I tried it like  
this

below and it did not work.
Is there a different syntax for negation ??


   false


In surefire plugin
  !${executeUnitTest}


If not can this syntax be supported 

Thanks
Raj
--
View this message in context:
http://www.nabble.com/Negation-of-boolean-property-tp23648816p23648816.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





--
View this message in context: 
http://www.nabble.com/Negation-of-boolean-property-tp23648816p23676651.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to create Hello World Projects using Maven for Spring, Hibernate, JPA, EJB, ActiveMQ?

[Wayne Fay]

> Is http://docs.codehaus.org/display/MAVENUSER/Archetypes+List the best list
> of archetypes?

As I sent in a previous email...
The listing of archetpes on the Maven User wiki is pretty complete, as
far as I am aware. There are no specific archetypes for "session
stateful ejb" -- just generic project/framework archetypes. Of course,
you're welcome to build something and contribute it back.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Negation of boolean property

[rajks]

Hi,

The team here want to by default skip the test/integration-test targets when
doing mvn install i.e skip test.

They would like to explicitly pass a system property when they want to
execute the tests also. Particularly when we want an automated build
happening periodically on a build machine.

We have different profiles and hence we want to control the tests. We do not
want to duplicate existing profiles and combine with this additional skip
test combination to produce more profiles.

The surefire plugin has a attribute
boolean
that allows the test to be skipped. So by default to skip test we were
trying to do something like this

 ! ${executeUnitTest}  ( note negation of boolean )

and we have a property

   false


This way test is disabled by default.

To enable from command line we can then do

 -DexecuteUnitTest=true

If I cannot use NEGATION then I have to do it other way which is not
intuitive

 ${skipUnitTest}

And by default

   true

  

And from command line we have to do

 -DskipUnitTest=false

The is like a negative logic.

I was looking for a way to keep it intuitive or if there some other way to
achieve this.

Thanks
Raj




mkr wrote:
> 
> Not sure the intent. But you can always *override* by passing in the key
> as
> system property.
> mvn -DexecuteUnitTest=true ...
> 
> 
> Thanks,
> mohan kr
> 
> -Original Message-
> From: rajks [mailto:ra...@hotmail.com] 
> Sent: Thursday, May 21, 2009 2:06 AM
> To: users@maven.apache.org
> Subject: Negation of boolean property
> 
> 
> Hi,
> 
> Is it possible to negate a boolean property value. I tried it like this
> below and it did not work.
> Is there a different syntax for negation ??
> 
> 
> false
> 
> 
> In surefire plugin
>!${executeUnitTest}
> 
> 
> If not can this syntax be supported 
> 
> Thanks
> Raj
> -- 
> View this message in context:
> http://www.nabble.com/Negation-of-boolean-property-tp23648816p23648816.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Negation-of-boolean-property-tp23648816p23676651.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: How to create Hello World Projects using Maven for Spring, Hibernate, JPA, EJB, ActiveMQ?

[siegfried]

Renaming .m2 to save.m2 seems to have fixed the problem. Thanks!

Is http://docs.codehaus.org/display/MAVENUSER/Archetypes+List the best list
of archetypes?

>
>> Ooops!  Do I need to delete me repository?
>>
>> [INFO] Required goal not found: archetype:generate in
>> org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7
>
>If you look at the documentation, you'll see the generate goal was not
>added until 2.0-alpha-4, so this error message is correct. Your
>archetype plugin is WAY out of date.
>
>> [INFO] The plugin 'org.apache.maven.plugins:maven-help-plugin' does not
>> exist or  no valid version could be found
>
>Try again with "mvn -U -e archetype:generate" and "mvn -U
>help:compile". If that doesn't work, you could try deleting your local
>repo cache and things would probably start working again. It sounds
>like you've managed to mess up some metadata, or something.
>
>Wayne
>


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Generating a jar multiple times using classifiers

[Martin Gainty]

the StudioEclipseMojo updates manifest.mf (with updateManifest method)
here is the code:
+   final List artifactList = 
createArtifactList();
+
+   // Update Bundle-Classpath in MANIFEST.MF
+   updateManifest(artifactList);

+   private void updateManifest(final List list)
+   throws FileNotFoundException, IOException {
+   final File manifestFile = new File(project.getBasedir(),
+   "META-INF/MANIFEST.MF");
+
+   // Build Bundle-ClassPath entry
+   final StringBuilder bundleClasspath = new StringBuilder(" .");
+   for (Artifact artifact : list) 
 {
//append all the filenames found in the list...
+   bundleClasspath.append(",").append(NEWLINE).append(" 
").append(
+   
classpathPrefix).append(File.separator).append(
+   artifact.getFile().getName());
+   }

//as long as the scope is NOT provided the outputted list will include the item
+   private List createArtifactList() {
+   List list = new ArrayList();
+   for (Iterator artifactItem = project.getArtifacts()
+   .iterator(); artifactItem.hasNext();) {
+   Artifact artifact = (Artifact) artifactItem.next();
+   if (!artifact.getScope().equalsIgnoreCase("provided")) {
+   list.add(artifact);
+   }
+   }
+   return list;
+   }

http://mail-archives.apache.org/mod_mbox/directory-commits/200712.mbox/%3c20071204215855.4b5001a9...@eris.apache.org%3e

usually a build engineer builds one version of source for 1.0 named 
module-1.0-src.jar
next iteration which is version 1.1 may be called 1.1 named module-1.1-src.jar

same with binaries which do not have a -src suffix for the same set of deployed 
jars containing config and .class
 usually a build engineer builds one version of source for 1.0 named 
module-1.0.jar

next iteration which is version 1.1 may be called 1.1 named module-1.1.jar


at the very least I would update manifest.mf which represents all 
characteristics of that jar with 'classifier' although that clearly breaks 
naming convention most (of us) developers are used to

does this help?
Martin 
__ 
Jogi és Bizalmassági kinyilatkoztatás/Verzicht und 
Vertraulichkeitanmerkung/Note de déni et de confidentialité
 Ez az
üzenet bizalmas.  Ha nem ön az akinek szánva volt, akkor kérjük, hogy
jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának
készítése nem megengedett.  Ez az üzenet csak ismeret cserét szolgál és
semmiféle jogi alkalmazhatósága sincs.  Mivel az electronikus üzenetek
könnyen megváltoztathatóak, ezért minket semmi felelöség nem terhelhet
ezen üzenet tartalma miatt.

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




> From: rbrac...@qualcomm.com
> To: users@maven.apache.org
> Date: Fri, 22 May 2009 11:40:04 -0700
> Subject: Generating a jar multiple times using classifiers
> 
> Hi,
> 
> How do people approach the need to generate a jar multiple times using 
> classifiers.
> My specific requirement is that I have a module which needs to be built 
> against Axis2 1.3 and Axis2 1.4 and have 2 jars in the repo with distinct 
> classifiers.
> I can get this to work using profiles but this only ever runs the module once 
> and then I have to run again with a different profile.
> 
> I've been thinking of generating a src package for the module and then define 
> two new modules that depend on the src dependency and thus build out the 
> required artifact and both artifacts would be deployed during the release 
> phase as well
> 
> Thanks,
> Robert
> 

_
Hotmail® goes with you. 
http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009

Generating a jar multiple times using classifiers

[Bracewell, Robert]

Hi,

How do people approach the need to generate a jar multiple times using 
classifiers.
My specific requirement is that I have a module which needs to be built against 
Axis2 1.3 and Axis2 1.4 and have 2 jars in the repo with distinct classifiers.
I can get this to work using profiles but this only ever runs the module once 
and then I have to run again with a different profile.

I've been thinking of generating a src package for the module and then define 
two new modules that depend on the src dependency and thus build out the 
required artifact and both artifacts would be deployed during the release phase 
as well

Thanks,
Robert

RE: Override dependency classes with another module's classes

[Brendan Haverlock]

Thanks Wayne...I just found a link to the other post about this: 
http://www.mail-archive.com/users@maven.apache.org/msg70079.html  Thanks for 
not redirecting me to the "What is Maven" page.

That seems like the only plausible solution to me for now.  Is there any plan 
for making the dependency order matter in the POM files?  That would be really 
useful!

Thanks again,

Brendan Haverlock

-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com] 
Sent: Friday, May 22, 2009 11:12 AM
To: Maven Users List
Subject: Re: Override dependency classes with another module's classes

> Unfortunately, we are overriding classes from a dependency library, so we
> are just putting the classes in the same package and wanting our overriding
> classes to get precedence on the classpath.  So, our classes are in the same
> package as the library's classes and have the same class name, we just want
> ours to be used at compile time.

This just won't work at all, at least not consistently. Build a
different jar containing just the classes you DON'T override, and
depend on it instead.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Override dependency classes with another module's classes

[Wayne Fay]

> Unfortunately, we are overriding classes from a dependency library, so we
> are just putting the classes in the same package and wanting our overriding
> classes to get precedence on the classpath.  So, our classes are in the same
> package as the library's classes and have the same class name, we just want
> ours to be used at compile time.

This just won't work at all, at least not consistently. Build a
different jar containing just the classes you DON'T override, and
depend on it instead.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Override dependency classes with another module's classes

[Brendan Haverlock]

Martin,

 

Unfortunately, we are overriding classes from a dependency library, so we
are just putting the classes in the same package and wanting our overriding
classes to get precedence on the classpath.  So, our classes are in the same
package as the library's classes and have the same class name, we just want
ours to be used at compile time.

 

Thanks,  

 

Brendan Haverlock

 

From: Martin Gainty [mailto:mgai...@hotmail.com] 
Sent: Thursday, May 21, 2009 6:15 PM
To: brend...@mirthcorp.com
Subject: RE: Override dependency classes with another module's classes

 


public interface ModuleC {
 public int doCalculationC(int a)
 {
   return(a+1);
  }
}
public class ModuleA implements ModuleC {
 public int doCalculationA(int a)
 {
   return (a+2);
 }
 public int doCalculationC(int a)
 {
   return(a+1);
  }
}
1. I have a Module A that is overriding a few, but not all, classes from its
> Dependency C.
//B extends A and all protected/public methods from A
//B implements C and all protected/public methods from C
public class ModuleB extends ModuleA implements ModuleC
{
  public int doCalculationB(int a)
  {
return (a+3);
  }
public int doCalculationA(int a)
 {
   return (a+2);
 }
 public int doCalculationC(int a)
 {
   return(a+1);
  }
}

> 2. I have another Module B that is dependent on Module A, but also on the
> Dependency C.
> 3. Module B is getting compile errors because it is using the classes from
> Dependency C but not finding the overridden classes from Module A.


> From: brend...@mirthcorp.com
> To: users@maven.apache.org
> Subject: Override dependency classes with another module's classes
> Date: Thu, 21 May 2009 17:39:46 -0700
> 
> Hi all,
> 
> I've run into an issue with my dependencies in Maven:
> 
> 1. I have a Module A that is overriding a few, but not all, classes from
its
> Dependency C.
> 2. I have another Module B that is dependent on Module A, but also on the
> Dependency C.
> 3. Module B is getting compile errors because it is using the classes from
> Dependency C but not finding the overridden classes from Module A.
> 
> Question: Is there a way for me to specify dependency precedence so that
> Module B knows to use the classes from Dependency C, except for the ones
> that were overridden in Module A?
> 
> Thanks,
> Brendan Haverlock
> 
> 
> 

  _  

Insert movie times and more without leaving HotmailR. See how.
 

maven cobertura plugin - haltonFailure ?

[huser]

Hi,

I am trying to use Maven Cobertura Plugin. I want to setup different
lineRate/branchRate for different packages. But this doesnt seem to be
working.

1. haltnFailure does not work even if I set the values to 100 for the top
level module.
2. regex doesnt seem to do anything. I specified higher values for critical
code and lower values for un-important code. But I dont see any difference.

Any ideas ?




org.codehaus.mojo
cobertura-maven-plugin

true

  xml

 

true
90
90
90
90
90

90

  
com.abc.t3.st
90
90
  
  
com.abc.t3.findservice.impl
40
30
  
   
 


-- 
View this message in context: 
http://www.nabble.com/maven-cobertura-plugin---haltonFailure---tp23675026p23675026.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: executions, phases and multiple goals

[Stephen Connolly]

2009/5/22 Stephen Connolly 

> OK, I just noticed this...
>
> If I have two mojo's annotated with different phases, i.e.
>
> /**
>  * @goal integration-test
>  * @requiresProject true
>  * @requiresDependencyResolution test
>  * @phase integration-test
>  */
> public class FailsafeMojo
> extends AbstractMojo
> {
> ...
> }
>
> and
>
> /**
>   * @goal verify
>   * @requiresProject true
>   * @requiresDependencyResolution test
>  * @phase verify
>  */
> public class VerifyMojo
> extends AbstractMojo
> {
> ...
> }
>
>
> If I add to my pom.xml
>
> 
>   ..
>   
> ..
> 
>   ...
>   
> 
> 
> ...
> ...
> *
>   
> 
>   integration-test
>   verify
> 
>   
> 
> *  
>   ...
> 
> ...
>   
> 
>
> Then the integration-test goal is bound to the integration-test phase and
> the verify goal is bound to the verify phase.
>
> My question is this... is this a feature or a bug?
>
> It'd be nice if it was a feature... but I suspect it is a bug...
>
> Just to confirm for everyone...
>
> If I add
>
> 
>   ..
>   
> ..
> 
>   ...
>   
> 
> 
> ...
> ...
> *
>   
> integration-test
> 
>   integration-test
>   verify
> 
>   
> 
> *  
>   ...
> 
> ...
>   
> 
>
> Then both goals are bound to the integration-test phase, as I would expect
>
> -Stephen



  
org.mortbay.jetty
maven-jetty-plugin
6.1.16

  ${integration-test-stop-port}
  STOP
  /


  
start-jetty
pre-integration-test

  
  stop
  run-exploded


  0
  true

  
  
stop-jetty
post-integration-test

  stop

  

  
  
@project.groupId@
@project.artifactId@
@project.version@

  

  integration-test
  verify

  

  

gives:

...
[INFO] [INFO]* [jetty:run-exploded {execution: start-jetty}]*
[INFO] [INFO] Configuring Jetty for project: run failing tests in jetty
container
[INFO] 2009-05-22 15:48:35.834::INFO:  Logging to STDERR via
org.mortbay.log.StdErrLog
[INFO] [INFO] Context path = /
[INFO] [INFO] Tmp directory =  determined at runtime
[INFO] [INFO] Web defaults = org/mortbay/jetty/webapp/webdefault.xml
[INFO] [INFO] Web overrides =  none
[INFO] [INFO] Starting jetty 6.1.16 ...
[INFO] 2009-05-22 15:48:35.906::INFO:  jetty-6.1.16
[INFO] 2009-05-22 15:48:35.999::INFO:  No Transaction manager found - if
your webapp requires one, please configure one.
[INFO] 2009-05-22 15:48:36.170::INFO:  Started
selectchannelconnec...@0.0.0.0:8080
[INFO] [INFO] Started Jetty Server
[INFO] [INFO] *[failsafe:integration-test {execution: default}]*
[INFO] [INFO] Failsafe report directory:
/home/connollys/src/mojo-sandbox/failsafe-maven-plugin/target/it/jetty-war-test-failing/target/failsafe-reports
[INFO]
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running basic.BasicIT
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.896
sec <<< FAILURE!
[INFO]
[INFO] Results :
[INFO]
[INFO] Failed tests:
[INFO]   testSmokes(basic.BasicIT)
[INFO]
[INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[INFO] [INFO] *[jetty:stop {execution: stop-jetty}]*
[INFO] [INFO] Stopping server 0
[INFO] [INFO]* [failsafe:verify {execution: default}]*
[INFO] [INFO] Failsafe report directory:
/home/connollys/src/mojo-sandbox/failsafe-maven-plugin/target/it/jetty-war-test-failing/target/failsafe-reports
[INFO] [INFO]

[INFO] [ERROR] BUILD FAILURE
[INFO] [INFO]

[INFO] [INFO] There are test failures.
[INFO]

executions, phases and multiple goals

[Stephen Connolly]

OK, I just noticed this...

If I have two mojo's annotated with different phases, i.e.

/**
 * @goal integration-test
 * @requiresProject true
 * @requiresDependencyResolution test
 * @phase integration-test
 */
public class FailsafeMojo
extends AbstractMojo
{
...
}

and

/**
  * @goal verify
  * @requiresProject true
  * @requiresDependencyResolution test
 * @phase verify
 */
public class VerifyMojo
extends AbstractMojo
{
...
}


If I add to my pom.xml


  ..
  
..

  ...
  


...
...
*
  

  integration-test
  verify

  

*  
  ...

...
  


Then the integration-test goal is bound to the integration-test phase and
the verify goal is bound to the verify phase.

My question is this... is this a feature or a bug?

It'd be nice if it was a feature... but I suspect it is a bug...

Just to confirm for everyone...

If I add


  ..
  
..

  ...
  


...
...
*
  
integration-test

  integration-test
  verify

  

*  
  ...

...
  


Then both goals are bound to the integration-test phase, as I would expect

-Stephen

Re: mvn install for ear project

[fachhoch]

my mvn version

Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_11
Java home: C:\Program Files\Java\jdk1.6.0_11\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

this is the same version  and still I am getting this error .
sairam



snicoll wrote:
> 
> It's a bug of the war plugin that has been fixed a while back. Please use
> the latest version.
> 
> S.
> 
> On Tue, May 19, 2009 at 8:55 PM, tubin gen  wrote:
> 
>> my project   has subprojects one for ear , one for war  and one for jar .
>>
>>
>> I get this error   when I run mvn install
>>
>>
>> java.lang.NullPointerException
>>at
>>
>> org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>>at
>>
>> org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>>at
>>
>> org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>>at
>>
>> org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>>at
>>
>> org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>>at
>> org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>>at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>>at
>>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
>>at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
>>at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
>>at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
>>at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>>at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>>at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>>at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>at java.lang.reflect.Method.invoke(Method.java:597)
>>at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>
>>
>> please help me, what is causing  this error ?
>>
> 
> 
> 
> -- 
> Large Systems Suck: This rule is 100% transitive. If you build one, you
> suck" -- S.Yegge
> 
> 

-- 
View this message in context: 
http://www.nabble.com/mvn-install-for-ear-project-tp23622756p23671801.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: maven-dependency-plugin odd behaviour

[Adam Purkiss]

Well that did not work

One thing to note is that CLI copies the jar NOT the classes folder where as 
m2eclipse wants to copy the classes folder and not the jar file as I expect so 
I am wondering if its a m2eclipse configuration or some classpath/command line 
type mess up.
 
> From: ajpurk...@hotmail.com
> To: users@maven.apache.org
> Subject: RE: maven-dependency-plugin odd behaviour
> Date: Thu, 21 May 2009 20:36:52 -0400
> 
> 
> Thanks will give that a try. I tried a few things around that idea that did 
> not seem to work but maybe that will address it. All else fails I will just 
> CLI it anyway for doing builds.
> 
> 
> > From: kmoh@gmail.com
> > To: users@maven.apache.org
> > Subject: RE: maven-dependency-plugin odd behaviour
> > Date: Thu, 21 May 2009 15:11:28 -0500
> >
> > Yup..seen that..be careful switching between CLI and m2eclipse..turn of
> > Build Automatically when running CLI..
> >
> >
> > Thanks,
> > mohan kr
> >
> >
> > -Original Message-
> > From: Adam Purkiss [mailto:ajpurk...@hotmail.com]
> > Sent: Thursday, May 21, 2009 2:18 PM
> > To: users@maven.apache.org
> > Subject: maven-dependency-plugin odd behaviour
> >
> >
> >
> > I have the following setup in a POM file during a transition phase between a
> > massive ANT based project and trying to mavenise it. When run using the
> > install target from the command line with maven 2.1 I get the expected
> > behaviour:
> >
> > [INFO] [dependency:copy {execution: copy}]
> > [INFO] Configured Artifact: com.intellimec.drive-sync:drive-sync-ias-common:
> > 3.3.0-SNAPSHOT:jar
> > [INFO] Copying drive-sync-ias-common-3.3.0-SNAPSHOT.jar to C:\iPaid\iPaid
> > Application Server\lib\drive-sync-ias-common-3.3.0-SNAPSHOT.jar
> >
> >
> > When I use the Eclipse Maven plugin however setup to use 2.1 I get:
> >
> > [INFO] [dependency:copy {execution: copy}]
> > [INFO] Configured Artifact: com.intellimec.drive-sync:drive-sync-ias-common:
> > 3.3.0-SNAPSHOT:jar
> > [INFO] Copying classes to C:\iPaid\iPaid Application Server\lib\classes
> > [INFO]
> > 
> > [ERROR] BUILD ERROR
> > [INFO]
> > 
> > [INFO] Error copying artifact from C:\iPaid\iPaid Application
> > Server\maven\modules\drive-sync-ias-common\target\classes to C:\iPaid\iPaid
> > Application Server\lib\classes
> >
> > Embedded error: C:\iPaid\iPaid Application
> > Server\maven\modules\drive-sync-ias-common\target\classes (Access is denied)
> >
> >
> >
> > Any idea what is going on? I must be missing something obvious. I just dont
> > get why one way works and the other fails. I am running Maven 2.1 on a
> > Windows XP box
> >
> >
> >
> > POM excert:
> >
> > 
> > org.apache.maven.plugins
> > maven-dependency-plugin
> > 2.1
> > 
> > 
> > copy
> > install
> > 
> > copy
> > 
> > 
> > 
> > 
> > com.intellimec.drive-sync
> > drive-sync-ias-common
> > ${project.version}
> > jar
> > true
> > 
> > 
> > ../../../lib
> > 
> > 
> > 
> > 
> >
> >
> >
> >
> >
> > Debug output
> >
> >
> >
> >
> >
> >
> >
> > [DEBUG] The following artifacts were filtered out for plugin:
> > org.apache.maven.plugins:maven-dependency-plugin:2.1 because they're already
> > in the core of Maven:
> >
> > org.apache.maven:maven-artifact:jar:2.0.9:runtime
> > org.apache.maven:maven-plugin-api:jar:2.0.9:runtime
> > org.apache.maven:maven-project:jar:2.0.9:runtime
> > org.apache.maven:maven-model:jar:2.0.9:runtime
> > org.apache.maven:maven-core:jar:2.0.9:runtime
> > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:runtim
> > e
> > org.apache.maven.reporting:maven-reporting-api:jar:2.0.6:runtime
> >
> > These will use the artifact files already in the core ClassRealm instead, to
> > allow them to be included in PluginDescriptor.getArtifacts().
> >
> > 　
> > [DEBUG] Configuring mojo
> > 'org.apache.maven.plugins:maven-dependency-plugin:2.1:copy' -->
> > [DEBUG] (s) groupId = com.intellimec.drive-sync
> > [DEBUG] (s) artifactId = drive-sync-ias-common
> > [DEBUG] (s) version = 3.3.0-SNAPSHOT
> > [DEBUG] (s) type = jar
> > [DEBUG] (s) overWrite = true
> > [DEBUG] (s) artifactItems =
> > [com.intellimec.drive-sync:drive-sync-ias-common:3.3.0-SNAPSHOT:jar]
> > [DEBUG] (s) local = Repository[local|file://C:\Documents and
> > Settings\apurkiss\.m2\repository]
> > [DEBUG] (f) outputAbsoluteArtifactFilename = false
> > [DEBUG] (s) outputDirectory = C:\iPaid\iPaid Application Server\lib
> > [DEBUG] (s) overWriteIfNewer = true
> > [DEBUG] (s) overWriteReleases = false
> > [DEBUG] (s) overWriteSnapshots = false
> > [DEBUG] (f) project = MavenProject:
> > com.intellimec.drive-sync:drive-sync-ias-common:3.3.0-SNAPSHOT @
> > C:\iPaid\iPaid Application
> > Server\maven\modules\drive-sync-ias-common\pom.xml
> > [DEBUG] (f) reactorProjects = [MavenProject:
> > com.intellimec.drive-sync:drive-sync-ias-common:3.3.0-SNAPSHOT @
> > C:\iPaid\i

Re: How to Sync Specific Artifact from One Repository to Another

[Brian Fox]

Both the dependency plugin and the assembly plugin are able to assembly a
repository layout from a list of dependencies.

2009/5/21 Rui Tang 

> Hello friends,
>
> I'm in trouble with the following problem:
>
> 1. In the ordinary software release, we always include our own jars and 3rd
> party jars in **lib** directory
>
> 2. After using maven, I have an idea that I want to release a tiny maven
> repository, containing self compiled jars and 3rd party ones, in my
> software
>
> 3. Now I can use deploy:deploy plugin to deploy my own jars into a specific
> folder (a repository using file:// protocol) (For example this repository
> locates at c:\my-repo)
>
> 4. But I'm wandering how to deploy the dependency jars with their
> descriptions into this folder. I've checked wagon, dependency, stage
> plugins, but none of them can archive the goal. The stage plugin can do
> what
> I need, but unfortunately it can only sync the whole repository but not the
> specific artifact.
>
> So I need a plugin like this
>
> mvn someplugin:someplugin
>  -DsrcRepository=
>  -DgroupId=
>  -DartifactId=
>  -Dversion=
>  -Dpackaging=jar
>  -DdestRepository
>
> then it can sync the groupId:artifactId:version artifact into the
> destRespository with all its description
>
> Does this plugin exist or can I do this in some other way, thank you!
> **
> --
> 唐睿
>
> 电话：+86 010 58732330 转 810
> 传真：+86 010 58732330 转 800
> 手机（北京）：+86 13717808625
> 手机（深圳）：+86 13510560457
>
> 汉星天（中国）公司
> 地址（北京）：北京市海淀区知春路甲 48 号盈都大厦 A 座 9B （100098）
>
> Hansky
> Better Software, Better Business
>
> WWW.HANSKY.COM.CN
>

Re: Maven: The Definitive Guide in French

[Emmanuel Hugonnet]

Hi,
There is also: In Libro Veritas (http://www.inlibroveritas.net) a small
editor for open content license books (Licence Art Libre,
Creative Commons ,
GFDL).
You can get the books in pdf or on paper for a price depending on the
quality of the paper (new or recycled) and on the number of pages (
http://www.inlibroveritas.net/presentation_livres.php).
They will give 10% back as royalties, I don't know but we could use it to
sponsor some opensource projects, the Apache Foundation, etc. (or maybe our
readers ;o) )

Emmanuel

Re: About Maven 1.0.2

[Brian Fox]

What's Maven 1? ;-)

On Fri, May 22, 2009 at 3:59 AM, Kerry Zhu  wrote:

> came accross a problem?
> could someone do me a favor?
> thanks!!
>
> //
> preparing goal: xdoclet:hibernatedoclet
> execution chain: []
> final list of plugins to prepare: []
> popping off org.apache.maven.jelly.mavenjellycont...@969c29 for
> org.apache.maven.jelly.mavenjellycont...@1e67e6a in
> maven-java-plugin:maven-java-plugin
> popping off org.apache.maven.jelly.mavenjellycont...@4a7df6 for
> org.apache.maven.jelly.mavenjellycont...@93df2c in
> avalon-meta-plugin:avalon-meta-plugin
> popping off org.apache.maven.jelly.mavenjellycont...@19e215b for
> org.apache.maven.jelly.mavenjellycont...@9ff0a8 in
> maven-antlr-plugin:maven-antlr-plugin
> popping off org.apache.maven.jelly.mavenjellycont...@137d090 for
> org.apache.maven.jelly.mavenjellycont...@15db314 in emc:emc-dao-impl
> Root cause
> Final Memory: 3M/6M
> Total time: 2 seconds
> Finished at: Fri May 22 14:32:50 CST 2009
>
> Best Wishes!!
>

Re: how to pack additional source-files (*.groovy) into *-sources.jar file?

[Stephen Connolly]

http://www.lmgtfy.com/?q=maven-soure-plugin+include+patterns+packaged+into+the+jar&l=1

2009/5/22 

> Hi,
>
> how can I pack additional source-files, in my case *.groovy files at
> src\main\groovy into the -sources.jar file, generated by
> maven-source-plugin?
>
> Thanx, torsten
>
>

how to pack additional source-files (*.groovy) into *-sources.jar file?

[torsten . reinhard]

Hi, 

how can I pack additional source-files, in my case *.groovy files at 
src\main\groovy into the -sources.jar file, generated by 
maven-source-plugin?

Thanx, torsten

About Maven 1.0.2

[Kerry Zhu]

came accross a problem?
could someone do me a favor?
thanks!!

//
preparing goal: xdoclet:hibernatedoclet
execution chain: []
final list of plugins to prepare: []
popping off org.apache.maven.jelly.mavenjellycont...@969c29 for
org.apache.maven.jelly.mavenjellycont...@1e67e6a in
maven-java-plugin:maven-java-plugin
popping off org.apache.maven.jelly.mavenjellycont...@4a7df6 for
org.apache.maven.jelly.mavenjellycont...@93df2c in
avalon-meta-plugin:avalon-meta-plugin
popping off org.apache.maven.jelly.mavenjellycont...@19e215b for
org.apache.maven.jelly.mavenjellycont...@9ff0a8 in
maven-antlr-plugin:maven-antlr-plugin
popping off org.apache.maven.jelly.mavenjellycont...@137d090 for
org.apache.maven.jelly.mavenjellycont...@15db314 in emc:emc-dao-impl
Root cause
Final Memory: 3M/6M
Total time: 2 seconds
Finished at: Fri May 22 14:32:50 CST 2009

Best Wishes!!

Re: mvn install for ear project

[Stephane Nicoll]

It's a bug of the war plugin that has been fixed a while back. Please use
the latest version.

S.

On Tue, May 19, 2009 at 8:55 PM, tubin gen  wrote:

> my project   has subprojects one for ear , one for war  and one for jar .
>
>
> I get this error   when I run mvn install
>
>
> java.lang.NullPointerException
>at
>
> org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>at
>
> org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>at
>
> org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>at
>
> org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>at
>
> org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>at
> org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>at
>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:597)
>at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
>
> please help me, what is causing  this error ?
>



-- 
Large Systems Suck: This rule is 100% transitive. If you build one, you
suck" -- S.Yegge

Re: How to create Hello World Projects using Maven for Spring, Hibernate, JPA, EJB, ActiveMQ?

[Wayne Fay]

> Ooops!  Do I need to delete me repository?
>
> [INFO] Required goal not found: archetype:generate in
> org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7

If you look at the documentation, you'll see the generate goal was not
added until 2.0-alpha-4, so this error message is correct. Your
archetype plugin is WAY out of date.

> [INFO] The plugin 'org.apache.maven.plugins:maven-help-plugin' does not
> exist or  no valid version could be found

Try again with "mvn -U -e archetype:generate" and "mvn -U
help:compile". If that doesn't work, you could try deleting your local
repo cache and things would probably start working again. It sounds
like you've managed to mess up some metadata, or something.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: SNAPSHOT for parent pom versioning

[Bocalinda]

I managed to get this working by having the artifactory name artifacts
uniquely (with timestamp).
Don't know if this is the proper way, but it's working so far.

2009/5/18 Anders Hammar 

> Could it be an Artifactory bug? What's the content of the
> maven-metadata.xml file of the
> seta.config:seta-general-configuration:1.0-SNAPSHOT artifact?
>
> On Mon, May 18, 2009 at 09:24, Bocalinda  wrote:
> > Hi Anders,
> >
> > Thanks a lot.. You are right, I need to specifically specify to update on
> > each build.
> > When I do so, I can see from Maven's output that it's trying to download
> my
> > POM again, but it actually isn't.
> > The POM changed in the remote repository, but it remained the same local
> > repository. I'm guessing this is a problem with my remote repository not
> > telling Maven that the file has changed.
> >
> > Just in case it would be useful in some way, here is the Maven output:
> >
> > [INFO] Scanning for projects...
> > [DEBUG] Searching for parent-POM:
> > seta.config:seta-general-configuration:pom:1.0-SNAPSHOT of project:
> > derivacion:Derivacion:pom:1.0
> >  in relative path: ../pom.xml
> > [DEBUG] Parent-POM:
> seta.config:seta-general-configuration:pom:1.0-SNAPSHOT
> > not found in relative path: ../pom.xml
> > [DEBUG] Retrieving parent-POM:
> > seta.config:seta-general-configuration:pom:1.0-SNAPSHOT for project:
> > derivacion:Derivacion:pom:1.0 f
> > rom the repository.
> > [INFO] snapshot seta.config:seta-general-configuration:1.0-SNAPSHOT:
> > checking for updates from releases
> > [DEBUG] Checking for pre-existing User-Agent configuration.
> > [DEBUG] Adding User-Agent configuration.
> > [DEBUG] Connecting to repository: 'releases' with url: '
> > http://172.18.0.78:/artifactory/releases/<
> http://172.18.0.78:/artifactory/sadiel-releases/>
> > '.
> > [DEBUG] Skipping disabled repository central
> > [DEBUG] seta-general-configuration: using locally installed snapshot
> > [DEBUG] Trying repository releases
> > [DEBUG] Checking for pre-existing User-Agent configuration.
> > [DEBUG] Adding User-Agent configuration.
> > [DEBUG] Connecting to repository: 'releases' with url: '
> > http://172.18.0.78:/artifactory/releases/<
> http://172.18.0.78:/artifactory/sadiel-releases/>
> > '.
> > Downloading:
> >
> http://172.18.0.78:/artifactory/sadiel-releases//seta/config/seta-general-configuration/1.0-SNAPSHOT/seta-general-configuration-1.0
> <
> http://172.18.0.78:/artifactory/sadiel-releases//es/sadiel/seta/config/seta-general-configuration/1.0-SNAPSHOT/seta-general-configuration-1.0
> >
> > -SNAPSHOT.pom
> > [DEBUG]   Artifact resolved
> >
> > It says "Downloading" but it didn't actually download anything.
> >
> > 2009/5/15 Anders Hammar 
> >
> >> I think SNAPSHOTs are only updated once a day or so, not for every
> >> build. You can force it through "mvn -U" or by settings updatePolicy
> >> in your settings.xml:
> >>
> >>
> http://maven.apache.org/ref/2.0.8/maven-settings/settings.html#class_releases
> >>
> >> Here's a blog about this:
> >>
> >>
> http://jlorenzen.blogspot.com/2008/07/maven-not-downloading-latest-snapshots.html
> >>
> >> /Anders
> >>
> >> On Fri, May 15, 2009 at 12:14, Bocalinda  wrote:
> >> > Hi List,
> >> >
> >> > According to the documentation, when specifying a version as
> -SNAPSHOT,
> >> > Maven downloads the artifact on each build.
> >> >
> >> > I specify:
> >> >
> >> >  
> >> >config
> >> >seta-general-configuration
> >> >1.0-SNAPSHOT
> >> >  
> >> >
> >> > and expected Maven to download the parent pom again from the
> repository,
> >> > however, this doesn't seem to be the case.
> >> > Is this a bug, or is it not supported?
> >> >
> >> > I manage the parent pom, which is used in many different projects. The
> >> > problem is that I am not the developer of all those projects, so if I
> >> would
> >> > change something in the parent pom, then I have no control over
> whether
> >> > people are updating the parant pom version in order to fetch te latest
> >> > version. It would be much easier if I could leave it as SNAPSHOT, and
> >> have
> >> > Maven download it each time a build is executed.
> >> >
> >> > I'm using Maven 2.1.0.
> >> >
> >> > Thanks.
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>