maven-assembly-plugin and file filter.properties problem

[houzecl]

With maven-assembly-plugin I can't filter files using a filter.properties
file
(note that it works with pom built-in properties e.g. ${project.groupId} or
toto)

I've created a small project using mvn archetype:create and inserted the
assembly configuration (see below)
Everything works fine, except the file filter.properties usage. It looks
like it is completely ignored
(even if this file is not present I dont get any error message from
assembly)

any hint ?

Thanks,

Christian-Luc


maven-assembly-plugin




src/main/assembly/dev/filter.properties





src/main/assembly/dev/packaging_descriptor.xml






make-assembly
package

directory-inline
attached




-- 
View this message in context: 
http://www.nabble.com/maven-assembly-plugin-and-file-filter.properties-problem-tf3690454s177.html#a10317652
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: dependency management problems...

[Wayne Fay]

If anyone actually wants this to happen, you probably need to file a
JIRA issue so this can be considered in 2.0.x (or 2.1). William, your
idea could perhaps even be implemented in 2.0.x.

Discussions like this, esp on the Users list, generally do not result
in new functionality as there are simply too many things to keep track
of...

Wayne

On 5/3/07, William Ferguson <[EMAIL PROTECTED]> wrote:

I was actually thinking that the "validate" phase would only compile a
list of dependencies up to the furthermost lifecycle phase required by
the list of goals specified. But I guess it amounts to the same thing.

William

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Friday, 4 May 2007 2:00 AM
To: Maven Users List
Subject: Re: dependency management problems...

So essentially you'd break up and move the monolithic "validate" phase
into a series of "mini-validates" that fire immediately before every
other lifecycle phase, to validate the artifacts necessary for (only)
that phase are available.

I think it would complicate things a bit, but it doesn't sound
unreasonable.

Wayne

On 5/2/07, William Ferguson <[EMAIL PROTECTED]> wrote:
> Interesting point.
>
> Aren't dependencies just compile time dependencies? So there is no
> need to resolve them unless your build includes the compile:compile
goal.
>
> Plugin dependencies are only resolved if that plugin is required as
> part of the current build.
> So why do the (compile) dependencies need to be resolved if
> compilation is not part of the build?
>
> William
>
>
> -Original Message-
> From: Wayne Fay [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 2 May 2007 1:24 PM
> To: Maven Users List
> Subject: Re: dependency management problems...
>
> As far as I know, you can't. Maven resolves all dependencies etc at
> the beginning of the lifecycle, so it can find all transitive
> artifacts etc and make sure EVERYTHING is available in the local cache

> before proceeding with the build.
>
> Wayne
>
> On 5/1/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> > Here's another way of phrasing this question - if a module has a
> > dependency on another one, how do you stop it from attempting to
> > download until absolutely necessary (say at compile time, NOT at
> > process-resources time)?
> >
> > -Original Message-
> > From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, May 01, 2007 3:11 PM
> > To: Maven Users List
> > Subject: dependency management problems...
> >
> > We're having problems building modules like this from scratch.  If
> > we run process resources from the top most level, submodule.B
> > complains about not being able to find module1's artifacts (why
> > would submodule.B need module 1's jar artifact just to process
resources?).
> >
> > parent - version 1.0-SNAPSHOT
> > |
> > |--->module1 - version 1.0-SNAPSHOT
> > |
> > |--->module2 - version 1.0-SNAPSHOT
> >|--->submodule.A- version 1.0-SNAPSHOT
> >|--->submodule.B- version 1.0-SNAPSHOT
> >
> >
> >
> > I'm really at the end of my rope on this one.  The only way to
> > successfully get this to go through is to run a mvn install from the

> > top most level first.  What's crazy is submodule.A has the same
> > dependency and goes through just fine.
> >
> > 
> > - 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]
>
>

-
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: dependency management problems...

[William Ferguson]

I was actually thinking that the "validate" phase would only compile a
list of dependencies up to the furthermost lifecycle phase required by
the list of goals specified. But I guess it amounts to the same thing.

William

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Friday, 4 May 2007 2:00 AM
To: Maven Users List
Subject: Re: dependency management problems...

So essentially you'd break up and move the monolithic "validate" phase
into a series of "mini-validates" that fire immediately before every
other lifecycle phase, to validate the artifacts necessary for (only)
that phase are available.

I think it would complicate things a bit, but it doesn't sound
unreasonable.

Wayne

On 5/2/07, William Ferguson <[EMAIL PROTECTED]> wrote:
> Interesting point.
>
> Aren't dependencies just compile time dependencies? So there is no 
> need to resolve them unless your build includes the compile:compile
goal.
>
> Plugin dependencies are only resolved if that plugin is required as 
> part of the current build.
> So why do the (compile) dependencies need to be resolved if 
> compilation is not part of the build?
>
> William
>
>
> -Original Message-
> From: Wayne Fay [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 2 May 2007 1:24 PM
> To: Maven Users List
> Subject: Re: dependency management problems...
>
> As far as I know, you can't. Maven resolves all dependencies etc at 
> the beginning of the lifecycle, so it can find all transitive 
> artifacts etc and make sure EVERYTHING is available in the local cache

> before proceeding with the build.
>
> Wayne
>
> On 5/1/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> > Here's another way of phrasing this question - if a module has a 
> > dependency on another one, how do you stop it from attempting to 
> > download until absolutely necessary (say at compile time, NOT at 
> > process-resources time)?
> >
> > -Original Message-
> > From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, May 01, 2007 3:11 PM
> > To: Maven Users List
> > Subject: dependency management problems...
> >
> > We're having problems building modules like this from scratch.  If 
> > we run process resources from the top most level, submodule.B 
> > complains about not being able to find module1's artifacts (why 
> > would submodule.B need module 1's jar artifact just to process
resources?).
> >
> > parent - version 1.0-SNAPSHOT
> > |
> > |--->module1 - version 1.0-SNAPSHOT
> > |
> > |--->module2 - version 1.0-SNAPSHOT
> >|--->submodule.A- version 1.0-SNAPSHOT
> >|--->submodule.B- version 1.0-SNAPSHOT
> >
> >
> >
> > I'm really at the end of my rope on this one.  The only way to 
> > successfully get this to go through is to run a mvn install from the

> > top most level first.  What's crazy is submodule.A has the same 
> > dependency and goes through just fine.
> >
> > 
> > - 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]
>
>

-
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: Maven Community news @ blog.octo.com

[Wendy Smoak]

On 5/2/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:


We're busy configuring the projects to deploy the site in a separate
space per version. Not sure how far we are, Wendy might answer that.


It was temporarily pre-empted by work and school, I should get back to
it next week.

The plugin docs on the main site will be for the latest official
release.  The docs should already clearly identify what version a
feature first appeared in, and any differences between versions.  If
you find that is not true, please open an issue.  In cases where there
were major changes, we may link to the docs for a prior version.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: trouble with file paths and maven packaging

[Wayne Fay]

This was recently discussed in the following thread:

Subject: How to access a file that's inside an executable jar assembly
From:  Ed Young
Date:  Fri, Apr 27, 2007 at 11:51 AM
To: Maven Users List

Check the archive or Nabble.

Wayne

On 5/3/07, sudhakar <[EMAIL PROTECTED]> wrote:

I'm using Eclipse with the Eclipse maven 2 plugin to develop a Java EE
application. My code reads in a properties file located in the
src/main/resources/ directory.

FileInputStream in = new
FileInputStream("src/main/resources/META-INF/config.properties");

I can run "mvn package" from with Eclipse and the tests run fine
indicating that the config.properties file is being read in correctly.
Now when I deploy to the server and access the application I get a
config.properties file not found error message in the server log.

I noticed that the config.properties is located in the META-INF
directory in the project root on the server.

If I relocate the META-INF folder to the projects root in the eclipse
project, maven does not include it in the jar package. I'm not sure what
is the correct way to do this and would appreciate any pointers.

Thanks
-sud

-
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]

trouble with file paths and maven packaging

[sudhakar]

I'm using Eclipse with the Eclipse maven 2 plugin to develop a Java EE
application. My code reads in a properties file located in the 
src/main/resources/ directory.

FileInputStream in = new
FileInputStream("src/main/resources/META-INF/config.properties");

I can run "mvn package" from with Eclipse and the tests run fine
indicating that the config.properties file is being read in correctly.
Now when I deploy to the server and access the application I get a
config.properties file not found error message in the server log.

I noticed that the config.properties is located in the META-INF
directory in the project root on the server.

If I relocate the META-INF folder to the projects root in the eclipse
project, maven does not include it in the jar package. I'm not sure what
is the correct way to do this and would appreciate any pointers.

Thanks
-sud

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: RequireMavenVersion failed

[A. Kevin Baynes]

Brian, you're right : there's a comment in the POM.xml also (found it
later), so the developers did a good job of trying to warn me... No
besmirchment of the Apache FTP team intended.

Thanks!

~Kevin

On 5/3/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:

That's correct and according to the commit message, it was intended to
be 2.0.5:
http://svn.apache.org/viewvc/incubator/ftpserver/


-Original Message-
From: Max Bowsher [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 03, 2007 2:11 PM
To: Maven Users List
Subject: Re: RequireMavenVersion failed

A. Kevin Baynes wrote:
> I recently installed Maven 2.0.6 and downloaded the Apache FTP
project.
>
> After running 'mvn clean install' in the main directory I get this
> strange error :
>
> [INFO] [enforcer:enforce {execution: default}] [WARNING] Rule 0:
> org.apache.maven.plugin.enforcer.RequireMavenVersion
> failed with message: Detected Maven Version: 2.0.6 is not in the
> allowed range [2.0.5,2.0.6).
> [INFO]
> --
> --
> [ERROR] BUILD ERROR
>
> It's saying that it detected version 2.0.6 but thinks it not in the
> allowed range which includes 2.0.6.

No, it doesn't.

[2.0.5,2.0.6) means "2.0.5 >= version > 2.0.6" - the version must be
strictly less than 2.0.6.

Max.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
A. Kevin Baynes

Life's a garden. Dig it!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RequireMavenVersion failed

[Brian E. Fox]

I will try to add some code to convert the range into english because many 
times the person getting this message doesn't know maven ranges. (ie users of 
the build) 

-Original Message-
From: A. Kevin Baynes [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 03, 2007 2:54 PM
To: Maven Users List
Subject: Re: RequireMavenVersion failed

Installing 2.0.5 fixed it. :-)

Thanks so much for the quick reply!

~Kevin

Ramblings follow :

Now I see where I was confused. The error message says 'not in the allowed 
range [2.0.5,2.0.6)'. I think of a range as the upper and lower bounds of an 
array (including the maximum and minimum), so I assumed that versions given 
were an inclusive range.

See how hard it is to unlearn what you already know? ;-)

Thanks again.



On 5/3/07, Roland Asmann <[EMAIL PROTECTED]> wrote:
> The range [2.0.5, 2.0.6) means, anything from and including 2.0.5, up 
> until but excluding 2.0.6.
> This means, you need to install 2.0.5 to run it!
>
>
> On Thursday 03 May 2007 19:58, A. Kevin Baynes wrote:
> > I recently installed Maven 2.0.6 and downloaded the Apache FTP project.
> >
> > After running 'mvn clean install' in the main directory I get this 
> > strange error :
> >
> > [INFO] [enforcer:enforce {execution: default}] [WARNING] Rule 0: 
> > org.apache.maven.plugin.enforcer.RequireMavenVersion
> > failed with message: Detected Maven Version: 2.0.6 is not in the 
> > allowed range [2.0.5,2.0.6).
> > [INFO]
> > 
> > 
> > [ERROR] BUILD ERROR
> >
> > It's saying that it detected version 2.0.6 but thinks it not in the 
> > allowed range which includes 2.0.6.
> >
> > Can you give me any suggestions on dealing with this error?
> >
> > Thanks!
>
> --
> Roland Asmann
>
> CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 
> 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien
>
> Tel.: +43/1/513 88 77 - 27
> Fax.: +43/1/513 88 62
> Email: [EMAIL PROTECTED]
> Web: www.cfc.at
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
A. Kevin Baynes

Life's a garden. Dig it!

-
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: RequireMavenVersion failed

[A. Kevin Baynes]

Installing 2.0.5 fixed it. :-)

Thanks so much for the quick reply!

~Kevin

Ramblings follow :

Now I see where I was confused. The error message says 'not in the
allowed range [2.0.5,2.0.6)'. I think of a range as the upper and
lower bounds of an array (including the maximum and minimum), so I
assumed that versions given were an inclusive range.

See how hard it is to unlearn what you already know? ;-)

Thanks again.



On 5/3/07, Roland Asmann <[EMAIL PROTECTED]> wrote:

The range [2.0.5, 2.0.6) means, anything from and including 2.0.5, up until
but excluding 2.0.6.
This means, you need to install 2.0.5 to run it!


On Thursday 03 May 2007 19:58, A. Kevin Baynes wrote:
> I recently installed Maven 2.0.6 and downloaded the Apache FTP project.
>
> After running 'mvn clean install' in the main directory I get this
> strange error :
>
> [INFO] [enforcer:enforce {execution: default}]
> [WARNING] Rule 0: org.apache.maven.plugin.enforcer.RequireMavenVersion
> failed with message: Detected Maven Version: 2.0.6 is not in the
> allowed range [2.0.5,2.0.6).
> [INFO]
> 
> [ERROR] BUILD ERROR
>
> It's saying that it detected version 2.0.6 but thinks it not in the
> allowed range which includes 2.0.6.
>
> Can you give me any suggestions on dealing with this error?
>
> Thanks!

--
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
A. Kevin Baynes

Life's a garden. Dig it!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RequireMavenVersion failed

[Brian E. Fox]

That's correct and according to the commit message, it was intended to
be 2.0.5:
http://svn.apache.org/viewvc/incubator/ftpserver/
 

-Original Message-
From: Max Bowsher [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 03, 2007 2:11 PM
To: Maven Users List
Subject: Re: RequireMavenVersion failed

A. Kevin Baynes wrote:
> I recently installed Maven 2.0.6 and downloaded the Apache FTP
project.
> 
> After running 'mvn clean install' in the main directory I get this 
> strange error :
> 
> [INFO] [enforcer:enforce {execution: default}] [WARNING] Rule 0: 
> org.apache.maven.plugin.enforcer.RequireMavenVersion
> failed with message: Detected Maven Version: 2.0.6 is not in the 
> allowed range [2.0.5,2.0.6).
> [INFO]
> --
> --
> [ERROR] BUILD ERROR
> 
> It's saying that it detected version 2.0.6 but thinks it not in the 
> allowed range which includes 2.0.6.

No, it doesn't.

[2.0.5,2.0.6) means "2.0.5 >= version > 2.0.6" - the version must be
strictly less than 2.0.6.

Max.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: RequireMavenVersion failed

[Max Bowsher]

A. Kevin Baynes wrote:
> I recently installed Maven 2.0.6 and downloaded the Apache FTP project.
> 
> After running 'mvn clean install' in the main directory I get this
> strange error :
> 
> [INFO] [enforcer:enforce {execution: default}]
> [WARNING] Rule 0: org.apache.maven.plugin.enforcer.RequireMavenVersion
> failed with message: Detected Maven Version: 2.0.6 is not in the
> allowed range [2.0.5,2.0.6).
> [INFO]
> 
> [ERROR] BUILD ERROR
> 
> It's saying that it detected version 2.0.6 but thinks it not in the
> allowed range which includes 2.0.6.

No, it doesn't.

[2.0.5,2.0.6) means "2.0.5 >= version > 2.0.6" - the version must be
strictly less than 2.0.6.

Max.




signature.asc
Description: OpenPGP digital signature

Re: RequireMavenVersion failed

[Roland Asmann]

The range [2.0.5, 2.0.6) means, anything from and including 2.0.5, up until 
but excluding 2.0.6.
This means, you need to install 2.0.5 to run it!


On Thursday 03 May 2007 19:58, A. Kevin Baynes wrote:
> I recently installed Maven 2.0.6 and downloaded the Apache FTP project.
>
> After running 'mvn clean install' in the main directory I get this
> strange error :
>
> [INFO] [enforcer:enforce {execution: default}]
> [WARNING] Rule 0: org.apache.maven.plugin.enforcer.RequireMavenVersion
> failed with message: Detected Maven Version: 2.0.6 is not in the
> allowed range [2.0.5,2.0.6).
> [INFO]
> 
> [ERROR] BUILD ERROR
>
> It's saying that it detected version 2.0.6 but thinks it not in the
> allowed range which includes 2.0.6.
>
> Can you give me any suggestions on dealing with this error?
>
> Thanks!

-- 
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RequireMavenVersion failed

[A. Kevin Baynes]

I recently installed Maven 2.0.6 and downloaded the Apache FTP project.

After running 'mvn clean install' in the main directory I get this
strange error :

[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugin.enforcer.RequireMavenVersion
failed with message: Detected Maven Version: 2.0.6 is not in the
allowed range [2.0.5,2.0.6).
[INFO] 
[ERROR] BUILD ERROR

It's saying that it detected version 2.0.6 but thinks it not in the
allowed range which includes 2.0.6.

Can you give me any suggestions on dealing with this error?

Thanks!

--
A. Kevin Baynes

Life's a garden. Dig it!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: M2-Plugin Development: Reading POM programmatically

[Mark Hobson]

On 03/05/07, Martin Bengl <[EMAIL PROTECTED]> wrote:

hello folks,

I use following solution (with maven 2.0.4) to create a MavenProject at
runtime to extract informations like artifactId and groupid - this could
be also done by manually parsing the xml file - but i think its a better
way to use the maven classes.

File pomFile = new File("pom.xml");
MavenProjectBuilder projectBuilder;
ArtifactRepository localRepository;

MavenProject pom = projectBuilder.build(pomFile, localRepository,
(ProfileManager)null );

My Question is: From which object can I receive a profileManager
instance? (the projectBuilder and localRepository are defined as plexus
components, the profileManager isn't!)


To simply parse the pom into a MavenProject, use something like:

MavenXpp3Reader reader = new MavenXpp3Reader();
Model model = reader.read(myreader);
MavenProject project = new MavenProject(model);

I've got a shared component to help with introspecting the Maven
environment, as you describe, which I'm hoping to submit when I get a
chance.

Cheers,

Mark

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Multi-module not picking up modules

[Wayne Fay]

First off... I think you're confused about some things... modules are
not dependencies! Module is simply a source code way to specify
children of a given parent module, to simplify the build process.

I'm surprised (and almost don't believe you) that your WAR is getting
packaged with all of the axis2 modules. I will need to try a little
test here and see what's going on. It sounds like a bug in WAR plugin
if this is actually happening.

The eclipse plugin should not add the modules of a dependency artifact
to the .classpath. This is correct behavior.

The modules of a dependency artifact should not be automatically
installed into your local repo. This only happens with actual
dependencies. So this is also correct behavior.

If you need to use all those axis2 modules, then you need to add them
as  in your own project. But I would generally doubt
that you actually need to use ALL of them -- more likely, you just
need a couple of them.

Wayne

On 5/3/07, lightbulb432 <[EMAIL PROTECTED]> wrote:


I have a question about the artifacts under
http://repo1.maven.org/maven2/org/apache/axis2, and the .pom at
http://repo1.maven.org/maven2/org/apache/axis2/axis2/1.2/axis2-1.2.pom/

My project depends on the axis2 artifact. When I do a mvn deploy, the
deployed WAR gets packaged including all of its JARs specified in 
(e.g. axis2-adb, axis2-codegen, etc...). However, there are two problems:

1) When I do a mvn eclipse:eclipse, these other JARs are not added to the
.classpath file in Eclipse.

2) These other JARs are not automatically put into my local repository. (I
assume this problem causes the previous problem, where even if .classpath
contained paths to those JARs, they wouldn't be in the repository to begin
with.)

How can I solve these problems? Thanks.



franz see wrote:
>
> Good day,
>
> That's because you're looking at the binary repository, and not the source
> repository :-)
>
> checkout the code from its source repository then reasses it again :-)
> ...as to where it is, I don't know. Try googling for it :-)
>
> The basedir is not
>
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/.
> It is the one that contains the pom.xml of axis2 in the source repository.
>
> If you take a look at the source, you would probably see something like
>
> .
>  |-- pom.xml
>  `-- modules
>   `-- parent
>`-- pom.xml
>
> ( note: you will not see this directory structure in the binary
> repository. it's in the source repository ).
>
> Furthermore, users use pom.xml ( this is where you do your mvn
> whatever:command ), while maven uses the .pom files ( ...i think for
> resolving dependencies ).
>
> Cheers,
> Franz
>
>
> lightbulb432 wrote:
>>
>> Thanks for your response.
>>
>> By basedir do you mean the path that directly contains the artifacts?
>> e.g.
>>
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/
>> in the case where org.apache.axis2 is the groupId?
>>
>> In this case, is the axis2-1.1.pom wrong, or am I mistaken? Because in
>> that .pom file, it refers to
>> modules/parent
>>
>> Shouldn't it refer to
>> ../axis2-parent
>> because that's how it looks to me to be structured in their repository.
>>
>> So it seems like 2 mistakes have been made - there's no modules directory
>> underneath the axis2 artifact directory, and it doesn't seem to be called
>> parent, but rather axis2-parent (or is their way of writing it correct
>> because of some default prefixing or something like that?)
>>
>> What also confuses me is that for each of the modules, for example
>> "java2wsdl" at
>>
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2-java2wsdl/1.1/
>> there is no pom.xml! Only a axis2-java2wsdl-1.1.pom...but that file looks
>> pretty close to a pom.xml...?
>>
>> Wow, I'm so confused. Please help! Thanks.
>>
>>
>>
>> franz see wrote:
>>>
>>> Good day,
>>>
>>> The  tag actually refers to directories from the ${basedir}.
>>> Thus if you have
>>>
>>> 
>>>   ...
>>>   
>>> ...
>>> modules/parent
>>> modules/java2wsdl
>>>   >> 
>>>
>>> Maven will try to find ${basedir}/modules/parent/pom.xml and
>>> ${basedir}/modules/java2wsdl/pom.xml.
>>>
>>> As for the difference between pom.xml and axis2-1.1.pom, ...the former
>>> is the one maven uses for its build and can be found in your source,
>>> while the latter is generated by maven when you're installing or
>>> deploying a maven project to a repository ( which would also be used by
>>> maven in some of its processes ).
>>>
>>> As for the packages, try looking at the modules/xxx/target/ for the
>>> generated binaries. If you don't see it there, try looking at the output
>>> log.
>>>
>>> If a module is a jar, then you'd probably see something like
>>>
>>> [INFO] Building 
>>> ...
>>> [INFO] jar:jar
>>> ...
>>> [INFO] Building jar: 
>>>
>>> Then from there, you can take a look at the 
>>> to see whether it really was created.
>>>
>>> The same goes for non-jar modules...you would have so

Re: [m2] Dependency Ordering Headache

[Jose Alberto Fernandez]

 Yes indeed, you could repackage the libraries by hand. But then WL can blame
you for any further problem as you are hand crafting the libraries as oppose
to using them as provided. Never mind if the library involves signed classes
of any sort.

I am not trying to defend WL or anyone else. But where I get a little of a
peeve is when people say "no the only way is this way and everyone else in
the world is wrong and no other way should be allowed." That only slows down
adoption.

And Maven has very many great things for that to happen.

J.A


Wayne Fay wrote:
> 
> I work in the corporate world every day, friend.
> 
> As for incorporating a patch like this, if it is a fairly trivial
> patch (many are just a couple fixed class files), I would personally
> just unpack the affected jars, copy the patched files in, and repack
> them with adjusted version numbers. I'm not saying this is ideal, but
> its not a 6mo delay either...
> 
> Wayne
> 
> On 5/3/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
>>
>> When I read things like this, I think some of the Maven people have never
>> been working in the real corporate world. You cannot expect a project to
>> stop for 6 month waiting for the next full release of Weblogic or any
>> other
>> product, just because there is no way on Maven to take a product patch
>> into
>> account.
>>
>> Try telling your manager that his flagship project must be delay half a
>> year
>> because your building tool does not like the way Weblogic distributes an
>> emergency patch. I mean how fast would you think it would take to be
>> asked
>> to clean your desk and leave the building?
>>
>> J.A.
>>
>>
>> Wayne Fay wrote:
>> >
>> > As a Weblogic customer, I'd complain until they resolve this issue.
>> >
>> > I agree entirely with Graham -- the fact that your dependency JARs
>> > must be ordered in a particular way to get a successful build should
>> > not be acceptable to you.
>> >
>> > Wayne
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-m2--Dependency-Ordering-Headache-tf3668646s177.html#a10305209
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> 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--Dependency-Ordering-Headache-tf3668646s177.html#a10308039
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Manage Maven Classpath

[Wayne Fay]

Not that I am aware of, at least, not without hacking some internal
Maven classes.

Wayne

On 5/3/07, GreJ <[EMAIL PROTECTED]> wrote:



Hi,

it's a simple question, and i think that the answer is "no", but i need a
confirmation ;)

Is it possible to manage manually the MavenClasspath ?

Thanks.
--
View this message in context:
http://www.nabble.com/Manage-Maven-Classpath-tf3685869s177.html#a10302892
Sent from the Maven - Users mailing list archive at Nabble.com.


-
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: dependency management problems...

[Wayne Fay]

So essentially you'd break up and move the monolithic "validate" phase
into a series of "mini-validates" that fire immediately before every
other lifecycle phase, to validate the artifacts necessary for (only)
that phase are available.

I think it would complicate things a bit, but it doesn't sound unreasonable.

Wayne

On 5/2/07, William Ferguson <[EMAIL PROTECTED]> wrote:

Interesting point.

Aren't dependencies just compile time dependencies? So there is no need
to resolve them unless your build includes the compile:compile goal.

Plugin dependencies are only resolved if that plugin is required as part
of the current build.
So why do the (compile) dependencies need to be resolved if compilation
is not part of the build?

William


-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 2 May 2007 1:24 PM
To: Maven Users List
Subject: Re: dependency management problems...

As far as I know, you can't. Maven resolves all dependencies etc at the
beginning of the lifecycle, so it can find all transitive artifacts etc
and make sure EVERYTHING is available in the local cache before
proceeding with the build.

Wayne

On 5/1/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> Here's another way of phrasing this question - if a module has a
> dependency on another one, how do you stop it from attempting to
> download until absolutely necessary (say at compile time, NOT at
> process-resources time)?
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 01, 2007 3:11 PM
> To: Maven Users List
> Subject: dependency management problems...
>
> We're having problems building modules like this from scratch.  If we
> run process resources from the top most level, submodule.B complains
> about not being able to find module1's artifacts (why would
> submodule.B need module 1's jar artifact just to process resources?).
>
> parent - version 1.0-SNAPSHOT
> |
> |--->module1 - version 1.0-SNAPSHOT
> |
> |--->module2 - version 1.0-SNAPSHOT
>|--->submodule.A- version 1.0-SNAPSHOT
>|--->submodule.B- version 1.0-SNAPSHOT
>
>
>
> I'm really at the end of my rope on this one.  The only way to
> successfully get this to go through is to run a mvn install from the
> top most level first.  What's crazy is submodule.A has the same
> dependency and goes through just fine.
>
> -
> 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]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

NYC Maven/Ant Build Engineer position...

[Bob Aiello]

I am looking to hire build engineer/junior java developer
to help me with Unix/Linux based Maven/Ant Java builds for 
a number of exciting large financial systems (www.accelortrading.com).

If you are interested please contact me directly.

Bob Aiello
Manager, Process
FXall LLC (www.fxall.com)
646 268 9914

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

eclipse:eclipse

[Borut Bolčina]

Hello,

checking out

svn checkout https://svn.sourceforge.net/svnroot/tacos/tacos-4.1/trunk/
tacos-project

and then

mvn eclipse:eclipse

inside tacos-project directory

gives me:

[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] org/codehaus/plexus/util/IOUtil
[INFO]

[INFO] Trace
java.lang.NoClassDefFoundError: org/codehaus/plexus/util/IOUtil
   at
org.apache.maven.plugin.ide.AbstractIdeSupportMojo.resolveSourceArtifacts(
AbstractIdeSupportMojo.ja
va:878)
   at org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(
AbstractIdeSupportMojo.java:416)
   at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:443)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:539)

   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
(DefaultLifecycleExecutor.
java:493)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:463)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleEx
ecutor.java:311)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.ja
va:278)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:143)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
   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)
[INFO]

[INFO] Total time: 2 minutes 23 seconds
[INFO] Finished at: Thu May 03 17:34:54 CEST 2007
[INFO] Final Memory: 6M/11M
[INFO]



Running the second time gives me:

[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Tacos - 4.1.0-SNAPSHOT
[INFO]   Tacos Core - 4.1.0-SNAPSHOT
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]

[INFO] Building Tacos - 4.1.0-SNAPSHOT
[INFO]task-segment: [eclipse:eclipse]
[INFO]

[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse]
[INFO] Not running eclipse plugin goal for pom project
[INFO]

[INFO] Building Tacos Core - 4.1.0-SNAPSHOT
[INFO]task-segment: [eclipse:eclipse]
[INFO]

[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse]
[INFO] Using source status cache: C:\Documents and
Settings\Borut\Desktop\Workspace\tacos-project\target\mvn-e
clipse-cache.properties
[INFO] Wrote settings to C:\Documents and
Settings\Borut\Desktop\Workspace\tacos-project\tacos-core\.settings\
org.eclipse.jdt.core.prefs
[INFO] Creating maven-eclipse.xml Ant file to handle resources
[INFO] Creating external launcher file
[INFO] Wrote Eclipse project for "tacos-core" to C:\Documents and
Settings\Borut\Desktop\Workspace\tacos-proje
ct\tacos-core.
[INFO]
[INFO]
[INFO]

[INFO] Reactor Summary:
[INFO]

[INFO] Tacos - 4.1.0-SNAPSHOT  SUCCESS [
0.921s]
[INFO] Tacos Core - 4.1.0-SNAPSHOT ... SUCCESS [
1.063s]
[INFO]

[INFO]

[INFO] BUILD SUCCESSFUL
[INFO]

[INFO] Total time: 2 seconds
[INFO] Finished at: Thu May 03 17:35:04 CEST 2007
[INFO] Final Memory: 5M/10M
[INFO]



On one worksta

Re: [m2] Dependency Ordering Headache

[Wayne Fay]

I work in the corporate world every day, friend.

As for incorporating a patch like this, if it is a fairly trivial
patch (many are just a couple fixed class files), I would personally
just unpack the affected jars, copy the patched files in, and repack
them with adjusted version numbers. I'm not saying this is ideal, but
its not a 6mo delay either...

Wayne

On 5/3/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:


When I read things like this, I think some of the Maven people have never
been working in the real corporate world. You cannot expect a project to
stop for 6 month waiting for the next full release of Weblogic or any other
product, just because there is no way on Maven to take a product patch into
account.

Try telling your manager that his flagship project must be delay half a year
because your building tool does not like the way Weblogic distributes an
emergency patch. I mean how fast would you think it would take to be asked
to clean your desk and leave the building?

J.A.


Wayne Fay wrote:
>
> As a Weblogic customer, I'd complain until they resolve this issue.
>
> I agree entirely with Graham -- the fact that your dependency JARs
> must be ordered in a particular way to get a successful build should
> not be acceptable to you.
>
> Wayne
>
>

--
View this message in context:
http://www.nabble.com/-m2--Dependency-Ordering-Headache-tf3668646s177.html#a10305209
Sent from the Maven - Users mailing list archive at Nabble.com.


-
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: Multi-module not picking up modules

[lightbulb432]

I have a question about the artifacts under
http://repo1.maven.org/maven2/org/apache/axis2, and the .pom at
http://repo1.maven.org/maven2/org/apache/axis2/axis2/1.2/axis2-1.2.pom/

My project depends on the axis2 artifact. When I do a mvn deploy, the
deployed WAR gets packaged including all of its JARs specified in 
(e.g. axis2-adb, axis2-codegen, etc...). However, there are two problems:

1) When I do a mvn eclipse:eclipse, these other JARs are not added to the
.classpath file in Eclipse.

2) These other JARs are not automatically put into my local repository. (I
assume this problem causes the previous problem, where even if .classpath
contained paths to those JARs, they wouldn't be in the repository to begin
with.)

How can I solve these problems? Thanks.



franz see wrote:
> 
> Good day,
> 
> That's because you're looking at the binary repository, and not the source
> repository :-)
> 
> checkout the code from its source repository then reasses it again :-)
> ...as to where it is, I don't know. Try googling for it :-)
> 
> The basedir is not
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/.
> It is the one that contains the pom.xml of axis2 in the source repository.
> 
> If you take a look at the source, you would probably see something like
> 
> .
>  |-- pom.xml
>  `-- modules
>   `-- parent
>`-- pom.xml
> 
> ( note: you will not see this directory structure in the binary
> repository. it's in the source repository ).
> 
> Furthermore, users use pom.xml ( this is where you do your mvn
> whatever:command ), while maven uses the .pom files ( ...i think for
> resolving dependencies ).
> 
> Cheers,
> Franz
> 
> 
> lightbulb432 wrote:
>> 
>> Thanks for your response.
>> 
>> By basedir do you mean the path that directly contains the artifacts?
>> e.g.
>> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/
>> in the case where org.apache.axis2 is the groupId?
>> 
>> In this case, is the axis2-1.1.pom wrong, or am I mistaken? Because in
>> that .pom file, it refers to
>> modules/parent
>> 
>> Shouldn't it refer to
>> ../axis2-parent
>> because that's how it looks to me to be structured in their repository.
>> 
>> So it seems like 2 mistakes have been made - there's no modules directory
>> underneath the axis2 artifact directory, and it doesn't seem to be called
>> parent, but rather axis2-parent (or is their way of writing it correct
>> because of some default prefixing or something like that?)
>> 
>> What also confuses me is that for each of the modules, for example
>> "java2wsdl" at
>> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2-java2wsdl/1.1/
>> there is no pom.xml! Only a axis2-java2wsdl-1.1.pom...but that file looks
>> pretty close to a pom.xml...?
>> 
>> Wow, I'm so confused. Please help! Thanks.
>> 
>> 
>> 
>> franz see wrote:
>>> 
>>> Good day,
>>> 
>>> The  tag actually refers to directories from the ${basedir}.
>>> Thus if you have  
>>> 
>>> 
>>>   ...
>>>   
>>> ...
>>> modules/parent
>>> modules/java2wsdl
>>>   >> 
>>> 
>>> Maven will try to find ${basedir}/modules/parent/pom.xml and
>>> ${basedir}/modules/java2wsdl/pom.xml.
>>> 
>>> As for the difference between pom.xml and axis2-1.1.pom, ...the former
>>> is the one maven uses for its build and can be found in your source,
>>> while the latter is generated by maven when you're installing or
>>> deploying a maven project to a repository ( which would also be used by
>>> maven in some of its processes ).
>>> 
>>> As for the packages, try looking at the modules/xxx/target/ for the
>>> generated binaries. If you don't see it there, try looking at the output
>>> log.
>>> 
>>> If a module is a jar, then you'd probably see something like
>>> 
>>> [INFO] Building 
>>> ...
>>> [INFO] jar:jar
>>> ...
>>> [INFO] Building jar: 
>>> 
>>> Then from there, you can take a look at the 
>>> to see whether it really was created.
>>> 
>>> The same goes for non-jar modules...you would have something like
>>> 
>>> [INFO] Building 
>>> ...
>>> [INFO] 
>>> ...
>>> [INFO] Building : 
>>> 
>>> Cheers,
>>> Franz
>>> 
>>> 
>>> lightbulb432 wrote:
 
 I want to build a multi-module project from the following pom, but I'm
 not sure if I'm doing it correctly. The POM of the containing project
 is below:
 
 http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/axis2/axis2/1.1/axis2-1.1.pom
 
 When I do a "mvn package" in that directly after downloading it, it
 only packages itself but not the specified modules. I'm not sure why
 the modules start with "modules/" and don't contain a prefix of
 "axis2-", which I'd guess it should be based on the naming of what the
 other modules are listed as (if you go up a couple of levels from the
 POM link above)
 
 Also, what's the difference between a pom.xml and a axis2-1.1.pom?
 
 Your help would be really appreciated.
 
>>> 
>>> 
>> 

Re: Guide to creating archetypes...

[nicolas de loof]

I allready tried this, but the generated archetype does not include modules
(only parent pom).

2007/5/3, Raphaël Piéroni <[EMAIL PROTECTED]>:


Try mvn -N archetypeng:create-from-project

Raphaël

2007/5/3, nicolas de loof <[EMAIL PROTECTED]>:
> I'm trying to use the archetypeNG plugin from an existing complex (multi
> module) project.
>
> The plugins ask me for archetype groupId and other properties on every
> module of the source project. It generates an archetype for every
module.
>
> I'd like to generate the complete project with modules from a single
> archetype, based on my sample project.
>
> How to do this ?
>
> Nico.
>
>
>
> 2007/5/3, Raphaël Piéroni <[EMAIL PROTECTED]>:
> >
> > 2007/5/3, Rémy Sanlaville <[EMAIL PROTECTED]>:
> > > >
> > > > > what's the difference ?
> > > > Mainly
> > > > - the descriptor is changed
> > > > - user is prompted for selecting the archetype and configuration
> > > > (unless using -B)
> > > > - any file can be resolved as packaged (using package in the
directory
> > > > resolution)
> > > > - any file can be resolved as binary (copied instead of velocity
> > template)
> > > > - support for multi project
> >
> > I forgot:
> > - archetype creation form an existing project (yes with the above
> > features packaged, filtered, multiproject)
> >
> > > >
> > > > >
> > > > > http://mojo.codehaus.org/maven-archetypeng/
> > > > which is not yet released
> > >
> > >
> > > Did you have a roadmap when it will be released ?
> > I got a roadmap (on paper without any date)
> > But i could say it need at least 2 weeks before putting a first alpha
> > release
> >
> > Raphaël
> >
> > > So, if I understand, maven-archetypeng has more features and seems
more
> > > powerful.
> > > So it's better to look at maven-archetypeng instead of
maven-archetype.
> > I
> > > will have a look.
> > > I imagine it will normally replace maven-archetype in the future.
> > >
> > > >
> > > > > or
> > > > >
> > > > > mvn archetype:create
> > > > >   -DgroupId=[your project's group id]
> > > > >   -DartifactId=[your project's artifact id]
> > > > >   -DarchetypeArtifactId=maven-archetype-archetype
> > > > >
> > > > >
> > > > > (cf.
> > http://maven.apache.org/guides/mini/guide-creating-archetypes.html)
> > > >
> > > >
> > > > Hope the answer makes sense
> > >
> > >
> > > Nice thanks.
> > >
> > > Rémy
> > >
> >
>

Re: Archiva on Tomcat Problems

[Alexey Kakunin]

Hello!

I followed this instruction:
http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat
Initially, I also has problem with

INFO   | jvm 1| 2007/03/10 01:20:26 | Missing "/security" package
namespace in xwork.xml

But after creation conf/archiva.xml with specified context (read
documentation I pointed) it started to work



2007/3/10, Brian Sam-Bodden <[EMAIL PROTECTED]>:


Followed the instructions at  http://maven.apache.org/archiva/guides/
getting-started/index.html

I get a 500 error showing:


===

===
Connection Factory "java:comp/env/jdbc/archiva" not found - action -
file:/opt/tomcat5/webapps/archiva/WEB-INF/classes/xwork.xml:176:78

com.opensymphony.xwork.config.providers.XmlConfigurationProvider.verifyA
ction(XmlConfigurationProvider.java:186)

com.opensymphony.xwork.config.providers.XmlConfigurationProvider.addActi
on(XmlConfigurationProvider.java:136)

com.opensymphony.xwork.config.providers.XmlConfigurationProvider.addPack
age(XmlConfigurationProvider.java:220)

com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadCon
figurationFile(XmlConfigurationProvider.java:676)

com.opensymphony.xwork.config.providers.XmlConfigurationProvider.init
(XmlConfigurationProvider.java:91)
com.opensymphony.xwork.config.impl.DefaultConfiguration.reload
(DefaultConfiguration.java:85)

com.opensymphony.xwork.config.ConfigurationManager.getConfiguration
(ConfigurationManager.java:54)
com.opensymphony.xwork.DefaultActionProxy.
(DefaultActionProxy.java:57)
com.opensymphony.xwork.DefaultActionProxyFactory.createActionProxy
(DefaultActionProxyFactory.java:46)
com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction
(DispatcherUtils.java:216)
com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter
(FilterDispatcher.java:202)
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage
(PageFilter.java:118)
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter
(PageFilter.java:52)
com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter
(ActionContextCleanUp.java:88)

===

===

In the catalina.out log I see this errors:


===

===
INFO   | jvm 1| 2007/03/10 01:20:14 | 2007-03-10 01:20:14,752
[http-8080-Processor5] INFO  EnvironmentCheck:required-roles -
Checking the existance of required roles.
INFO   | jvm 1| 2007/03/10 01:20:26 | 2007-03-10 01:20:26,830
[http-8080-Processor5] ERROR
Interceptor:pssEnvironmentCheckInterceptor - EnvironmentCheck Failure.
INFO   | jvm 1| 2007/03/10 01:20:26 |
==
INFO   | jvm 1| 2007/03/10 01:20:26 |  ENVIRONMENT FAILURE !!
INFO   | jvm 1| 2007/03/10 01:20:26 |
INFO   | jvm 1| 2007/03/10 01:20:26 | Missing "/security" package
namespace in xwork.xml
INFO   | jvm 1| 2007/03/10 01:20:26 | Missing [1] xwork.xml
configuration elements.
INFO   | jvm 1| 2007/03/10 01:20:26 |
INFO   | jvm 1| 2007/03/10 01:20:26 |
==
INFO   | jvm 1| 2007/03/10 01:20:26 | 2007-03-10 01:20:26,864
[http-8080-Processor5] INFO  Interceptor:pssSecureActionInterceptor -
org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor
initialized!
INFO   | jvm 1| 2007/03/10 01:20:28 | 2007-03-10 01:20:28,444
[http-8080-Processor5] ERROR VelocityComponent  -
ResourceManager : unable to find resource 'VM_global_library.vm' in
any resource loader.
INFO   | jvm 1| 2007/03/10 01:20:28 | 2007-03-10 01:20:28,748
[http-8080-Processor5] INFO  Interceptor:pssSecureActionInterceptor -
org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor
initialized!
INFO   | jvm 1| 2007/03/10 01:20:28 | 2007-03-10 01:20:28,750
[http-8080-Processor5] INFO  Interceptor:pssSecureActionInterceptor -
org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor
initialized!
INFO   | jvm 1| 2007/03/10 01:20:29 | 2007-03-10 01:20:29,620
[http-8080-Processor5] ERROR DispatcherUtils- Could
not find action
INFO   | jvm 1| 2007/03/10 01:20:29 | Connection Factory
"java:comp/env/jdbc/archiva" not found - action - file:/opt/tomcat5/
webapps/archiva/WEB-INF/classes/xwork.xml:176:78

===

Re: Guide to creating archetypes...

[Raphaël Piéroni]

Try mvn -N archetypeng:create-from-project

Raphaël

2007/5/3, nicolas de loof <[EMAIL PROTECTED]>:

I'm trying to use the archetypeNG plugin from an existing complex (multi
module) project.

The plugins ask me for archetype groupId and other properties on every
module of the source project. It generates an archetype for every module.

I'd like to generate the complete project with modules from a single
archetype, based on my sample project.

How to do this ?

Nico.



2007/5/3, Raphaël Piéroni <[EMAIL PROTECTED]>:
>
> 2007/5/3, Rémy Sanlaville <[EMAIL PROTECTED]>:
> > >
> > > > what's the difference ?
> > > Mainly
> > > - the descriptor is changed
> > > - user is prompted for selecting the archetype and configuration
> > > (unless using -B)
> > > - any file can be resolved as packaged (using package in the directory
> > > resolution)
> > > - any file can be resolved as binary (copied instead of velocity
> template)
> > > - support for multi project
>
> I forgot:
> - archetype creation form an existing project (yes with the above
> features packaged, filtered, multiproject)
>
> > >
> > > >
> > > > http://mojo.codehaus.org/maven-archetypeng/
> > > which is not yet released
> >
> >
> > Did you have a roadmap when it will be released ?
> I got a roadmap (on paper without any date)
> But i could say it need at least 2 weeks before putting a first alpha
> release
>
> Raphaël
>
> > So, if I understand, maven-archetypeng has more features and seems more
> > powerful.
> > So it's better to look at maven-archetypeng instead of maven-archetype.
> I
> > will have a look.
> > I imagine it will normally replace maven-archetype in the future.
> >
> > >
> > > > or
> > > >
> > > > mvn archetype:create
> > > >   -DgroupId=[your project's group id]
> > > >   -DartifactId=[your project's artifact id]
> > > >   -DarchetypeArtifactId=maven-archetype-archetype
> > > >
> > > >
> > > > (cf.
> http://maven.apache.org/guides/mini/guide-creating-archetypes.html)
> > >
> > >
> > > Hope the answer makes sense
> >
> >
> > Nice thanks.
> >
> > Rémy
> >
>

Re: How to add project specific dependencies

[John Patrick]

Kiran,

Project level defined repositories can be specified within the pom: e.g.
[Extract from http://maven.apache.org/pom.html]

 ...
 
   
 central
 Maven Repository Switchboard
 default
 http://repo1.maven.org/maven2
 
   false
 
   
   ...
 
...


I've not used that section personally, I tend just to use settings.xml and
have all requests going via maven proxy to reduce network traffic and
central manage external and internal repositories.

If you want more information take a look at:
http://maven.apache.org/pom.html
http://maven.apache.org/xsd/maven-4.0.0.xsd

John
On 03/05/07, Kiran Kodlady <[EMAIL PROTECTED]> wrote:




Hello,

I got struck while doing migration of maven 1.0.2 to maven 2.0.6. In maven
1.0.2 we had a file called build.properties, which consists of paths for
both remote as well as local repositories. But in maven 2.0.6 i am unable
to
find  any corresponding file which holds these values. Can anyone help me
how this can be handled in maven 2.0.6?

Thank you.
--
View this message in context:
http://www.nabble.com/How-to-add-project-specific-dependencies-tf3686150s177.html#a10303903
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Cleaning before assembly

[Steven Rowe]

Hi Jose,

maven-clean-plugin's "clean" goal can clean other directories besides
the default - see


Steve

Jose Alberto Fernandez wrote:
> Hi,
> 
> Can someone point me at the correct way to tell Maven's assembly or cleaning
> plug-in to clean the assembly area before assembling a new. Currently as the
> assembly area is not cleaned up we finish with old jars still there from
> older builds.
> 
> Any hints will be appreciated.
> 
> Jose Alberto


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Guide to creating archetypes...

[nicolas de loof]

I'm trying to use the archetypeNG plugin from an existing complex (multi
module) project.

The plugins ask me for archetype groupId and other properties on every
module of the source project. It generates an archetype for every module.

I'd like to generate the complete project with modules from a single
archetype, based on my sample project.

How to do this ?

Nico.



2007/5/3, Raphaël Piéroni <[EMAIL PROTECTED]>:


2007/5/3, Rémy Sanlaville <[EMAIL PROTECTED]>:
> >
> > > what's the difference ?
> > Mainly
> > - the descriptor is changed
> > - user is prompted for selecting the archetype and configuration
> > (unless using -B)
> > - any file can be resolved as packaged (using package in the directory
> > resolution)
> > - any file can be resolved as binary (copied instead of velocity
template)
> > - support for multi project

I forgot:
- archetype creation form an existing project (yes with the above
features packaged, filtered, multiproject)

> >
> > >
> > > http://mojo.codehaus.org/maven-archetypeng/
> > which is not yet released
>
>
> Did you have a roadmap when it will be released ?
I got a roadmap (on paper without any date)
But i could say it need at least 2 weeks before putting a first alpha
release

Raphaël

> So, if I understand, maven-archetypeng has more features and seems more
> powerful.
> So it's better to look at maven-archetypeng instead of maven-archetype.
I
> will have a look.
> I imagine it will normally replace maven-archetype in the future.
>
> >
> > > or
> > >
> > > mvn archetype:create
> > >   -DgroupId=[your project's group id]
> > >   -DartifactId=[your project's artifact id]
> > >   -DarchetypeArtifactId=maven-archetype-archetype
> > >
> > >
> > > (cf.
http://maven.apache.org/guides/mini/guide-creating-archetypes.html)
> >
> >
> > Hope the answer makes sense
>
>
> Nice thanks.
>
> Rémy
>

Re: [m2] Dependency Ordering Headache

[Jose Alberto Fernandez]

When I read things like this, I think some of the Maven people have never
been working in the real corporate world. You cannot expect a project to
stop for 6 month waiting for the next full release of Weblogic or any other
product, just because there is no way on Maven to take a product patch into
account.

Try telling your manager that his flagship project must be delay half a year
because your building tool does not like the way Weblogic distributes an
emergency patch. I mean how fast would you think it would take to be asked
to clean your desk and leave the building?

J.A. 


Wayne Fay wrote:
> 
> As a Weblogic customer, I'd complain until they resolve this issue.
> 
> I agree entirely with Graham -- the fact that your dependency JARs
> must be ordered in a particular way to get a successful build should
> not be acceptable to you.
> 
> Wayne
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-m2--Dependency-Ordering-Headache-tf3668646s177.html#a10305209
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How do I get a list of all available properties?

[Steinhauer, Frank]

Hi,
 
How do I get a list of all available properties? I already found a
static list
(http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide), but
there should be a way to create a list of all available properties and
their values during the build , e.g. by using a Properties-Plugin. Is
there something like that?

Cheers,

Frank

 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How to add project specific dependencies

[Kiran Kodlady]

Hello,

I got struck while doing migration of maven 1.0.2 to maven 2.0.6. In maven
1.0.2 we had a file called build.properties, which consists of paths for
both remote as well as local repositories. But in maven 2.0.6 i am unable to
find  any corresponding file which holds these values. Can anyone help me
how this can be handled in maven 2.0.6? 

Thank you.
-- 
View this message in context: 
http://www.nabble.com/How-to-add-project-specific-dependencies-tf3686150s177.html#a10303903
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: Cleaning before assembly

[Steinhauer, Frank]

Just look into the description of the clean plugin 
http://maven.apache.org/plugins/maven-clean-plugin/examples/delete_additional_files.html

Frank



-Ursprüngliche Nachricht-
Von: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 3. Mai 2007 14:22
An: users@maven.apache.org
Betreff: Re: Cleaning before assembly


For reasons of our configuration, we cannot really assembly inside the target
directory, but on an staging area pointed by an environment variable and
where we can start or server for manual testing.

This is why I would like having a way to tell either the cleaning plug-in or
assembly itself to clean up its content.

Any ideas?

J.A.

MALICE wrote:
> 
> If you use a directory under 'target', it should be cleaned by the 
> clean-plugin... Maybe the answer lies in configuring the assembly-plugin
> to 
> use anothe dir, instead of telling the clean-plugin to clean up other
> dirs?
> 
> 
> On Thursday 03 May 2007 13:46, Jose Alberto Fernandez wrote:
>> Hi,
>>
>> Can someone point me at the correct way to tell Maven's assembly or
>> cleaning plug-in to clean the assembly area before assembling a new.
>> Currently as the assembly area is not cleaned up we finish with old jars
>> still there from older builds.
>>
>> Any hints will be appreciated.
>>
>> Jose Alberto
> 
> -- 
> Roland Asmann
> 
> CFC Informationssysteme Entwicklungsgesellschaft m.b.H
> Bäckerstrasse 1/2/7
> A-1010 Wien
> FN 266155f, Handelsgericht Wien
> 
> Tel.: +43/1/513 88 77 - 27
> Fax.: +43/1/513 88 62
> Email: [EMAIL PROTECTED]
> Web: www.cfc.at
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Cleaning-before-assembly-tf3685941s177.html#a10303664
Sent from the Maven - Users mailing list archive at Nabble.com.


-
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: Cleaning before assembly

[Jose Alberto Fernandez]

For reasons of our configuration, we cannot really assembly inside the target
directory, but on an staging area pointed by an environment variable and
where we can start or server for manual testing.

This is why I would like having a way to tell either the cleaning plug-in or
assembly itself to clean up its content.

Any ideas?

J.A.

MALICE wrote:
> 
> If you use a directory under 'target', it should be cleaned by the 
> clean-plugin... Maybe the answer lies in configuring the assembly-plugin
> to 
> use anothe dir, instead of telling the clean-plugin to clean up other
> dirs?
> 
> 
> On Thursday 03 May 2007 13:46, Jose Alberto Fernandez wrote:
>> Hi,
>>
>> Can someone point me at the correct way to tell Maven's assembly or
>> cleaning plug-in to clean the assembly area before assembling a new.
>> Currently as the assembly area is not cleaned up we finish with old jars
>> still there from older builds.
>>
>> Any hints will be appreciated.
>>
>> Jose Alberto
> 
> -- 
> Roland Asmann
> 
> CFC Informationssysteme Entwicklungsgesellschaft m.b.H
> Bäckerstrasse 1/2/7
> A-1010 Wien
> FN 266155f, Handelsgericht Wien
> 
> Tel.: +43/1/513 88 77 - 27
> Fax.: +43/1/513 88 62
> Email: [EMAIL PROTECTED]
> Web: www.cfc.at
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Cleaning-before-assembly-tf3685941s177.html#a10303664
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: OT: JAXWS Maven2 plugin

[Gonne Martens]

Hi,

I took the JAXWS maven2 plugin (current version 1.2) from the following 
repository:



maven2-repository.dev.java.net
Java.net Repository for Maven
http://download.java.net/maven/2/





This is e.g. my plugin entry to run wsimport with JAX-WS 2.1 for 2 wsdl files:


org.codehaus.mojo
jaxws-maven-plugin


rel510

wsimport



REL-5-MM7-1-0.wsdl



customSchema510.xml

customWsdl510.xml


${project.build.directory}/jaxws/stale/rel510.staleFlag.




rel513

wsimport



REL-5-MM7-1-3.wsdl



customSchema513.xml

customWsdl513.xml


${project.build.directory}/jaxws/stale/rel513.staleFlag.





${basedir}/src/main/wsdl
${basedir}/src/main/jaxws

${basedir}/target/generated-sources/jaxws

true



Kind regards,
Gonne



-Ursprüngliche Nachricht-
Von: Dan Tran [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 2. Mai 2007 23:00
An: Maven Users List; [EMAIL PROTECTED]
Betreff: Re: OT: JAXWS Maven2 plugin

where did you get it?

java.net?


On 5/2/07, Seth Mason <[EMAIL PROTECTED]> wrote:
>
> Apologies if this is too off topic, but has anyone used the JAXWS
> maven2 plugin?  I just downloaded the samples and those don't even
> run.  I keep getting errors about the plugin not existing even though
> I've tried many different repos and many different versions.
>
> There doesn't seem to be any support for it otherwise I'd ask there.
>
> Thanks in advance,
> SETH
>
> -
> 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: Cleaning before assembly

[Roland Asmann]

If you use a directory under 'target', it should be cleaned by the 
clean-plugin... Maybe the answer lies in configuring the assembly-plugin to 
use anothe dir, instead of telling the clean-plugin to clean up other dirs?


On Thursday 03 May 2007 13:46, Jose Alberto Fernandez wrote:
> Hi,
>
> Can someone point me at the correct way to tell Maven's assembly or
> cleaning plug-in to clean the assembly area before assembling a new.
> Currently as the assembly area is not cleaned up we finish with old jars
> still there from older builds.
>
> Any hints will be appreciated.
>
> Jose Alberto

-- 
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Cleaning before assembly

[Jose Alberto Fernandez]

Hi,

Can someone point me at the correct way to tell Maven's assembly or cleaning
plug-in to clean the assembly area before assembling a new. Currently as the
assembly area is not cleaned up we finish with old jars still there from
older builds.

Any hints will be appreciated.

Jose Alberto
-- 
View this message in context: 
http://www.nabble.com/Cleaning-before-assembly-tf3685941s177.html#a10303138
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Manage Maven Classpath

[GreJ]

Hi, 

it's a simple question, and i think that the answer is "no", but i need a
confirmation ;)

Is it possible to manage manually the MavenClasspath ? 

Thanks. 
-- 
View this message in context: 
http://www.nabble.com/Manage-Maven-Classpath-tf3685869s177.html#a10302892
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

M2-Plugin Development: Reading POM programmatically

[Martin Bengl]

hello folks,

I use following solution (with maven 2.0.4) to create a MavenProject at 
runtime to extract informations like artifactId and groupid - this could 
be also done by manually parsing the xml file - but i think its a better 
way to use the maven classes.


File pomFile = new File("pom.xml");
MavenProjectBuilder projectBuilder;
ArtifactRepository localRepository;

MavenProject pom = projectBuilder.build(pomFile, localRepository, 
(ProfileManager)null );


My Question is: From which object can I receive a profileManager 
instance? (the projectBuilder and localRepository are defined as plexus 
components, the profileManager isn't!)


greetings
martin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Access file resources from ant based plugin

[Marcel Schutte]

Hello,

I've written an ant based plugin that needs access to file based resources. For 
example, an xslt task needs a file path to the stylesheet it applies. Simply 
putting this stylesheet in src/main/resources won't work, because it will end 
up in the plugin's jar file.

The only way around it I could think of was to find the plugin jar file in the 
local repository and extracting it to a temp dir. Not the most elegant of 
solutions. There is a thread on the developers list by Jason about this 
(http://www.nabble.com/-vote--Allowing-Ant-based-plugins-to-use-file-based-resources-tf2398452s177.html#a6749541).
 Does anybody know what happened to his suggestion? Has it already been 
implemented in some way?

Thanks,
Marcel



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: how to disable a profile ?

[nicolas de loof]

Thanks !

2007/5/3, Jörg Schaible <[EMAIL PROTECTED]>:



mvn -s alternate-settings.xml

:)

nicolas de loof wrote on Thursday, May 03, 2007 12:02 PM:

> In fact, I was wrong, the settings descriptor doesn't allow to set
>  in a profile. I'll have to comment the XML block any time I
> want to disable mirrors...
>
> 2007/5/3, nicolas de loof <[EMAIL PROTECTED]>:
>>
>> Hello,
>>
>> my settings.xml contain a set of . In some circunstances I'd
>> like to disable them. To do this, I've set them in a profile that is
>> enabled by default.
>>
>> How can I disable this profile from the command line ?
>>
>> Nico.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: how to disable a profile ?

[Jörg Schaible]

mvn -s alternate-settings.xml

:)

nicolas de loof wrote on Thursday, May 03, 2007 12:02 PM:

> In fact, I was wrong, the settings descriptor doesn't allow to set
>  in a profile. I'll have to comment the XML block any time I
> want to disable mirrors...
> 
> 2007/5/3, nicolas de loof <[EMAIL PROTECTED]>:
>> 
>> Hello,
>> 
>> my settings.xml contain a set of . In some circunstances I'd
>> like to disable them. To do this, I've set them in a profile that is
>> enabled by default. 
>> 
>> How can I disable this profile from the command line ?
>> 
>> Nico.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: how to disable a profile ?

[nicolas de loof]

In fact, I was wrong, the settings descriptor doesn't allow to set 
in a profile. I'll have to comment the XML block any time I want to disable
mirrors...

2007/5/3, nicolas de loof <[EMAIL PROTECTED]>:


Hello,

my settings.xml contain a set of . In some circunstances I'd like
to disable them.
To do this, I've set them in a profile that is enabled by default.

How can I disable this profile from the command line ?

Nico.

how to disable a profile ?

[nicolas de loof]

Hello,

my settings.xml contain a set of . In some circunstances I'd like to
disable them.
To do this, I've set them in a profile that is enabled by default.

How can I disable this profile from the command line ?

Nico.

Re: Guide to creating archetypes...

[Raphaël Piéroni]

2007/5/3, Rémy Sanlaville <[EMAIL PROTECTED]>:

>
> > what's the difference ?
> Mainly
> - the descriptor is changed
> - user is prompted for selecting the archetype and configuration
> (unless using -B)
> - any file can be resolved as packaged (using package in the directory
> resolution)
> - any file can be resolved as binary (copied instead of velocity template)
> - support for multi project


I forgot:
- archetype creation form an existing project (yes with the above
features packaged, filtered, multiproject)


>
> >
> > http://mojo.codehaus.org/maven-archetypeng/
> which is not yet released


Did you have a roadmap when it will be released ?

I got a roadmap (on paper without any date)
But i could say it need at least 2 weeks before putting a first alpha release

Raphaël


So, if I understand, maven-archetypeng has more features and seems more
powerful.
So it's better to look at maven-archetypeng instead of maven-archetype. I
will have a look.
I imagine it will normally replace maven-archetype in the future.

>
> > or
> >
> > mvn archetype:create
> >   -DgroupId=[your project's group id]
> >   -DartifactId=[your project's artifact id]
> >   -DarchetypeArtifactId=maven-archetype-archetype
> >
> >
> > (cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html)
>
>
> Hope the answer makes sense


Nice thanks.

Rémy

memory settings for site generation

[emerson cargnin]

Hi

I'm using the latest maven-1.1-RC1-SNAPSHOT.

I ended up with the following memory OPTS that enabled the site for
one quite big multiproject to be run without getting out of memory
errors:

export MAVEN_OPTS="-Xmx2600m -XX:MaxPermSize=512m"

The think is that, using top, it reaches 80%

Then when I run from inside CC, it gets to the top of the memory (as
shown in top). Furthermore, i couldn't run more than one site at the
same time.
This server has 2 gig memory. From sub-project to sub-project, the
memory just doesn't goes down.

I have a not related question, regarding to checkstyle, is it possible
on a multi module project to get statistics of which problems occurs
most? This would be a useful multiproject report.

Thanks
emerson

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

TestNG documentation

[Martin Gilday]

The TestNG docs have been updated to cover the current state of play in
getting Maven, Surefire and TestNG working together.

http://testng.org/doc/maven.html

Thanks,
Martin.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Guide to creating archetypes...

[Rémy Sanlaville]

> what's the difference ?
Mainly
- the descriptor is changed
- user is prompted for selecting the archetype and configuration
(unless using -B)
- any file can be resolved as packaged (using package in the directory
resolution)
- any file can be resolved as binary (copied instead of velocity template)
- support for multi project

>
> http://mojo.codehaus.org/maven-archetypeng/
which is not yet released



Did you have a roadmap when it will be released ?
So, if I understand, maven-archetypeng has more features and seems more
powerful.
So it's better to look at maven-archetypeng instead of maven-archetype. I
will have a look.
I imagine it will normally replace maven-archetype in the future.



> or
>
> mvn archetype:create
>   -DgroupId=[your project's group id]
>   -DartifactId=[your project's artifact id]
>   -DarchetypeArtifactId=maven-archetype-archetype
>
>
> (cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html)


Hope the answer makes sense



Nice thanks.

Rémy

Re: Multi-module passing properties to children

[Roland Asmann]

If you include a -tag for your parent-POM, your project automatically 
inherits its version (unless you set it manually).
In case you need to reference it in other places as well, try using 
${parent.version}


On Thursday 03 May 2007 01:04, Jared Blitzstein wrote:
> Does using the parent tag require the project to be in a repository?
> I planned on having this "suitepom" accessible via CVS but not
> something that is going to be installed in our company repo. I may be
> way off base though.
>
> Also, how would you pass something through like a version? The
> version tag is required in the child pom so you can't leave it out,
> and if I do ${version} it doesn't pick that up from the definition in
> the master pom, it just uses "${version}" literally.
>

-- 
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Guide to creating archetypes...

[Raphaël Piéroni]

2007/5/3, Rémy Sanlaville <[EMAIL PROTECTED]>:

Hi,

If I want to create an archetype, which one is better to use ?

If you want to create it right now, i would say the actual archetype
If you can wait for the archetypeng to have a first release
(i would say the archetype ng - but i'm obviously biased)



what's the difference ?

Mainly
- the descriptor is changed
- user is prompted for selecting the archetype and configuration
(unless using -B)
- any file can be resolved as packaged (using package in the directory
resolution)
- any file can be resolved as binary (copied instead of velocity template)
- support for multi project



http://mojo.codehaus.org/maven-archetypeng/

which is not yet released



or

mvn archetype:create
  -DgroupId=[your project's group id]
  -DartifactId=[your project's artifact id]
  -DarchetypeArtifactId=maven-archetype-archetype


(cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html)

Rémy


Hope the answer makes sense

Raphaël

Re: Guide to creating archetypes...

[Rémy Sanlaville]

Hi,

If I want to create an archetype, which one is better to use ?
what's the difference ?

http://mojo.codehaus.org/maven-archetypeng/

or

mvn archetype:create
 -DgroupId=[your project's group id]
 -DartifactId=[your project's artifact id]
 -DarchetypeArtifactId=maven-archetype-archetype


(cf. http://maven.apache.org/guides/mini/guide-creating-archetypes.html)

Rémy

RE: dependency management problems...

[William Ferguson]

Interesting point.

Aren't dependencies just compile time dependencies? So there is no need
to resolve them unless your build includes the compile:compile goal.

Plugin dependencies are only resolved if that plugin is required as part
of the current build.
So why do the (compile) dependencies need to be resolved if compilation
is not part of the build?

William


-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 2 May 2007 1:24 PM
To: Maven Users List
Subject: Re: dependency management problems...

As far as I know, you can't. Maven resolves all dependencies etc at the
beginning of the lifecycle, so it can find all transitive artifacts etc
and make sure EVERYTHING is available in the local cache before
proceeding with the build.

Wayne

On 5/1/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> Here's another way of phrasing this question - if a module has a 
> dependency on another one, how do you stop it from attempting to 
> download until absolutely necessary (say at compile time, NOT at 
> process-resources time)?
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 01, 2007 3:11 PM
> To: Maven Users List
> Subject: dependency management problems...
>
> We're having problems building modules like this from scratch.  If we 
> run process resources from the top most level, submodule.B complains 
> about not being able to find module1's artifacts (why would 
> submodule.B need module 1's jar artifact just to process resources?).
>
> parent - version 1.0-SNAPSHOT
> |
> |--->module1 - version 1.0-SNAPSHOT
> |
> |--->module2 - version 1.0-SNAPSHOT
>|--->submodule.A- version 1.0-SNAPSHOT
>|--->submodule.B- version 1.0-SNAPSHOT
>
>
>
> I'm really at the end of my rope on this one.  The only way to 
> successfully get this to go through is to run a mvn install from the 
> top most level first.  What's crazy is submodule.A has the same 
> dependency and goes through just fine.
>
> -
> 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]